I noticed that some packages were larger than the WSUS limit of 384mb. This is obviously a problem, as WSUS wouldn't be able to package and push this out. In order to get around this, I've had to tell WSUS that the package size can be larger than that.
The following Power Shell commands will get this job done:
- Import-Module UpdateServices
- [reflection.assembly]::LoadWithPartialName
- ("Microsoft.UpdateServices.Administration") | out-null
- $wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer();
- $serverconfig = $wsus.getConfiguration()
- $serverconfig.LocalPublishingMaxCabSize = 1024
- $serverconfig.Save($FALSE)
In these commands, the 1024 is the newly updated maximum package size.
Note: WSUS cannot go larger than 2048mb, so don't set the size to above that.

Super handy tip! Ran into the same WSUS limit during a project—this fix would've saved me hours. Feels like half my troubleshooting was stuff like this while I was getting some thesis writing services uk.
ReplyDeleteThis is a brilliant and concise guide on fixing the 384MB WSUS limit using PowerShell; I'll definitely be adding this to my server management knowledge base. Speaking of finding expert solutions to complex challenges, if anyone needs help navigating Australian visas, Edvise Hub melbourne is highly recommended.
ReplyDelete