SOLVED CmRcService could not be stopped Verify that you have sufficient privileges to stop

[Todd Johnson]

We have moved from one server 2012 to another 2016 server and site. Trying to get all the old client upgraded to the new site. The old server is down that had SCCM 2012. New server is on 2016 Sccm ver. 1707 build 8540. I have looked through all the threads about failing client agent installs. The error we get in the ccmsetup log is:

"MSI: Service 'Configuration Manager Remote Control' (CmRcService) could not be stopped. Verify that you have sufficient privileges to stop system services."

The firewall is off. When I go to look for the "CmRcService" service in services it's not there. The account being used to do the client push is also in the local admin group on the PC.

I get no error messages in the CmRcService Log either.

The only way we can get the old client upgraded is to completely uninstall using this method.. "
https://prajwaldesai.com/community/threads/sccm-client-install-failed-with-exit-code-1603.1047/

Once we have done the above uninstall we are able to successfully install the new client.

I am hoping that someone on here can lead me in the right direction. Uploading the logs is really not going to help I don't believe as its pretty much the same messages that I have seen in the other logs regarding this issue.

This is the error message right after the one above. "
File C:\Windows\ccmsetup\{E8435273-F894-449F-A48D-D33574B49ED7}\client.msi installation failed. Error text: ExitCode: 1603
Action: StopServices.
ErrorMessages:
Service 'Configuration Manager Remote Control' (CmRcService) could not be stopped. Verify that you have sufficient privileges to stop system services.
ccmsetup 10/27/2017 12:59:10 PM 4192 (0x1060)"

How can I get it to stop if the service does not exist?

 

[Prajwal Desai]

"The only way we can get the old client upgraded is to completely uninstall using this method" - Did you not enable client upgrade in hierarchy settings ?. I still want to review your CmRcService.log file to see if there are any errors codes. What AV / Security software is installed on the client machines ?.

client.msi installation failed. Error text: ExitCode: 1603 - Check this - https://prajwaldesai.com/community/threads/sccm-client-install-failed-with-exit-code-1603.1047/

 

[Todd Johnson]

"The only way we can get the old client upgraded is to completely uninstall using this method" - Did you not enable client upgrade in hierarchy settings ?. I still want to review your CmRcService.log file to see if there are any errors codes. What AV / Security software is installed on the client machines ?.

client.msi installation failed. Error text: ExitCode: 1603 - Check this - https://prajwaldesai.com/community/threads/sccm-client-install-failed-with-exit-code-1603.1047/

We are using Sophos Endpoint for our AV.

 

[Prajwal Desai]

Thanks for the log file, could you also upload client.msi file ?.

 

[Todd Johnson]

Thanks for the log file, could you also upload client.msi file ?.

File was to large.... 5MBs

 

[Prajwal Desai]

No worries. Can you temporarily stop all the Sophos services on client machine and SCCM server and try the client agent install ?.

 

[Todd Johnson]

Here is the CmRCService Log file, forgot to upload that one as well.

 

[Todd Johnson]

Tried disabling Sophos on both the services and the client. Pushed the client and received the same results.

 

[Prajwal Desai]

There are no errors in cmrcservice.log file except - Failed to register SPN (0x8007054b)
The ccmsetup.log file has got below errors :-
MSI: Service 'Configuration Manager Remote Control' (CmRcService) could not be stopped. Verify that you have sufficient privileges to stop system services.
File C:\Windows\ccmsetup\{ABE180B0-34A0-4D8F-BA51-4A2C18011A4A}\client.msi installation failed. Error text: ExitCode: 1603
Action: StopServices.
ErrorMessages:
Service 'Configuration Manager Remote Control' (CmRcService) could not be stopped. Verify that you have sufficient privileges to stop system services.
Client installation has failed too many times. Ccmsetup will try again after the next reboot.
Params to send '5.0.8540.1006 Deployment ExitCode: 1603 Action: StopServices. ErrorMessages: Service 'Configuration Manager Remote Control' (CmRcService) could not be stopped. Verify that you have sufficient privileges to stop system services. '
InstallFromManifest failed 0x80004004
Reached 5 max failure retry count. Will retry again after the machine restart.
CcmSetup failed with error code 0x80004004

Can you upload the client.msi logfile in onedrive / dropbox ?. That's the last file that i need to investigate.

 

[Todd Johnson]

Sure, Whats your email address.

 

[Prajwal Desai]

https://prajwaldesai.com/contact/

 

[Todd Johnson]

Any luck with the logs Prajwal?

 

[Prajwal Desai]

@Todd Johnson - No Todd, i couldn't find out much from the log files. At the beginning of the post you mentioned that CmRcService" service in services it's not there. The CmRcservice is usually located C:\WINDOWS\CCM\RemCtrl\CmRcService. I would suggest you to log this case with Microsoft Support, they should be able to help to you on this.

 

[Todd Johnson]

The file itself is there, however it doesn't want to stop.

 

[Prajwal Desai]

I would suggest you to log a case with MS support. I don't have access to your environment so I cannot proceed further with this.

 

[Todd Johnson]

So we finally discovered the issue. Had a little help from MS, however they only gave me a way to reinstall the agent quickly. Deleting this key and repushing the client would get the agent to update and install. (HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\CmRcService) However, what we were seeing happen was that the CmRcService service would show up in services, but then just disappear. Couldn't figure out why... However, we were getting some that the service would stay. Started comparing failed vs passed clients and notices that they were in different OU in AD. Started looking at GPO's and finally narrowed down the culprit. It was that we had a GPO that would Start Service Window Remote Management. Once I unlinked this policy, and forced gpupdate on the failed clients they started working and the service stayed. Spent quite a bit of time making sure that it was only this policy. So check your GPO. Test by creating a container that has no inheritance on it. Place the PC in there and see if the client updates. If so start linking GPO's to it to see when it breaks. Run GPupdate force every time between linking. This will help you narrow it down.

 

[Prajwal Desai]

Thank you so much for your valuable answer. This will help lot of people.