Ian Burnell
My feedback
-
53 votesIan Burnell
supported this idea
·
-
36 votesIan Burnell
shared this idea
·
-
1,836 votes
Today we published a new article and related flowchart to provide some insight and guidance for using the Install Software Updates task sequence step.
Announcement
https://twitter.com/AaronCzechowski/status/1102647530339221504Link to document:
https://docs.microsoft.com/en-us/sccm/osd/understand/install-software-updatesFlowchart at full size
https://docs.microsoft.com/en-us/sccm/osd/understand/media/ts-step-install-software-updates.svgIan Burnell
commented
Agree. Generally it works fine during build but my beef is the TIME it takes to run - can add up to 20-30 minutes to the Task Sequence. Its hard enough selling SCCM to management without having to explain it takes some 90 minutes to build a machine. You need to have an install updates offline like MDT than can run in tandem with the build process. I also don't understand why it needs to install the SCCM client when it is build into the captured WIM - at the very least it should only need to be activated rather than a complete install of client which adds another 5 minutes to the build
I logged a forum thread on this
https://social.technet.microsoft.com/Forums/en-US/a925dd95-3646-4d33-81ee-fb8280f0a037/usb-port-protection?forum=ConfigMgrCBGeneral#5ccd5ba2-91d4-4364-a36b-2586306ae562
It may be possible via Group Policy but would surely be much easier to control USB access through the EndPoint Policies built into SCCM which could then be deployed to specific collections to allow or deny access as required