SCCM Update Package does not match files on WSUS

[Newbee]

It appears that when we delete expired or superceded updates from an ongoing list and the ongoing update package it appears we have not always had the files removed from the corresponding WSUS folders. Thus we showing way more folders in the WSUS update folder than we have in the Update Package in SCCM. Is there anyway to identify easliy the folders that can be removed from the WSUS server leaving only the matching Updates that are applied in the SCCM Ongoing updates Package?

 

Or creating a new list and package be the only way?

[Peter van der Woude]

You can create Search Folders, so you only see the updates that you want.

[Newbee]

You can create Search Folders, so you only see the updates that you want.

 

The search folders are working and we use them. The problem appears that when an old update was removed from an Ongoing Update Package it was not told to remove it from the WSUS and DP's. Leaving the old folders in the package in place and adding folders as new updates are added to the package. I am trying to find a way to identify in WSUS the old folders so they can be removed and save space and not also refreshing on all the DP's. Once i can remove these a refresh to the DP's should remove them from there also.

[Peter van der Woude]

I assume that with WSUS you mean SUP from ConfigMgr. SUP will just show all the updates that there are for the categories that you selected. That's why you should make search folders that filter at least on expired and superceded. You probebly already have that part.

When you delete some expired and superceded updates from your update package, you always have to update the DP after that.

[Newbee]

True

 

But in our case the when the updates were deleted that were expired or superceded, it appears the option to remove from DP's was not selected. This left the updates on the WSUS and the DP's. I am trying to identify those folders of updates on the WSUS to remove them and then refresh the DP's.

 

In short if we have say 200 updates in our ongoing update package but have twice that many folders on the WSUS containing that corresponding packages updates. They should be 1 for 1.

[Peter van der Woude]

True

 

But in our case the when the updates were deleted that were expired or superceded, it appears the option to remove from DP's was not selected. This left the updates on the WSUS and the DP's. I am trying to identify those folders of updates on the WSUS to remove them and then refresh the DP's.

 

In short if we have say 200 updates in our ongoing update package but have twice that many folders on the WSUS containing that corresponding packages updates. They should be 1 for 1.

 

Why do you have the updates in WSUS??? Because ConfigMgr SUP only uses the metadata of WSUS...

 

Besides that you can always at anytime update your Deployment Packages

[Newbee]

Why do you have the updates in WSUS??? Because ConfigMgr SUP only uses the metadata of WSUS...

 

Besides that you can always at anytime update your Deployment Packages

 

I need to review thier setup here, but the WSUS is seperate from the SCCM server. They do all of the configuration and updating using the SCCM. But it appears to me that the WSUS downloads the updates when instructed and the DP's get the package from the WSUS. The SCCM package name is a folder containing the updates for the package residing on WSUS after you initiate a download of updates.

 

When you remove updates from a package it gives you the option to delete from the DP's. If you select this option it removes from all DP's and the WSUS package folder. My guess is this option has not always been selected thus updates are left behind and continue to reside and sync with the DP.s.

[inf]

I think I have similar problem. Deleting expired and superseded updates from deployment package does not delete them from package source, which is in the SCCM server local hard disk. Do I have to delete and create whole package again?

[inf]

Is it safe to run server cleanup wizard from wsus options? There is no such tool in SCCM.