Mike Terrill
My feedback
-
19 votes
An error occurred while saving the comment -
47 votesMike Terrill
supported this idea
·
-
65 votesMike Terrill
shared this idea
·
-
67 votesMike Terrill
supported this idea
·
-
94 votesMike Terrill
supported this idea
·
-
40 votesMike Terrill
shared this idea
·
-
415 votesstarted ·
AdminBob Mac Neill
(Software Engineer, Microsoft Endpoint Configuration Manager)
responded
Hi,
Our 2010 Technical Preview is now released and contains a many improvements for the task sequence as deployment type.
Doc: https://docs.microsoft.com/mem/configmgr/core/get-started/2020/technical-preview-2010
Blog: https://techcommunity.microsoft.com/t5/configuration-manager-blog/view-syntax-highlighting-for-scripts-and-queries-in/ba-p/1740062Mike Terrill
supported this idea
·
-
162 votesMike Terrill
shared this idea
·
-
51 votes
Thanks for the feedback and suggestion. Updating status to Noted
https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
Mike Terrill
shared this idea
·
-
201 votes
Refreshing status and adding link to https://docs.microsoft.com/en-us/mem/configmgr/core/understand/find-help#send-a-suggestion to explain what status values mean.
Mike Terrill
supported this idea
·
-
126 votesMike Terrill
supported this idea
·
The trigger for the reboot (or at least make it an option) should be based on the install completion time (and not the required deadline time). For example, we are working on a method to upgrade Office 2016 to Office 365. Office 365 strongly recommends restarting after an upgrade from Office 2016. We plan on giving users 4 weeks to opt-in at their convenience. Someone opt-ing in early wouldn’t be required to reboot for 4 weeks based on how it works today.