How to recreate Fileserver running DFS replication and DFS namespaces

Question

I am currently having issues with our fileserver which is a VM running Windows server 2016 and hosts the DFS replication and namespace of our company. I am having issues with the WinSxs folder and no type of cleanup helps resolve the issue of this folder eating up disk space. I asked here on the Microsoft community and Microsoft advised if all else fails the server will need to be rebuilt. Our namespace data is hosted on a separate VHD therefore I was wondering if it would be possible to migrate the dfs configuration to a new VM and then attach the VHD with the already existing data to it? Will this sort of workaround work? Or would it be best just to completely start a new fileserver? I also thought of creating a new fileserver and adding it to the existing replication group but I do not want to stay replicating all the data from the old fileserver to the new fileserver when we already have this data available and can simply attach it to the new VM. Has anyone had this sort of issue before?

Answer 1

Hello Stephanie,

Thank you for your question and for reaching out with your question today.

If you're experiencing persistent issues with the WinSxs folder on your Windows Server 2016 file server and other cleanup methods haven't been successful, migrating the DFS configuration to a new VM and attaching the existing data VHD can be a valid workaround. Here's a suggested approach to implement this solution:

1. Set up a new VM: Deploy a new Windows Server 2016 VM that will serve as the replacement file server.
2. Install DFS services: Install the DFS services role on the new VM. This will allow you to configure the DFS namespace and replication settings.
3. Configure DFS namespace: Recreate the DFS namespace structure on the new file server, ensuring that it matches the existing configuration.
4. Set up replication group: Create a replication group on the new file server and add the existing file server as a member. This will initiate replication to synchronise the data between the old and new file servers. Depending on the size of the data and network bandwidth, this initial replication process may take some time.
5. Verify data synchronisation: Monitor the replication process and ensure that the data is successfully synchronised between the old and new file servers.
6. Attach existing data VHD: Once the data replication is complete, detach the existing data VHD from the old file server and attach it to the new file server. Make sure to update the relevant file paths and permissions as necessary.
7. Update DFS configuration: Modify the DFS configuration to reflect the new file server and data path. Update any references or mappings to the old file server with the new server's details.
8. Test and validate: Validate that the DFS namespace and replication are functioning correctly on the new file server. Test file access and ensure that clients can access the data without issues.
9. Decommission the old file server: Once you have confirmed that the new file server is functioning as expected and all data is accessible, decommission the old file server. Remove it from the replication group and ensure that all clients are directed to the new file server.

By following this approach, you can migrate the DFS configuration to a new VM while preserving the existing data. This will help you address the WinSxs folder issue and ensure a smooth transition to the new file server. Remember to thoroughly test the new setup and have proper backups of your data before proceeding with any major changes.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.