Will
My feedback
-
1 voteWill
shared this idea
·
-
772 votesWill
supported this idea
·
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Will
commented
This exists, you have to add the column.
-
0 votes
An error occurred while saving the comment Will
commented
This is a great idea, but wording is not clear.
-
1 vote
An error occurred while saving the comment Will
commented
I have an opened bug with premier support on this. o365 updates behave in the same way.
-
3 votes
An error occurred while saving the comment Will
commented
Also a different timer to force the reboot as the machine is only clear key encrypted when the feature update suspends bitlocker.
-
11 votes
An error occurred while saving the comment Will
commented
win10 feature updates should be independent as well , as they suspend bitlocker until the reboot is performed, leaving your PC clear key encrypted.
-
113 votesWill
supported this idea
·
-
15 votes
An error occurred while saving the comment Will
commented
This now exists in SCCM, if you don't think its working review that you are going from one release of o365 to the next. Skipping a release can result in a full download.
-
84 votes
Updated by bobmn for sangeev/OSD
An error occurred while saving the comment Will
commented
This is basic functionality that should be included.
Will
supported this idea
·
-
172 votes
An error occurred while saving the comment Will
commented
I'd like to see this as a client notification task..
-
2 votesWill
shared this idea
·
-
3 votes
Thanks for the feedback
We’ve incorporated the ask for a task sequence lock option with our planning for https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8339997-daisy-chain-task-sequences-osd-and-non-osd – the thinking being that if you have ‘gold’ task sequence you want to call from another task sequence then you want to prevent them being edited.
An error occurred while saving the comment Will
commented
You can also accomplish this same action by using scope. Only your ADM account (you have a separate account for non-full admin activities I assume) should have access to the 'prod' scope.
-
1 voteWill
shared this idea
·
-
1,156 votes
Updated by bobmn for sangeev/OSD
Will
supported this idea
·
-
41 votes
An error occurred while saving the comment Will
commented
Use CMTrace to open all the relevant log files and select the 'merge' option..
-
29 votes
Updated by bobmn for sangeev/OSD
An error occurred while saving the comment Will
commented
Create a deployment type that detects if the application is running during a task sequence (you can use provisioning mode key ) and modify the reboot exit code to be treated as normal success.
-
24 votes
Updated by bobmn for sangeev/OSD
An error occurred while saving the comment Will
commented
Task sequence install application wizard should definitely be able to determine whether any of the DT's within the app meet the requirements for a task sequence.
-
4 votesWill
shared this idea
·
If this resulted in the ability to force win10 feature updates ASAP and avoid the length of the condition where bitlocker has been suspended until a reboot occurs, Id be all in favor of this.