I have a client that Remote Tools continues to become disabled somehow. I have uninstalled and reinstalled the client, and it will seem to be ok, and then when we try to remote control it later, we get Remote Control is disabled, and in the RemoteControl.log we see "Remote Tools is disabled. Re-enable it in the SMS client agent settings". The SCCM Site server that this PC resides on is working fine, and has the correct settings enabled in the Remote Tools ClientAgent. No other clients on this site seem to have this issue.I have the UpdateEnabled=NO registry key on this PC so no one needs to be present to allow remote control. When I uninstalled and reinstalled, I did remove this string so it could properly install. Any ideas? This is a shop PC, and I know the people supporting it, are not enjoying running out to it to work on it. Remote Tools would be very helpful.Thanks!

I suggest using PolicySpy from the SMS/SCCM toolkits as a debugging tool. Perhaps a locally applied SCCM policy is disabling it?I don't believe that setting UpdateEnabled=NO will accomplish what you want. Create a file called Remote.mof containing the following code, andapply it on the client machine: "\windows\system32\wbem\mofcomp.exe Remote.mof". This will override "Permission Required".Nick.#pragma namespace("\\\\.\\root\\ccm\\policy\\machine\\requestedconfig")[CCM_Policy_PartialPolicy(true)] instance of CCM_RemoteToolsConfig {// Header properties PolicyID = "1"; PolicySource = "local"; PolicyVersion = "1"; PolicyRuleID = "1"; PolicyInstanceID = "1"; Type = 1; // Data properties[CCM_Policy_Override(TRUE)] PermissionRequired = 0; };

I had been fighting the same problem with a machine in the shop "remote control is disabled". Rich's fix took care of my problem!! THANKS!!

I only had one PC that would give this error and after applying this it resolved my issue.

While we've seen this on a handful of machines over the past few months, now that we've done our R3 upgrade we are seeing this on most of our workstations. While manually changing the registry key works, has anyone had any luck in figuring out why the Remote Control client agent would fail to set this correctly? I've poked through the machines with PolicySpy but failed to find an obvious cause.

I have also had this widely after applying the KB977384 Advanced Client Hotfix which is required as prep for R3. Fortunately, the registry key highlighted by Rich can be pushed out by SCCM still as the client still works. Only the Remote Control is disabled. The fix allowed me to quickly resolve the issue as my Service Desk have been getting very upset and gave me a list of 60 PCs in a week which had the problem. We have 4500 PCs but for whatever reason it has not affected all of them.