General discussion


Win2003 Domain Migration

By jbm ·
Company consolodation has occured - we are migrating 2 Win2003 Active directory domains in a new Forest Root domain. The domain have been previously been migrated from a WinNT 4.0 domain structure to Win2000 AD and then upgraded to Win2003. We would like to do a step approach to the migration. Migrate some accounts, then migrate client systems and at the end migrate File & Print Servers. Question - If a user account is migrated then the users laptop - will the user be able to access his/her resources still in the old domain? (i.e. printers, file shares and folders, etc...) or will this require the file & print server be migrated at the same time?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to Win2003 Domain Migration

well your senario says that the DCs of an existing AD domain [which contain user accounts and profiles] are going to change to a new domain which will be a new root domain. e.g. change from: <your domain>.com to <new domain>.com.

On what DCs will the old user accounts reside that you would use the ADMT to migrate accounts?

The only senario in which you would have 2 domains [old and new] that you migrate user account and computer account info using the ADMT and users can log on to both the old domain and new domain is if you use new hardware for the new domain and still have old equipment for the old domain running. Users then can access both domains [provided that users have connectivity to both domains].

Collapse -

by CG IT In reply to Win2003 Domain Migration

This is straight from MS KB article 310997

Getting Information About Objects in Another Domain
With all this talk about partitioning the directory catalog, you might be wondering how information from one domain partition gets accessed by users in another domain. After all, if the domain controllers in one domain contain information about objects only in their domain, what happens when users need to get information about objects that reside in another domain? Good question, and fortunately the answer is straightforward: Active Directory services uses DNS lookups and queries to resolve queries, just like the Internet.

Although Active Directory services and Windows 2000 or Windows Server 2003 use DNS for their lookup service, they both use a special service (SRV) resource record (RR) entry that designates a given DNS entry as a domain controller. Domain controllers, in turn, determine whether they are able to resolve a query, such as would be the case if the query were about an object in their local domain. If they cannot, the request is referred to a domain controller that either can resolve the request itself or can point the domain controller to the next logical server to which the request should be made. Eventually, the domain controller that can resolve the query is found (or is definitely not found), at which time the client is referred to that server to continue with the query process.

here's a link

users can use UNC to access the old domain e.g. \\server name\user name\resource from run provided that the old domain is on the same subnet.

Related Discussions

Related Forums