SCCM 2012 R2 SP1 CU1 patch failing during OSD

[VRDRF]

I recently upgraded the OS of my SCCM server to 2012 R2 by doing a site recovery on a new OS and for some reason during the Windows 7 OSD install the update for the sccm client fails for no real apparent reason and to make it even stranger is the fact that My windows 10 and Server 2012 R2 work just fine with the same client package.

 

I can see the following in the log files:

configmgr2012ac-sp2r2sp1-kb3074857-x64.log:

 

MSI (s) (8C:CC) [17:43:31:702]: Product: Configuration Manager Client - Update 'ConfigMgr2012AC-SP2R2SP1-KB3074857-x64' kan niet worden geïnstalleerd. Foutcode: 1603. Meer informatie is beschikbaar in logboekbestand C:\WINDOWS\ccmsetup\Logs\configmgr2012ac-sp2r2sp1-kb3074857-x64.msp.log.

MSI (s) (8C:CC) [17:43:31:702]: Een update is geïnstalleerd. Productnaam: Configuration Manager Client. Productversie: 5.00.8239.1000. Producttaal: 1043. Fabrikant: Microsoft Corporation. Naam van update: ConfigMgr2012AC-SP2R2SP1-KB3074857-x64. Status van geslaagde/mislukte installatie: 1603.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 1729

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (8C:CC) [17:43:31:702]: Transforming table Error.

MSI (s) (8C:CC) [17:43:31:702]: Product: Configuration Manager Client -- Configureren mislukt.

MSI (s) (8C:CC) [17:43:31:702]: Het product is opnieuw geconfigureerd. Productnaam: Configuration Manager Client. Productversie: 5.00.8239.1000. Producttaal: 1043. Fabrikant: Microsoft Corporation. Status van geslaagd/mislukt opnieuw configureren: 1603.

MSI (s) (8C:CC) [17:43:31:702]: Attempting to delete file C:\WINDOWS\Installer\2bab0.msp

MSI (s) (8C:CC) [17:43:31:702]: Unable to delete the file. LastError = 32

MSI (s) (8C:CC) [17:43:31:702]: Attempting to delete file C:\WINDOWS\Installer\2bab1.mst

MSI (s) (8C:CC) [17:43:31:702]: Unable to delete the file. LastError = 32

MSI (s) (8C:CC) [17:43:31:717]: Deferring clean up of packages/files, if any exist

MSI (s) (8C:CC) [17:43:31:717]: Attempting to delete file C:\WINDOWS\Installer\2bab0.msp

MSI (s) (8C:CC) [17:43:31:717]: Attempting to delete file C:\WINDOWS\Installer\2bab1.mst

MSI (s) (8C:CC) [17:43:31:717]: MainEngineThread is returning 1603

MSI (s) (8C:98) [17:43:31:717]: RESTART MANAGER: Session closed.

MSI (s) (8C:98) [17:43:31:717]: No System Restore sequence number for this installation.

=== Logboekfunctie beëindigd: 3-11-2015 17:43:31 ===

MSI (s) (8C:98) [17:43:31:717]: User policy value 'DisableRollback' is 0

MSI (s) (8C:98) [17:43:31:717]: Machine policy value 'DisableRollback' is 0

MSI (s) (8C:98) [17:43:31:717]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (8C:98) [17:43:31:717]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (8C:98) [17:43:31:717]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (8C:98) [17:43:31:717]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI (s) (8C:98) [17:43:31:717]: Restoring environment variables

MSI (s) (8C:98) [17:43:31:717]: Destroying RemoteAPI object.

MSI (s) (8C:F8) [17:43:31:717]: Custom Action Manager thread ending.

MSI © (7C:B8) [17:43:31:717]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI © (7C:B8) [17:43:31:717]: MainEngineThread is returning 1603

MSI © (7C:80) [17:43:31:717]: RESTART MANAGER: Session closed.

=== Verbose logging stopped: 3-11-2015 17:43:31 ===

 

I've tried using the PATCH= Function but that doesn't seem to solve anything.

 

Edit: found this in the ccmsetup.log:

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

Action: CcmSetObjectSecurity.

ErrorMessages:

Setup was unable to apply security permissions to C:\Windows\CCM\nl\SCNotification.resources.dll

The error code is 80070003

 

 

[Config Mangler]

I got the patch method working this very morning :-)

 

Command in the TS is:

 

PATCH="%_SMSTSMDataPath%\OSD\00100002\x64\PATCH\configmgr2012ac-sp2r2sp1-kb3074857-x64.msp"

 

I made a directory called PATCH referenced above and copied the MSP in there

 

The path is under the client install folder - so for x64 this was:

 

\\sccmserver\sms_site\client\x64\PATCH - obviously use your own server and site name here..........

 

Ensure you distribute the content for the patch under Applications/ Packages/ Configuration Manager updates

 

The final missing link for me was to Update Content on the original SCCM client package - this has the Package ID 00100002 as in the command above. It will probably be the same reference for you so should work.

[VRDRF]

I tried doing that but it still fails for the same reason, I can see in the ccmsetup that the file is there so its not like like it can't find the update file.

[Config Mangler]

Sure you did an update content on the original SCCM client package?

 

Mine was doing the same until I did that.

[VRDRF]

Yeah I did.

 

I managed to solve it in the end, for some reason the old sysprepped windows 7 didn't like the patch but a clean install.wim did.

Removed the updates folder from the client folder and redistributed the package and it worked again.

 

Now trying to find out what is actually in that sysprepped image apart from someone deciding it was a good idea to put office 2010 and adobe reader in the base image.