I make use of deduplication feature on Windows Server 2012, and Windows Server 2016 quite extensively. And, it does wonders. Its deduplication ranges from 10% (wsus content, backup server) to upwards of 55% ( File Share servers and SCCM Distribution Points with ISOs and .wim images, as well as packages and applications).
Recently, a case was brought to my attention where a drive with wsusContent on freshly installed Windows 2016 server has started running out of space. Initial drive size was about 100GB, and after fe Continue reading →
Ah yes, you have had enough of it. Wsus content folder keeps growing in size day by day. You have tried feeding it 20 GB, then another 50, then 100 GB. No, it won’t stop growing and keeps demanding more and more space.
No worries, there is a solution for that… Maybe… in any case as gecko says ” 15 minutes could save you 15% or more on” of your valuable disk space on your (v)SAN storage
Solution 1) Have workstation download updates from MS directly
Downside; traffic, bandwidth, time, multiple unknown variables on how long, amount of bandwidth, cost of bandwidth
Set your workstations to report statistics and detect updates to your internal SUS Server:
Choose an option to “Do not store update files locally; computers install from Microsoft Update”
Solution 2) Download to sus server, only what you need
Don’t download the “Express installation files”; downsideis it will take longer for workstations to get the necessary updates
Check mark “Download update files to this server only when updates are approved”
Plan is to retain current WSUS data and configuration while moving the SUS service from old Windows 2016 TP 5 server to an new fully licensed Windows 2016 Standard server, and move database from WID to a standalone SQL 2014 server.
1) Setup a new Windows 2016 Server, update. Patch, reboot. Install the WSUS role on it, choose the WID database during the install. Make sure to point to a drive\folder for wsusContent.
a. Copy the wsusContent folder from old server to the new one. Make sure you placing it to the proper drive\path, you identified during post-install configuration for new WSUS service. Continue reading →