Solved

Transfer NT AD to 2003

Posted on 2008-06-17
3
194 Views
Last Modified: 2010-04-21
Hello,

I am trying to transfer a NT AD to a Windows 2003. My plan is to make the 2003 server a bdc of the NT domain in order to copy the users, then switch off the old NT server and promote the 2003 to PDC; might as well leave it as bdc.

I have made the 2003 member of the NT domain but when trying to run dcpromo on the 2003 I get the below error:

The domain name estdom1 might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain estdom1:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.estdom1

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:

192.168.0.7
192.168.1.1

- One or more of the following zones do not include delegation to its child zone:

estdom1
. (the root zone)

For information about correcting this problem, click Help.

I have set up DNS but I am not at all good in configuring NT so I can not understand what is wrong with old domain so I can troubleshoot.

Can someone please assist?

Thanks in advance.

0
Comment
Question by:Lastdim
3 Comments
 
LVL 13

Expert Comment

by:dhoffman_98
ID: 21802355
For 20 points?

Here's a clue... look for information on single label domain names and fully qualified domain names. estdom1 is not fully qualified and can't be looked at in DNS for authoritative information without a domain suffix.

That's my 20 point answer.
0
 
LVL 13

Accepted Solution

by:
ocon827679 earned 20 total points
ID: 21805699
Dude - do some searching on the support.microsoft.com site.  Look for something like "migrating NT to windows 2003 AD."  There's tons of info.  The lowdown is simple.  You do not make a W2K3 server a bdc to NT.  The W2K3 server will become the new "head honcho."  Do not try and run dcpromo here.  You upgrade the NT PDC to W2K3 with the installation media, and hopefully you have a fall-back plan.

You've got a lot of reading to do.  Don't be foolish and try and do this on the cheap, as it will bite you in the .... well lets just say "where the sun don't shine" ... and cause more problems that you haven't even begun to dream about yet.
0
 

Author Closing Comment

by:Lastdim
ID: 31467932
Thank you ocon827679. I already started to build the domain on the 2003 server from scratch :)
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

837 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question