FSMO from DC2012 to DC2019

[discoveranother]

Hi all,

 

I have run a FSMO role transfer from DC2012 to DC2019. Prior to that I ran the migrate from FRS to DFSR and all went fine. ADUC and everything has transferred over fine and I ran the adreplication tool and it says all successful. The DC2019 also shows it is the schema master when running netdom query fsmo.

 

However, the Sysvol folder has not shared and there are no policies inside it. The sysvol folder is empty.

 

Any help much appreciate.

 

Thanks

[discoveranother]

Doing a sysvol share check below, the new server is DC2019 but the old one is DC2012. When I previously ran this on the DC2012 before commencing, all tests passed. I am running the below on the DC2019.

 

C:\Windows\system32>Dcdiag /e /test:sysvolcheck /test:advertising

 

Directory Server Diagnosis

 

Performing initial setup:

Trying to find home server...

Home Server = DC2019

* Identified AD Forest.

Done gathering initial info.

 

Doing initial required tests

 

Testing server: Default-First-Site-Name\DC2012

Starting test: Connectivity

......................... DC2012 passed test Connectivity

 

Testing server: Default-First-Site-Name\DC2019

Starting test: Connectivity

......................... DC2019 passed test Connectivity

 

Doing primary tests

 

Testing server: Default-First-Site-Name\DC2012

Starting test: Advertising

......................... DC2012 passed test Advertising

Starting test: SysVolCheck

......................... DC2012 passed test SysVolCheck

 

Testing server: Default-First-Site-Name\DC2019

Starting test: Advertising

Warning: DsGetDcName returned information for \\DC2012.fulmouth.local, when we were trying to reach DC2019.

SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

......................... DC2019 failed test Advertising

Starting test: SysVolCheck

......................... DC2019 passed test SysVolCheck

 

 

 

Running partition tests on : ForestDnsZones

 

Running partition tests on : DomainDnsZones

 

Running partition tests on : Schema

 

Running partition tests on : Configuration

 

Running partition tests on : fulmouth

 

Running enterprise tests on : fulmouth.local

 

C:\Windows\system32>

[Michael]

Presumably DNS is all in order? And I presume also the schema was updated on Server 2012 to accommodate Server 2019? I still prefer to do things this way.

 

Another thing to rule out is firewall - should be perfectly fine to disable on the LAN.

[discoveranother]

Presumably DNS is all in order? And I presume also the schema was updated on Server 2012 to accommodate Server 2019? I still prefer to do things this way.

 

Another thing to rule out is firewall - should be perfectly fine to disable on the LAN.

 

Good point about the firewall, it was enabled. I did a re-replication and also checked this article as well and it seems to have sorted it after doing tests. Fingers crossed:-

 

https://andreagx.blogspot.com/2018/01/ws-2016-recently-added-dc-do-not-work.html

[discoveranother]

Hi all,

 

Running DCdiag, ad replication tool, netdom query fsmo, DFSR state and checking the new server over all seems successful. But thought I would have a look at an article I came across which shows the output of running this command:-

 

For /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo WHERE replicatedfoldername='SYSVOL share' get replicationgroupname,replicatedfoldername,state

 

Which then gives one of these outputs:-

 

The state values can be any of:

0 = Uninitialized

1 = Initialized

2 = Initial Sync

3 = Auto Recovery

4 = Normal

5 = In Error

 

In the article the user shows the following:-

 

 

and they followed these instructions to correct the number 2 above to number 4 as below

 

https://docs.microsoft.com/da-dk/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization

 

which should show:-

 

 

I ran the command on the new server and it shows number 2 as in the first image above even though all tests on the server show fine. Do I need to do the force synchronization and if so am I performing a non-authoritative synchronization or a authoritative synchronization as per the article in the link above ?

 

Thanks all

[kevin_lane]

This utility will give you a good over view of any replication issues within your forest / domain

 

https://www.microsoft.com/en-gb/download/details.aspx?id=30005

[kevin_lane]

Personally I would let nature takes its course from my understanding you can run the

 

dfsrmig /GetMigrationState which should give you an idea where each dc is at

 

https://judeperera.wordpress.com/2019/03/19/sysvol-migration-from-frs-to-dfsr-step-by-step/

[discoveranother]

Thanks Guys for the replies.

 

The getmigrationstate shows all is fine.

[Neil83]

I had a similar issue recently after adding a 2019 DC and transferring FSMO Roles. Some of the folders were hidden in SYSVOL on the 2019 DC and I hadn't switched on - View - Hidden Items.

 

Thought I'd mention just in case.