Lock host upon disconnect
I find it odd that RESOLVE does not have an issue to lock the host upon disconnect like other LogMeIn products have (Central has this). This is a BIG security issue because if I am using RESOLVE to work on an unattended host and my connection drops, that leaves the host computer wide open (especially if I am working on it with an Admin user). This is PARAMOUNT. My work around is I created a remote execution Powershell command to lock the computer. Then I have to run it once I disconnect. CUMBERSOME! RESOLVE has so many features that I find this a big overlook.
Site Filtered Login
Would like a function so an admin at a separate site of the company can sign in and work with items only in their location. Ex. Joe at Plant 1 can see and change Plant 2 and 3 devices. How can Joe sign in and see only Plant 1 but be able to add/update/delete/enroll devices as needed?
Dynamic groups and areas to use them
We would like to see Dynamic groups, that can be set up using a keyword, device category, Device manufacturer etc. These groups could then be selected for Remote Execution jobs or Policies. This would save time and guarantee that a new device is automatically added to the jobs in this area. For example, when setting up a Remote Execution or Policies, instead of selecting a device, you can select a Dynamic group. The system then will apply the jobs against these groups and any devices within them.
Allow User Groups to be assign permission to device groups
Hi All, I have a suggestion that I think would help streamline the provisioning and user management processing in GoToAssist/GoToResolve, allowing user group to be assigned permissions to a device group. The primary efficiency here would be that you can assign a single user group to multiple device group and thus lower the amount of user configuration needed to a single assignment. For more advanced enterprises this change will also allow automatic provisioning, which can already add users to a user group on creation, to provision access to device groups with zero administrative interaction. In organizations that have role based access control implemented this could result in a true zero touch identity architecture for GoToResolve. Suggestion Example: User Group 1 has access to Device Groups A, B, and C User Group 2 has access to Device Groups A, B
