Upgrading WIN2K Server to WIN2K3 R2 Server

[dufresnem]

My original server is six years old and I have built a new box to replace it. To complicate matters even further, I will be performing an upgrade from Microsoft Windows 2000 Server(Active Directory) PDC to Microsoft Windows 2003 R2 Server(Active Directory)PDC.

I want to choose the best possible upgrade path available to get the data from the old box over to the new one with little impact to data and applications.

I am looking at a couple of options, and want to know your advice on upgrading, across the wire migration, new install of a backup DC along side a Primary DC, and then promotion?

Note: Before I upgrade I will ensure I have RAID 1 implemented on SYSTEM/BOOT Partition, just in case!!!!

Option 1: ( IN PLACE UPGRADE)
(SYSTEMBOOT Partition) RAID 1
(DATA Volume) RAID 5

1. Upgrade existing server to WIN2K3, test and verify everything is OK.
2. Before bringing down the server, install the driver for the new SATA controller that will be on the new box. Since the driver is previously installed, all I have to do then is transfer the SYSTEM/BOOT RAID 1 set over to the new box and the server should boot.
3. Regenerate SID from original server(need to find how to do this).
4. Once I verify I can login to the domain, I will transfer the DATA VOLUME RAID 5 set over to the new box.

Question: SID broadcasting on the original Domain will no longer be vaild, and might have to rejoin every machine under the domain on the new box. I have read somewhere that before doing the above, there is a utility that can capture the SID and regenrate it on the new box.

Anyone know about this utility and where is it????

Option 2: (Install WIN2K server on new box, transfer hardware, upgrade to WIN2K3 Server)
(SYSTEMBOOT Partition) RAID 1
(DATA Volume) RAID 5

1. Install WIN2K server on new box.
2. Restore from tape the complete contents of the SYSTEM/BOOT Partition.
3. Regenrate SID for new box.
4. Reboot server, test and verify.
5. Transfer DATA VOLUME RAID 5 over.

Option 3 (Install WIN2K3 on new box as a Domain controller as a member of the current domain, then promote it Primary DC)
(SYSTEMBOOT Partition) RAID 1
(DATA Volume) RAID 5

1. Install WIN2K3 Server R2 on new box as a backup DC.
2. Once AD is replicated to the backup DC, then test login to new domain controller.
3. transfer data.

Any ideas would be appreciated.

 

[itsp1965]

Why don't you go with option 3 but use MS' Active Directory Migration Tool which can help "automate" the migration.
If you want to do it manually you will need run DCPROMO /ADPREP and /FORESTPREP on the existing Win2K box (using your Win2K3 R2 CD) then dcpromo your Windows 2003 server. Proceed to migrate your FSMO roles to the new server (if you are not keeping the old server around). Hope this helps.

 

[dufresnem]

I was considering towards option 3, but might have an issue with a critical application. I leaning towards Option 2.

If I resotre from tape onto the new hardrive ofd another server, I have to use the SysPrep utility to transfer the SID so all workstations can login to the Domain located on the new server.

I just found out that I cannot use the Sysprep tool for a Win2k server DC with Active Directory.

Do you know what tool I can use to prepare the Win2K server to be restored onto another drive?

 

[58sniper]

No such thing as a PDC. Get that out of your head.

This process has been discussed here MANY times, and is available via a search.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[LWComputingMVP]

I'm not sure I follow why either of your posted options are being considered. Neither makes a whole lot of sense to me.

But 58sniper is correct - PDC in active domain is not what you think it is. Before you go about this, can I recommend you STUDY and learn what is involved? Also, setup a test network (even using Virtual PC or VMWare) and TEST the processes involved - mine and/or the ones you want to use).

Here's what I would do:
1. Make the new server a member server in your existing domain.
2. Read the links in yellow below. Understand the updates you need to do and the commands you need to run. Then run DCPROMO and upgrade the 2003 DC to a Domain Controller.
3. Turn off the 2000 server for a few days (preferrably weeks) and make sure everything is working. If it's not, you can just turn it back on and troubleshoot. Otherwise, after 3-4 weeks (and BEFORE 8 weeks or you could have other issues with a tombstoned DC), power it back on and run DCPROMO to demote it. The only thing this doesn't preserve is the computer name - which SHOULDN'T matter. It also means you can do this upgrade with little chance of causing significant down time.

[highlight]Here are some links that should get you going for upgrading a 2000 domain to 2003:

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/...03-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

[/highlight]

 

[dufresnem]

I will reveiw the links you have highlighted in yellow.

Thanks.

 

[dufresnem]

I recently ran the Windows Server 2003 checkupgrade utility against my Windows 2000 Server and it indicates the following;

"Remote Storage Services"
Setup cannot complete because Remote Storage is not included in Windows Server 2003 Standard Edition. To use Remote Storage, you must upgrade to Windows Server 2003 Enterprise Edition.

I am unsure if I require remote storage. How can I determine what applications are using this service?

 

[LWComputingMVP]

Hopefully, this will explain it a little.

http://support.microsoft.com/kb/234776

 

[dufresnem]

That's what I was looking for.

Somehow that was installed. I don't use Remote Storage, so I removed it.