Chris Nackers

ConfigMgr / SCCM

ConfigMgr 2007 Quick Fix: Remote Tools fail with Access Denied

2011-04-23

From the archive (2011). Written for the tools of the time, so some details may be out of date.

Read the original post here.

This post was contributed by:

Nuno Oliveira | Senior System Center Support Engineer

Here’s an issue I ran into the other day and since I didn’t see a lot documented about it I thought I’d go ahead and post the fix here.  If you’re getting an Access Denied error when trying to connect to a client using the Remote Tools then here are some permissions you should check.

Symptoms

When launching a System Center Configuration Manager 2007 Remote Tools session against a Windows 7 x64 (64-bit) client, the session will fail with one of the two messages below:

  • If launching the RC.EXE > File > Connect > IP of the Windows 7 x64 client > you get error Unable to contact host

  • If instead from we use the command prompt and execute RC.EXE 1 you get Access Denied

In the RemoteControl.log you will see entries similar to the following:

Remote Control Server started. RemoteControl 01.02.2010 16:32:29 2856 (0x0B28)
Failed to activate launcher object (0x80070005) RemoteControl 01.02.2010 16:32:29 2856 (0x0B28)
Server is no longer in use. Shutting down. RemoteControl 01.02.2010 16:32:29 2856 (0x0B28)
Remote Control Server terminated normally. RemoteControl 01.02.2010 16:32:29 2856 (0x0B28)

If ProcMon is executed on the Windows 7 64-bit client you see an “Access Denied” for the following directories:

C:\Windows\SysWOW64\CCM\clicomp\RemCtrl\RCLaunch.exe
C:\Windows\SysWOW64\CCM\Logs\RemoteControl.log

Cause

This issue can occur due to a lack of permissions for the Windows 7 x64 client file \Windows\SysWOW64\CCM\clicomp\RemCtrl\RCLaunch.exe.

Resolution

To resolve this issue, give Read and Execute rights to the “ConfigMgr Remote Control Users” group for the Windows 7 x64 client file \Windows\SysWOW64\CCM\clicomp\RemCtrl\RCLaunch.exe.