Hi all,
now that Windwos 10 v 1909 is out, we have started preparing our environment (SCCM Current Branch 1906) to deploy this new version and updating existing clients.
OSD Task Sequences for new machines with 1909 seem to run pretty smooth (after figuring out some Language Pack annoyances). However, we are facing issues with SCCM Feature Update Task Sequences that bomb out after the base os installation. We are trying to update Windows 1709 and also 1809 versions. This is what we have encountered so far:
The Task Sequence for the OS upgrade starts fine, performs a few expected reboots, then displaying "Windows is working in updates 0%, 15%, ..." When it reaches 100%, this Windows Upgrade step remains at 100% for a long long time and then suddenly shows the Windows login screen. All TS Post Processing steps (i.e. Language Packs, etc.) are skipped.
SMSTS.LOG indicates, that the base OS upgrade seems to have finished without errors:
- Successfully completed the action (Upgrade Operating System) with the exit win32 code 0
After that we can discover several "Start top compile TS policy" steps, but suddenly the following errors happen:
<![LOG[Failed to initate policy evaluation for namespace 'root\ccm\policy\machine', hr=0x80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="utils.cpp:5007"><![LOG[Error compiling client config policies. code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1577"><![LOG[Task Sequence Manager could not initialize Task Sequence Environment. code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1654"><![LOG[Task sequence execution failed with error code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1305">
After that the Task Sequence stops any further processing without showing any errors. Digging through all other SCCM logs I have found out that at the time time when the error above happens there is the following in CCMEXEC.LOG:
<![LOG[Detected faulty configuration. Repair will be started in 5 minutes.]LOG]!><time="10:07:11.521-60" date="11-25-2019" component="CcmExec" context="" type="3" thread="6560" file="entrypoint.cpp:3079"><![LOG[Entering main message loop.]LOG]!><time="10:07:11.521-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3104"><![LOG[WM_QUIT received in the main message loop.]LOG]!><time="10:12:11.521-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3121"><![LOG[Initiated repair of configuration. Service will now exit.]LOG]!><time="10:12:11.599-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3130"><![LOG[Shutting down CCMEXEC...]LOG]!><time="10:12:11.599-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="shutdown.cpp:53">
This looks to me, that immediately after the OS upgrade, the system seems to start a repair of the SCCM client (for unknown reason). This repair seems to break the entire Task Sequence.
have triple-checked countlessly that the SCCM client is healthy before the upgrade but something seems to happen during the 1909 upgrade that makes Windows trying to repair the SCCM client.
Any thoughts what might go wrong here?
Thanks in advance
Regards
Udo