Shall we expect this bug to be sorted out? Deploying new computer, either Apple or Intel chip, will fail to enroll in SM when 3.1.1 is utilized. To work around the problem I have to either manually install the agent using the environment script to provide network ID/etc or to roll back to default to 3.0.2 which breaks automatic install on Apple silicon macs because Rosetta does not deploy automatically. Duh!! ... View more

I am pushing it from SM on a brand new supervised machine. ... View more

That's great the fixes for 3.1.1   I see the agent now deploys Rosetta, but it does not install itself as it is missing the necessary parameters. The only way to enroll is from the device, which is not the desired result. How can we have 3.1.1 install and enroll on a fresh new computer without having to enroll from the computer itself? [Bug fix] Installing agent over MDM now automatically enrolls without needing any user intervention. this does not work for me. Agent reports  "no organization_id, no enrollment_code, no silent upgrade; preflight quitting. No install.  ... View more

Is there documentation on 3.1 agents for macOS (how to deploy without network ID prompt)? ... View more

Installing Rosetta2 is simply a workaround. The proper solution would be to make agent binaries compiled as universal architecture. There are also rumors Apple will remove Rosetta on macOS 11.3 in some regions, that would break the agent on these affected.  ... View more

How do we specify the network ID for unattended install (applicable for imaging tools like MDT/etc)?   Is the macOS version compatible with M1 Macs now?  ... View more

I had this problem too - I was on agent 1.0.98. After reaching to Meraki support, the issue is now resolved once they pushed agent version 3.0.2 to our tenant. Remote desktop access will work once the permissions are added in macOS settings.   ... View more