Forum Discussion
Solved
Mac OS Big Sur compatibility issue
With Mac OS 11 I can control the the Screen of the remote Mac, but when I click on the File manager Logmein crashes. Any Help would be greatly appreciated.
Hey everyone, thanks for your patience.
We've made the Mac beta version available for download publicly here (Big Sur compatible): https://beta.logmeinrescue.com/Files/TechConsoleMAC/LogMeInRescueTechnicianConsoleMAC.dmg
Full release depends upon how stable this is, so please let us know if you see any new issues.
A few basics:
- I'm using a corporate license and have no control over the technician console
- I can't speak on behalf of the company
- I've already alerted our IT for investigation on their end
- I've confirmed the issue on M1 and Intel Mac running the stated OS as well as within Parallels on an Intel Mac
- Technician console is running in Windows 10
Essentially, once the LMI.app is downloaded and the client attempts to launch it, nothing happens. You get the launch animation and that's it. I've checked in the System Monitor (?) and don't see LMI hiding in the background. I've tried enabling/disabling the OS' firewall as well as adding the applet to the white list. I've tried pre-adding LMI to the appropriate permissions. My instincts point me to the fact that the random PIN prevents LMI from being used from the App store, but that wasn't an issue with Beta nor 11.0.1.
Just adding that I Did successfully connect to an Intel MacOS 11.1 device today without issue, so now I'm a little confused as to what may be wrong.
Aries_LMI The Accessibility permissions on Mac should be the only hurdle to overcome there. Agents using Rescue to connect from Macs should utilize the beta version we just released (in this thread).
- Accessibility and Screen Recording in my case, but I'm having hit/miss issues with this version of the OS for some reason on my test bench as well. I've tried when the client machine is running on Intel/M1 hardware or Intel VM. After it's downloaded, the Mac acts like it's launching the app, but nothing happens. I've tried 6 browsers just in case (seems to be less of an issue with Edge?) and restarting the device/VM doesn't seem to consistently fix it simply being able to launch let alone ask for the permissions. I've even tried pre-authing the permissions and no change.
