Meraki Windows client 3.1.0 - new install behaviour

[DavR]

Just in case anyone else comes across the same issue, discovered the below whilst preparing the updated Meraki System Manager client for SCCM deployment.

 

The install behaviour for the Meraki Windows client has changed as of v3.1.0. You now need to give your enrolment code during the client install - https://documentation.meraki.com/SM/Device_Enrollment/Windows_Enrollment

 

The new silent install string is:

 

msiexec.exe /i  /q ENROLLMENT_CODE=

 

As far as I can tell, this still doesn't enrol the device into Meraki, you still need to do the profile thing so I'm not sure what this adds, but maybe it's another step toward the Meraki client being a truly silent install.