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.