Hi, i think part of this request should be also: When user do the reboot by himself (click start - reboot), SCCM will accept it and will not require reboot after real reboot again
Hi, i think part of this request should be also: When user do the reboot by himself (clisk start - reboot), SCCM will accept it and will not require reboot after real reboot again.
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)
Technical description: PC not booting due to wrong resource ID
Computers were discovered by AD Group discovery and recod was created with resource ID starting with "209". After that action Manual machine entry was created starting with resource ID "168".
After while those two records were merged together but resource ID starting with "209" wins - that's the issue.
TS was deployed on merged object to start staging.
PC was not able to boot from PXE, because IDs that are higher than "200" are excluded when WDS is trying to enumerate available TS for OSD. Returned message to PC is, that there is no OSD assigned to Object.Ondrej Seda shared this idea ·
1,322 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Admin, System Center Configuration Manager) responded
Saw a working demo of this recently so updating to planned.