Hi all,

I've been going through the motions of installing SCCM 2012 in my workplace.  SCCM 2012 is on a Win Server 2012 box and I have been following the instructions layed out by Train Signal tutorials which has been working very well for me until now.

I am at the point where I need to get the client installed on client machines, and so far I have only been able to install it on my 2008 R2 servers.  I need to be able to deploy the client to Win 7 x64 Ent boxes and on my test machine the install is unsuccessful.  I have tried pushing from SCCM 2012 and manually installing from the SCCM server and as a last resort copied the client folder to the local W7 machine and ran it there also.  All what happens is the ccmsetup.exe process appears in task manager processes and it doesn't ever go.  No configuration manager button appears in control panel (as it has done with my 2008 R2 servers) and my two server 2012 hosts for both the sql 2012 and sccm 2012 servers.  I have turned windows firewall off for the purpose of this testing.

I have installed a hotfix http://support.microsoft.com/kb/2552033?wa=wsignin1.0 on the Server 2008 R2 machines prior to installing the client on them.  This URL also says that this hotfix should be installed on Win 7 machines too.  So I installed this also on my Win 7 x64 Ent machine.  The client didn't install correctly.  I have also uninstalled this hotfix from the Win 7 machine and it still does not install correctly.

I've copied and pasted the highlighted red lines from the ccmsetup.log file when run using the CM Trace Log Tool:

MSI: Action 14:40:53: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 17/05/2013 14:40:53 3596 (0x0E0C)
MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 17/05/2013 14:40:57 3596 (0x0E0C)
MSI: Action 14:41:30: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint. ccmsetup 17/05/2013 14:41:30 3596 (0x0E0C)
MSI: Action 14:41:38: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 17/05/2013 14:41:38 3596 (0x0E0C)
File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action:
ErrorMessages:
 ccmsetup 17/05/2013 14:42:03 3596 (0x0E0C)

Hoping someone can read between the lines and tell me what they think is going on, because from what I can make out it just doesn't want to install on Win 7 x64 Ent.

Many thanks in advance...

sccm_student

See client.msi.log. Search for "return value 3". The cause of the error should be listed in the lines before the occurance.

For reference: http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx

Hi Torsten,

Thanks for pointing me in the right direction...  the lines above are:

MSI (s) (90:B0) [14:42:02:665]: Creating MSIHANDLE (12619) of type 790536 for thread 1456
MSI (s) (90:D4) [14:42:02:665]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI94B0.tmp, Entrypoint: CcmStartService
MSI (s) (90!D8) [14:42:02:680]: Creating MSIHANDLE (12620) of type 790531 for thread 5080
MSI (s) (90!D8) [14:42:02:680]: Closing MSIHANDLE (12620) of type 790531 for thread 5080
MSI (s) (90!D8) [14:42:02:680]: Creating MSIHANDLE (12621) of type 790531 for thread 5080
[14:42:02] WARNING: Failed to delete setup in progress time-stamp with error 0x80070002
MSI (s) (90!D8) [14:42:02:680]: Closing MSIHANDLE (12621) of type 790531 for thread 5080
MSI (s) (90:D4) [14:42:02:680]: Closing MSIHANDLE (12619) of type 790536 for thread 1456
MSI (s) (90:B0) [14:42:02:680]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (90:B0) [14:42:02:680]: Error in rollback skipped. Return: 5
MSI (s) (90:B0) [14:42:02:680]: Entering MsiProvideAssembly. AssemblyName: Microsoft.ConfigurationManager.AssetProvider.dll,Version="5.0.0.0",Culture="neutral",PublicKeyToken="31bf3856ad364e35", AppContext: , InstallMode: -4
MSI (s) (90:B0) [14:42:02:680]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (90:B0) [14:42:02:680]: MsiProvideAssembly is returning: 1607
[14:42:02] The service 'ccmexec' is not installed
MSI (s) (90:B0) [14:42:02:914]: Note: 1: 2318 2:  
MSI (s) (90:B0) [14:42:02:914]: No System Restore sequence number for this installation.
MSI (s) (90:B0) [14:42:02:914]: Unlocking Server
MSI (s) (90:B0) [14:42:03:351]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 14:42:03: INSTALL. Return value 3.

Any ideas what it means?

Thanks Jason,

That's an interesting read !

You need to read all of the lines above the line containing "Return value 3" until you hit the one with a fatal error. It's not just ten or twenty lines, it could be 200 lines above. Reading Windows Installer verbose log files is an art and not a science.

Jason and Torsten,

Having looked at the lines above Return Value 3, I am still none the wiser.  I appreciate it is an art to reading these logs, and the use of Configuration Manager Trace Log Tool makes life easier, however I still am unsure what I'm looking for.

There is nothing that says specifically "fatal error" so once again I am stuck.

Would you be able to offer some assistance in glancing through the log file?  If so, what is the best method of getting this to you?

Thanks in advance,

Ok,

If anyone is interested in the outcome of this... then here's the answer (2 years later - just never updated when I resolved this issue)

It was a Group Policy that was effecting this.  Can't remember which one, but you're best to move the computer you're trying to deploy to into an OU unaffected by Group Policies.  You can always reapply the GPs one by one to see which one stops the client deployment.

There was nothing in the log file that I could make any sense of that explained my fix for this.

Regards,

• Proposed as answer by DanielRatliff 15 hours 12 minutes ago