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
Be able to apply App.Config files or settings based on the Session Group(s) a computer is in.
CW#7546987
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Can this option be split in 2 sections one for servers and one for workstations or have it auto hide after a certain time?
We too would like to separate servers from workstations so we can apply the "AccessLockMachineOnDisconnect" to servers but not to workstations when disconnecting. Ideally we'd like to add a value to custom property, as our servers are spread across several groups and applying the setting to just one group is not ideal, where as creating a custom property (for example IsServer : True / False) would be perfect.
Yeah, that's exactly what I'm looking for, too, Trevor! We're currently working around it with an LabTech/CW Automate script that swaps app.configs on servers, but would be nice to have it built in.
I would like to see this available both ways. Based on a custom property would be very useful for things like servers but I would also like to specify different app.config settings based on a group. One example of this would be that we currently allow technicians in with no prompt for access as they are often remoting into machines that do not have someone at the box but we do not want this action for say a group that contains all of the VP's or HR's computers where they may have access to sensitive information.
Yeah, that's exactly what I'm looking for, too, Trevor! We're currently working around it with an LabTech/CW Automate script that swaps app.configs on servers, but would be nice to have it built in.
Would you be willing to share the script you have that swaps this? We're trying to have AutoLockonDisconnect enabled on servers, but not on workstations. Any help you could provide would be greatly appreciated.
Would you be willing to share the script you have that swaps this? We're trying to have AutoLockonDisconnect enabled on servers, but not on workstations. Any help you could provide would be greatly appreciated.
James,
See if http://forum.screenconnect.com/yaf_postst10827_Extension--Selective-Lock-on-Disconnect--6-3.aspx can be of help.
The #1 use case for me is AccessLockonDisconnect. We use that on servers and turn it off for workstations. I have my servers and workstations in separate session groups and it is a pain when I go to update or install Access as I have to change the app.config depending on which it is.
AutoLockonDisconnect, the extension isn't useful for us currently as we can't afford the time to manually go through the hundreds of servers to change this setting one at a time.
HideWallpaper, ShowBalloon, Consent, BeeponConnect, etc are some others that make sense on workstations but not servers or vice versa.
I would really LOVE to see remote printing control moved to an app.config setting instead of system wide web.config, and this would be a great thing for that as well. We have to disable this system wide as im sure 99% of partners do because of the issues it causes but there are a few clients that use Control/Automate to connect back to their workstations at the office and would really like remote printing and I would like to give it to them but I can't currently. I would also like to disable toolbox and many other settings (most of the bitmask features) for these users.
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!