Guest Scott Posted May 22, 2008 Posted May 22, 2008 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!
Guest Lanwench [MVP - Exchange] Posted May 22, 2008 Posted May 22, 2008 Re: Upgrading Domain Controller from W2k to W2k3 Scott <Scott@discussions.microsoft.com> wrote: > 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, No, I wouldn't upgrade anything in place. I'd install a new W2003 machine, patch it, run adprep /forestprep & /domainprep (see http://support.microsoft.com/kb/325379#2) Make this a DC/DNS box, and a GC. You can move the DHCP & file sharing over if you wish, or leave the old server in place - no harm in having two DCs (it's recommended) You can also check out http://technet2.microsoft.com/windowsserver/en/library/7532bc9c-eee8-440e-8620-b29bbf3996641033.mspx?mfr=true - and google. There are *tons* of hits for this stuff. > 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? Yes, see above. > Is Exchange 2000, running on a Server 2000 machine going to integrate > with a Windows 2003 DC? Yes. And you can't upgrade Windows on that box anyway. :-) > 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? They aren't officially supported by MS and they aren't needed. > It looks as though doing this project without > these applications is going to be pretty intuitive. I think so. > Also any other words of wisdom that might help us in this situation > would be greatly appreciated. Thanks! Make backups first. ;-)
Guest leew [MVP] Posted May 22, 2008 Posted May 22, 2008 Re: Upgrading Domain Controller from W2k to W2k3 I'll post some the links I've offered on forums below. And I'm sure others will have something to say. In addition to the links below, here's a few of my own recommendations: 1. Create System State backups of all systems and do a full backup of Exchange. 2. Make sure you know the Directory Services Restore Mode Password - if not, reset it AND TEST IT. 3. Depending on the size of your network, it can easier to shut all workstations and devices down and start with a fresh DHCP server rather than moving the DHCP database. I do not have any experience with third party apps. You do not need to install 2000 on the new server in order to complete the upgrade. THE LINKS: Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain http://support.microsoft.com/default.aspx?scid=kb;en-us;555040 How to upgrade Windows 2000 domain controllers to Windows Server 2003 http://support.microsoft.com/kb/325379 [if using R2 release of Windows 2003] Extending Your Active Directory Schema for New Features in Windows Server 2003 R2 http://www.microsoft.com/downloads/details.aspx?familyid=5B73CF03-84DD-480F-98F9-526EC09E9BA8&displaylang=en Hotfixes to install before you run adprep /Forestprep on a Windows 2000 domain controller to prepare the Forest and domains for the addition of Windows Server 2003-based domain controllers http://support.microsoft.com/?kbid=331161 Commodore.ca | Windows | How To Upgrade Windows 2000 Domain to Windows 2003 Server Quote from the top of this article: "Several glossy Microsoft presenters have stated that all you need to do to complete a Windows 2003 Domain upgrade is run ADPREP and then upgrade away. This may work for very small / simple environments but it is definitely not good advice for most companies. After upgrading five servers in two unrelated domains and installing many fresh copies of 2003 I can say that I personally would not skip a single step in the process I have developed below." http://www.commodore.ca/windows/windows_2003_upgrade.htm Windows Server 2003 Upgrade Assistance Center http://www.microsoft.com/windowsserver2003/upgrading/nt4/upgradeassistance/default.mspx Here are some links that should help you in replacing existing domain controllers and/or transferring services and Active Directory functions to another/new system: How can I transfer some or all of the FSMO Roles from one DC to another? http://www.petri.co.il/transferring_fsmo_roles.htm How To Create or Move a Global Catalog in Windows 2000 http://support.microsoft.com/?kbid=313994 How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003 http://support.microsoft.com/?id=325473 How can I move a DHCP database from one server to another? http://www.windowsitpro.com/Article/ArticleID/13473/13473.html How can I move DNS from one Windows 2000 Server to another Windows 2000 Server? (Two Related if going 2000 to 2003 - read both before moving) http://www.jsifaq.com/subG/TIP3300/rh3357.htm http://www.jsifaq.com/SUBN/tip6700/rh6731.htm Exchange Considerations: [if you run Exchange 2000] Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers http://support.microsoft.com/default.aspx?kbid=314649 Scott wrote: > 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!
Guest Scott Posted May 22, 2008 Posted May 22, 2008 Re: Upgrading Domain Controller from W2k to W2k3 With having an Exchange 2000 Environment, and the problems addressed in the Microsoft KB article 314649, would it make sense to upgrade our Exchange server to Server 2003 and then Exchange 2003 before we upgrade our PDC? We are going to move our Exchange server over to New Hardware as well. "leew [MVP]" wrote: > I'll post some the links I've offered on forums below. And I'm sure > others will have something to say. > > In addition to the links below, here's a few of my own recommendations: > > 1. Create System State backups of all systems and do a full backup of > Exchange. > 2. Make sure you know the Directory Services Restore Mode Password - if > not, reset it AND TEST IT. > 3. Depending on the size of your network, it can easier to shut all > workstations and devices down and start with a fresh DHCP server rather > than moving the DHCP database. > > I do not have any experience with third party apps. > > You do not need to install 2000 on the new server in order to complete > the upgrade. > > THE LINKS: > > Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 > Domain > http://support.microsoft.com/default.aspx?scid=kb;en-us;555040 > > How to upgrade Windows 2000 domain controllers to Windows Server 2003 > http://support.microsoft.com/kb/325379 > > [if using R2 release of Windows 2003] Extending Your Active Directory > Schema for New Features in Windows Server 2003 R2 > http://www.microsoft.com/downloads/details.aspx?familyid=5B73CF03-84DD-480F-98F9-526EC09E9BA8&displaylang=en > > Hotfixes to install before you run adprep /Forestprep on a Windows 2000 > domain controller to prepare the Forest and domains for the addition of > Windows Server 2003-based domain controllers > http://support.microsoft.com/?kbid=331161 > > Commodore.ca | Windows | How To Upgrade Windows 2000 Domain to Windows > 2003 Server > Quote from the top of this article: "Several glossy Microsoft presenters > have stated that all you need to do to complete a Windows 2003 Domain > upgrade is run ADPREP and then upgrade away. This may work for very > small / simple environments but it is definitely not good advice for > most companies. After upgrading five servers in two unrelated domains > and installing many fresh copies of 2003 I can say that I personally > would not skip a single step in the process I have developed below." > http://www.commodore.ca/windows/windows_2003_upgrade.htm > > Windows Server 2003 Upgrade Assistance Center > http://www.microsoft.com/windowsserver2003/upgrading/nt4/upgradeassistance/default.mspx > > > > > Here are some links that should help you in replacing existing domain > controllers and/or transferring services and Active Directory functions > to another/new system: > > How can I transfer some or all of the FSMO Roles from one DC to another? > http://www.petri.co.il/transferring_fsmo_roles.htm > > How To Create or Move a Global Catalog in Windows 2000 > http://support.microsoft.com/?kbid=313994 > > How to move a DHCP database from a computer that is running Windows NT > Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is > running Windows Server 2003 > http://support.microsoft.com/?id=325473 > > How can I move a DHCP database from one server to another? > http://www.windowsitpro.com/Article/ArticleID/13473/13473.html > > How can I move DNS from one Windows 2000 Server to another Windows 2000 > Server? > (Two Related if going 2000 to 2003 - read both before moving) > http://www.jsifaq.com/subG/TIP3300/rh3357.htm > http://www.jsifaq.com/SUBN/tip6700/rh6731.htm > > > > > Exchange Considerations: > [if you run Exchange 2000] Windows Server 2003 adprep /forestprep > Command Causes Mangled Attributes in Windows 2000 Forests That Contain > Exchange 2000 Servers > http://support.microsoft.com/default.aspx?kbid=314649 > > > > > Scott wrote: > > 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! >
Guest Lanwench [MVP - Exchange] Posted May 23, 2008 Posted May 23, 2008 Re: Upgrading Domain Controller from W2k to W2k3 Scott <Scott@discussions.microsoft.com> wrote: > With having an Exchange 2000 Environment, and the problems addressed > in the Microsoft KB article 314649, would it make sense to upgrade > our Exchange server to Server 2003 and then Exchange 2003 before we > upgrade our PDC? We are going to move our Exchange server over to New > Hardware as well. No - don't upgrade it in place. Set up a new E2003/W2003 server in the same admin group & move mailboxes, replicate PFs, etc. > > "leew [MVP]" wrote: > >> I'll post some the links I've offered on forums below. And I'm sure >> others will have something to say. >> >> In addition to the links below, here's a few of my own >> recommendations: >> >> 1. Create System State backups of all systems and do a full backup of >> Exchange. >> 2. Make sure you know the Directory Services Restore Mode Password - >> if not, reset it AND TEST IT. >> 3. Depending on the size of your network, it can easier to shut all >> workstations and devices down and start with a fresh DHCP server >> rather than moving the DHCP database. >> >> I do not have any experience with third party apps. >> >> You do not need to install 2000 on the new server in order to >> complete the upgrade. >> >> THE LINKS: >> >> Common Mistakes When Upgrading a Windows 2000 Domain To a Windows >> 2003 Domain >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555040 >> >> How to upgrade Windows 2000 domain controllers to Windows Server 2003 >> http://support.microsoft.com/kb/325379 >> >> [if using R2 release of Windows 2003] Extending Your Active Directory >> Schema for New Features in Windows Server 2003 R2 >> http://www.microsoft.com/downloads/details.aspx?familyid=5B73CF03-84DD-480F-98F9-526EC09E9BA8&displaylang=en >> >> Hotfixes to install before you run adprep /Forestprep on a Windows >> 2000 domain controller to prepare the Forest and domains for the >> addition of Windows Server 2003-based domain controllers >> http://support.microsoft.com/?kbid=331161 >> >> Commodore.ca | Windows | How To Upgrade Windows 2000 Domain to >> Windows 2003 Server >> Quote from the top of this article: "Several glossy Microsoft >> presenters have stated that all you need to do to complete a Windows >> 2003 Domain upgrade is run ADPREP and then upgrade away. This may >> work for very small / simple environments but it is definitely not >> good advice for most companies. After upgrading five servers in two >> unrelated domains and installing many fresh copies of 2003 I can say >> that I personally would not skip a single step in the process I have >> developed below." >> http://www.commodore.ca/windows/windows_2003_upgrade.htm >> >> Windows Server 2003 Upgrade Assistance Center >> http://www.microsoft.com/windowsserver2003/upgrading/nt4/upgradeassistance/default.mspx >> >> >> >> >> Here are some links that should help you in replacing existing domain >> controllers and/or transferring services and Active Directory >> functions to another/new system: >> >> How can I transfer some or all of the FSMO Roles from one DC to >> another? http://www.petri.co.il/transferring_fsmo_roles.htm >> >> How To Create or Move a Global Catalog in Windows 2000 >> http://support.microsoft.com/?kbid=313994 >> >> How to move a DHCP database from a computer that is running Windows >> NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer >> that is running Windows Server 2003 >> http://support.microsoft.com/?id=325473 >> >> How can I move a DHCP database from one server to another? >> http://www.windowsitpro.com/Article/ArticleID/13473/13473.html >> >> How can I move DNS from one Windows 2000 Server to another Windows >> 2000 Server? >> (Two Related if going 2000 to 2003 - read both before moving) >> http://www.jsifaq.com/subG/TIP3300/rh3357.htm >> http://www.jsifaq.com/SUBN/tip6700/rh6731.htm >> >> >> >> >> Exchange Considerations: >> [if you run Exchange 2000] Windows Server 2003 adprep /forestprep >> Command Causes Mangled Attributes in Windows 2000 Forests That >> Contain Exchange 2000 Servers >> http://support.microsoft.com/default.aspx?kbid=314649 >> >> >> >> >> Scott wrote: >>> 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!
Guest Meinolf Weber Posted May 23, 2008 Posted May 23, 2008 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!
Recommended Posts