4 servers were running under Windows 2000 active directory. We've
been migrating from Windows 2000 to Windows 2003 server. The Schema
master had been successfully updated (forestprep) then domainprep.

Windows 2003 has been installed on a server. Now we're about to
change the hot swappable disks - where the OS is installed - on
another server, which is currently a Windows 2000 DC.

I was thinking about keeping the current disks where Windows 2000 is
installed, NOT REMOVING this DC from the active directory. AD would
think this server has been shuted down. So if one day I need to put a
DC in service, this one could quickly come into use again. Nothing
keeps me from removing this DC, I could simply make a system backup.
But those 2 36GB SCSI U320 won't be used anymore, every server has
already 6 72GB to 146GB in RAID 5

QUESTION: what's happen when a DC is not connected for a long period
of time? Would you suggest to remove (DCPROMO) the DC or to keep it
so it could quickly come back online in the event that something goes
wrong.

thank you

Thomas Lally

Thomas you should demote the domain controller, Domain Controllers offline
for a long time can cause broken computer accounts between DCs.

--
Regards
Christoffer Andersson

No email replies please - reply in the newsgroup

"Thomas Lally" <(E-Mail Removed)> skrev i meddelandet
news:(E-Mail Removed)...
> 4 servers were running under Windows 2000 active directory. We've
> been migrating from Windows 2000 to Windows 2003 server. The Schema
> master had been successfully updated (forestprep) then domainprep.
>
> Windows 2003 has been installed on a server. Now we're about to
> change the hot swappable disks - where the OS is installed - on
> another server, which is currently a Windows 2000 DC.
>
> I was thinking about keeping the current disks where Windows 2000 is
> installed, NOT REMOVING this DC from the active directory. AD would
> think this server has been shuted down. So if one day I need to put a
> DC in service, this one could quickly come into use again. Nothing
> keeps me from removing this DC, I could simply make a system backup.
> But those 2 36GB SCSI U320 won't be used anymore, every server has
> already 6 72GB to 146GB in RAID 5
>
> QUESTION: what's happen when a DC is not connected for a long period
> of time? Would you suggest to remove (DCPROMO) the DC or to keep it
> so it could quickly come back online in the event that something goes
> wrong.
>
> thank you
>
> Thomas Lally

Thank you Criss

Thomas

"Chriss3" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Thomas you should demote the domain controller, Domain Controllers offline
> for a long time can cause broken computer accounts between DCs.
>
> --
> Regards
> Christoffer Andersson
>
> No email replies please - reply in the newsgroup
>
> "Thomas Lally" <(E-Mail Removed)> skrev i meddelandet
> news:(E-Mail Removed)...
> > 4 servers were running under Windows 2000 active directory. We've
> > been migrating from Windows 2000 to Windows 2003 server. The Schema
> > master had been successfully updated (forestprep) then domainprep.
> >
> > Windows 2003 has been installed on a server. Now we're about to
> > change the hot swappable disks - where the OS is installed - on
> > another server, which is currently a Windows 2000 DC.
> >
> > I was thinking about keeping the current disks where Windows 2000 is
> > installed, NOT REMOVING this DC from the active directory. AD would
> > think this server has been shuted down. So if one day I need to put a
> > DC in service, this one could quickly come into use again. Nothing
> > keeps me from removing this DC, I could simply make a system backup.
> > But those 2 36GB SCSI U320 won't be used anymore, every server has
> > already 6 72GB to 146GB in RAID 5
> >
> > QUESTION: what's happen when a DC is not connected for a long period
> > of time? Would you suggest to remove (DCPROMO) the DC or to keep it
> > so it could quickly come back online in the event that something goes
> > wrong.
> >
> > thank you
> >
> > Thomas Lally