We are beginning our client migrations from 2007 to 2012 soon and I have hit a snag. I am trying to deploy the client with the CU3 patch and the setups are stalling.

When I deploy the 2012 client using a 2007 advertisement, the setup starts, removes the 2007 client, then stops.

The ccmsetup.log gives the following error:

<![LOG[File C:\WINDOWS\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1635

The client.msi.log gives this error as well:

MSI (s) (3C:24) [06:33:23:247]: Unable to create a temp copy of patch 'configmgr2012ac-sp1-kb2882125-x64.msp'.
MSI (s) (3C:24) [06:33:23:247]: Note: 1: 1708 
MSI (s) (3C:24) [06:33:23:247]: Product: Configuration Manager Client -- Installation failed.

MSI (s) (3C:24) [06:33:23:247]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1635.

I have found that the error code is related to the inclusion of 'PATCH=configmgr2012ac-sp1-kb2882125-x64.msp' in the ccmsetup command line, but it is a little cryptic to me as to how I can include the CU3 update in a single command line.

Here is the full command line we are using:

x64:

ccmsetup.exe /noservice /mp:MYSERVER.MY.ORG SMSSITECODE=XXX FSP=MYSERVER.MY.ORG SMSMP=MYSERVER.MY.ORG CCMENABLELOGGING=TRUE CCMLOGLEVEL=0 PATCH=configmgr2012ac-sp1-kb2882125-x64.msp

x86:

ccmsetup.exe /noservice /mp:MYSERVER.MY.ORG SMSSITECODE=XXX FSP=MYSERVER.MY.ORG SMSMP=MYSERVER.MY.ORG CCMENABLELOGGING=TRUE CCMLOGLEVEL=0 PATCH=configmgr2012ac-sp1-kb2882125-x86.msp

Thanks in advance for your help!

--Matt

1635 = 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.

Is the update package available on the DP?

Yes, the update package is in the data source location and distributed to the DP.

Configure a path to the patch executable.

eg PATCH = \\server\.....\configmgr2012ac-sp1-kb2882125-x86.msp

Note that ccmsetup.exe will run under the context of the System account which probably won't have access to the share containing the hotfix. You will have to give "Domain Computers" access to the share

See here

http://blog-en.netvnext.com/2011/11/how-to-install-sccm-client-with.html

 

Just to add a little info, the file specified in a PATCH property of an msiexec command-line must be fully qualified to its location, it cannot be relative even if it';s in the same directory as the msi be executed. This is a Windows Installer thing and has nothing to do with ConfigMgr.

Given that you are using a 2007 package, instead of putting the MSP on a share and referencing it from there, leave the MSP in the package and put your command-line in a batch file, then, from with your batch file you can use the %~dp0 batch parameter (see http://blog.configmgrftw.com/?p=78) to fully qualify the path to the MSP. Thus, in your batch file, you should include something like this:

ccmsetup.exe /noservice SMSSITECODE=XXX FSP=MYSERVER.MY.ORG SMSMP=MYSERVER.MY.ORG CCMENABLELOGGING=TRUE PATCH="%~dp0configmgr2012ac-sp1-kb2882125-x86.msp"

Also, I generally would *not* use /mp (it doesn't do what you think it does: http://blog.configmgrftw.com/?p=598) and I also would not set the log level to 0 -- too much detail is often a bad thing and the logs may wrap too quickly for you to see what happened.

Thanks Jason and Gerry.

I would up adding the full path to the MSP.

--Matt

In my case, the only thing that helped, was to create custom CM Client package By myown. Some problems was seeing in Client.log of installation, where it fails to create temp-folder at Client machine. Even using PATCH=\\server... method didnt help. I guess this has something to do with folder rights and Access of CM server.