SYSVOL Large file replication

Question

Anyone seen any side affects of putting a 25 GB or larger file on Sysvol? This is for a tool that needs the file local to every DC, so there is a reason. 2012 R2 Levels with DFS-R. The only thing I would think would be needed is maybe increase size of the Staging Quota

Answer 1

Hello anonymous user,

Thank you for posting here.

Q: Anyone seen any side affects of putting a 25 GB or larger file on Sysvol?
A: Based on the description, you want to put 25 GB or larger file on Sysvol on each DC and the large file is a tool instead of GPO file.

Because the file is not GPO file, we do not recommend that you put this large file in the SYSVOL path on the domain controller, so as not to affect the replication of SYSVOL and the application of GPO.

Here are my suggestions for you reference.

Suggestion 1
If you do not have so many Domain Controllers in your AD forest, you can put this large file into another path instead of SYSVOL path on every Domain Controller manually.

Suggestion 2
Or you can put this large file on each Domain Controller via GPO.
Create a GPO and link it to Default Domain Controller Policy.
Edit the GPO, navigate to Computer Configuration\Preferences\Folders\New folder.

For example:

Run gpupdate /force on each DC to make this GPO take effect.
It will create a new folder C:\folder on each DC.

Then put the large tool file on one folder and share this folder.
Copy the large tool file from shared path to local path on each DC via GPO.
Create another GPO and link it to Default Domain Controller Policy.
Edit the GPO, navigate to Computer Configuration\Preferences\Files\New files.

For example:

Run gpupdate /force on each DC to make this GPO take effect.
It will Copy the large tool file from shared path to local path on each DC.

Hope the information above is helpful.

Should you have any question or concern, please feel free to let us know.

Best Regards,
Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

I'd suggest some other method rather than potentially disruption active directory domain services. Maybe create a new namespace for this purpose.
https://learn.microsoft.com/en-us/windows-server/storage/dfs-namespaces/create-a-dfs-namespace

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

Answer 3

Just checking if there's any progress or updates?

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

Answer 4

Thank you all for the suggestions and I think they are all acceptable. In the end I did a manual copy to a different location on the DC's.