Updated by bobmn for sangeev/OSD
Updating status to started – see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each value.
Our 1905 Technical Preview is now released.
This release has the first round of changes in the App model to allow a Task sequence as a deployment type allowing task sequences to be deployed to users/user groups.
Updating this item as there’s support for Windows 10 In-place upgrade using the Cloud Management Gateway – see https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1802
Adding this in case some folks missed it or Win 10 In-place upgrade addresses their requirement.
I recognize this it not full OS Deployment as there’s no WinPE phase (WinPE has no wireless stack)
Updated by bobmn for sangeev/OSDGhostMonkey commented
Agreed. The current implementation of Applications in a Task Sequence has missed the whole purpose of having multiple deployment types in an Application. With the current configuration, if there is a single deployment type set to run when a user is logged on, the entire application is not available to assigned to a Task Sequence. This is backwards. If there is any deployment type that can run in a Task Sequence, then that application should be available. Only when *all* deployment types are not compatible with running in a Task Sequence should the application get removed.
The above suggestion would also allow us to be even more granular in controlling the execution of our task sequences, by
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.
BobMN on behalf of SangeeV for SCCM OS Deployment