SCCM 2012 R2 - ReImage Windows 7 x64 - Fail to install agent at the end

[ZeZe]

Hi all,

 

For a while I’m building a standard image to deploy.

 

When I deploy the image over a workstations everything goes well until it start SCCM Agent installation.

 

I don't know why, but it fails to install the Agent. During the installation process it doesn’t tell me that fails to install the agent, but when you logon on the workstation you can tell that the agent was not correctly installed because it misses some information on the general tab. Take a look at the image attached. My task sequence have additional packages at the end, but because the agent is not present or not well register to the SCCM server, it misses all those packages to be installed.

 

 

This not a production environment but lab and all my workstations are running over a hyper-v server (non clustered).

 

Somehow I managed to install correctly but for some reason now starts to fail again. It appears to be random. The only changes were the schedule updates on the WIM image. The error on the SMSTS.log is: Failed to install SMS Client (0x80004005). I have also attached the log.

 

I have a workaround to this problem – I can simply apply to install the agent from the console over that workstation (with the remove options on). This does not work for me because I idea is to install several packages upon windows installation and that is not happening. Any help on this matter I would really appreciate. It sounds that the problem might be on the VM, but not sure.

 

EDITED: Just add the ccmsetup.log / clientmsi.log

 

 

Thanks in advanced,

 

smsts.log

ccmsetup.log

client.msi.log

Edited May 7, 2014 by vasconcelos

[ZeZe]

Update: I just create new image (captured and build) and apparently the installation went OK!

 

But my main concern persists: how can updates create this problem? How can we avoid this?

I’m also using the previous image (restored from the bak file generated after schedule updates) and applying that image to see if it fails.

[Peter van der Woude]

When the client installation fails, check the ccmsetup.log file.

[ZeZe]

Hi Peter,

I have seen this error before but I can't find a reason for it. I have another task sequence that runs perfecly and it does the same things. The only thing that is different is the image, but it's the same version.

The error starts from there:

File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1603

Action:

ErrorMessages:

ccmsetup 06/05/2014 13:24:45 2360 (0x0938)

Next retry in 1 minute(s)... ccmsetup 06/05/2014 13:24:46 2360 (0x0938)

C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

Running installation package

Package: C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi

Log: C:\WINDOWS\ccmsetup\Logs\client.msi.log

Properties: REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" FSP="SCCM-CONSOLE.LAB.LOCAL" CCMEVALHOUR="13" SMSMP="SCCM-CONSOLE.LAB.LOCAL" SMSCACHESIZE="20480" SMSPROVISIONINGMODE="1" SMSSITECODE="001" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" SMSSLP="SCCM-CONSOLE.LAB.LOCAL" CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A40000525341310008000001000100135A27FB94A890A9D31B23CB75EDF91292D9362438C3DD514E6E41ADF33503EE4E27D7336D8659D032696BAA77AE77CB8A4F804D3023B3A9EAD4B35B1DCDA7DD6872D95DEBAE7EE257AA12EBC00DE0AF865229B7E60B3B03384E4F00A7673D69D353876D243DA54EB3024D0D1E1CF8FE93186B3C69D55EA00FEF3B39EEF015F107DD3961A57688C60C7FDF75EDE974E7B92B7923E8F1B084963D5A0C9DBBA9841A1A9D0BFFCDC13C772EEEED196257049250F5202218F18E107FD331B9C68E0540DDE5FCB890C24142592C18992440B7C2679314E0E844238BF132892A7415C16D5754772FDBA18B7612D52937FB9A8B6E0308E19389A16FBD947EE2A07ED6AD ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: INSTALL. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: System64Folder.8AE6A59B_5597_4D75_9BFD_7F566BF56500. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: SystemFolder.8AE6A59B_5597_4D75_9BFD_7F566BF56500. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: System64Folder.98C5B086_7EB0_422A_B0A8_674010F525CD. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: System64Folder.50F68C19_42FD_4094_A3C6_DF681B809B3A. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: System64Folder.4C5E03E8_F8E5_47CB_8FF4_E46FE34D35A6. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: SystemFolder.FD3895C1_4398_4C8C_B697_EA56FAFF0C78. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: SmsCheckConfig. Enumerates the source for client config as specified in SMSCONFIGSOURCE and signals an abort install if a specific condition arises. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:46: CcmCheckSupportedEmbedded. Checks whether the current OS is a supported Windows Embedded Platform and sets appropriate MSI properties. ccmsetup 06/05/2014 13:25:46 2360 (0x0938)

