FSMO role issues after demoting and re-promoting server

Was in the middle of a migration from a Windows 2000/Exchange 2000 Server to
a Windows 2003/Exchange 2003 server. The plan was to keep the old Windows
2000 Server online afterwards as a backup Domain Controller, print server,
etc.

I joined the new server to the domain, made it a DC, migrated Exchange, etc.
I also made it a Global Catalog Server and transferred all the FSMO roles to
it.

I had a problem with it fully replicating the domain, basically not
replicating the SYSVOL/etc shares. Without thinking, I ran DCPROMO on the
new server to demote it, then about 30 mins later ran DCPROMO on it again to
make it a domain controller again to see if the problem would be corrected.

The replication problem has now been solved, but I think I made a mistake by
not transferring the FSMO roles off the server before demoting it.

Once I solved all the issues and everything was running well, I went ahead
and made it a Global Catalog Server again. I figured I'd also check the
FSMO roles. I checked the Schema Master role and it was set back to
OLDSERVER. I changed the Domain Controller to NEWSERVER, that took fine. I
then went to change the Operations Master, and it told me it could not
locate the source server and I would have to seize the role (which it
advised against).

I then changed the Domain Controller back to OLDSERVER and it looks like the
Schema Master is set to OLDSERVER and is working, but I have my doubts.

I really don't care which server the FSMO roles are on, but now I'm
concerned they are not functioning correctly and it will come back to haunt
me.

I'm afraid to 'seize' the roles because both servers are still online and
I'm not sure of the ramifications in this situation.

In summary, OLDSERVER was the original FSMO roles owner. I set NEWSERVER as
the owner for all FSMO roles, then demoted it and re-promoted it without
moving the FSMO roles first. Now AD thinks OLDSERVER is the owner, but it
won't allow me to change it to NEWSERVER.

Any advice would be greatly appreciated.

Thanks!


.

Relevant Pages

  • Re: Use second Domain controller
    ... Your environment can stay workable for quite some time with some of the fsmo ... To learn where the fsmo roles currently reside: ... If you don't have the tools installed, install them from your server install ... Windows 2000 domain controller in the domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: FSMO issues
    ... Start with a backup of all important user DATA from all machines, including exchange databases. ... If you have seized FSMO roles, NEVER connect the old FSMO machine back to the domain. ... If everything is fine you can REINSTALL from scratch the 2003 machine and add it as an additional DC to the domain, make it DNS server and Global catalog server. ... The new domain controller is running windows server 2003. ...
    (microsoft.public.win2000.active_directory)
  • RE: 2003 Upgrade
    ... the current Windows 2000 domain to Windows 2003 domain. ... new Windows 2003 domain controller as a GC and transfer all the FSMO roles ... servers as GC and transfer FSMO roles to them. ... enable the Global Catalog on the new Windows Server 2003 domain controller. ...
    (microsoft.public.windows.server.migration)
  • Re: FSMO issues
    ... If you have seized FSMO roles, ... add it as an additional DC to the domain, make it DNS server and ... The new domain controller is running windows server 2003. ... figuration,DC=koyocorp,DC=com is the Schema Owner, but is deleted. ...
    (microsoft.public.win2000.active_directory)
  • Re: FSMO role issues after demoting and re-promoting server
    ... Once you seize a role ... >> Was in the middle of a migration from a Windows 2000/Exchange 2000 Server ... >> Windows 2000 Server online afterwards as a backup Domain Controller, ... >> by not transferring the FSMO roles off the server before demoting it. ...
    (microsoft.public.windows.server.active_directory)
Loading