Share on linkedin. Share on reddit. Share on email. You may also like Log4j and Lansweeper December 17, Asset IP History December 3, Try Lansweeper for Free. Learn why Lansweeper is used by thousands of enterprises worldwide.
Download Lansweeper. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No.
Any additional feedback? Submit and view feedback for This product This page. View all page feedback. If you use this option, you don't need to use the script described later in this section either by manually running it or by setting up as task to run it on a schedule. Or you can run this PowerShell script. This script is provided as is. It should be fully tested in a lab before you use it in production. Microsoft makes no guarantees regarding the use of this script in any way.
Always run the script with the -SkipDecline parameter first, to get a summary of how many superseded updates will be declined. If Configuration Manager is set to Immediately expire superseded updates see below , the PowerShell script can be used to decline all superseded updates. If updates are not configured to be immediately expired in Configuration Manager, the PowerShell script must be run with an exclusion period that matches the Configuration Manager setting for number of days to expire superseded updates.
In this case, it would be 60 days since SUP component properties are configured to wait two months before expiring superseded updates:. Running the script with a -SkipDecline and -ExclusionPeriod 60 to gather information about updates on the WSUS server, and how many updates could be declined:. Running the script with -ExclusionPeriod 60 , to decline superseded updates older than 60 days:.
The output and progress indicators are displayed while the script is running. Note the SupersededUpdates. If issues occur when attempting to use the above PowerShell script to decline superseded updates, see the section Running the Decline-SupersededUpdatesWithExclusionPeriod. In a Configuration Manager environment, Computers not contacting the server and Unneeded update files options are not relevant because Configuration Manager manages software update content and devices, unless either the Create all WSUS reporting events or Create only WSUS status reporting events options are selected under Software Update Sync Settings.
If you have one of these options configured, you should consider automating the WSUS Server Cleanup to perform cleanup of these two options. If you are using Configuration Manager current branch version or a later version, enabling the Decline expired updates in WSUS according to supersedence rules option handles declining of Expired updates and Superseded updates based on the supersedence rules that are specified in Configuration Manager.
Enabling the Remove obsolete updates from the WSUS database option in Configuration Manager current branch version handles the cleanup of Unused updates and update revisions Obsolete updates. It's recommended to enable these options in the software update point configuration on the top-level site to allow Configuration Manager to clean up the WSUS database.
If you've never cleaned up obsolete updates from WSUS database before, this task may time out. You can review WsyncMgr. My WSUS has been running for years without ever having maintenance done and the cleanup wizard keeps timing out once, which would allow subsequent attempts from Configuration Manager to run successfully.
In that case, reindex with step 2 and step 3 first, then run the cleanup with only the Unused updates and update revisions option checked. If you have never run WSUS Cleanup wizard, running the cleanup with Unused updates and update revisions may require a few passes. If it times out, run it again until it completes, and then run each of the other options one at a time. Lastly make a full pass with all options checked.
My WSUS has been running for years without ever having maintenance done and the cleanup wizard keeps timing out. It is located under Options , as shown here:. For more information, see Use the Server Cleanup Wizard. After it reports the number of items it has removed, the cleanup finishes. If you do not see this information returned on your WSUS server, it is safe to assume that the cleanup timed out.
In that case, you will need to start it again or use the SQL alternative. Reinstall WSUS with a fresh database. There are a number of caveats related to this, including length of initial sync, and full client scans against SUSDB, versus differential scans. After it finishes, follow all of the above instructions for running maintenance. This last step is necessary because the spDeleteUpdate stored procedure only removes unused updates and update revisions.
Before you run the script, follow the steps in The spDeleteUpdate stored procedure runs slowly to improve the performance of the execution of spDeleteUpdate. Make a note of this setting. Run the following query. If this is set to expire immediately, the value in the SQL query for thresholdDays should be set to zero. In case if there is a proxy server in your organization, you should type the credentials for proxy server while configuring WSUS. Synchronize from Microsoft Update — After Selecting this option will download the updates from Microsoft update.
Select the languages for which you want updates and then click next. From the list of products, we can select individual products or product families for which we want our server to synchronize updates.
In my case, I will select Windows Server and Windows 10 Click Next. Select whether to perform synchronization manually or automatically. What we need to do is approve the update by right-clicking the update and then select Approve.
All Computers: this group registers computer accounts when they contact to the WSUS server and this group you should not populate manually Unassigned computers: this group is not assigned to other groups by the WSUS Administrator.
0コメント