I know that there's many of you that have workflows that involve the manual install of the SM agents on macOS, such as Silent installer for MacOS    However, with the changes in the SM agent 3.1.0 and above, instead of being able to do silent installs, you know have to specify your enrollment code manually, as per Mac Enrollment - Command Line Options    You can optionally specify the network enrollment code / string with the following command:   sudo launchctl unsetenv enrollment_code && sudo launchctl unsetenv organization_id && sudo launchctl setenv enrollment_code  <network enrollment code or enrollment string>  && sudo installer -pkg  <path/to/package.pkg>  -target / && sudo launchctl unsetenv enrollment_code && sudo launchctl unsetenv organization_id   There's two optional parameters here:   <network enrollment code or enrollment string> : This is the enrollment code that's quoted in Systems Manager > Add Devices, or Network Wide > General   <path/to/package.pkg> : This is the path to the SM agent installer     This is, understandably, unwieldy, primarily due to not being able to pass parameters to installers in macOS.   However, there is an alternative: You can actually build an installer that allows you for silent enrollments, and this is how   1. Download the Current SM Agent Installer From Systems Manager  > Add devices > macOS, download the SM agent   2. Create a new folder on your Desktop: SMAgent3.1.1 (for example)   3. Open Terminal and type the following cd ~/Desktop/SMAgent3.1.1 mkdir Scripts cd Scripts touch postinstall chmod a+x postinstall cd .. mkdir Content cd Content open .   This last command will open the Content directory   Move the previously download SM agent into here and rename it SMAgent.3.1.1.pkg   Go back to terminal and type   cd .. cd Scripts open .   This will open the Scripts directory in Finder.   4. Edit postinstall   With a suitable text editor, open the postinstall file and type:   #!/bin/bash sudo launchctl unsetenv enrollment_code && sudo launchctl unsetenv organization_id && sudo launchctl setenv enrollment_code XXXX-XXXX-XXXX && sudo installer -pkg /tmp/SMAgent-3.1.1.pkg -target / && sudo launchctl unsetenv enrollment_code && sudo launchctl unsetenv organization_id   NOTE: Replace XXXX-XXXX-XXXX with the network enrollment code or string   Save this file   5. Create installer Go back to Terminal and type:   cd .. sudo pkgbuild --identifier com.meraki.smautoenroll --root Content --script Scripts --install-location /tmp com.meraki.SMAgent3.1.1-autoenroll.pkg   This should result in:   paulf@Paul-F-MBP-680 SM3.1.1pkg % sudo pkgbuild --identifier com.meraki.smautoenroll --root Content --script Scripts --install-location /tmp com.meraki.SMAgent3.1.1-autoenroll.pkg Password: pkgbuild: Inferring bundle components from contents of Content pkgbuild: Adding top-level postinstall script pkgbuild: Wrote package to com.meraki.SMAgent3.1.1-autoenroll.pkg   You should now have an installer that will silently install the SM agent without prompts!           ... View more

Hi.   Whilst packaging files and script (and even plists) is relatively trivial on the Mac (you can even do it from the command line with pkgbuild), things aren't as easy for Windows   Because of this, I've put together a guide on how to package scripts, files, .exe and .bat files, and even run one of the files after install, so that you can completely provision your windows devices:   There’s many ways to create an installer for windows that performs functions above and beyond what a ready packaged installer will do. For example, reading and setting registry entries, placing files in various places, running batch files, etc. Whilst there’s plenty of commercial applications to do this, I’ve used a app called NSIS to show what can be achieved   Steps.   Download NSIS from https://nsis.sourceforge.io/Main_Page Install. This show place a shortcut on your desktop Run. This should spawn a window like this:       For the basis of this demo, we are going to put some files into a folder on the current users desktop and execute one of them Create a folder on your desktop (NSIS_Test_Project in this case) and move the files you need into it Create a file called FileInstaller.nsi in here using notepad (or a similar text editor) Drop in the following text   OutFile “AcmeInstaller.exe”   InstallDir $Desktop\AcmeFiles   Section   SetOutPath $INSTDIR   File AcmeIncConfigData.json File catchyCorpJingle.wav File customerInformation.csv File font1.font File readme.txt File runme.bat File runme.exe   SectionEnd   Section nsExec::Exec $DESKTOP\AcmeFiles\runme.bat SectionEnd   Save   Notes: AcmeInstaller.exe : the name of the file you’re going to create with the app $Desktop is a variable which will have the correct path for the currently logged in user, to the Desktop $Desktop\AcmeFiles : A folder on the users Desktop where we will install the files $INSTDIR The above folder, $Desktop\AcmeFiles $DESKTOP\AcmeFiles\runme.bat : The bat file that we will run as part of the installer process. This could be an msi, exe, bat or even cmd. Having a bat file means that you can have complex logic being used   I've used the Desktop as it's a useful place (and easy) to spot that the files are being installed and executed correctly: For production, I'd use somewhere that's available whether the user is logged in or not: /tmp for transitory files, Program Files, or somewhere more convenient for you   You should now have:     Click Compile NSI Scripts in the NSIS app You’ll be asked to load an NSI file     select the one we’ve just created: The screen will run through your script and identify any issue   You can click Test Installer to run through and text everything You’ll now have a new file that you can use with Meraki Systems Manager!   ... View more