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 applyCommunicate with user at the computer before connecting
Can we have an option to send a message to a PC where a user is currently logged in. So we don't have to shut their sessions off or access their info. A chat windows where both admin and the user could interact, it will be preferable. (edited GlennD 5/7/25)
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.
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 affect all computers assuming that other computer manufacturers/OEMs follow Microsoft's push to Modern Standby. At least in my case, my affected computers will still successfully 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.
Sub-Groups
Sub-Groups Currently, each customer is a group. This works well enough. Some have a great many endpoints. Would be great if I could Sub-Group "Accounting" under "Customer-1". They could read like: [Customer-1.Accounting] AcctReceivable AcctPayable Invoicing AcctMgr [Customer-1.Production] South Mix Room North Mix Room Dry Room Prod.Manager Any addition in this direction would be appreciated.exclude sub folders for folder size alerting
it would be a great feature in the alerting section, to add a rule for "folder size" but excluding sub folders. e.g. i am monitoring a folder where i upload photos to, they than get processed and moved to a sub folder. when the main folder exceeds x amount of MB that would tell if the photos get processed or notLogMeIn 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!
