Dave
Thu May 01 08:40:11 PDT 2008
Thanks for all the info. It is an Exchange 2003 Server that will be
decommissioned after the new server is up and running.
<Meinolf Weber> wrote in message
news:ff16fb66980758ca78ea46759eca@msnews.microsoft.com...
> Hello Dave,
>
> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
>
> One question first:
> Is the old server also Exchange server and will it be taken out of the
> domain
> forever, when the new server is running?
>
> - On the old server open DNS management console and check that you are
> running Active directory integrated zone (easier for replication, if you
> have more then one DNS server)
>
> - run dcdiag and netdiag on the old machine to check for errors, if you
> have some post the complete output from the command here or solve them
> first
>
> - Install the new machine as a member server in your existing domain
>
> - configure a fixed ip and set the preferred DNS server to the old DNS
> server only
>
> - run dcpromo and follow the wizard to add the 2003 server to an existing
> domain
>
> - if you are prompted for DNS configuration choose Yes (also possible that
> no DNS preparation occur), then install DNS after the reboot
>
> - for DNS give the server time for replication, at least 15 minutes.
> Because you use Active directory integrated zones it will automatically
> replicate the zones to the new server. Open DNS management console to
> check that they appear
>
> - if the new machine is domain controller and DNS server run replmon,
> dcdiag and netdiag on both domain controllers
>
> - if you have no errors, make the new server Global catalog server, open
> Active directory Sites and Services and then double-click sitename,
> double-click Servers, click your domain controller, right-click NTDS
> Settings, and then click Properties, on the General tab, click to select
> the Global catalog check box (
http://support.microsoft.com/?id=313994)
>
> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
> (
http://support.microsoft.com/kb/324801)
>
> - you can see in the event viewer (Directrory service) that the roles are
> transferred, also give it some time
>
> - reconfigure the DNS configuration on your NIC of the 2003 server,
> preferred DNS itself, secondary the old one
>
> - if you use DHCP do not forget to reconfigure the scope settings to point
> to the new installed DNS server
>
> - export and import of DHCP database (if needed)
>
http://support.microsoft.com/kb/325473
>
>
> Demoting
>
> - reconfigure your clients/servers that they not longer point to the old
> DC/DNS server on the NIC
>
> - to be sure that everything runs fine, disconnect the old DC from the
> network and check with clients and servers the connectivity, logon and
> also with one client a restart to see that everything is ok
>
> - then run dcpromo to demote the old DC, if it works fine the machine will
> move from the DC's OU to the computers container, where you can delete it
> by hand. Can be that you got an error during demoting at the beginning,
> then uncheck the Global catalog on that DC and try again
>
> - check the DNS management console, that all entries from the machine are
> disappeared or delete them by hand if the machine is off the network for
> ever
>
>
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> I need to upgrade the lone server, running AD, DNS and DHCP, in the
>> domain
>> to a completely new box. I would like to do it a seemlesly as
>> possible and
>> wanted input regarding suggested steps for doing the migration and any
>> pitfalls I should avoid. Is it as simple as installing Server 2003,
>> making
>> the device a member server, synchronizing the AD and DHCP, demoting
>> the old
>> server, promoting the new server and then copying the file structure?
>> Any help will be greatly appreciated.
>> Dave
>
>