Yes, but as Jason said, you control membership of that group with the remote control client settings.
Jeff Sent from my Windows Phone ________________________________ From: Heaton, Joseph@Wildlife<mailto:[email protected]> Sent: 3/26/2015 3:25 PM To: '[email protected]'<mailto:[email protected]> Subject: [mssms] RE: Cfg Mgr Remote Control tool So would the local ConfigMgr Remote Control Users group be the one I need? From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, March 26, 2015 1:15 PM To: [email protected] Subject: [mssms] RE: Cfg Mgr Remote Control tool The local windows Remote Desktop Users group has nothing to do with Remote Control in ConfigMgr - that's used for Remote Desktop, two different things. The user must be a member of a group specified in Client Settings for Remote Control or a local admin on the target system. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Thursday, March 26, 2015 3:06 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Cfg Mgr Remote Control tool I'm getting more requests to allow folks that are in charge of specific applications to be able to remote in to end users' PCs to "shadow" them, and help troubleshoot issues. Historically, we would add those folks to the group that has local admin rights on PCs in the organization, and they were then able to do this. I'd really like to move away from that. In testing, I added my test user to the Builtin\Remote Desktop Users group, thinking that would give them the permissions needed, then add them to the Remote Tools Operators group in SCCM. I'm not having success with this. What rights does someone need, to be able to use the Remote Control tool through SCCM? Thanks, Joe Heaton Enterprise Server Support Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: (916) 323-1284
