Re: Upgrading Domain Controller from W2k to W2k3
Hello Scott,
!!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
- For Exchange start here before running adprep command:
http://support.microsoft.com/?id=314649
- Additional Exchange should run on member servers, NOT on Domain controllers,
also NOT recommended from MS.
- See also here for Exchange:
http://support.microsoft.com/kb/307917/
http://support.microsoft.com/kb/274737/ http://support.microsoft.com/kb/916694
http://support.microsoft.com/kb/899328
- 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 replmon, 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
- run adprep /forestprep and adprep /domainprep from the 2003 installation
disk against the 2000 server, with an account that is member of the Schema
admins, to upgrade the schema to the new version
- 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 again 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
> We have our Domain Controller on an old server running Windows Server
> 2000.
> We want to migrate this to over to new server hardware and upgrade it
> to at
> least Windows Server 2003. On this server we have our Active
> Directory, Print
> Server, User Profiles, User shared drives, Applications, DNS, DHCP,
> Anti-Virus server, and we have another Windows Server 2000 running
> Exchange
> 2000 integrated with this DC.
> Couple questions about this. First off, what is the logical order of
> upgrading? Should we install Windows Server 2000 on the new machine,
> then
> copy everything over, and then upgrade to Windows Server 2003? Or can
> we
> migrate to the new machine with Windows Server 2003 in a fresh
> install?
> Is Exchange 2000, running on a Server 2000 machine going to integrate
> with a
> Windows 2003 DC?
> I have seen a couple programs such as "Server Migrator 2007" and
> "Umove"
> that claim they can copy everything from a server (even AD, DNS, DHCP,
> ect.)
> over to a new one with some simple setup. Are these programs reliable?
> It
> looks as though doing this project without these applications is going
> to be
> pretty intuitive.
> Also any other words of wisdom that might help us in this situation
> would be
> greatly appreciated. Thanks!