MSI: Action 13:25:47: LaunchConditions. Evaluating launch conditions ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: SmsCheckNewRemoteTools. Check if we should install the new version of remote tools. This applies to Windows XP and above clients only. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: AppSearch. Searching for installed applications ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: ValidateProductID. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: CcmSetInstallDir64. Property action for setting installation directory for Configuration Manager Client on 64-bit platform. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: CcmSetInstallDirFromCmdLine. Property custom action for setting install directory from command line. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: CcmSetPrimaryFolder. Property action for setting target installation folder. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: FindRelatedProducts. Searching for related applications ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: CostInitialize. Computing space requirements ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: ResolveSource. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: FileCost. Computing space requirements ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: PolicyDefinitionsENUS.50F68C19_42FD_4094_A3C6_DF681B809B3A. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: PolicyDefinitions.50F68C19_42FD_4094_A3C6_DF681B809B3A. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: WBEM.812B0603_EFD0_4199_8B2F_F17F6A0D5261. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: CostFinalize. Computing space requirements ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: MigrateFeatureStates. Migrating feature states from related applications ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:47: SmsSwDistSetCacheDir. This custom action determines if there is an existing cache directory available or not. If not, it creates one and configures it to be used by MSI. ccmsetup 06/05/2014 13:25:47 2360 (0x0938)

MSI: Action 13:25:48: CcmSuppressReboot. Suppress machine reboot after installation. ccmsetup 06/05/2014 13:25:48 2360 (0x0938)

MSI: Action 13:25:48: CcmLookupAccountNames. Looks up the name of the Administrators group, Users group, and Creator Owner account, then sets the properties CcmAdministratorGroupName, CcmUsersGroupName, and CcmCreatorOwnerAccountName. ccmsetup 06/05/2014 13:25:48 2360 (0x0938)

MSI: Action 13:25:48: InstallValidate. Validating install ccmsetup 06/05/2014 13:25:48 2360 (0x0938)

File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1603

Action:

ErrorMessages:

ccmsetup 06/05/2014 13:25:49 2360 (0x0938)

Next retry in 1 minute(s)... ccmsetup 06/05/2014 13:25:50 2360 (0x0938)

C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

Running installation package

Package: C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi

Log: C:\WINDOWS\ccmsetup\Logs\client.msi.log

Properties: REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" FSP="SCCM-CONSOLE.LAB.LOCAL" CCMEVALHOUR="13" SMSMP="SCCM-CONSOLE.LAB.LOCAL" SMSCACHESIZE="20480" SMSPROVISIONINGMODE="1" SMSSITECODE="001" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" SMSSLP="SCCM-CONSOLE.LAB.LOCAL" CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A40000525341310008000001000100135A27FB94A890A9D31B23CB75EDF91292D9362438C3DD514E6E41ADF33503EE4E27D7336D8659D032696BAA77AE77CB8A4F804D3023B3A9EAD4B35B1DCDA7DD6872D95DEBAE7EE257AA12EBC00DE0AF865229B7E60B3B03384E4F00A7673D69D353876D243DA54EB3024D0D1E1CF8FE93186B3C69D55EA00FEF3B39EEF015F107DD3961A57688C60C7FDF75EDE974E7B92B7923E8F1B084963D5A0C9DBBA9841A1A9D0BFFCDC13C772EEEED196257049250F5202218F18E107FD331B9C68E0540DDE5FCB890C24142592C18992440B7C2679314E0E844238BF132892A7415C16D5754772FDBA18B7612D52937FB9A8B6E0308E19389A16FBD947EE2A07ED6AD ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: INSTALL. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: System64Folder.12C909B6_5F69_4C4D_8EC3_C225C1607933. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: System64Folder.A6940213_CD40_4753_8BA2_E803376DECC3. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: System64Folder.8AE6A59B_5597_4D75_9BFD_7F566BF56500. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: SystemFolder.8AE6A59B_5597_4D75_9BFD_7F566BF56500. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: System64Folder.98C5B086_7EB0_422A_B0A8_674010F525CD. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: System64Folder.50F68C19_42FD_4094_A3C6_DF681B809B3A. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: System64Folder.4C5E03E8_F8E5_47CB_8FF4_E46FE34D35A6. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: SystemFolder.FD3895C1_4398_4C8C_B697_EA56FAFF0C78. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:50: SmsCheckConfig. Enumerates the source for client config as specified in SMSCONFIGSOURCE and signals an abort install if a specific condition arises. ccmsetup 06/05/2014 13:26:50 2360 (0x0938)

