This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 60%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Hello - I have an Active Directory environment that is at Forest Functional Level 2003 (Domain fl of 2008R2). Also, the sysvol migration from FRS to DFSR was partially completed and all DC's are in State 2 (REDIRECTED). My question is.. should we complete the sysvol migration and get to the final state of 3 (eliminated), or is it required to have our Forest Functional Level to Server 2008R2 prior to completing the sysvol migration. We're in this limbo state with sysvol (prior tech did this years ago and then left without letting anyone know). I read an article indicating the FFL should be changed to 2008r2 prior to the sysvol migration to DFSR. We have 4 DC's in total.. 3 are Server 2012R2 and one is Server 2008R2. Thanks to anyone who may have experience with this and can offer any advice.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 28.999999999999996%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVW%3C/text%3E%3C/svg%3E)
Hi,
Thank you for posting on us.
This article may help you
reference:https://judeperera.wordpress.com/2019/03/19/sysvol-migration-from-frs-to-dfsr-step-by-step/
Tip: This answer contains the content of a third-party website. Microsoft makes no representations about the content of these websites. We provide this content only for your convenience.
Hope this information can help you
Best wishes
Vicky
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I think its your only option. No this in of itself would not cause additional problems. I'd also confirm the required ports are flowing between sites.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts
--please don't forget to Accept as answer if the reply is helpful--
Thanks again for your reply. Since our Domain Functional Level is at Server 2008R2, it seems like we may be ok to complete the sysvol migration without rolling back, I originally read a post on a random blog indicating the Forest Functional Level needed to be at 2008R2 prior to completing the Sysvol migration, but i think it's just the domain functional level, which is what you wrote. if that is the case, then i should be able to complete the migration from redirected to eliminated without rolling back.? the ports should be fine but i will review them just in case!
Sounds good. Redirected state should be both sysvol and dfs are replicating in parallel. In redirected state the DFSR copy of SYSVOL starts to response for SYSVOL service requests. FRS will continue the replication of its own SYSVOL copy but will not be involved with production SYSVOL replication.
Let us know.
--please don't forget to Accept as answer if the reply is helpful--
Thanks for your reply. The tech who did this got to the Redirected state and then left. Nobody knew he did this so it's been in this state for about 1.5 to 2 years. The health of the domain looks fine. We were also thinking of going back to state 0 but wasn't sure if that would cause problems. I'll have to look into it more.
The domain functional level needs to be at 2008 or higher. It should have gone fairly quickly assuming domain health is 100%. Certainly shouldn't have been years. Since it redirected state I'd suggest canceling
dfsrmig /setglobalstate 0
then confirm health is good before trying again.
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405
--please don't forget to Accept as answer if the reply is helpful--
