--
RCE Defiant
Start by setting the new machine up as a second AD server. Then
migrate the FSMO roles.
Next move DHCP. You can only have a single DHCP server
Then setup a secondary DNS service on the new machine. When working
change the DNS server in DHCP. Remove the old DNS server after the
clients have renewed their address.
Write a logon script to map the printers and shared folders (you'll
find load on the net) Get this working then you can switch all the
clients in one hit by changing the logon script.
Install the printers on the new server and maybe the shares too.
Rewrite the logon script and test it maps correctly. Now move all the
data from the old share to the new and implement the new logon script.
Remove permission to access the old shares so you get an alert if
something goes wrong on the odd client and the users can edit the old
data (which will soon be deleted).
After you a certain that the old server is no required switch it off
for a while. If there are dependencies you can switch it on and fix
things. When the server has been off for a few days without any
problems switch it on and run DCPROMO to demote it form being a DC.
Remove it from the domain then do with it want you wish.
"RCE Defiant" <pstones578...@hotmail.com> wrote:
in message <1116158073.11916e0d4a7bc9988b97b4105b3e9119@teranews>
Thanks for the reply. Luckily for me it's a bit easier of a job as there is
no DHCP at the site. I've already DCPROMO'd the new server and disabled all
but one share on the old server. Just need to take care of printers and
move data from the old box to the new one. There's also a SCSI card and
backup device inlcuding an installation of BackupExec that I need to get
across. Good idea about turning off the old box for a week to see if there
are any issues before doing the DCPROMO on it to remove it completely, less
risky than just demoting it and hoping you did everything right first time.
--
RCE Defiant