We have a mix of Windows 7 and Windows XP PC's in our SCCM 2007 Console. About 4 to 6 months ago, "something" happened. We are not sure what happened, but Remote Tools will not work on random PC's. Anyone that tries to remote control an affected PC, will get the Credentials Required prompt. After doing some Googling, etc, I have found that the settings at HKLM\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control are not being updated with the correct settings. I noticed that when I first install the SCCM client on a machine, the default settings show the PermittedViewers as Administrators. In our console, we have a different group - called rights-all-pcs. A few minutes after the client install is complete, I can watch the registry settings above automatically change, including adding Rights-ALL-PCs to the PermittedViewers key. Then, and only then will the Remote Tools work again. The only way I have been able to repair this issue involves uninstalling the client, deleting the CCM folder, deleting the SMS registry setting, and reinstalling the client from my console. I am looking for a few things here: 1. Anyone have any idea why these registry settings are not updating? What can I look at? 2. Where are the settings stored that cause the changes? 3. Is there a quicker solution than what I have to do know to get Remote Tools working again? I can tell you this much: 1. Manually entering the settings does no good 2. Resetting the User Policy with Right-click tools does not work either Any help or thoughts appreciated! Matt

Give the AD-group read rights to %systemroot%\SysWOW64\CCM\clicomp\RemCtrl\RCLaunch.exe on the machines they will use remote tools against. Try to use below commands to grant access. %systemdrive%\Windows\SysWOW64\CCM\clicomp\RemCtrl\RCLaunch.exe /grant "ConfigMgr Remote Control Users":F %systemdrive%\Windows\SysWOW64\CCM\clicomp\RemCtrl\ /grant "ConfigMgr Remote Control Users":F

Tried that in the past and it does nothing. In fact, I checked on the PC's that are working and I don't see ConfigMgr Remote Control Users listed there at all. All PC's with the issue get this message in the EventViewer as well: Event Type: Error Event Source: DCOM The application-specific permission settings do not grant Remote Activation permission for the COM Server application with CLSID {126C0D0F-1F6E-4BD2-A805-B9343F6D8FB5} to the user BLAIRNET\mjd SID (S-1-5-21-8915387-1693803139-1862565094-20373). This security permission can be modified using the Component Services administrative tool. Again - once the registry settings change, everything works. Still looking for a way to get the registry on the remote PC to update with the correct settings without having to uninstall/ reinstall, etc. Matt Dillon

I can tell you that when I add my name to the Remote Tools Client Agent, refresh the policies on a machine that is working, within 30 seconds I see the change I made in the PermittedViewers registry setting. I guess what I am looking for is a way to fix the clients on the PC's that are not getting the policies updated. Matt Dillon

Client Status reporting can make your task easy to identify unhealth clinets .Check : http://technet.microsoft.com/en-us/library/cc161956

I have the "fix" to at least work so I don't have to visit a desk. I delete the Remote Control key from the registry, then use the Right-click tools to run a repair. When the repair is complete, I make sure the key was rebuilt, and then do a Machine Policy refresh and within a few minutes the client is working again. Its better than completely uninstalling, etc. I would still like to know why the settings from the console are not getting updated at some clients, why is only Remote Tools affected, and is there a better fix than what i am doing. Matt

Hi, Have you enabled terminal service in your XP client? The "Terminal Services" service provides other functionality beyond "Terminal Services" like the APIs needed to determine username information, fast user switching etc. About DCOM permission for remote tool: From documents, we can find it mentioned ConfigMgr Remote Control Users Group must have the following DCOM permissions on the Remote Tools Agent, Launcher and Server in the following link http://technet.microsoft.com/en-us/library/bb680755.aspx These components can be found under dcomcnfg.exe->My computer->DCOM Config It means the ConfigMgr uses the DCOM to launch these components to make sure the remote tool can be launched on the client successfully, the DCOM needs to be enabled. Hope this will help. Thanks