Jump to content
BlueToast

Control Center fat client in RDS environment with non-administrative users

Recommended Posts

Has anyone successfully gotten working the ConnectWise Automate Control Center fat client within their RDS environment for users who do not have any local/domain administrative rights? If so, how?

Share this post


Link to post
Share on other sites

Try adding "Full Control" permissions for the users on the following folders.

 

C:\ProgramData\LabTech Client\

C:\ProgramData\LabTech PlugIns

C:\Program Files (x86)\LabTech Client\

Share this post


Link to post
Share on other sites

I tried this a long time back on workstations and it never worked. Support were useless and just blamed it on some unknown plugin, despite having no plugins enabled. The problem has been consistently present in every version going back a couple of years.The problem turned up after one of the releases but I can't remember which one.

 

  • Sad 1

Share this post


Link to post
Share on other sites

We do, in fact, have the desktop CC client running on our RDS for non-administrative users. It's not fun, but for our Mac guys who have been left in the lurch by the migration to Automate... it's what we've gotta do. Once we get the software running (a lot of "run as Administrator" during initial setup, and every time there's a patch update to the client) it seems to behave okay. It's mostly a case of run-as-Administrator until you don't need to use run-as-Administrator to get in anymore as a local admin account, at which point non-admin users seem to be able to run it again.

Yeah, that's a bit confusingly worded, sorry.

Share this post


Link to post
Share on other sites

This is an issue facing me at the moment.  I want to do a server upgrade (we're two versions behind on Automate) but a stumbling block is the requirement to enter local admin rights to allow the fat client to update the first time it's launched post-upgrade.  Traditionally someone would 'nip' around the office of 50 users and put in their credentials, but in these current times that's not really practical.  I've tried relaxing permissions on the ProgramData\Labtech folders and registry keys but the 'Downloading dependencies' stage always demands local admin rights.

If anyone's got a workaround I'd love to hear it.

 

Share this post


Link to post
Share on other sites
Posted (edited)

Just came across this thread.  We have been running all LOB applications - Manage, Automate, password server, web apps, EVERYTHING - via RDS/RemoteApp for over 4 years.  We lock down destination (e.g. Cannot login to Manage from anything other than RDS server / Have RDS server use specified/exclusive IP on our gateway and then lockdown webapps to only allow traffic from that IP). No logins from anywhere but our data center.  This provides a lot of comfort and not worrying about anyone doing anything crazy.  Also, do not give your team ability to be local admins - EVER - as there is no reason.  With the RDS server, they don't need it.  As for the challenge of the applications and permissions, whenever there is a patch we just update the app on the RDS server.  No permissions issues whatsoever as the next time the user logs in, it's already updated.  

Edited by Rmanyc

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...