A new version of the SM Agent (v3.1.0) is now available for download on macOS and Windows. Some important updates include the ability for SM admins to define the default version of the Agent used in a network or on a specific device, and workflow changes to the installation process.
For more details check out the new feature announcement here.
I'm not finding documentation about how to specify the network ID or enrollment string as a parameter (for unattended installs) to the new 3.1.0 Agent installer. Could you point me to the guide that specifies how to do this?
I like this chart showing the difference between agent and profile features.
Any reason the enrolment info now has to be manually entered or scripted, the old method worked fine and meant we could quickly download the install and deploy it.
Seems a step backwards to me.
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?
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.
The documentation refers to the 3.1.0 Windows agent installer with a filename pattern of "SMAgent-x.x.x.msi", however, the download link on our dashboard still points to a "MerakiPCCAgent.msi" file. Has our dashboard link not been updated yet? Since this new version isn't tied to our tenant, is there a more generic download link from which we can obtain the 3.1.0+ installers?
@Kevin_C, thanks for that information, that was exactly what I needed! It wasn't obvious to me that changing the "Preferred agent version" would also change the manual download link, but now I understand the linkage and the desire to unify them. Perhaps a small note on the "Add Devices" -> "Agent" box informing the admin that the version available for download is controlled via the "Preferred agent version" option would be helpful for others? That would have been helpful for me.
Avoid deploying for a couple of months. Not all bugs have been identified but here are the ones I'm aware of:
Still waiting to see a response to this one also. @Kevin_C, thanks for providing the documentation for Windows agents, but we do still need the documentation for including the network ID when deploying to macOS.