Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

FSMO Roles Server 2008 Functional level w/new 2012 DC


  • Please log in to reply
1 reply to this topic

#1 jcf01

jcf01

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:59 AM

Posted 10 August 2016 - 06:21 PM

Hello,

 

First post.

 

I am setting up a new 2012 DC for a customer.  The existing forest functional level is 2008.  All went well and replication is solid (repadmin, etc).  Let's call the 2008 server DC1 and the 2012 server DC2.  When I went to move FSMO roles from DC1 to DC2, it showed that I am able to move the PDC, RID and Infrastructure master role to DC2 (it shows DC2 in the second field and DC1 as the current holder of the role in the first field).  However, when I attempt to change the Schema master role and Domain naming master role, it shows DC1 in both fields (Current owner of the role is DC1 and DC1 is also in the 'Change to' field) so I am unable to change the roles.

 

Currently DC1 still has all FSMO roles.

 

Seizing the roles is not an option as the both DCs are staying put in the environment.

 

Has anyone seen this behavior?

 

Thanks in advance,

 

Jon

 



BC AdBot (Login to Remove)

 


#2 jcf01

jcf01
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:59 AM

Posted 10 August 2016 - 08:09 PM

Disregard. Figured it out. Needed to connect to DC1 and initiate the change from there instead of initiating the change from DC2.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users