Adding W2K8R2 to W2K3 Domain

When I try to add a W2K8R2 server to a 2003 domain I get the following error.

Changing the Primary Domain DNS name of this computer to "" failed.  The name will remain "domain name".

The error was:

The specified server cannot perform the requested operation.
LVL 5
ubsocAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

redesystemsCommented:
How are you adding the server?  During setup?
0
ubsocAuthor Commented:
I am not adding at setup.  I am manually adding after I apply all the security patches
0
ConchCrawlCommented:
There shouldn't be any problem in doing this.. I would make sure the member server is not part of a domain.
Check to make sure the computer name is not in AD if it is delete the object from AD and then rejoin the server to the domain.
To join a computer running Windows Server 2008 as a member server to the AD 2003 network

Log on to the computer that is running Windows Server 2008 by using the local administrator account.

Click Start, right-click Computer, and then click Properties. The System control panel appears.

Click Change settings.

On the Computer Name tab, click Change.

Select Domain, type the name of your internal domain name, and then click OK.

Type the user name and password for the domain administrator account, and then click OK.

Click OK twice, and then click Close to save your settings.

Restart the server.
 
I hope this helps, if this doesn't work please let me know.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

eridzoneCommented:
rename the new machine and then try to join domain
0
ambatihpCommented:
Windows 2008 by default expects IPV6 to be present/active; If you have assigned a static IP address to your network card, and unchecked the IPV6 option in the LAN/Adapter Properties.. You made a big mistake !!
Enable the IPV6; and Make sure your IPV4 Primary DNS is the IP address of your Windows2003 AD.
0
ConchCrawlCommented:
thx, ambatihp, i wish everyone would quit doing that, it just mucks things up in w2k8, you just have to make sure it's your primary. The first time I did this taught me the lesson :-). The quick fix isn't always the right one :-). I hate stating the obvious sometimes, I hope that isn't what happened, but hey if it fixes the problem so be it:-).
0
ubsocAuthor Commented:
ambatip,

I didn't uncheck the IPV6 option.  This server was part of the domain and I had to do a reload.  I forgot to dis-join before reloading. After the reload, I deleted the object in AD prior to re-joining.  This is when I get this pop-up error message.  The odd thing when deleting the object in AD is I get a new window. (see attached).  I didn't check the box "Use Delete Subtree server control".  What is the purpose of this box?  
Screen-shot-2010-03-26-at-8.59.3.png
0
Darius GhassemCommented:
Post ipconfig /all.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ubsocAuthor Commented:
eridzone,
Renaming the host did not fix the issue.   I get the same error.  
0
ConchCrawlCommented:
Was this W2K8 server a member server or domain server before you reloaded it?
0
ubsocAuthor Commented:
It was a member server.  

Just as a side note, the old server was running System Center Operations Manager 2007 R2 (MOM).  

0
ConchCrawlCommented:
What it seems to whining about is you may have setup a printer or network share or some other container on that server and it was published in AD, then you reloaded the server and didn't disjoin it from the domain first the container still exists in AD.
I would check in AD Users & Computers and from the view menu view select Users,Groups,Computers as containers.
This should let you see what it is whining about.
Let me know if this helps.
 
0
ubsocAuthor Commented:
When I switch to that view, do I seach for the object.  What am I looking for?  

Thanks
0
ConchCrawlCommented:
I would click on find objects in AD DS, it should be an option icon at the top, do a search on the entire domain for each type of container, especially printers and network shares and see if anything comes up relating to that server.
To search on the entire domain click on the domain open the search window and select the container and click find now. This will find everything published in AD.
Hope this helps.
0
ubsocAuthor Commented:
The issue has been resolved.  

This issue was it couldn't resolve the domain controller by name.  I had to add the domain in the dns suffix in the network properties.  Bingo everything worked.

Thanks for all the help.  
0
Darius GhassemCommented:
A ipconfig /all would have determined that issue. I'm glad you got it fix.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.