Can't add ACS 5.1 Secondary Instance to AD

Unanswered Question

I have a two node deployment and was able to successfully join AD on the primary node and see the computer account in the domain. We discovered that the secondary node was causing our account to lock up after a password change. After review we saw no computer account for the secondary instance. As you can image the secondary is 'read-only' and there is no way to add it to the domain. Multiple attempts to re-add the first node do not seem to correct the problem. In an effor to work around the issue, I attempted to promote the secondary but of course that gave me an error as well. How do I get both instances on the domain?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
jrabinow Sat, 01/23/2010 - 22:46

There appear to be some errors related to replication.

What error do you see when you try to promote the secondary

Actions

This Discussion