Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2044
  • Last Modified:

Cannot demote from DC to Member Server.

One of my clients purchased a new server. He wishes to stay in a single server environment (5 employees). I installed the new server and promoted it without any problems. A couple of days later I am trying to demote the other and I get the following message.

"The box indicating that this domain controller is the last controller for the domain tapanganpediatrics.com is unchecked. However, no other Active Directory domain controllers for that domain can be contacted.

Do you with to proceed anyway?

If you click Yes, any Active Directory changes that have been made on this domain controller will be lost.

YES NO "

I have verified connectivity between the two. What else can I check?
0
smetterd
Asked:
smetterd
1 Solution
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Did you transfer the FSMO roles?  Did you make it a global catalog?  Are either of the servers running Small Business Server (for a 5 user network, that's what they SHOULD be running).
0
 
smetterdAuthor Commented:
I didn't manually transfer any FSMO roles. I think that they should auto-transfer to other DCs during the demotion process. Yes I made both global catalogs. Neither is running SBS.
0
 
Netman66Commented:
They will transfer, but it's a dangerous assumption.  You're safer (and wiser) to transfer them manually - this way you're certain there are no underlying issues.

Check to make sure the old server is now pointing to the new server for DNS and that both servers are registered.  Do not put any ISP DNS addresses on any NIC inside your LAN.

0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Jay_Jay70Commented:
i have seen dcpromo fail time and time again, there is a forceremoval switch that you can use if all else fails, but then you manually have to remove all traces from DNS, AD, Sites and Services etc, you also have to perform a metadata cleanup afterwards on the DC that is left

DCPROMO /Forceremoval

Personally, i would leave it as a redundant DC, better to have two on the network anyway
0
 
smetterdAuthor Commented:
Leaving it as a redundant DC is not an option according to the owner of the equipment.
0
 
smetterdAuthor Commented:
So would y'all recommend that I manually transfer all FSMO roles (seize if necessary)?
0
 
Netman66Commented:
Yes, transfer them gracefully if possible.  Only seize them if you cannot do it by any other means and do so once the other server is pulled offline permanently.

Then follow Jay's link to cleanup AD, DNS and AD Sites and Services of any traces of the old DC.

0
 
smetterdAuthor Commented:
Jay's link? Is it a hyperlink? I can't find it.
0
 
Netman66Commented:
Oops, sorry about that.  He posted something similar in another Q.

Here is the article:

http://support.microsoft.com/kb/216498/en-us

0
 
smetterdAuthor Commented:
I cleaned it all out and the system still cannot "find" itself. When I try to open Active Directory Users and Comptuers locally, many times even that cannot be found. In order to re-hook it, I have to right click then select Connect To Domain Controller.

How can I force this machine to always look at its own copy of AD?
0
 
Netman66Commented:
It sounds like the GC isn't available or all the entries for it in DNS are not present.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now