NEWSCCM 2303 - SUG - Deployment issues

[Charlieferreira]

Hello, everyone.

I'm having an issue with SCCM 2303, specifically regarding the SUG, which I'll explain.



I have an ADR to get all Edge security updates that runs once a week.


It is configured to create a SUG with each execution.


It has the deployment package.


The problem occurs in the SUG, where when a new SUG is created, the previous one shows the information "Deployed" = "No" and "Downloaded" = "No," and all KBs disappear.




The support team indicates that this is the expected behavior and that it did not happen in the past.
Can you help me understand if this is the expected behavior, and if so, in which logs can I find evidence to support this conclusion?

Thank you.

[Garth]

If there are no KB within the SUG then they can't be downloaded nor can they be deployed. Keep in ming that old SU will get removed once they expirer (default setting)

[Charlieferreira]

If there are no KB within the SUG then they can't be downloaded nor can they be deployed. Keep in ming that old SU will get removed once they expirer (default setting)

Thank you for the quick response.

So, the behavior I'm describing is completely normal, that is, if the KBs from SUG are installed on all computers, it displays that information, and the KBs disappear because they are expired, right?

In this case, if they are not installed on all computers, that is 100% compliant, so the old one is supposed to still be in use, right?

[Garth]

Thank you for the quick response.

So, the behavior I'm describing is completely normal, that is, if the KBs from SUG are installed on all computers, it displays that information, and the KBs disappear because they are expired, right?

In this case, if they are not installed on all computers, that is 100% compliant, so the old one is supposed to still be in use, right?

if SU is expired it mean that the KB doesn't apply anymore or is "bad" or supersede. In either case you should not be applying it.