Moving the WSUS Content Folder

nocluejoe used Ask the Experts™
Hello Support,

We have a server that has Windows Server 2012 and it has WSUS 3.0 SP2 on it. We are having an issue with the server's storage getting full so fast. Is there a way for us to move JUST the WSUS content that contains all of the updates to a different server and keep the WSUS 3.0 SP2 database on the original server so that we will have enough space for all of the updates. Does the WSUScontent folder have to stay on the local server with the database on it?
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2017

Wsusutils includes an option to move the content
C:\program files\update services\tools\wsusutils.exe /?

Depending on your classifications, the folder can Verne large.... Or you are moving it from c:\


We want to move the WSUScontent folder from C:\ on the original server to a different server that is a domain controller such as \\servername\WSUScontent. We want to keep the database on the original and put the storage onto a DC server. Will the move content command be able to complete this task for us or does the WSUS content folder have to be still on the local server but onto a different drive?
Distinguished Expert 2017
that is not possible to have the WSUS be on serverA and its content be on server B  Yes the content must be on the same server as the data as that is where the service retrieving the data is.
If you can make the drive where the content will be stored local, i.e. server B via ISCSI allocates space from its storage to Server A that mounts it as drive D. The content on this server can be moved from C: to D: but it will not change which server will be accessed to get the data, Server A. IIS port 8530 or default port depending on your configuration/setup.

ADd wsus role on the new server, make sure to configure its content location where you want it. Configure this WSUS server as a replica of your existing one. IT will copy all the data from existing including approvals, etc. (The approvals can only be done on the primary,master WSUS server)
Once the data is transferred, the only thing you will have to do manually, is to configure the auto approvals if any exist on your original server since these do not transfer.
Depending on how you target clients, GPO + DNS record, adjust the DNS to point to the new servers IP. IF GPO only, you should consider using GPO to point to a generic DNS record which can be altered/adjusted to point to a single Host or to multiple IPS that have WSUS setup.

once the clients transition to the new wsus Server and the auto-approvals have been done, you can change it from being a subordinated replica to be a primary, make sure to update/adjust the product classiffication to match the existing.....
Now you can subordinate the original to the new in the event some systems still report to it, GPO targeting not refreshed......

Why would you want to put the WSUS on a DC? The targetting is by GPO and WSUS can be on any server in the environment.

used the above over the years to transition between three or four servers. usually have two (one is subordinated) for redundancy.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial