We don't put the SCCM client in our master templates either, but we do load it every quarter, patch, and unload it. The big benefit is we get to use the same SUPs for patching our normal images.
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, December 18, 2015 2:56 PM To: [email protected] Subject: RE: [mssms] SCCM / WSUS question don't manually approve updates, you will do bad things. a better solution is to have a separate wsus instance, and use the following approval script so the same updates are approved in the standalone wsus instance as ConfigMgr. http://www.adamtheautomator.com/sccm-wsus-update-sync/ ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of HELMS, DAVID C [[email protected]] Sent: Friday, December 18, 2015 11:18 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] SCCM / WSUS question I have some systems that are being used for VDI in which they do not want the SCCM client installed because this image is the parent for all other VDI sessions. However they do need it to be patched on a monthly basis. Is it possible to set the WSUS location in the registry and point it to the SCCM/WSUS server for manual windows updates? I know the updates aren't approved in WSUS but in SCCM. Can you approve with updates in WSUS without it affecting SCCM SUP patch distributions? Is this advisable? Appreciate any input from anyone that has tried this before or knows if this can be done. Thanks. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
