question

SharynSchmidt-5224 avatar image
0 Votes"
SharynSchmidt-5224 asked DSPatrick commented

checking sysvol replication type when there is only 1 DC in the domain!?

Hi.
I have a single DC, 2012 server R2. I want to add a 2019 DC because I know it is not a best practice to only have 1 DC (just started this job . Trust me, I freaked when I discovered there was only 1 DC!!!!)

Here is the problem. I have gone thru all the prerequisite steps on the 2012 DC and everything looks fine. What I can't figure out how to do is check the sysvol replication type because this DC has NEVER REPLICATED! I want to ensure when it starts replicating to the 2019 DC after I promote it, it is using DFSR. I have looked in the registry and ran the diagnostic that indicates what it's running but since it's not running either DFSR or FSR at the moment, I'm not sure how I can tell what it's going to run.

When I run dfsrmig /getmigrationstate on the 2012 DC, I get this message:
All Domain Controllers have migrated successfully to Global state (‘Eliminated’). Migration has reached a consistent state on all Domain Controllers. Succeeded.

So does that mean the 2012DC is going to replicate to the 2019 DC using DFSR by default now? Ultimately this is what I want!

Thanks in advance
Sharyn

windows-active-directorywindows-server-2012
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

DSPatrick avatar image
0 Votes"
DSPatrick answered DSPatrick commented

Take a look here, if you find 48 then using DFSR, if null or 0, 16, 32 then FRS or some state of migration from FRS


31270-image.png

Also some general info

The two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also [making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.



--please don't forget to Accept as answer if the reply is helpful--









image.png (343.3 KiB)
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you.

I'm good to go!

0 Votes 0 ·

You're welcome.


0 Votes 0 ·

LOL don't go anywhere. I just promoted my 2019 server and I'm waiting to see........

The 2012 dc has never replicated so it's initializing too.

0 Votes 0 ·

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations.




0 Votes 0 ·

I did that already.

I did all the prep work, the replication was my last issue/question.

Everything looks good with new 2019 DC for the moment.

At one point soon I need to just shut the old one down for a few minutes and make sure authentication is working

Now I'm off to configure a Bastion server and subnet in Azure. KNow anything about that?

LOL just kidding!

Sharyn

0 Votes 0 ·
Show more comments