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.

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.

Find more posts tagged with

Accepted answers

anguss

So I figured out the issue with our installation failures. We added some PowerShell logging to our installation process and realized that a mutex lock lock on another process was taking up a resource needed for the installation to go through correctly.

Thank you!

All comments

GlennD

@anguss Thank you for returning and updating us. I'm sure this will help other customers in the future.

anguss

Hi Glenn, thanks so much! I will work with support on this and be sure to post the solution here for anyone that may need it for future reference.

GlennD

@anguss I've opened a ticket for you with our support team so they can connect with you directly and investigate.

anguss

Hi GlennD, Thank you! The previous version we were deploying was 4.1.15732, and auto update is enabled on hosts, which I then verified certain hosts updated to 4.1.15880. I tried repackaging the MSI installer with version 4.1.15880 straight from the LogMeIn portal and deploying it, but the issue still persists.

GlennD

Hi @anguss, the consensus is that for some reason the deployID was not assigned to the affected computers when they were set up. Can you please let us know which version/build of Central you are deploying and if the hosts are set to update automatically or not?

GlennD

Hi @anguss, welcome to the community.

I am sharing this internally with the broader team to see if we have any Intune experts.