I'm currently seeing the following behaviour when running an In-Place
upgrade to Win 10 in my client.msi log.

Client MSI

'This update package could not be opened. Verify that the update package
exists and that you can access it, or contact the application vendor to
verify that this is a valid Windows Installer update package.'

In the ccmsetup.log it is using the following syntax to run the install:

MSI PROPERTIES are  REINSTALL=ALL REINSTALLMODE=vmous  INSTALL="ALL"
PATCH="C:\_SMSTASKSEQUENCE\OSD\***00004\HOTFIX\KB2938441\X64\CONFIGMGR2012AC-R2-KB2938441-X64.MSP"
 SMSSITECODE="***" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224"
CCMFIRSTCERT="1" CCMCERTID="SMS;651D68A957E24DB0FDA887EB1494580F1A0ECFC0"
REMEDIATE="true" CCMUPDATEOSVERSION="6.4.9841" SMSPUBLICROOTKEY=********

My initial thought is is that it is calling up the patch command issued as
part of my Win 7 TS build originally laid down on the machine. The
C:\_SMSTASKSEQUENCE\OSD\***00004\HOTFIX\KB2938441\X64\ no longer being
available on the endpoint post original O/S build.

Is anyone successfully running in-place upgrade with the patch command
being used in their original OSD TS?

Cheers
Paul


Reply via email to