Dear Brothers,

I have an issue with two (2) of my Site Servers, I have below scenarioa and explained issue details:

Scenario:

1. Server1: Windows 2012 Server, CAS, SCCM 2012 Hierarchy Roles: Management Point, DP, SUP, Component Server.

2. Server2: Windows 2008 R2 Server, Secondary Site Role, SCCM 2012 Hierarchy Roles: Management Point, DP, Component Server.

Issue:

After updating the SCCM 2012 Client to CU4 on the actual Site Server, the "ccmsetup" appears also with "SMS Agent Host" at the Service MMC. Which I believed this is very unusual behavior.

  The Client however it seems properly installed and working please see below details:

Questions: I believed the Client installations are still running on the background, even though the Client tends to look working on the Control Panel.

1. How can I resolved this issue?

2. Should I need to perform a total Client uninstallation, even depth till removing entries in the Registry levels?

3. Or this is a normal behavior for the scenario?

Advance thanks for your future replies, my brothers in technology.

 

SMS Agent Host is the component that's shared between a client and a management point. It is expected (for a short period of time) that both services will be running. Examine ccmsetup.log if there are any errors logged.

Dear Brother,

2 Weeks since I installed the CU4, it seems a little bit to long isn't it? for both the ccmsetup and the SMS Host Agent Services to exist, for the errors on the ccmsetup.log there are some errors after uninstallation since I am trying to removed the issue .

CCMsetup.log

==========[ ccmsetup started in process 5376 ]========== 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on platform X64 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\cache\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Launch from folder C:\Windows\ccmsetup\ 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup version: 5.0.7804.1500 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on OS (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 3 7/1/2014 7:14:45 PM 4104 (0x1008)
Ccmsetup command line: ccmsetup.exe  /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required. 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line: ccmsetup.exe  /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
SslState value: 224 7/1/2014 7:14:45 PM 4104 (0x1008)
Detected client version 5.00.7804.1500 from WMI. 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Another instance of ccmsetup is already running. 7/1/2014 7:14:45 PM 4104 (0x1008)
Task 'Configuration Manager Client Upgrade Task' does not exist 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup is exiting with return code 3 7/1/2014 7:14:45 PM 4104 (0x1008)
MSI: Action 19:15:20: SmsRemoveUIEvents. This custom action is no longer used. The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. We no longer use COM+ events for UI notifications. 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:20: CcmUnregisterPerfCounters. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:20: CcmRemoveLanternDocuments. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: SmsDeinstallDesktopClient. This custom action uninstalls the desktop client with following steps-
1. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.
2. Checks the desktop client version and gets the installation direcotry.
3. Stops remote control and other desktop components.
4. Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.
5. Saves information needed for migration and uninstalls the desktop components followed by clean up. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUse. Moves files that are in use so that they will be deleted upon the next reboot. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:31: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Action 19:15:31: InstallFiles. Copying new files 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Internal Error 2902. ixfAssemblyCopy 7/1/2014 7:15:32 PM 5628 (0x15FC)
MSI: Action 19:15:32: Rollback. Rolling back action: 7/1/2014 7:15:32 PM 5628 (0x15FC)
File C:\Windows\ccmsetup\configmgr2012ac-sp1-kb2882125-x64.msp installation failed. Error text: ExitCode: 1603
Action: InstallFiles.
ErrorMessages:
Internal Error 2902. ixfAssemblyCopy
 7/1/2014 7:15:33 PM 5628 (0x15FC)
A Fallback Status Point has not been specified.  Message with STATEID='301' will not be sent. 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\ccmsetup.xml 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\client.msi 7/1/2014 7:15:33 PM 5628 (0x15FC)
CcmSetup failed with error code 0x80070643 7/1/2014 7:15:33 PM 5628 (0x15FC)

Regards,

I'm getting the same issue. Anyone have a solution?

I'm getting the same issue. Anyone have a solution?

Have the same issue here. The SMS Agent host service is restart now and then. I do not have any clue what is causing this or what a solution/work-around might be... Till now I'm getting an error when forcing a Machine policy retrieval. The error is "The selected cycle cannot start."

Anyone an idea??

You need to post your ccmsetup.log and client.msi.log from a failed machine. Please make sure to post the entire log, usually best to upload to a file hosting site such as OneDrive.

As a total shot in the dark have a look at what version of windows installer you have installed on that device and maybe update it to a newer version then attempt another installation, try it without AV enabled.