Be able to apply app.config settings per session group
Be able to apply App.Config files or settings based on the Session Group(s) a computer is in.
CW#7546987
Welcome to our community!
Duplicates 13
Enable or disable AccessShowUnderControlBanner depending on session group
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?
Replies 40
Some settings that would be useful on a per session group basis:
- AccessLockMachineOnDisconnect: While we would like this on POS machines, servers and such, for user computers around the office this is generally not the way we want to leave a support session after helping someone.
- AccessShowUnderControlBanner: We would like this for personal computers for executives, corp office etc but would not like to have a store know if we are monitoring a POS or store device.
- Change certain Commands: On executive and corp employees we do not want a tech to have access to Block control or blank a users monitor, yet these can be essential when trouble shooting a POS or store computer.
Thanks
Two factor authentication for a group of users with sensitive data, so that remote access needs to be explicitly granted by them (they have the authentication codes). This is the only solution where they can grant access without being present at the machine, but tech cannot access at will
Without digging to deap these are the 2 options that jump out at me as something we'd like to control at group level. Idealy we'd be able to to control all options that affect how the agent works/allows connections or responds to them from the group level.
Lock machines on disconnect: we have servers and workstations that are unattended no one uses them and we'd like to be able to lock these on disconnect.
Ask for Consent. - We have workstations and servers which are unattended and we'd like to be able to connect to these without consent but all users machines we want to default/continue to ask for consen.
James,
See if http://forum.screenconnect.com/yaf_postst10827_Extension--Selective-Lock-on-Disconnect--6-3.aspx can be of help.
I looked at this, you have to use a GPO/Script/Labtech/Automate anyways to deploy the system variable that plugin needs based on your criteria for which machines need which settings. I got that working and then realized it would be easier to just distribute the app.config files and restart the service so that's what I'm doing now until you guys can get this feature in place.
Hello guys. I was told this is where I should post this. Basically i'm looking to set individual permissions for my users. Specifically myself and my supervisor prefer to connect as view only to machines first​ before we take control. Here is our scenario.
1st, Employee places a helpdesk case on an issue.
2nd, We connect within 5 minutes of the case being opened as view only.
3rd, We evaluate if the user is still on the stuck page they opened the case on or if the user is working feverishly.
4th, If the user is on the page, we switch to take control and start fixing the issue,
5th, If the user is busy, locked or away from the desk, we then contact the user to find out more information.
View only allows us as technicians to get an in depth look into the problem before we connect to see what is actually going on and how we need to actually fix the issue.
However not everyone in our organization needs this permission. What I want is a choice to startup in view only or control mode. and I want to lock this down by not allowing everyone to have view only permissions. My other 15 techs will not need that view only permission. I'm told right now that Suspend Control At Startup is the only way to accomplish this. But it affects everyone, not just myself and my supervisor, So we need a way to set this just for us since that is how 99% of the time we connect is view only and everyone else is 100% connecting by control.
Also as a side case, When my current solution switches between view only and Control, I can tell at a glance which way my session is. In my current solution the menu bar at the top of a control session turns red if it is view only and the mouse pointer turns to a red circle with a line through it to further indicate it is view only, If in Control mode it stays a grey color. I typically work on up to 15 machines at a time in different sessions, So being able to tell which one is view only and which one is in control is a huge deal for us.
Also View only allows for us to allow a 3rd party tech into our systems and allows us to go view only so we can work with the tech via phone calls and not disturb his mouse movements. So being able to see that as red as an indicator it is view only is a huge help is us not making a mental mistake and messing up a tech working for us.
Just wondering if this suggestion would work for your suggestion if ever implemented:
If so, give it a thumbs up and maybe we can get movement on it with the ConnectWise team.
I want to confirm that this feature request, if/when implemented, will also allow for a custom app.config at the user level in addition to at the group level? Or should I create a new feature request, or should I decouple the existing per-user request in the duplicates listed on this FR?
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!