David W
My feedback
-
11 votes
David W supported this idea ·
-
118 votesstarted ·
AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Changing status back to “Started” as there’s more work to do here. We plan to simplify adding requirements to DTs as well as complete the missing scenarios for detection methods in a future release. Stay tuned for more updates.
David W supported this idea ·
-
3 votes
David W shared this idea ·
-
1,829 votes
I’m updating the status. For 1606 we’ve made some changes, listed below.
As more are added we’ll update what Tech Preview/Release they appear in.Timeout scan is now configurable
We added a new task sequence variable to allow a configurable timeout for scan. Variable name is SMSTSSoftwareUpdateScanTimeout, default is 30 minutes. Value is set in seconds so an hour is 60×60=3600Logging changes
In the SMSTS.log we list the log files to check for updates download and evaluation.
These are UpdateDeployment.log, UpdatesHandler.log, WUAHandler.log and WindowsUpdate.logNew Option for full scan
There’s a new checkbox added to the Install Updates step – ‘Evaluate software updates from cached scan results’
If the checkbox is on we use cached results, if the checkbox is off we do a full scan
Task Sequences that are upgraded will have this option checked on – this is parity with the existing behaviorPower management changes…
How about the ability to deploy directly from a selected list of Update Groups instead of having to have an active software update deployment?