"Dave Mills" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> You cannot easily keep the old name. It's a new server so decide on a
> new name then gradually migrate everything to the new server. This way
> the old server continues to support the things not yet migrated and as
> the new server is set up to replace each service remove the service
> from the old served. When is has nothing left to do remove it from
> production.
>
> 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" <(E-Mail Removed)> wrote:
> in message <1116158073.11916e0d4a7bc9988b97b4105b3e9119@teranews>
>
>>I have a 2k box that is a DC for a stand-alone domain. Due to problems
>>with
>>the server a new 2k server was installed to run an application that users
>>needed to access. They continue to use the old server with the prolems
>>for
>>logon and file/print etc. I want to DCPROMO the new server and have it
>>take
>>full control of the domain and then rmove the old server totally. Could
>>anyone point me in the right directionm of any articles I could read that
>>would point out thing's should be thinking about when I do this or provide
>>me tips here in response to this post? The hostname of the new server is
>>different than that of the old one so there would be problems with
>>printers
>>and drives on clients machines using the old server name but I think a DNS
>>alias would take care of that, even if it doesn't I'm not too concerned as
>>there aren't too many clients that I can't go round and manually re-map
>>and
>>re-install drivers. Thing is though I do not want to have to go around
>>and
>>re-create profiles for everyone so I want the whole domain moving to the
>>new
>>server totally.
>
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
|
Similar Threads
