Updates injected into WSUS are assigned the "SoftwareApplciation" UpdateType and "Applications" Update classification, which both hides them from being displayed in the WSUS console and disallows them from being scheduled via ConfigMan. Assigning them the "Software" UpdateType and "Updates" classification, or giving the ability to choose, will resolve this problem.
Product | Application Manager |
These changes can't be made using method supported by Microsoft. Therefore we do not implement this functionality to AM WSUS integration
After further research, I was incorrect on which properties require changing to both be visible in the WUSU console and sync with MEMC.
In the susdb.dbo.tbUpdate table
changing the IsLocallyPublished value to 0, makes the update visible in the WSUS console
changing the UpdateType from' SoftwareApplication' to 'Software' via the UpdateTypeID allows the update to synchronize with MECM
I made these changes via SQL and have not looked/do know if these values can be set via the WSUS API.
Neither. The Powershell updates are directly from Microsoft.
AM for WSUS is using Local Publishing to feed applications to WSUS environment. It might not be possible to change the update type with this method as there is only three options to choose from and we are already using the 'Software' update type (https://learn.microsoft.com/en-us/previous-versions/windows/desktop/bb902488(v=vs.85)#updatetype)
Classification is something that can be set and is already now set to Updates as classification. What method the Powershell applications in your screenshot were added to WSUS environment? Using Local Publishing or 3rd party catalog, or something else?