The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
dac72
7 years agoActive Contributor
MacOS Catalina Support
Does the current version of LogMeIn Pro support MacOS Catalina? Just upgraded to Catalina last night and I am able to remotely connect to the device device, however, I cannot manage it. When I c...
- 7 years ago
Ok, I ran the uninstall script and completely removed logmein, downloaded it again and this time it comes up as the 64bit app version 4.1.7151.
Would be nice if LogMeIn was a little more clear about this!
Jazmine_Clough
6 years agoGoTo Contributor
There are permissions that need to be set when the client or the host machine is a mac Catalina or a mac Mojave. The first thing is thing is to go to system preferences then security and privacy then accessibilty, Click the lcon to make changes.
Put a check mark in LMI Gui and AEServer and Bash if you see that.
Next go down to full disk access and put a check mark in the same. LMI Gui or Bash pr both
Then screen recorder , check that off as well,
then input monitor
All files and folders and Full DIsk Access
You will see the LogMein Control panel icon in this folders, PLease check mark them and then click the lcok to make changes.
Save then try again.
This information is from a LogMeIN Support Staff.
computica
6 years agoNew Contributor
I've found that adding or ticking the check for LogMeIn in Accessibility and most importantly, in Screen Recording (after Catalina) worked. You don't mention LogMeIn.app. I have that in my list and that is checked on.
I have AEServer in my Accessibility and that is NOT checked on. What exactly does that do?
Being that there are several items in System Preferences that need to be checked, maybe it's best that we get a definitve list. And better would be that LogMeIn does all the check boxes or walks us through all of them like it does for SOME of the settings.
Here are all the possible ones I can find:
Microphone
LogMeIn.app
Accessbility
AEServer
LMIGUIAgent.app
LogMeIn Client
LogMeIn.app
Full Disk Access
LogMeIn Control Panel
LogMeIn.app
Files and Folders
LogMeIn Client
Downloads Folder
Documents Folder
Desktop Folder
Screen Recording
LogMeIn.app
I'm working fine with the way mine are set now, but not all of them are checked on so it would be nice to know what all of them do and which are needed on, since I don't have AEServer on and I'm working fine for what I need to do.
- SW416 years agoNew Contributor
We also need to adapt the solution to use Jamf to manage the Macs so they can accept sessions with logmein.
- dac726 years agoActive Contributor
I have this same issue on several of my machines, afer many attempts to fix it on my own I finally called the logmein support line for advice. I spent over an hour troubleshooting this issue with them and in the end they were totally useless and blamed it all on the MacOS. When it became clear they ran out of things to "try" they became rude and told me it was not their issue and deferred me to Apple. This is clearly an issue with their software but judging by their attitudes they have no intention to address it. This last support (lack of support) experience was the final straw for me with this rediculously overpriced software, I will not be renewing my subscription to this service after it expires.
BTW... its comical to see that I was the one who started this thread back in October 2019 and there is still so much activity on these MacOS issues, all the while LogMeIn has done nearly nothing to correct their software to help their customers.
- djzlmi6 years agoNew Member
I have Catalina 10.15.2. Have installed 64 bit version of app. Every time I restart computer, Security and Privacy in System Preferences opens up. I have all the requisite boxes checked off (and in fact remote control works from another computer), however after 10 restarts, the Systems Preferences dialog opens. I have checked login startup settings and dock settings, and Systems Preferences is not supposed to open upon startup. I have installed and reinstalled LogmeIn several times.
Please advise fix.
- Jazmine_Clough6 years agoGoTo Contributor
In the Mojave/Catalina OS
Go to System Preferences: System and Security, Privacy Tab then go to
Accessibility,( Click the lock at the bottom to make changes), enter credentials, then put check marks anything LMI(LogMeIn or G2p GoToMyPc Related (for your plan, including gotoassist if subscribed) also look fo BASH (very important for mouse control)and AESERVER ,
Then go down to all other folders expecially Full Disk Acces and SCREEN RECORDER put check marks.
Click lock to save changes, and then restart if that doesnt work go back again two more times Restart go back to system preferences, and that should, do it.If you are having any trouble installing, then get rid of any antiviruses.
- Jazmine_Clough6 years agoGoTo Contributor
Full Disk Access is when we are remoted in with the client app and need access to the machine, If you see LMIGuiAgent or Logmein in there, pleae put a check mark in there and click the lock at bottom to save changes.
- ahankins6 years agoActive ContributorWhat is the Full Disk Access permission for? LogMeIn seems to work just fine In Catalina without it and I don’t think it’s a good idea to advise users to blindly allow full disk access without providing a reason.
- Jazmine_Clough6 years agoGoTo Contributor
Thank you for contacting LogMeIn.
Anyone who has Mojave Mac or Cataline is advised to go to System Preferences, Privacy and Security, then Privacy tab then Accessibility on the left, click the lock to make changes, enter Mac Credentials, then make sure check marks in LmiGui Agent and Lmi then go down to Input Monitoring, put check marks in anything lmi related. go down to Screeen Recorder and do the same instructions and then full disk access.
So total you should be looking for Accessibility, Input monitoring, Full disk Access, and Screen Recorder, and checking off anything LMI(logmein ) related.
If that doesn't solve the issue, then restart the Mac and go back to these instructions