Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.ĥ. Stops remote control and other desktop components.Ĥ. Checks the desktop client version and gets the installation directory.ģ. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.Ģ. This custom action uninstalls the desktop client with following steps-ġ. MSI: Action 11:48:07: SmsDeinstallDesktopClient. MSI: Action 11:48:06: RemoveRegistryValues. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. ccmsetup 11:47:56 16608 (0x40E0) MSI: Action 11:47:56: CcmRemoveLanternDocuments. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action ccmsetup 11:47:56 16608 (0x40E0) MSI: Action 11:47:56: CcmUnregisterPerfCounters. We no longer use COM+ events for UI notifications. ccmsetup The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. Enumerates all providers and unloads them, verifies they are unloaded, and then reloads them. ccmsetup 11:47:56 16608 (0x40E0) MSI: Action 11:47:56: CcmUnloadWmiProvidersMsi. This custom action forces all open client UI and SCNotification components to stop and exit. ccmsetup 11:47:56 16608 (0x40E0) MSI: Action 11:47:56: SmsStopUserComponents.
I tried that, this is from the ccmsetup.log file: I can't find anything in the Microsoft online documentation about this. Without impacting the custom location of the ccmcache folder & without causing the ccmcache folder being recreated in the default location? How do I run a repair on problem SCCM clients OR reinstall the SCCM client The client) what happens is the ccmcache is recreated in C:\Windows and the ccmcache folder in D:\SCCM\ccmcache cannot be accessed. if I run the 'Install client' command against a problem pc from the SCCM console (without ticking uninstall
#Reinstall voobly client install
I couldn't find a way to get the SCCM clients into a stable state, so I want to install the client again - this is where I have run into problems.
#Reinstall voobly client software
This isn't impacting the ccmcache folder but is certainly impacting customer use of Software Centre to download and install applications. On some machines though, the SCCM client is repairing itself every day.
#Reinstall voobly client upgrade
However we're seeing problems with the SCCM client on some of the machines.Īs part of the upgrade, we move the SCCM client ccmcache location to D:\SCCM\ccmcache and again this works fine at the end of the upgrade all content downloaded after the ccmcache location change is in the new location. After a great deal of work, this working reliably well. We've started upgrading to Windows 10, via a refresh task sequence (from Windows 7) from SCCM 1806.
0 kommentar(er)
