
Also for a unmannaged client disabling ADCįeature wont have that much impact on the client. Once this went out to the clients it was a smooth uninstall of Symantec and a smooth install of System Center Endpoint Protection without bothering the end user or rebooting the client PC.According to the troubleshooting steps we followed for the previous case,Īpplication and Device control feature is the one which blocks the user fromĪccessing the DPot application. HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC In the registry file add “-“ after “=” on these two keys NOTE: The default password for Symantec Endpoint Protection is symantec. Regedit.exe /s \\SERVERNAME\SHARENAME\removesymantecep.reg This is what was in my batch file:Ĭd C:\Program Files\Symantec\Symantec Endpoint Protection I placed my batch file in the packages directory on the SCCM server and pushed it out via software deployment to the clients.

The System Center Endpoint Protection Setup wizard was unable to remove one or more programs that conflict with System Center Endpoint Protection. HRESULT=0x8004FF67 Description=System Center 2012 Endpoint Protection installation error. %systemdrive%\WINDOWS\CCM\Logs\EndpointProtectionAgent.logįailed to install endpoint protection client with exit code = 0x8004ff67.ĭetail error message is :

Sure enough the require uninstall password was causing the issue. I knew I would run into problems because Symantec Endpoint Protection was on these clients and there was a password required to uninstall it.

Recently I had to deploy System Center Endpoint Protection (SCEP).
