mcarriere893
Posts: 3626
Score: 300 Joined: 4/12/2002 From: Manitoba, Canada Status: offline
|
We use security groups to allow access via RDP or RA. Baisically IT technical staff have rights to RDP, and application support staff have rights to RA (allow them to shadow end user sessions for application support issues). Every use who wants access must request it, and they are given appropriate rights (via their justification). They are also notified (and some training if required) of their access rights (and warned about abusing those rights). We also provide these two tools via a custom web application (all users of SMS/ConfigMgr use the custom web app for reports, remote tools, etc, etc). Security is also setup so that if a user has RA access only, they can't even run the RDP button (they get a "no permission" message if they attempt to run). (simple button clicks/messages in the web app). We also have simple button clicks that show if the machine is on, a user is logged on, and WOL (among others). This is useful for the IT staff to help detemine how they will need to connect. Of course everyone is informed to always contact the end user before attempting any connection. Now of course they can run the tools without going through the web app (the web app does make use of unsolictedRCUI.htm for RA so they like using it), but without appropriate rights, they don't gain access. By default, local admins have RDP access (if it is not enabled, they can enable it right ), but I guess having it in a wrapper saves them a couple of steps to enable, and then disable. Might be a popular download on the site if you make a nice one. Edit: quote:
There is a secret way to start up RA without asking permission right? Don't knwo if it's a secret, but yes.
< Message edited by mcarriere893 -- 11/16/2007 8:49:16 AM >
_____________________________
Mark Carriere Microsoft MVP-SMS www.SMSUG.ca
|