[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

The specified directory is not bound to a remote resource (Error)

When I go to change anything in my Primary roles holder ACTIV Directory  I get the titled error. I already moved the FSMO roles to another server in the forest so that is safe what do I need to do to fix this issue? Do I need to demote said server and the run DCPROMO once again or is there a fix for this issue? any help would be appreciated. I have attached .png file of the error.
AD-Error.png
0
LLUIGI
Asked:
LLUIGI
  • 4
  • 2
1 Solution
 
Will SzymkowskiSenior Solution ArchitectCommented:
Even though you had transferred your FSMO roles to another DC you need to check if the changes actually happened.
Run the command
- netdom /query fsmo

Make sure that it is pointing to the proper DC. This seems like a RID Master issue. Was this DC holding all of the roles?

You may need to demote this server and Seize the roles if the changes did not apply to the other DC you transferred them to.

Will.
0
 
LLUIGIAuthor Commented:
Already verified query returns the new role holder
0
 
LLUIGIAuthor Commented:
Yes the DC with the issue was holding all the roles
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Will SzymkowskiSenior Solution ArchitectCommented:
You will need to make sure that if you had moved the PDC role from this server to another one that you need to configure the registry settings on the DC that you moved them to.

Configure PDC Authoritative Time Source

I would then demote this machine from the domain. If you cannot successfully do this I would seize any other roles it has (FSMO) move any other roles like DHCP etc to another server and power it down. Perform a metadata cleanup.

Promote a new DC into the environment.

Will.
0
 
LLUIGIAuthor Commented:
Will look into it thank you.
0
 
LLUIGIAuthor Commented:
No solution was provided I researched the issue and applied a fix on my own you can close the query but no solutions was provided.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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