Recent Discussions
LogMeIn Intune deployment prompting users for login on certain devices
Hi everyone, I'm currently facing a challenge with LogMeIn where, despite successful installations, certain users are still prompted to log in manually every time the application starts. On about 15-20% of intune deployments it seems to have this issue prompting users for login. This occurs even though we've configured the installations to include the DEPLOY_ID when pushing the MSI. Here's what I've observed and tried so far: Registry Checks: We've inspected various registry keys on successful installs and installs prompting users for login and have not seen any differences. I have also verified that our license key is being passed into our license registry. Installation Versions: We've confirmed that we are using the latest installation package directly from the LogMeIn portal, specifically intended for mass installs. Log Files: We've looked application log files for any errors that could explain the login prompts but found nothing out of the ordinary. Hardware Verification: We have also checked the hardware settings to ensure there are no underlying issues that could affect the software’s operation, and everything meets the necessary requirements. This seems to happen with models that it succeeded on previously. I have referenced the two articles/posts below as well. Trying to deploy from intune | GoTo Community GoTo Resolve unattended MSI deployment in Intune (Microsoft Endpoint Manager) - GoTo Resolve Support Would there be any way to check any of the client install files or any registry keys that may point us to why this failure occurs? Thank you in advance.
Pre-Host Connection 2FA for Technicans
Hello Is there a way in LMI Central to force all IT Technicians accessing client host agents (EUC or Server) to receive a 2FA authentication code via text or email before a connection is made. They either and/or use the Web Client or LMI Client. So put another way, when they go to remote control a PC or Server (with correct credentials cached) it would always send a 2FA before the connection is made. Thanks TimConnected laptop acts entirely different when lid is open versus closed
I recently purchased an ASUS laptop and added it to our Central account as a device to connect to. Laptop is Windows 11 Home, and it has integrated Intel Xe graphics. No dedicated GPU and no external monitors hooked up to it. The laptop was configured to never go to sleep when on AC power, and power mode was set to performance. The first two days of use had no issues. The lid was closed, and I was able to do my work remotely. Immediately after two days I noticed the following behavior: Some of my Windows programs and folders will either open or not open. File explorer will not show at all. Entirely a hit or miss on what will open. The Start menu will not display when clicked on. I can open a program like MS Edge, but I cannot close it. I can Alt+Tab to see the available open windows to cycle thru, but it will not display the window I want. Here's what happens next... When my laptop lid is opened, all of these windows and registered clicks will then work. Meaning that instance of MS Excel I tried to open or File Explorer will pop up multiple times. Basically, it appears everything decides to "work" once the laptop's lid is open. Before anyone says it's the laptop, I hooked up an external monitor to see if it has to do with the lid being closed at all. I can confirm the issues are NOT repeated with an external monitor. Laptop works like normal. We have a Dell Latitude laptop connected to our Central account, and after turning off all the sleep settings etc.., that one has no issues when the lid is closed. Apps and windows work perfectly fine. It also has an integrated Intel GPU (I forget if it's Xe or an older chip). So, in short, I need help troubleshooting why this is happening when the lid is closed and connected to Logmein and how to make it work while keeping the lid closed.
Reports not tracking session end time
I am running a report of user and device logins for the previous week. Nearly every single entry states that every session lasted a number of seconds (Anything from 5s to 40s) only. Any ideas on why this is the case (I know the sessions lasted much much much longer than a few seconds) before I have to call support?
Username for remote controlling AzureAD/Entra/Intune computers seem inconsistent and unpredictable.
I still have a lot of Windows 10 computers on my network that are domain joined. LogMeIn Central is very easy with those. I can sign in with my (domain admin) username and password to access any of these computers. I'm talking about the "Sign in as you would if you were sitting at the remote computer" prompt here. When I buy new Windows 11 computers, I do not join them to the domain. I just sign in to 365/Entra/whatever the right terminology is. If my initial sign in name is my own username and password, then I can remote control with that. If my initial sign in name is the user's, there is no guarantee that their username and password (which I do not have and do not want to ask for) will work, and I have to create a local admin account and remote with that. If I sign in as myself later, again, no guarantee that it will work. One one instance, the only username that is accepted is AZUREAD\UsersFullName. This is super wacky because UsersFullName is neither their username, their UPN, nor their email address. Clearly I am doing something wrong when provisioning these devices for LogMeIn. Any advice?
