I have found the easiest and fastest fix is to remove and reinstall WSUS. ** Now is a great time to move the WSUS database and content repository to another drive.Below are the steps for SBS 2011*: * For the SBS 2008 the steps are the same, but WSUS 3.0 SP2 will need to be downloaded from the Microsoft site. It will be more difficult to move the WSUS DB later.
Right mouse click and click edit, and bring up the filter. SBS 2011 Essentials (and standard) need an adjustment to allow for remote desktop and also RWA into these workstations. Call it Windows 10, For the filter value click add and merely use Now build a new policy. Right mouse click and click on create a GPO in this domain and link it here. Windows 10 computers (or something equality descriptive).To add this ability a new policy and ensure it has a wmi filter so that it applies to Windows 10. Our final changes required a needed evaluation of the needs of and control of patching of Windows 10 in a network where WSUS 3.2 will not get the needed fixes in order to manage branch patching for Windows 10.While WSUS 3.2 can handle normal security releases, it will not be getting the hotfix needed to support WSUS deployment of branch updates.If you have the ability to install the WSUS role on a Server 2012 or 2012 R2 member server inside the SBS 2011 standard or SBS 2008 domain, you may wish to do so.According to the research I have done Microsoft does not limit resources or the size of the WSUS database.
However in practice I have seen that when the SUSDB exceeds 10GB issues start to crop up.More specifically I want to talk about the most common issue I see with my customers.The WSUS database grows to a very large size causing a number of symptoms.My thinking is The clients will update automatically only after I manually OK the updates, yet this morning everything has been updated Windows updates, Office updates…Is Microsoft pulling a fast one or am I missing something?To do this, though, your WSUS install will need to be patched with KB 3095113.