Win 10 1709 Upgrade Task Sequence issues

[dinci5]

Hi,

I'm testing an Upgrade TS to Win 10 1709.

I tested 4 devices now.
On  devices, all was working fine. Update was successful.

On other two devices, the OS upgrade was successful, but after the OS boots again the TS doesn't complete successfully.
I have two batch files in the Post-Processing group which are not executed. One of them just creates a txt file so I know it did run actually. 

In Software Center, the TS has status "Installing..." and it keeps spinning like that for hours.

The smsts.log files is also not updated anymore after the last reboot.
So the Setup command executed successfully, device rebooted, did the OS upgrade successfully, and when booted to the OS the TS just stopped.
New Windows 10 works perfectly fine though.
I can install other apps via Software Center as well without issues.

Anyone has an idea where to look?
Due to this, the status of the deployment is also not reported back to CM.
 

If 2 out of 4 devices have this problem, I guess it's not a good sign.

Of course I'll do some more testing but this is definitely not a good sign.

[anyweb]

what os are you upgrading from ?

[Phred]

--post removed--

Edited November 8, 2017 by Phred
acted too soon.

[dinci5]

On 11/6/2017 at 9:05 PM, anyweb said:

what os are you upgrading from ?

From 1607 and 1703.

I think I figured out what was going on.
In Setupact.log I saw this line: "Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd"

So the SetupComplete.cmd script didn't run which caused the TS to stop and the CM client to remain in Provisioning Mode.

Due to the specific nature of the client they have devices with OEM licenses as well.
This is because many employees work in remote locations (Africa, South America, Asia, etc...) and they purchase devices locally with OEM licenses. Those are then joined to the domain CM Client is installed manually and devices is encrypted with Symantec Endpoint Encryption.

I did test on random devices where some of them were indeed activated with OEM license and others via KMS. Those activated via KMS worked just fine.

Is there any way to change the Setup.exe command line string that's executed by the TS?
I do append extra switches, like /ReflectDrivers, but can you actually change the default switches?

 

[anyweb]

i guess you'll have to change the SKU to match the version you are installing as part of the installation, you can do that as documented here but i don't know if OEM is covered

 

https://blogs.technet.microsoft.com/mniehaus/2017/10/09/changing-between-windows-skus/

 

can you please tell me what version of Windows 10 are you upgrading from (home/pro ?)

 

[dinci5]

4 hours ago, anyweb said:

i guess you'll have to change the SKU to match the version you are installing as part of the installation, you can do that as documented here but i don't know if OEM is covered

 

https://blogs.technet.microsoft.com/mniehaus/2017/10/09/changing-between-windows-skus/

 

can you please tell me what version of Windows 10 are you upgrading from (home/pro ?)

 

Upgrading from Pro.

I'll have to use MAK keys then because those remote users rarely connect to our network so devices won't stay activated forever.

That's why the OEM keys were ok for us. We don't use any features from from W10 Enterprise anyway.

[dinci5]

I'm starting to hate SCCM. This product has so many bugs it really isn't fun anymore.

Now all my upgrades hang at setupcomplete.cmd until it times out.
After OS starts the CM client is stuck in Provisioning Mode.
 

The OS is upgraded though and it works fine. But the TS never completes successfully.

Only thing I see in smsts is this:

Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL'	TSManager	11/14/2017 10:28:08 AM	5952 (0x1740)
Failed to create an instance of COM progress UI object. Error code 0x80040154	TSManager	11/14/2017 10:28:08 AM	5952 (0x1740)
Timed out waiting for ccmexec service to be fully operational	TSManager	11/14/2017 10:58:17 AM	5952 (0x1740)
0, HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,5348)	TSManager	11/14/2017 10:58:17 AM	5952 (0x1740)
Failed to wait for Ccmexec service to be fully operational (0x80004005)	TSManager	11/14/2017 10:58:17 AM	5952 (0x1740)
TS::Utility::WaitForCcmExec(g_hShutdownEvent), HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmanager\tsmanager.cpp,1343)	TSManager	11/14/2017 10:58:17 AM	5952 (0x1740)
Process completed with exit code 0	TSMBootstrap	11/14/2017 10:58:17 AM	5764 (0x1684)
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs	TSMBootstrap	11/14/2017 10:58:17 AM	5764 (0x1684)

 

[anyweb]

have you tried changing SKU as described here (from Mr. Niehaus)

 

You can force it by adding a “/pkey <key>” switch to the command.  For example, if you want to force it to upgrade to Windows 10 Enterprise, use “/pkey NPPR9-FWDCX-D2C8J-H872K-2YT43”. 

 

[anyweb]

and as regards your new error it could be related to anything, for example what version of the ConfigMgr client are you installing ? stick with it, you'll get it working

the error you are seeing (

Failed to create an instance of COM progress UI object. Error code 0x80040154

means...

 

Class not registered

Source: Windows
-----

why, I do not know... but check your ConfigMgr client agent version for starters...

[dinci5]

On 11/14/2017 at 8:32 PM, anyweb said:

have you tried changing SKU as described here (from Mr. Niehaus)

 

You can force it by adding a “/pkey <key>” switch to the command.  For example, if you want to force it to upgrade to Windows 10 Enterprise, use “/pkey NPPR9-FWDCX-D2C8J-H872K-2YT43”. 

 

Yes yes, that's what I do.

I change the key to the KMS key and I don't get the OEM issue anymore.

Now I'm still struggling with the issue where the TS doesn't complete successfully and CM Client is messed up.
The Windows upgrade is successful. It's also reflected in the Setupact.log

 

It all starts here:

Quote

::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,842)    TSManager    11/16/2017 9:03:07 AM    4628 (0x1214)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    11/16/2017 9:03:07 AM    4628 (0x1214)
GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    11/16/2017 9:03:07 AM    4628 (0x1214)
End program:     TSManager    11/16/2017 9:03:07 AM    4628 (0x1214)
Finalize logging request ignored from process 4624    TSManager    11/16/2017 9:03:07 AM    4628 (0x1214)
Waiting for CcmExec service to be fully operational    TSManager    11/16/2017 9:03:07 AM    4628 (0x1214)
Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL'    TSManager    11/16/2017 9:03:08 AM    4628 (0x1214)
Failed to create an instance of COM progress UI object. Error code 0x80040154    TSManager    11/16/2017 9:03:08 AM    4628 (0x1214)
Timed out waiting for ccmexec service to be fully operational    TSManager    11/16/2017 9:42:55 AM    4628 (0x1214)
0, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5347)    TSManager    11/16/2017 9:42:55 AM    4628 (0x1214)
Failed to wait for Ccmexec service to be fully operational (0x80004005)    TSManager    11/16/2017 9:42:55 AM    4628 (0x1214)
TS::Utility::WaitForCcmExec(g_hShutdownEvent), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1357)    TSManager    11/16/2017 9:42:55 AM    4628 (0x1214)
Process completed with exit code 0    TSMBootstrap    11/16/2017 9:42:55 AM    4548 (0x11C4)