The expired updates are now removed. I gues s i just had to wait one day 🙂

And another issue…my expired updates are not removed. I ran the script Adjust-WSync_UpdateCleanupAge and fill in my server name en site code. i ran the script with servername and site code. I changed the sync shedule from my sup to start syncing in 5 minutes (which happen) i checked that there are no expired updates in in SUG (which are not) i ran the script Invoke-DGASoftwareUpdateMaintenance with the -force option (because it already run this day) i used you config.ini file

What am i missing and why are the expired updates still showing up ?

a lot of question and i apologise for any inconvienance.

To makes things clear, we do support windows 11 but only enterprise

Implemented this in my test environment.
I have a lot lesser ugrades in my windows 10 servicing plan. I went from 2438 to 82 🙂
Problem nos is as follows ….76 of them are windows 11 upgrades (business edition) and windows 11 (consumer editions) in various languages. How do i get rid of them with the scripts you described

I’m planning on making an updated video for WSUS maintenance soon. TBH, I would just use the built-in feature at this point: https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/wsus-maintenance-guide

I’d like to know how I can use the config.ini file

Thanks a lot

The built-in maintenance will probably work fine now https://docs.microsoft.com/en-us/mem/configmgr/sum/deploy-use/software-updates-maintenance

Which topics in this video do you recommend still to be done?

I got it working, crazy my runas account lost is rights..

I have noticed it can take a few syncs now to purge. I think there was a code-change maybe that affected the wscynmgr thread, because I know it used to always be almost immediate.

Regarding my VB script issue – it resolved itself. The updates purged but took several hours. Still better than waiting 7 days though!

Thanks for the great guides! I have a question I’m hoping you can help with.

I ran the VB script you provided to change the wsyncmgr expired purge time from 7 days to 0 days (after putting in my server’s FQDN and site code). Next, I declined an update in WSUS, saw that it was expired in ConfigMgr, and scheduled a full SUP sync. The expired update is still showing in ConfigMgr and wsyncmgr doesn’t show any sign of this update being deleted.

Have you seen this problem before?

Can I ask where this script comes from? I cant find much documentation on it and am wondering if it’s supported with ConfigMgr 1910.

Hoping you can help as it’s a bit annoying waiting 7 days for expired updates to purge from the ConfigMgr console.

I think i may know the answer. I assume you remove the product in question from the decline script I just want to be sure . Thanks

Right-click approve then leave the computer group(s) not selected.

Thanks

Yes, I did.

Did you replace the sitecode and server in the script?

I’m trying to use Adjust-WSync_UpdateCleanupAge.vbs with SCCM 1810 (5.00.874.1033) and receiving the error:
‘Failed to open desired object with error code -2147217379 (Unexpected error). Aborting!’

The logic there is really quite simple so it shouldn’t be overly hard to troubleshoot. The script is filtering on Win 10 updates then looping through each supported language to see if it’s on the list.

Just pinged Bryan to see if he can chime in on this question.

I am only able to keep English language updates. I have the array setup as this $SupportedUpdateLanguages=@(“en”,”de”,”zh”,”jp”,”all”) . Then run the script using the whatif parameter to see what is being declined. What I’m I doing wrong?

I think once a week would probably be fine.

Quick question about the Re-index the WSUS 3.0 Database script you ran on SQL. You mentioned that you could set this up as a maintenance plan. Wondering what you recommend for how often to run that?