FRS migration to DFSR, SYSVOL not deleted

Romar 86 Reputation points


I migrated 8 Windows Server (2012 R2 and 2016) from FRS to DFSR. A root domain has 4 servers and a child domain 4 servers.
On 6 servers I see Sysvol_DFSR only and 2 servers have Sysvol and Sysvol_DFSR. The two servers are in the child domain. On all 8 servers the File Replication Service is disabled and replication is working fine.

My question is if the Sysvol folder can be deleted manually, there are only a few empty Policy folders inside.


Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,311 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,004 questions
0 comments No comments
{count} votes

Accepted answer
  1. Thameur-BOURBITA 32,606 Reputation points


    After sysvol migration from FRS to DFS , the old sysvol folder should be removed in the end of migration:

    User's image

    If the replication working fine using the new sysvol , that means that sysvol replication has been switched to the new folder successfully.

    Now you should check if last step of sysvol migration was completed correctlty , you should run the following command to confirm the end of migration : ``dfsrmig /Getglobalstate`. Once the migration is completed the old sysvol folder should be deleted.

    If it not deleted , check the sysvol share is pointed on new sysvol folder using the command net share before delete it manually.

    Please don't forget to mark helpful reply as answer to helps forum visitors to identify the correct answer

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP

    The underlying folder on the DCs that were migrated (FRS to DFSR) will be Sysvol_DFSR but the share name for all is Sysvol the folder name and share name for new DCs will be Sysvol when migration is completed the original SYSVOL folder is removed from the DC. If it's still there I'd make sure the migration completed without errors. (check DFSR Replication event logs) and check Dfsrmig /getmigrationstate (especially on the suspect ones)

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