Heath Calhoun
asked on
Server 2003 FSMO roles reported wrong
We have a statewide network, with each office having a 2003 AD server as a backup. At our hq, we have the main 2003 AD server.
Recently, we had problems with the original server. Rolese were transerverd to our ms-vicksburg server from the original AD ms-dc1. Now, we have a new 2003 server box ms-dc. We transfered the roles to this box, and everything seems to be replicating through the districts.
Recently, trying to add a user to a computer, AD said on ms-dc that the user was there. However, when trying to add him, it would not. Looking at ms-dc1's AD, the user was not there.
I did a netdom query fsmo roles, and everything is pointing to the ms-vicksburg server. However, do the same on the ms-dc, and everything is pointing to the ms-dc server.
Is there any way to without removing AD from ms-dc1 to force it to look at ms-dc? I would like to keep dc1 as a backup for the main server.
Thanks.
Recently, we had problems with the original server. Rolese were transerverd to our ms-vicksburg server from the original AD ms-dc1. Now, we have a new 2003 server box ms-dc. We transfered the roles to this box, and everything seems to be replicating through the districts.
Recently, trying to add a user to a computer, AD said on ms-dc that the user was there. However, when trying to add him, it would not. Looking at ms-dc1's AD, the user was not there.
I did a netdom query fsmo roles, and everything is pointing to the ms-vicksburg server. However, do the same on the ms-dc, and everything is pointing to the ms-dc server.
Is there any way to without removing AD from ms-dc1 to force it to look at ms-dc? I would like to keep dc1 as a backup for the main server.
Thanks.
ASKER
All other servers are showing ms-dc as the 5 FSMO's. Just ms-dc1 is still showing ms-vicksburg as the holder of the FSMO's. I used the GUI's to transfer from vicksburg to dc.
Possiblt because ms-dc1 was the original role holder, it has not registered the change from ms-vicksburg to the new role master; try setting the roles back to dc1 and then transferring them to the new primary
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
see http://support.microsoft.com/kb/255504