Support for Modern Standby
LogMeIn (LMI) apparently currently does not support wake on LAN (WoL) functionality for any computer which uses "Modern Standby". Here's a link to Microsoft's website for some background info. According to this document from Dell (link), Dell will no longer support disabling Modern Standby. So that appears to indicate that LMI will no longer support any Dell computer going forward. Realistically, at some point this could affectall computers assuming that other computer manufacturers/OEMs follow Microsoft's push to Modern Standby. At least in my case, my affected computerswillstillsuccessfully wake when they receive the WoL packet from any other tool. So although complete and full LMI support for Modern Standby might take some time to develop, it seems like a workaround could be implemented by LogMeIn developers in the meantime. Since these computers do successfully respond to WoL packets, it seems like it should just be a matter of making the LMI servers believe it so that they can send the commands which generate the WoL packet. I can provide more details, talk to developers (or whoever), maybe even help beta test if desirable. But please add support.
Logged In User integration into LogMeIn Client and Central
While we do have some computers that only is used by one user, alot of our computers are used by multiple users. Instead of naming each computer in our computer list with the name of user + hostname. It would be great If one of the fields in the list of computers in Central and the LogMeIn client was Current Logged In User. Than we can have it searchable in the search bar in central and the logmein client app. This way we can remote into computers without asking more questions to the users or getting them to follow instructions. It's not something super important but it would be a nice to have.
LogMeIn Client credentials
We would like the option to NOT allow users to save their LogMeIn credentials in LogMeIn Client. Allowing users to save those credentials on their remote computers lets them bypass the requirement for multi-factor authentication each time the log into their work computer. Or is there another way to remove those credentials daily and force them to log back in with MFA daily? Thank you!
View client names when using update module
when selecting devices inside 'Updates' > 'Applications', be able to see the device names which the updates are going to apply to, same goes for the 'Updates' > 'Windows' area. The history tab should also show what software has failed to update. For example; i've selected multiple devices inside 'Updates' > 'Applications' and clicked 'Apply Updates' - see image below, it doesn't show which devices are getting what update: History tab does not show what software updates have failed to apply:
Invite Another Agent to an Ongoing Support Session
We have computers at end customers that are primarily serviced by a local dealership that logs in remotely. When the local dealership cannot solve a problem we log in to try and solve it. It would be very beneficial if at that time the dealership could still be logged in as well (view only) so they can see what we do.
Patch Management
The ability to ignore or disable specific updates would be nice. We currently run Windows 10 machines as we are in the process of testing Windows 11 and it has become more tedious to send out OS updates because I have to individually select all of the updates and then unselect the Windows 11 update. This isn't a problem with a couple computers but with 80 its tedious and time wasting.
Help Desk wishlist
I love the platform so far and understand it is still in it's growing phase so I'd like to offer some ideas. After using other Help Desks for about the last 16 years, there's I have a few things that I have found helpful in the past that I would love to see implemented in GoTo Resolve. Ability to close a ticket when a comment is added. Something like a simple check box to prompt the ticket to be closed when the comment is added. Ability to add checklists to tickets in order to track work within a ticket. For example, when a new user needs to be created, a checklist of all the common items that need to be done for this task. Ability to merge tickets. If a ticket is opened by a user and another user is CC'd on the ticket, both parties should be able to comment back to the same ticket. Right now if a user requests permission change and CC their manager on the ticket email, when the manager replies back approving/denying the request it creates another ticket.
