aaron240
asked on
Cannot Transfer FSMO Roles
Having a heck of a time transferring FSMO roles between DCs that are both online. Here's what happened:
3 physically separated DCs - 2 servers at main location (HQ), 1 server at secondary location (L1) and 1 server at tertiary location (L2)
The DC at HQ was destined to be reformatted, rebuilt, etc, and it held all of the FSMO roles. In order to handle the FSMO roles locally, the other server at HQ (originally not a DC) was given AD/DNS via DCpromo. Then DCpromo was used to remove from original server AD/DNS (mistake to do this before manually reassigning the PDC, RID, etc). Original AD/DNS server pushed out settings to L1 which assumed all FSMO roles. Now I can't get L1 to transfer to HQ, despite both servers being online, using the ntdsutil command line utility. It simply states that the FSMO role holder cannot be contacted (which doesn't make sense since the connections->connect to server servername successfully binds the remote server).
Can ping between HQ and L1. I don't want to usurp with ntdsutil seize because both servers are online.
Ideas
3 physically separated DCs - 2 servers at main location (HQ), 1 server at secondary location (L1) and 1 server at tertiary location (L2)
The DC at HQ was destined to be reformatted, rebuilt, etc, and it held all of the FSMO roles. In order to handle the FSMO roles locally, the other server at HQ (originally not a DC) was given AD/DNS via DCpromo. Then DCpromo was used to remove from original server AD/DNS (mistake to do this before manually reassigning the PDC, RID, etc). Original AD/DNS server pushed out settings to L1 which assumed all FSMO roles. Now I can't get L1 to transfer to HQ, despite both servers being online, using the ntdsutil command line utility. It simply states that the FSMO role holder cannot be contacted (which doesn't make sense since the connections->connect to server servername successfully binds the remote server).
Can ping between HQ and L1. I don't want to usurp with ntdsutil seize because both servers are online.
Ideas
ASKER
this has been resolved. dns issues and stale/missing records were purged/updated and after an extended period of time propagation allowed the servers to transfer FSMO roles successfully
No comment has been added to this question in more than 21 days, so it is now classified as abandoned..
I will leave the following recommendation for this question in the Cleanup topic area:
PAQ - Refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
Pseudocyber
EE Cleanup Volunteer
I will leave the following recommendation for this question in the Cleanup topic area:
PAQ - Refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
Pseudocyber
EE Cleanup Volunteer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://support.microsoft.com/default.aspx?scid=kb;en-us;332199