Hello all,

 am using a Software Update Group that encompasses the entire year's updates. 
What is the best timing for managing this group? It seems like when we move 
expired/superseded updates out that SCCM is reapplying the update group again 
later and that there is a possibility that machines will reboot when we don't 
expect that to happen. If we have our software update group applied to all 
machines and then remove some expired/superseeded updates, will it try to 
reapply the software update group to all machines - at the same time?

Also, when I review the compliance reports and see that not all machines in the 
group are in compliance, how do I determine which updates are causing the 
machines to not be in compliance?

Thanks,

Brian
                                          


Reply via email to