Thanks for the feedback. We’re looking at moving the functionality of the Check Readiness step to the task sequence properties and this is one of the additions were considering. Please note this is not scheduled work yet.
Updated by bobmn for sangeev/OSD
Network would be good too.
1,865 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Admin, System Center Configuration Manager) responded
Updating to started since this just shipped in the 1902 technical preview.
Something to consider... 100% of our end-user fleet is Surface Pro and with everyone working different hours and having different requirements, we effectively never have a maintenance window that these devices are on in. We set updates to install outside the maintenance window, but suppress reboots. It's up to the user to restart, and because the current notification functionality is sub-optimal, they never see the one prompt that disappears within a few seconds. We end up emailing people asking them to restart. We don't force OS upgrade task sequences for the same reason - these are just available not required, because we can't control the prompts and reboot process enough.
Yes, this needs to be way more visible than the balloon hidden in the tray. How about a reminder that pops up every x hours until they have done a reboot (configurable by admin).
The root cause of this in our environment is that the users just shut down their surface pro and start it again and think that's a reboot... The Surface fast startup feature means hat this isn't a reboot as far as update installation is concerned. Perhaps that can be fixed and then the other problem won't be so severe.
Updating status to Started.
Our 1901 Technical Preview now shows the name of the task sequence step that failed
This can be done today w/ #SCCM 1802 (and previous versions too). I will mark started… and watch comments for why this doesn’t just work… before I mark this straight up completed…
1) On the CAS (or standalone primary), go to Administration → Hierarchy Configuration → Discovery methods
2) right click on Active Directory System Discovery and bring up the Properties form. Active Directory Attributes tab, and then click on Custom. In the form that appears, type the name of the attribute. Click OK, and make sure you have added it as an attribute to discover. Run discovery after exiting properties form.
3) Now when you go to the Devices view and right click on a device and go to its Properties form, you will see the new attribute showing up there.
We use this to keep track of our build versions and, yes, we can build queries and collections on it. But we need a column. Not just a column, but a filterable column.
Could you do this with a single Apply Drivers task sequence step and set it to run hidden?
This is in 1806 TP
Perhaps also do a cleanup of the content share and the distribution points after the updates are expired in case there are orphaned distribution packages
Updating status to Noted, thanks for the feedback
... until Microsoft re-release the update and the new version shows up in the root level again. Doh!
Thanks Ryan. This works, and fully satisfies my requirement. You're a legend!