Jump to content

Recommended Posts

Posted

I'm currently supporting a network that still has Windows Server 2012 Standard DCs. (Not my fault, honest. They're still resisting moving beyond 2012 yet because of licensing costs, but I need to get things onto R2 at least to move their AV over to Defender. I've spent most of my career supporting antiquated networks for people who can't afford proper ones and this doesn't look likely to change soon.)

 

Although most of it is running on 2012R2 VMs under a 2019 host, the PDC is a separate physical box, and this is one I need to upgrade to 2012R2. There's a secondary 2012R2 DC running as a VM.

 

Should I consider making the 2012R2 VM the PDC first, move the FSMO roles etc., or just cross my fingers and go for it...?

Posted
My experience of upgrading a DC without moving FSMO roles has been very good. I just upgraded the server in place, knowing that worst case I’d have to seize the roles on the other DC. With that in mind, back up any other roles (like DHCP) that it may be running in case it bricks.
  • Thanks 1
Posted
My experience of upgrading a DC without moving FSMO roles has been very good. I just upgraded the server in place, knowing that worst case I’d have to seize the roles on the other DC. With that in mind, back up any other roles (like DHCP) that it may be running in case it bricks.

 

Aye , seconded. I’ve done this in the past

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...