MSI: Action 13:26:51: CcmCheckSupportedEmbedded. Checks whether the current OS is a supported Windows Embedded Platform and sets appropriate MSI properties. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: LaunchConditions. Evaluating launch conditions ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: SmsCheckNewRemoteTools. Check if we should install the new version of remote tools. This applies to Windows XP and above clients only. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: AppSearch. Searching for installed applications ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: ValidateProductID. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: CcmSetInstallDir64. Property action for setting installation directory for Configuration Manager Client on 64-bit platform. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: CcmSetInstallDirFromCmdLine. Property custom action for setting install directory from command line. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: CcmSetPrimaryFolder. Property action for setting target installation folder. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: FindRelatedProducts. Searching for related applications ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: CostInitialize. Computing space requirements ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: ResolveSource. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: FileCost. Computing space requirements ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: PolicyDefinitionsENUS.50F68C19_42FD_4094_A3C6_DF681B809B3A. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: PolicyDefinitions.50F68C19_42FD_4094_A3C6_DF681B809B3A. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: WBEM.812B0603_EFD0_4199_8B2F_F17F6A0D5261. ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:51: CostFinalize. Computing space requirements ccmsetup 06/05/2014 13:26:51 2360 (0x0938)

MSI: Action 13:26:52: MigrateFeatureStates. Migrating feature states from related applications ccmsetup 06/05/2014 13:26:52 2360 (0x0938)

MSI: Action 13:26:52: SmsSwDistSetCacheDir. This custom action determines if there is an existing cache directory available or not. If not, it creates one and configures it to be used by MSI. ccmsetup 06/05/2014 13:26:52 2360 (0x0938)

MSI: Action 13:26:52: CcmSuppressReboot. Suppress machine reboot after installation. ccmsetup 06/05/2014 13:26:52 2360 (0x0938)

MSI: Action 13:26:52: CcmLookupAccountNames. Looks up the name of the Administrators group, Users group, and Creator Owner account, then sets the properties CcmAdministratorGroupName, CcmUsersGroupName, and CcmCreatorOwnerAccountName. ccmsetup 06/05/2014 13:26:52 2360 (0x0938)

MSI: Action 13:26:52: InstallValidate. Validating install ccmsetup 06/05/2014 13:26:52 2360 (0x0938)

File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1603

Action:

ErrorMessages:

ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

Client installation has failed too many times. Ccmsetup will now abort. ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

Sending Fallback Status Point message to 'SCCM-CONSOLE.LAB.LOCAL', STATEID='313'. ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

Params to send FSP message '5.0.7958.1000 Deployment ExitCode: 1603 Action: ErrorMessages: ' ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

State message with TopicType 800 and TopicId {C42565E8-DE6B-4057-A718-7351CBDFE5A7} has been sent to the FSP FSPStateMessage 06/05/2014 13:26:54 2360 (0x0938)

InstallFromManifest failed 0x80070643 ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

Deleted file C:\WINDOWS\ccmsetup\SCEPInstall.exe.download ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

CcmSetup failed with error code 0x80070643 ccmsetup 06/05/2014 13:26:54 2360 (0x0938)

[willisj318]

It almost sounds like the sccm client is already a part of the image. In the ccmsetup.log you attached.

 

Client (5.00.7958.1000) is installed and is the same or lower version. Initiating repair.
Repairing version 5.00.7958.1000 of the client with product code {8864FB91-94EE-4F16-A144-0D82A232049D}

 

My guess is the new image works because you captured it without the client installed. The log looks weird, it shows start date of 4/14 then a date of today 5/6

[ZeZe]

Thanks for the post Will!

 

I have used this image before and worked OK. I recently updated the image with windows updates. I create this image using that standard process "build and capture", very simple and easy. I assume the agent is installed during that process and therfore, exists on the operating system. I guess that the task sequences (that captures) prepares the agent to be removed, before it starts to capture the image. What you are saying is true, but other images that I have worked OK. Why would this one be different?

 

Thanks!

[willisj318]

I don't know that as a fact, just what it seems like via the log. I don't believe the client is supposed to stay installed doing the capture. We don't really use that method here and I have not messed with it much. My knowledge is that the client is wiped/removed when done capturing or prepping it. Did you use the built in servicing option to install updates? Is it possible that you are using a SUP to install the client and it got caught in those updates during servicing?

[ZeZe]

Yes, I used the built in servicing to install the updates. I setup the WSUS and configure a package of updates. Then I rollout those updates to the WIM image, using the schedule updates on the console.

[willisj318]

Sorry if I missed this but have you tried updating the new image yet? And then testing?

[Peter van der Woude]

Also, your CCMsetup.log shows a 1603 error, which is a very generic MSI error. You might want to look at the client.msi.log for even more information.