Be able to apply app.config settings per session group

Avatar
  • updated
  • Under Review

Be able to apply App.Config files or settings based on the Session Group(s) a computer is in.

CW#7546987

Duplicates 13
Enable or disable AccessShowUnderControlBanner depending on session group

I want to use the AccessShowUnderControlBanner only if consent from the client is needed.

At the moment, I have two different session groups in use. One needs consent from client, the other one (for servers) does not. If I connect with a client, it would be nice to get a banner on top which indicates I'm connected with the machine at the moment. On servers/own desktops I don't want this bar.


Please extend the AccessShowUnderControlBanner option, so I can choose on which session groups I want the banner enabled/disabled.


Thanks!

Customize groups for app.config

I would like to be able to create customer groups that will allow me to apply different app.config files to them. For instance most times I want the screen to lock on exit, but not on my Kiosk screens.

Disable Connection Notifications for selective machines.

I understand that there currently exists a series of settings to disable the connection banner and the system tray for Connectwise Control, but these are only at a global level. I'd like to be able to disable these features for selective machines. 

Hello, add feature to request control per computer
Apply app.config changes to specific clients

We would really like to have the ability to make changes to the behavior of Control for several clients without effecting the configuration for all of our other clients.

Advanced Settings at the Company or Computer level

I would like to request making changes to the Advanced Quick Settings and Other Settings at the Company or computer level so it is not a Global change for all of our clients. One of the settings is to Lock guest machine when host disconnect and another one is Automatically lock the guest machine when a host connects, however we cannot enable this Globally as some customers need both the end user and the person remoting in to see the screen. It would really help if we could make setting changes at the Company or computer level. Thank you.

Selective disable of features on a per company basis

I would like to be able to set some features to be unavailable on a per company / per client basis.

I have some clients where people aren't using the chat feature as it should be used and I'd like to disable the chat feature for just these clients as I do use it well with other clients......

I know it's not possible now, but I guess it shouldn't be too hard.

App.config files based on session Groups vs Global

We have 2 ConnectWise Control on-premises licenses used for our medical data portal where our users have various needs based on their "group" for screen sharing, remoting in, other controls that some need and others have no business having certain control access.  Our solution initially was to buy more licenses since App.config files are "global" but that is not practical.

Other companies like Splashtops allow the streamers deployment to be based on "groups".  This makes so much sense and I would think that the ConnectWise "client" could also have a grouping based on the app.config file.  In our case, it would not be practical nor feasible to buy a license for each individual company that wants to make a few changes to how they see and use the ConnectWise Control.

Please consider adding this ability.

Session Lock by Access Session Group

I am looking at setting up a specific group of machines with access sessions. I would like to have these sessions lock whenever a technician disconnects from the session. I see that there is the option to set this globally for all access sessions. I would like a feature that would allow me to set this option for only a specific access session group.

Using Control via Automate - Specify tailored app.config for a couple of different Clients

We use Control through Automate and would like to be able to apply different app.config settings for a couple of Clients.  I see there are similar requests but wasn't sure if I should raise my own.  Happy for it to be bundled in.

Allow disable guest input and blank guest monitor to be set per session group

Be able to set disable guest input and blank guest monitor per session group.  I would like to be able to target specific groups and not allow guest input and blank the guest screen, specifically servers)  Currently they are global settings that apply to all machines.  I would like to be able to set them at the session group level for more granularity and control.

Gain the ability to change default session settings by user group - Not just globally

I would like to be able to apply the following settings per user and not just globally

-Blank the monitor

-Block guest input

-Automatically lock the screen on disconnect

I need to apply these security settings to remote users but not all technicians for security reasons.

"your computer is being controlled by" disable for server but enabled for workstations

Can this option be split in 2 sections one for servers and one for workstations or have it auto hide after a certain time?

Avatar
0
Joshua A. Szántó

Please bring this to CWC ASAP. Example real world scenario: "lock on disconnect" (an important security feature) prevents digital signage display machines from fulfilling their role.

Michael Legato (CW) linked me to this enhancement request.

Avatar
0
Ron Muttillo

This is desperately needed!  Like 10 years ago.  Some clients require servers to be locked on disconnect for security reasons (enforce), but not on workstations (for obvious reasons). I mean best practice would be to enforce lock on disconnect on servers anyway, and you would not want to inconvenience a user by locking their workstations every time you disconnected after helping them.  Also Law Enforcement clients (LEADS compliancy), as one example, require the consent when accessing their workstations, but not all clients require this consent. Nor would servers, obviously.

Avatar
2
wadekingston

This feature would elevate control in my opinion more than any other feature request. I do however think that this issue touches on several other issues. We need the ability to manage app.config settings on a session group basis but also, the application server should automatically send an updated app.config to the corresponding agents anytime there is a change to the settings. It is not feasible and is irresponsible from a network utilization standpoint to require the agent be re-installed just to get the current settings. When you have hundreds or thousands of machines, and you multiply that by 2-4MB, the bandwidth required to handle these requests is immense. Alternately, an app.config file may only be 2KB, this is a huge difference. The alternative is an extremely clunky solution to manually manage app.config files on machines and hope that the agent doesn't get re-installed. In addition I think it would be helpful if the app.config file had a switch where we could specify commands that would be executed automatically upon connection for example, blank guest screen and block input. I envision managing servers where the screens blank and input is blocked upon connection and the session is locked upon disconnection. If we control these items at a session group level, much like the security role hierarchy allowing for inheritance etc, ConnectWise Control would gain so much functionality and be far superior that it is today.

Avatar
0
Shirley

Please make this happen! Thank you!

Avatar
0
Preston Eaves

This is SO needed. Can y'all please make this happen? Please and thank you!

Avatar
0
Erik van Putten

If setting it up per group is too hard, having the option to have multiple app.config sets,  and than per agent assign which app.config to use would also work.(Naming or Numbering the App.config sets)

Groups can overlap, per agent would take care of that problem.

Avatar
0
Brandon Wilcox

We are also looking for a solution for this issue. Our use case is slightly different, but the need to customize the session by computer or user is there.

We want Administrators (supervisors or management) to be able to connect "incognito", meaning no banner, pop up notification, suspended input, etc.

We do not want all Hosts (technicians) to have this ability.

Avatar
0
Kilo
Quote from Erik van Putten

Come on, this has been promised already years ago. Put it on the road-map instead of just considering it.

This really makes the product so much more useful and sell-able (the last both for you and us)

We have several different views from customers on Control. Those who want the icon to show those who dont. Those who want to allow remote control consent and those who dont mind.This would fix those issues and o so many more.

Couldn't agree more....  Have been actively considering other products because of this

Avatar
2
Erik van Putten

Come on, this has been promised already years ago. Put it on the road-map instead of just considering it.

This really makes the product so much more useful and sell-able (the last both for you and us)

We have several different views from customers on Control. Those who want the icon to show those who dont. Those who want to allow remote control consent and those who dont mind.This would fix those issues and o so many more.

Avatar
0
Grant (AU)

We would like to see this so we can present different features, icon, banner etc to different clients and different options to servers vs workstations



Top contributors

Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar