Gibson99
My feedback
-
550 votes
Hi. I’m setting the status back to Noted – this was mixed up with the item “Add support for TFTP Window Size” – that has been Started and is available in the 1603 tech preview build.
Thanks,
BobMN on behalf of SangeeV for SCCM OS Deployment -
332 votes
bobmn for sangeev/OSD
Gibson99
commented
This would be really useful in my environment because not all TSes are for OSD. For example, one of my TS is for updating the BIOS, but I only want our techs to be able to run it, not regular users. Right now I have a somewhat hokey password prompt in place to keep regular users out, but I have other TS that I'd like to restrict just to certain users/groups.
Gibson99
supported this idea
·
-
41 votes
Updating status to Noted. See https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
Gibson99
commented
also useful for things like BIOS updates (so the TS can control the reboot). Everything else can be deployed to either a user or device collection, so why not a TS? not all TSes are for OSD.
Gibson99
supported this idea
·
-
186 votes
Updating status to Started.
Our 1901 Technical Preview now shows the name of the task sequence step that failed
Doc: https://docs.microsoft.com/sccm/core/get-started/2019/technical-preview-1901
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/A-New-Perspective-on-Client-Health-in-ConfigMgr-Technical/ba-p/324621Gibson99
commented
THIS!!! A THOUSAND TIMES THIS!!! 3 votes is not enough for this. I can't tell you how many times my techs email/call me and say "it failed" and if they actually give me an error code, it's usually 80004005 which is about as useful as ye olde 1603 from msiexec - completely worthless. it doesn't matter how many times i tell the techs to move the error message or hit alt-tab and tell me WHICH step it failed on, and extending the auto-reboot time didn't help either (except for my own testing). having the error message NOT be system modal or having it moved up/down so that it doesn't cover up the progressUI window would be ideal if you can't just include the actual task sequence step name in the error dialog box itself.
Gibson99
supported this idea
·
-
188 votes
Thanks for the feedback.
Updated by bobmn for sangeev/OSD
Gibson99
supported this idea
·
Any updates on this? With newer machines that don't have an ethernet jack (MS Surface series, Latitude 7370, plenty of others), PXE boot is painfully slow - ranging from 30 minutes to several HOURS (if it doesn't just fail outright). Would be great to have a cure for that, not to mention speeding up the 3-5 minute PXE boot times of other machines.