Question : Active Directory migration (Win200 to Win2003) on same name servers

I am building a new network to replace our old one.

Currently we have a Windows 2000 Server with Exchange 2000 at our main property on IP 10.0.10.3.

A Windows 2000 file server is on the same network on IP 10.0.10.5

At another property we have a third Windows 2000 file server on another  linked through leased line VPN, on IP 10.0.0.2

I am replacing all three and adding another file server at our main building.

Here is the hard part:

The new machines will run Windows Server 2003/Exchange Serevr 2003.

I am using the same machine names, IP addresses and network names as the old ones for the new machines, and they are all running on a switch not currently connected to the main network (for obvious reasons).

I need a method of migrating users and groups from our existing Windows 2000 AD to the Windows 2003 server.

Active Directory Migration Tool seems to require servers currently online and talking to one another.

What I am looking for is an offline solution, where the AD user and group information can be extracted from the current Windows 2000 AD and then imported into the new Windows Server 2003 box.

I know there are other ways of doing this but I inherited our current network in a real mess and I dont want to risk any more problems by linking the new servers to the currently used machines the way I normally might.

Total separation is important at this point, and when I am ready the old servers will simply be switched off and the new ones will go live, without any of them ever having been aware of the other.

So, any ideas of a workable and reliable solution to pull out User and Group details for use in a new network that uses the same machine and network names and IP addresses as the current, live network ?

Thanks in advance.

Answer : Active Directory migration (Win200 to Win2003) on same name servers

You can use the csvde utility to export them and import them from an Excel sheet. It would be better to do an online migration, however I understand your reasons for not doing so.  This website http://www.windowsitpro.com will has some articles that relate exactly to what you are trying to do (I have used it myself in doing similar migrations, though it has been a while since I have done one.