Avatar of SC Team
SC Team
Flag for Malaysia asked on

FRS to DFSR Migration Failure

I am trying to perform FRS to DFSR Migration
PDC (TESTDC1 ) -  Wins2019 (Domain and Forest Functional Level at Wins2008, Schema at Wins2019)
New Secondary DC (TESTDC2) -  Wins2016 (Domain and Forest Functional Level at Wins2008, Schema object version at 88 Wins2019) 
-------------------------------------------------------
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\Administrator.besoosay> dfsrmig /getglobalstate

DFSR migration has not yet initialized. To start migration please
set global state to desired value.

PS C:\Users\Administrator.besoosay > dfsrmig /setglobalstate 1

Current DFSR global state: 'Start'
New DFSR global state: 'Prepared'

Migration will proceed to 'Prepared' state. DFSR service will
copy the contents of SYSVOL to SYSVOL_DFSR
folder.

If any domain controller is unable to start migration, try manual polling.
Or run with option /CreateGlobalObjects.
Migration can start anytime between 15 minutes to 1 hour.
Succeeded.

PS C:\Users\Administrator.besoosay > dfsrmig /getmigrationstate
The following domain controllers have not reached Global state ('Prepared'):
Domain Controller (Local Migration State) - DC Type
===================================================

TESTDC1 ('Start') - Primary DC
TESTDC2 ('Start') - Writable DC

Migration has not yet reached a consistent state on all domain controllers.
State information might be stale due to Active Directory Domain Services latency.
PS C:\Users\Administrator.besoosay > dfsrmig /getmigrationstate
The following domain controllers have not reached Global state ('Prepared'):
Domain Controller (Local Migration State) - DC Type
===================================================

TESTDC1 ('Start') - Primary DC
TESTDC2 ('Waiting For Initial Sync') - Writable DC

Migration has not yet reached a consistent state on all domain controllers.
State information might be stale due to Active Directory Domain Services latency.
PS C:\Users\Administrator.besoosay > dfsrmig /getmigrationstate
The following domain controllers have not reached Global state ('Prepared'):
Domain Controller (Local Migration State) - DC Type
===================================================

TESTDC1 ('Start') - Primary DC
TESTDC2 ('Waiting For Initial Sync') - Writable DC

Migration has not yet reached a consistent state on all domain controllers.
State information might be stale due to Active Directory Domain Services latency.
PS C:\Users\Administrator.besoosay >
---------------------------------------------------------------------------
DFS Replication Event Viewer -Event ID 8013
DFSR was unable to copy the contents of the SYSVOL share located at C:\Windows\SYSVOL\domain to the SYSVOL_DFSR folder located at C:\Windows\SYSVOL_DFSR\domain. This could be due to lack of availability of disk space or due to sharing violations.
 
Additional Information:
Sysvol NTFRS folder: C:\Windows\SYSVOL\domain
Sysvol DFSR folder: C:\Windows\SYSVOL_DFSR\domain
Error: 367 (The process creation has been blocked.


There is sufficient disk space therefore this is not an issue. Any idea how can I resolve this issue?

* Distributed File System Replication (DFSR)Windows OSWindows Server 2019Active Directory

Avatar of undefined
Last Comment
SC Team

8/22/2022 - Mon
arnold

Where is the original DC with 2008 or 2012 where FRS exists?
You have to transition first before joining the 2019 since it does not have FRS capability, e 2016 is questionable.
M A

Agree with Arnold, You are supposed to migrate to DFSR before introducing a new 2019 DC.
Now you have to remove it and migrate FRS to DFSR and promote it again.
SC Team

ASKER
The Original DC was Wins2012 (Domain and Forest was at 2008) it was already decomm for almost 2 months ago by another person after they migrated to OS Win2019 (Domain and Forest were still in 2008). The FRS and DFSR Migration was not implemented before upgrading the PDC OS to Wins 2019. At the moment on production, it is a single domain forest.

I encountered an error while promoting a secondary DC with OS wins2019 about FRS. This lead us to perform FRS to DFSR migration testing of the restored PDC on an isolated network. We had to introduce a Wins2016 server to successfully promote the secondary DC before implementing the FRS to DFSR migration and now we are stuck at the above state. We need a solution to this issue because we will be terminating the on-prem server and moving to the cloud as IAAS.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
M A

Take a backup and cleanup of the new DC as it is failed while promoting.
Then migrate from FRS to DFSR and make sure your DC is healthy.
Once it is confirmed please promote the 2019 server.
arnold

Does the 2019 sysvol contains data?
This would have been empty and causing issues from the begining.

If your environmen has virtual.capacity.

Thinking other than getting the 2012 as a DC by hook or by crook
As the only set of DCs using FRS for sysvol replication. Restore the sysvol data from the old DC's backup.
Migrate the FRS to dfsr and then rejoin the 2019/2016 retiring the 2012's as MAS pointed out after the DC is sync up and in good health.

The other option, is to get an MS case opened if it is possible to update the AD data to switch from FRS to DFSR by configuration, while you stil would need to restore data from the sysvol data of the 2012 server...
ASKER CERTIFIED SOLUTION
SC Team

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question