Central Discussions

A support forum for users of Central.806 Posts

Forum Widgets

Recent Discussions

GoTo and Logmein's Failure to keep up with IT Needs - Microsoft ID Authentication
More and More computers are being setup with Microsoft ID Authentication and Logmein Central has NO METHOD to Authenticate! I have been a LogMein Central Admin for 10 years and have had no problem Logging into remote computer's connected to our Domain or had Local Profiles. If I did it was because I had the wrong username or password. The verbiage in the Authentication portion of a remote connection states: 'Enter the Windows user name and password you use when physically sitting at the remote computer.' Well that's just more and more wrong these days. New computers running Windows 11 and 10 are forcing setups to use a Microsoft ID and making it increasingly hard to setup a local profile. More and more computers are using Windows Hello. Biometrics, or pincodes are the only things users ever use to get into their machines. Both of which Logmein has no method to Authenticate with. This is becoming more and more frustrating as I need to connect to these PC's and GoTo / Logmein Support has no legitimate answer on how to connect! I am surprised there aren't more articles from frustrated Admins like myself. After this post I have to start looking for a GoTo/Logmein Replacement because it doesn't look like they are going to do anything or that they even recognize there is a problem. It's not going to go away it's just going to get worse as Microsoft moves farther away from local profiles.
CkGottafly
New Contributor
11 days ago
415Views
0likes
7Comments
Antivirus - Manage Section Bug
Hi, When accessing the Antivirus - Manage section, if you choose 'Custom View', go into a device, make changes, and then come back to the Manage section, the 'Custom View' is selected, but the view is not active, it defaults back to the 'Default View. Happens in all web browsers. This is a small issue but could definitely be improved and hopefully fixed quite easily. Thanks
HappyHippo
Contributor
13 days ago
23Views
0likes
1Comment
Issues Accessing Remote Computers from iPhone
Recently, I noticed that the LogMeIn App icon on my iPhone has changed and now I'm not able to access any of my computer remotely through the LogMeIn app on my iPhone. It keeps saying "Login Failed - Please check that you are entering the user name and password that you use to log into your computer." I'm entering my username and password exactly the same way as if I am sitting in front of my computer but it's still not working. Has anyone come across this issue?
Solved
Lox711
New Member
31 days ago
44Views
0likes
1Comment
Outdated and vulnerable OpenSSL v3.0.14.0 in use
Apologies if this has been asked already but I couldn't find anything relevant. Most of our LMI clients use an outdated and vulnerable version of OpenSSL (v3.0.14.0) This is way behind the current version of OpenSSL, what are the plans to update? Also, which is such an old version used anyway? Thanks Rich
RJ-user
New Member
2 months ago
34Views
0likes
1Comment
Cached Credentials no longer work?
Slower and slower computer connections... then broken screen blanking, broken multi-monitor support and now broken credentials caching? At first I thought it was my PC but now I am not able to used saved credentials on both computers I use on a regular basis - "Login failed. (1327) Enter the Windows user name and password you use when physically sitting at the remote computer." I'm getting so sick of LogMeIn... wish I had more time to explore other options... maybe it's time to just move on to ST.
Solved
LockonCC
Active Contributor
2 months ago
1.9KViews
2likes
12Comments
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.
Solved
anguss
Active Contributor
2 months ago
150Views
0likes
7Comments
Suddenly cant control client pc
I have been accessing a clients pc several times in the last 2 days to fix an issue. suddenly when i connect back on i cant control anything cant move the mouse or click on anything. this has never happened before its just this one client? what could have changed?
Solved
simonoestop
New Member
2 months ago
73Views
0likes
2Comments
Problema com câmera
My laptop's camera is not working, this error message appears Soon after I noticed this in logmein AV What can I do through the administrative panel or on the machine so that this doesn't happen
Solved
DiegoDash
Active Contributor
2 months ago
26Views
0likes
1Comment
command prompt issue
we are using logmein central. throur the logmein client when you click on the home icon then go through computer management and clicking on command prompt you receive the following error: error title: script error error header: an error has occured in the script on this page. Line: 1136 Char: 59 Error: the operation attempted to access data outside the valid range code: 0 URL: https://console-xlyfethvvn.lmi-app22-02.logmein.com/htem/htem_all.js Do you want to continue running scripts on this page? yes or no. does not make any difference what option you select. however, if we go via the loginme website and selecting command prompt it works with no issues. Does anyone have any suggestion on how to fix this?
Solved
sergen
New Contributor
2 months ago
2.7KViews
0likes
10Comments
macOS Sequoia 15.2 - LMI Run at Boot?
I feel like I have to be doing something wrong, but I can't figure it out. We got a new 2024 Mac Mini M4, and I'm working on configuring it to function basically the same as our old/existing 2019 iMac (which runs Ventura 13.7). I got LMI installed on the new Mini, I got all the permissions granted, etc. It works fine - but only after one of the Mac user accounts is logged into locally, and not immediately after system boot. Immediately after system boot, my LMI admin portal still shows the Mac Mini as offline (even though I am physically looking at the machine being online). If I walk over to the Mini and log into any of the Mac user accounts, then the Mini immediately shows as online in my LMI admin portal, and I can remote control as normal. If I then log out of all Mac user accounts (but otherwise leave the Mini powered on), it still shows as online in my LMI admin portal, and I can still access it for remote control. But now if I reboot the Mini, after it finishes booting (and I tried waiting a few minutes), it shows as offline and can't be reached. I wasn't expecting the "switch on" button to do anything at this point, and indeed it doesn't seem to. I tried: double-checking all Security & Privacy permissions, and they all seem to be granted. looking through LMI Control Panel to check for any settings seeming to be about boot behavior. uninstalling and reinstalling the LMI host software. checking for and installing all available software updates. checking for any LMI software updates (nope - host already on 13393) comparing /library/launchdaemons to the older iMac - they seem to match. using nano to examine the plist, runatload is set to true, as is keepalive. comparing /library/launchagents to the older iMac - the names of the plist files which are present seem to match, although when using nano to view their contents, it seems that they are a different format/structure (totally different content). googling and chatgpt'ing for help. I can't seem to find anyone else experiencing this issue. Can anyone recommend anything I might be doing incorrectly? Or is there any chance that Sequoia 15.2 broke something which needs to be fixed now?
Solved
etb
Contributor
2 months ago
164Views
0likes
3Comments

What's New?

Check out the latest Release Notes

Community Feedback

Did you find what you were looking for?