Figure 1. Uninstalling an update to determine whether it is the source of a problem. Follow the prompts that appear and restart the computer if required. You can also remove an update using the Wusa.exe tool. If removing the update does not resolve the problem, you should reapply the update. If removing the update does solve the problem, inform the application developer (in the case of a program incompatibility) or your Microsoft support representative of the incompatibility. The update probably fixes a different problem, so you should make every effort to fix the compatibility problem and install the update. Log on to a computer running Windows 7 as an administrator.
Click Start and then click Control Panel. Under Programs, click Uninstall A Program. On the Programs And Features page, click View Installed Updates. Right-click one of the updates and then click Uninstall. Click Yes when prompted.
Jan 8, 2018 - Remove All Windows Xp Updates From Wsus Console. How to identify and decline superseded updates in WSUS How to identify and decline.
If prompted, restart the computer. Uninstalling this update allows you to reinstall it later using WSUS. Click System And Security and then click Windows Update. Click Check For Updates. At least one update should be available.
Click View Available Updates. Because the computer running Windows 7 has the default setting, Windows Update is contacting Microsoft directly to find the latest updates. Exercise 2 Configure WSUS In this exercise, you install WSUS on a server, approve updates, and then configure a client running Windows 7 to retrieve updates from that server. Log on to a computer running Windows Server 2008 R2 as an administrator. Click Start, click Administrative Tools, and then click Server Manager.
Click the Roles node, and then click Add Roles in the Details pane. The Add Roles Wizard appears. On the Before You Begin page, click Next.
On the Select Server Roles page, select the Windows Server Update Services role. When prompted, add any required role services. Click Next four times, and then click Install. When the Windows Server Update Services Setup Wizard appears (it might be behind the Add Roles Wizard), click Next.
Note WSUS VERSION When you add the WSUS server role, Windows Server 2008 R2 downloads the latest version directly from Microsoft. As of the time of this writing, the current version of WSUS is WSUS version 3.0 with Service Pack 2. If Microsoft has updated WSUS to a newer version, the steps required to install WSUS will vary. You probably can accept the default settings, but you should choose not to store updates locally. On the License Agreement page, read the license agreement. Then, click I Accept The Terms Of The License Agreement, and click Next. On the Required Components To Use Administration UI page, click Next.
On the Select Update Source page, clear the Store Updates Locally check box to prevent the WSUS server from copying updates locally. In a production environment, you would leave this check box selected so that clients could download updates from your WSUS (across your local area network) instead of directly from Microsoft (using your Internet connection). On the Database Options page, click Next. If the Connecting To SQL Server Instance page appears, click Next. On the Web Site Selection page, click Next to use the default IIS Web site. In a production environment, you would create a new WSUS Web site if the WSUS server hosted other Web sites. On the Ready To Install page, click Next.
On the Completing The WSUS Setup Wizard page, click Finish. On the Installation Results page, click Close.
Restart your computer if prompted. Next, you configure WSUS to install updates only after you approve them. To do so, perform these steps.
The Windows Server Update Services Configuration Wizard might have opened automatically. If it did not, click Start, click Administrative Tools, and then click Windows Server Update Services. On the Before You Begin page, click Next. On the Join The Microsoft Update Improvement Program page, click Next. On the Choose Upstream Server page, click Next.
On the Specify Proxy Server page, click Next. On the Connect To Upstream Server page, click Start Connecting. Wait while the WSUS Configuration Wizard downloads information from Microsoft Update.
When the Next button is available, click it. On the Choose Products page, notice that only Office and Windows updates are downloaded by default.
Browse through the other update types that are available so that you become familiar with them, and then accept these default settings by clicking Next. On the Choose Classifications page, select the All Classifications check box. On the Set Sync Schedule page, click Next.
On the Finish page, click Next. On the What's Next page, make note of other WSUS configuration steps. Click Finish. Note WSUS configuration in the real world Because this exam focuses on the client running Windows 7 and not the WSUS server, this exercise does not go through all these configuration steps. However, in a production environment, WSUS would require additional configuration. Next, you need to configure AD DS Group Policy settings so that domain members synchronize with the WSUS server. On the computer running Windows Server 2008 R2, click Start, click Administrative Tools, and then click Group Policy Management.
In the Group Policy Management console, select the Group Policy Management Forest Domains nwtraders.msft Default Domain Policy node. Right-click Default Domain Policy, and then click Edit. In the Group Policy Management Editor, select the Computer Configuration Policies Administrative Templates Windows Components Windows Update node.
Double-click the Specify Intranet Microsoft Update Service Location setting. Click Enabled. In the Set The Intranet Update Service For Detecting updates box, type and the name of your computer running Windows Server 2008 R2 (such as This configures clients to which the Group Policy Object (GPO) is applied to contact the WSUS server instead of Microsoft Update. In the Group Policy Management Editor, double-click the Configure Automatic Updates policy.
Click Enabled. In the Configure Automatic Updating list, examine the different possible settings. Select 3 – Auto Download And Notify For Install. Accept the default settings by clicking OK. Double-click the Turn On Recommended Updates Via Automatic Updates policy. Click Enabled.
This enables Windows Update to install both recommended updates, which include driver updates and new Windows features, and important updates. Open the Windows Server Update Services console from the Administrative Tools folder on the Start menu. In the Update Services console, if your server does not appear in the Update Services list, click the Connect To Server link in the Actions pane, type the server name, and then click Connect. Select the Update Services Computers Synchronizations node. If a synchronization is currently running, select it. Wait until the synchronization completes. Select the Update Services Updates All Updates node.
In the Approval, select Unapproved. In the Status list, select Failed Or Needed. Then, click Refresh, and wait several minutes for the Update Services console to display the list of unapproved updates.
Right-click any updates that appear, and then click Approve. To select all updates, press Ctrl+A. If no updates appear, verify that your computer running Windows 7 appears when you select the Computers All Computers node. If you still see no updates, verify that the WSUS server has downloaded available updates from Microsoft. If updates have been synchronized, you might need to wait until Windows Update on the client notifies the WSUS server of its current status. In the Approve Updates dialog box, select the All Computers list and then click Approved For Install, as shown in Figure 2.
Then, click OK. Log on to your computer running Windows 7. Wait a few minutes for Windows 7 to display a notification bubble informing the user of the presence of updates. Click the bubble. In the Windows Update window, click Install Updates.
![Wsus Wsus](/uploads/1/2/5/3/125363974/224311568.jpg)
Follow the prompts that appear to complete the update installation, and restart the computer if required. Exercise 4 Remove an Update In this exercise, you remove an update from your client computer running Windows 7.
In the real world, you might do this if an update caused application compatibility problems.
68 Shares I recently added Windows 10 to my WSUS Product and Classifications and got very surprised by the 100 GB of updates that was queued for download! Let’s learn how to clean up WSUS content folder.
Unfortunately, cancelling the download queued is not that straight forward, so I decided to use the opportunity to clean up my WSUS content folder and reclaim my VMFS datastore at the same time. The reason why the updates where 100 GB was because I had all Classifications selected and an Automatic Approval Rule!
After the changes below the updates where only 1 GB. Lesson Learned, Be Careful with Automatic Approval Rules Clean Up WSUS Before you start make sure to disable your Automatic Approval Rule(s). I have a very nice script below that saved me 300% of downloads. It’s also a good time to verify that only the Products and Languages you actually need are selected. From Update Files and Languages, make sure that you don’t have Express installation files selected. Let’s clean up WSUS by running the following commands. # EOF Open PowerShell ISE as Administrator and run the script.
Do you belive that? Out of 6467 updates, 4179 where declined.
Now run the Automatic Approval Rule to start the downloads. Many people might argue that is unnecessary to run the wsusutil.exe reset command, simply because all updates will be re-downloaded. Well, you could always search and decline all updates you don’t want and then run the Server Cleanup Wizard, but its PITA.
My WSUS folder went from 75 GB to 20 GB so I’m happy. Reclaim VMFS Datastore I’m not sure if you’re aware, but when you’re using Thin Provisioning it doesn’t matter if you delete unwanted files. When the space has been alllocated it will stay that way until you do the following steps below. My WSUS folder was located on C: then moved to D: and finally E: To reclaim the space after all unnecessary files has been deleted run on all volumes.
Still getting error Error Occurred Exception Message: The specified string is invalid. Parameter name: ServerName at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object args) at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber) at GetUpdateServer(Object, Object ) at System.Management.Automation.MethodInformation.Invoke(Object target, Object arguments) at System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object target, Object arguments, MethodInformation methodInformation, Object originalArguments). I have not checked above solution, However Following command help me clean the WSUS server.
Run all the command one by one – if you get any error like ” Invoke-WsusServerCleanup: Execution Timeout Expired. Re-run the command till it give you result. I cleaned up around 250 GB Invoke-WsusServerCleanup -CleanupUnneededContentFiles Invoke-WsusServerCleanup -DeclineExpiredUpdates Invoke-WsusServerCleanup -CleanupObsoleteComputers Invoke-WsusServerCleanup -CleanupObsoleteUpdates Invoke-WsusServerCleanup -CleanupUnneededContentFiles Invoke-WsusServerCleanup -CompressUpdates. Hi, the PS script is not working for me: Error Occurred Exception Message: Invalid URI: The hostname could not be parsed. PS C: Windows system32 $updateServer = Microsoft.UpdateServices.Administration.AdminProxy::getUpdateServer($updateSer ver1,$useSecureConnection,$portNumber) Exception calling “GetUpdateServer” with “3” argument(s): “The specified string is invalid. I have an issue with my WSUS server and I would love your advice. In an effort to clean up the server I selected the option under “Update Files and Languages” to “Do not store updates files locally; computers install from Microsoft Update”.
Since the status has been “Cannot save configuration because the server is still processing a previous configuration change”. My plan was to set that option, run the cleanup wizard to purge the updates and then set it back to storing updates locally.
It’s been over 24hrs and the status is the same. From what I’ve read there’s not a lot of ways to stop this. Hi Trond, I don’t mean to spam your blog post, but can I offer an alternative, and a much better, more user friendly way of cleaning out WSUS for your readers.
It does way more than what you’re post says, and it’s so easy to setup and use. Have a peek at my Adamj Clean-WSUS script.
It is the last WSUS Script you will ever need! What it does: 1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster.
Remove all Drivers from the WSUS Database (Default; Optional). Shrink your WSUSContent folder’s size by declining multiple types of updates including by default any superseded updates, preview updates, expired updates, Itanium updates, and beta updates. Optional extras: Language Packs, IE7, IE8, IE9, IE10, Embedded, NonEnglishUpdates, ComputerUpdates32bit, WinXP. Remove declined updates from the WSUS Database.
Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs). Compress Update Revisions. Remove Obsolete Updates.
Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days). Application Pool Memory Configuration to display the current private memory limit and easily set it to any configurable amount including 0 for unlimited. This is a manual execution only. Checks to see if you have a dirty database, and if you do, fixes it. This is primarily for Server 2012 WSUS, and is a manual execution only. Run the Recommended SQL database Maintenance script on the actual SQL database.
Run the Server Cleanup Wizard. It will email the report out to you or save it to a file, or both. Although the script is lengthy, it has been made to be super easy to setup and use so don’t over think it. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment (email settings only if you are accepting all the defaults), simply run:. Clean-WSUS.ps1 -FirstRun If you wish to view or increase the Application Pool Memory Configuration, or run the Dirty Database Check, you must run it with the required switch. See Get-Help.
Clean-WSUS.ps1 -Examples If you’re having trouble, there’s also a -HelpMe option that will create a log so you can send it to me for support. I ran the script in PS in admin mode. This is where it errors out. Any help would be great. PS C: Users Kamran.Manii $updateServer = Microsoft.UpdateServices.Administration.AdminProxy::getUpdateServer($updateS erver1,$useSecureConnection,$portNumber) Exception calling “GetUpdateServer” with “3” argument(s): “The specified string is invalid. Hi people, i found out if i have a wsus server that i named it as Up-Stream-WSUS, you have to remove line no 3,4 and 5 and replace $FQDN with “Up-Stream-WSUS”. Then open PS with admin rights and run the script.
It will perform flawlessly. I am a lazy person who do not want to reset and sync the database again.
So after running the script i performed the command below as suggested by nitin Invoke-WsusServerCleanup -CleanupUnneededContentFiles Invoke-WsusServerCleanup -DeclineExpiredUpdates Invoke-WsusServerCleanup -CleanupObsoleteComputers Invoke-WsusServerCleanup -CleanupObsoleteUpdates Invoke-WsusServerCleanup -CleanupUnneededContentFiles Invoke-WsusServerCleanup -CompressUpdates It shaved quite 50GB of disk spaces. Before it was 60GB of disk space Cheers to Trond Eirik Haavarstein. Without your script, my wsus would have exploded due to windows defender definition updates. Windows Definition updates is exploding my WSUS.
Greetings Trond.