A company I support are about to go ahead with a new computer system upgrade.
They will be moving from Windows 2000 up to Windows 2003 R2, and we have been asked to handle the migration/upgrade.
To give you a brief overview, currently there are 2 sister companies who share resources. 1 of the companies is also split over 2 sites.
Main Site : Company A + Company B
Additional Sites: Company B
Future Sites: Possibilty of Company B expanding further
Company A: Exchange
Company B: Exchange (both sites), SQL (shared with company A), Intranet (shared with company A),
Both companies have users that have specific roles in each of the companies.
The Forest is split into 2 root level domains one for each company, Company B are looking to upgrade/migrate to Windows 2003 R2.
What we need to do is get some hints and pointers on handling this. We have read a lot of the following document http://support.microsoft.com/?kbid=555040
regarding migrating 2000 -> 2003 however it has some quite worrying little points that it raises, for instance:
It mentions that you shouldn't use OEM versions of Windows 2003 to do the upgrade, but as they are all being supplied with the new kit all the versions will be OEM.
There are a lot of other points that need looked at and look applicable to us. There are only about 130 users in total between the 2 companies so we were wondering if it's not just better to rebuild the Forest with the new kit and re-create the AD? The main problem we see with this is that Company A would somehow need to be migrated on to the new forest and we are not sure if this is possible?
Alternativly would we be better to create a new root level domain and build the new servers up in that, then move everything from the old domain over before decomissioning it?
We need to look to do this with as little chance of failure and switch over as fast as possible as the company works 7 days a week.
The company that are staying on 2000 we are trying to get to upgrade to 2003 for ease of exchange upgrade... lets hope they go for it.