6 votesMurray Webber commented
Okay, I make this sound easy, and I know it's not... because I've tried to automate this myself with zero luck. But here's what I've found while trying (including suggestions):
a) It's easy to disable the default "Partitioning" steps to retain the existing disk contents.
b) We then need a template unattended answer file to continue allowing customisations. The best option here, is to have an option within the "Apply Operating System" step that disables the current two "Apply" steps for the WIMs, but otherwise retains the use of a package for the unattended answer file.
c) If the above step can be solved, we should still be able to use the "Apply Windows Settings" (osdwinsettings.exe /config), "Apply Network Settings" (osdnetsettings.exe configure), and "Apply Device Drivers" (osddriverclient.exe /auto /bestmatch:%OSDAutoApplyDriverBestMatch% /unsigned:%OSDAllowUnsignedDriver%) steps to customise the unattended XML that now resides in the "_SMSTaskSequence" folder.
d) Next, we can still mostly run the "Setup Windows and Configuration Manager" step, as we will still need to download andprepare th ConfigMgr Client instalaltion package, will still need to generate the "SetupComplete.cmd" to reinitialise the TS after reboot, and will still need to ensure that we inject the required binaries from within WinPE (i.e. OSDSetupHook.exe, TSProgressUI.exe, tres.dll), and then perform the OSD Hook setup, etc. Without the source folder for the OS "Setup.exe", some magic may need to be done, but I suspect an action that will copy the customised XML to the Panther folder should suffice.
e) Do whatever it is I'm missing from above (because I can't get this working myself), and automate the existing OOBE, then continue with the Task Sequence as normal.
This could save a lot of time for some admins, and would also be perfect for those one-off devices that we suddenly have to support. Obviously, the first step could be handled by a Provisioning Package (PPKG) instead, but those have their own limitations and issues that take time to deal with. I honestly believe the above suggestion would be a great addition to ConfigMgr's capabilities.
Try this out over CMG in #SCCM TP 1906
Updating status to started.
The first iteration/slice of this is available in the 1905 Tech Preview.
1,403 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Saw a working demo of this recently so updating to planned.