Automatic Client Upgrade does not happen

[spgsitsupport]

I can see in the log

Execution Request for advert SP12000E package SP100018 program Configuration Manager Client Upgrade Program state change from WaitingContent to WaitingContent
Persisting request for program Configuration Manager Client Upgrade Program package SP100018 in state WaitingContent

But such advert for Package SP100018 = Configuration Manager Client Upgrade Package no longer seems to exist in the site

Used PowerShell Script to locate SCCM objects in SCCM console

PS C:\PSScripts> .\Locate-SCCMObject.ps1 SCCM-server SP100018
Object Type: Unknown
Console Path: Academic Departments

Or Content Library Explorer:

So now I can not get client upgraded to latest CU4 KB3195483 version via Automatic client upgrades

Any idea how to fix it?

Seb

[spgsitsupport]

So I followed this, but hman.log shows

INFO: Current client upgrade settings are: FullClientPackageID=SP100017, StagingClientPackageID=(null), ClientUpgradePackageID=SP100018, ClientUpgradeAdvertisementID=SP12000E, ClientPilotingAdvertisementID=(null), ClientUpgradeVersion=5.00.8239.1000


INFO: Full client package content hasn't been changed. Skip updating.
INFO: Client upgrade package content hasn't been changed. Skip updating.

Which is plain wrong as the client is (in CU4) 5.0.8239.1502

[spgsitsupport]

I suppose the version of the client does not actually change with CU, one must just apply the update to colelctions - as per this

Is that right?

Seb

[spgsitsupport]

I will answer myself, yest it is as per this

[spgsitsupport]

Now any new machine that get imaged fails the TS process with:

File C:\WINDOWS\ccmsetup\configmgr2012ac-sp2r2sp1-kb3195483-x64.msp installation failed. Error text: ExitCode: 1603

Params to send '5.0.8239.1502 Deployment Error: 0x80070643, '    ccmsetup    16/06/2017 12:50:25    2576 (0x0A10)

 

So completely buggered install!

Seb

[michael.lecomber]

Have you recently done an update to your SCCM site server? IE CB1607 to 1703

[spgsitsupport]

No, NOT on that server/site

It is running 2012 R2 SP1 CU4 (exactly what I upgraded to)

In client.msi.log I get:

MSI (s) (18:C0) [14:12:13:255]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

All good, so far, but then in ccmsetup.log there is

Launch from folder C:\_SMSTaskSequence\OSD\SP1000D6\
CcmSetup version: 5.0.8239.1502
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18
Ccmsetup command line: "C:\_SMSTaskSequence\OSD\SP1000D6\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SP1000D6 /config:MobileClient.TCF /status:572:11:09	2384 (0x0950)
Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.
Command line: "C:\_SMSTaskSequence\OSD\SP1000D6\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SP1000D6 /config:MobileClient.TCF /status:572	2384 (0x0950)
Copying config file from C:\_SMSTaskSequence\OSD\SP1000D6\MobileClient.TCF to folder C:\WINDOWS\ccmsetup\. Return result: 0x0
.
.
.
.
.
MSI: Action 14:13:57: Rollback. Rolling back action:
File C:\WINDOWS\ccmsetup\configmgr2012ac-sp2r2sp1-kb3195483-x64.msp installation failed. Error text: ExitCode: 1603
Action: 
ErrorMessages:

configmgr2012ac-sp2r2sp1-kb3195483-x64.msp.log shows:

Executing op: TypeLibraryRegister(,,FilePath=C:\WINDOWS\system32\ccmcore.dll,LibID={90C7E669-C86D-48A6-8F7A-B16521DB52BD},,,Language=0,,BinaryType=1,IgnoreRegistrationFailure=0,)
QueryPathOfRegTypeLib returned 0 in local context.	Path is 'C:\WINDOWS\system32\ccmcore.dll'
Note: 1: 1402 2: UNKNOWN\TypeLib\{90C7E669-C86D-48A6-8F7A-B16521DB52BD}\100.0\0\win32 3: 2 
CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.
ProcessTypeLibraryCore returns: -2147319780. (0 means OK)
Note: 1: 2107 2: C:\WINDOWS\system32\ccmcore.dll 3: -2147319780 
Transforming table Error.
Transforming table Error.
Note: 1: 2262 2: Error 3: -2147287038
.
.
.
.
Product: Configuration Manager Client - Update 'ConfigMgr2012AC-SP2R2SP1-KB3195483-x64' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\ccmsetup\Logs\configmgr2012ac-sp2r2sp1-kb3195483-x64.msp.log.
Windows Installer installed an update. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: ConfigMgr2012AC-SP2R2SP1-KB3195483-x64. Installation success or error status: 1603.
Note: 1: 1729 
Transforming table Error.
Transforming table Error.
Note: 1: 2262 2: Error 3: -2147287038 
Transforming table Error.
Transforming table Error.
Note: 1: 2262 2: Error 3: -2147287038 
Product: Configuration Manager Client -- Configuration failed.
Windows Installer reconfigured the product. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.
MainEngineThread is returning 1603

After hours of testing it seems to ONLY happen if the machine is imagined with USB media (SCCM created) in UEFI mode, but firmware does not have an option for UEFI network stack (ie Latitude  3540, has UEFI boot that works fine, but no UEFI network stack exists)

That problem did NOT exist with previous CU2 client, so something in CU4 (client .1502 update) that causes 1603 error

Had to revert all machines back to legacy MBR/PXE to be able to imagine them again (can use the same USB media to boot!)

Seb