Migration from NT and 2000 to 2003 domains using ADMT v2.0

Tags:
We have multiple forests in our organisation.We are now planning to consolidate them into a single forest and a single domain.We have more than 200 different sites spread all across the world. We have now upgraded all our domain controllers to 2000 and 2003 servers.We have a proper test lab being setup for performining all the tasks in it. We have tested inplace upgrade and we came up with our own procedures and we proceeded and we were sucessful in upgrading both from NT to 2000 and NT to 2003 depending on the availability of the licenced copies of the OS.We planned to use ADMT V2.0 (since we are microsoft's clients) We have faced problems drastically since day one of testing ADMT with trusts and user profile migrations. We have been getting errors such as 1.error 53 which talks about network path not found 2.Schema mismatch 3.RPC unavailable 4.access denied 5.Server is unwilling to perform the task 6.No logon servers available. 7.Everyone is not a part of domain admins group(We solved this by adding in the reqd place) These were the most prominent errors which we could list in our test. We have raised this with microsoft and they have asked us to wait for their resolution. We would like to hear from you too. Ambar

Answer Wiki

Thanks. We'll let you know when a new response is added.

Without more information it is difficult to say. However, the trust relationships between Windows NT domains and Windows 2000/2003 domains can get into problems. Windows NT of course, relies much more heavily on WINS for name resolution and location of services. Windows 2000+ focuses on DNS. I have run into cases where I have see issues similar to the ones you have mentioned, and had to create LMHOSTS files on the Windows 2000+ machines and the Windows NT machines to make sure that the systems could see each other. The LMHOSTS would need to contain the domain controllers of the Windows NT domains and the PDC emulators from each of the Windows 2000+ domains. The NT machines will not communicate trust relationships with the other DCs in a Windows 2000+ domain, only the one with the PDC Emulator FSMO role. This may resolve all of the issues, aside from the Schmea Mismatch issue.

Schema Mismatch may be more indicative of a replication issue. Check on the replication between DC’s and also check the FSMO roles in relation to Global Catalog servers. Recall that in a complex domain forest it is very important that the Infrastructure Master is NOT a Global Catalog Server.

Paul

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following