MeshCentral
MeshCentral copied to clipboard
Ylianst
Update MacOS Agent instaler (MeshAgent.mpkg)
Hello,
we find out that we are not able to do anything on connected Apple devices. We just see the desktop, we are able to move with mice but we can not click on anything and we can not see any open windows.
Terminal a and files work properly.
We are using macOS Monterey v.12.1
Can I ask you to check it?
Thank you!
Did you enable the permissions requested on macos? There are two separate ones. If you only accept one of the two, I think is when you get the scenario where you only see the background.
Yes, I have allowed meshagent_osx64 in Security & Privacy - Accessibility and Screen recording. Should I have it also somewhere else? Thanks
And I'm still getting this message.
I found that someone install Agent via wget but it also doesn't work https://issueexplorer.com/issue/Ylianst/MeshAgent/104
I haven't reproduced it, but I will try a clean install with my Monterey System. Let me get back to you.
Same here Intel MAC with Monterey 12 and 12.1. On connect system is always asking for Screenrecord but it is already granted. Just Desktop-Background and Mousemove, no Windows at all.
Same here! permissions already granted but keeps asking on every connection
Same here Intel MAC with Monterey 12 and 12.1. On connect system is always asking for Screenrecord but it is already granted. Just Desktop-Background and Mousemove, no Windows at all.
I'll take a look on my Monterey System. One thing I've seen on occasion, is that the gatekeeper gets confused with permissions, as I've noticed that the UI is keyed by app name, but the actual permission is keyed by file hash. This can cause issues when the app binary is updated. I've filed a bug against Apple, but they never responded.
Anyways, I've seen scenarios where the permissions are messed up until you delete all the permissions for the app, and let it re-request permissions
In this case, it's not the agent causing the issues, but the OS itself that is getting in a wierd state
Is there an update on this? 3/22/2022 on M1 MacBook Pros' still doing the same thing. Even though permissions are granted.
Have you tried removing all permissions, and letting it re-request the permission?
Have you tried removing all permissions, and letting it re-request the permission?
Yep. Two computers for test purposes, same issue with both.
Not yet. But I'm going to work on seeing if I can sign the macos agents, which should help with the permissions aspect of things.
Hey all,
I was about to make a new ticket about this, but found this. I've been experiencing similar issues. On some it's the above where there's just the desktop and we can control the mouse, but can't see anything regardless of how we enable permissions.
On my new 14" Macbook Pro, I'm only seeing a black screen in MeshCentral and do not have the ability to move the mouse. Please let us know if we can forward any log data.
Have you guys tried downloading the binary installer and using that to install the agent, instead of the package installer? Does that make a difference for you?
Hi Bryan,
I have. On MacOS 11, this seemed to fix my issue on my M1 Macbook Air. Once I replaced the universal binary with the Arm one, things began working, but so far on both Intel and Arm I haven't been able to MeshCentral to work with Monterey.
On a side note, we have a handful of clients running Mac, and Monterey in general has been REALLY difficult to deploy things like screen sharing on. The solution for some apps has been going into system recovery and disabling SIP.
Actually now that it crossed my mind, I'm going to try it now to see if it fixes this issue.
Ok... I can definitely confirm this is a binary related issue. At least on my M1, the only agent that works is the x86 binary, the Universal and Arm binaries both endlessly ask for permission each time I try to connect.
Same here on Monterey on a M1... it seems that the binary works fine, you need to install homebrew first
I've got the same issue here. A brand new Macbook Air 2020 M1 running the latest Monterey 12.5 and installed the "Apple macOS Agent (64bit)". continuous popups asking for screen record permissions.
@matt-cylanda you made reference to the x86 binary. what am I selecting to get this? If I select "Linux / BSD / macOS Binary Installer" the only Apple download i can see is "Apple OSX Universal" which i think you mentioned does not work.
UPDATE: i uninstalled the previous "Apple macOS Agent (64bit)" and i've installed the "Apple OSX Universal" (via the command line) from "Linux / BSD / macOS Binary Installer" and now that's working as expected. the machine already had Rosetta v2 installed from another package if that's relevant.
SECOND UPDATE: with the agent i have installed now, i can't see the screen when it's sitting at a login prompt. i had to use ScreenConnect to remotely login to the Mac. once logged in i was able to disconnect/reconnect from Mesh and the desktop appeared.
side note - after uninstalling the "Apple macOS Agent (64bit)" using the procedure here: https://github.com/Ylianst/MeshCentral/issues/365 i note that "meshagent_osx64" still exists throughout Security & Privacy. the universal agent i installed above appears as "meshagent". not a big deal, but i just thought I would mention that the uninstall didn't remove that. perhaps that's just a Mac thing?
Exactly the same problem here.
I have a MacBook Pro 16 M1 running Monterey 12.5.
The normal "Apple macOS" client installs fine, but every time you try to use Desktop > Connect, you are prompted with this and it never works:
Using the Apple OSX Universal client works, but it's no where near as elegant.
We have a large user base of M1 Macs and I can see that this is going to be a major issue if we try to move them to MeshCentral @krayon007
So if I understand correctly, when using an M1 Mac you are only seeing issues with the arm binary but not the universal or Intel binary?
When using this one (macOS Agent (64bit), remote control does not work. Each time you are prompted to grant access.
When using this one, everything works, however it just installs wherever you have downloaded it. I cannot find any information on how to get this to work in the same was the the macOS Agent (64bit).
The ideal for me @krayon007 would be for the macOS Agent (64bit) to be updated so that it works correctly, as a .pkg is much neater for mass deployment.
Interesting. I may have to update my M1 to Monterey Mine is still on Big Sur and works fine with all the binaries.
That would be really helpful if you could, as we are looking to roll this out for all of our clients, but a lot of them are using MacBook Pro M1 with Monterey.
Keep in mind that Apple Macs with M1 chip are not 64bits, they are M1 (Apple Silicon) an ARM architecture, macOS agent 64bits is not going to work on M1 macs as they are different architecture...
Yes, but it does work when Rosetta2 is installed, with the exception of remote control.
Would an Apple Silicon build of the .pkg be a possibility please?
hey gang, just looking at all the mac issues now as somebody kindly donated an M1 to fix bugs! has anybody found a way to actually get the remote control working on M1 12.7.2 ? ive tried the mpkg and the binarys and they just dont wanna work? if i can find a way to get it working i can look into why it needs to be done that way
Yes, after many attempts I got it to work with macOS 13 Ventura. If I remember correct, it was this way: https://github.com/Ylianst/MeshCentral/issues/3397#issuecomment-1198706281 and myabe you have to install rosetta first: sudo /usr/sbin/softwareupdate --install-rosetta --agree-to-license
macOS 12 Monterey will be EOL end-of-life at the end of 2024, so testing with Ventura makes more sense.
