Home > Enterprise Mobility Management > Apps and Software > Installing Software on Windows and Mac Devices

Installing Software on Windows and Mac Devices

One of the most powerful features of Systems Manager is its ability to remotely install and uninstall applications from your devices. The Software Installer's flexibility allows for one-click deployment of applications across all of your devices, regardless of operating system.

To see information on how to deploy scripts to Windows and Mac devices, see this article.

This feature is not available for Legacy Systems Manager users.

Prerequisite: Installing applications on Mac and Windows devices requires that the agent be installed. Read more about agent installation here.

Installing Applications on Devices

Using Systems Manager, suites of applications can very easily be deployed to end user devices.

The following instructions outline how to deploy a new application, as well as overview additional installation options:

  1. Navigate to Systems Manager > MDM > Apps
  2. Click on the “Add new” dropdown and select the desired OS:

     
  3. Once an OS is selected, fill in the following information about the application:
  • Application name: The name of the application as it will appear on the end device (e.g. Firefox, FileZilla, etc). If the application is already installed on managed clients, it will be listed in the drop-down menu. This name can be changed at any time.
  • Vendor: The vendor of the specified application.
  • Version: The version number of the application to be installed.
  • Description: A brief description of the application.
  • Install file host: This option denotes whether the application's installer will be hosted in Dashboard, or on an external server (e.g. Dropbox).
    • Upload to the Meraki Cloud: Select this option and click Browse to upload the installer file directly to Dashboard. Please note that Dashboard can only host up to 3GB of installer files.
    • Specify a URL: Select this option if the installer file is hosted on an external server or file share site, and specify the URL for the hosted file. The URL field must point to the direct download link to a publicly hosted file such as the following, or an internally hosted server accessible by the end user's device.
Note: The installer must be silent (require no user interaction) in order for the application to install correctly in the background. Windows applications can be installed in the foreground in order to prompt user interaction.

Note: The following installer file types are supported:
-Windows: .exe or .msi 
-macOS: .dmg, .pkg*, or .app*.

*A .pkg or .app file can be used, but it must be wrapped in a .dmg. Please refer to Apple's documentation for their recommended steps.
  • Scope: Specifies a scope of devices that will have this application installed. Please refer to our documentation for more information on scoping by device tag.
  • Disable install on save: By default, the application will be auto-installed the moment the Save button is clicked. If auto-install is disabled, the application won't be installed until it's manually pushed by navigating to Systems manager > MDM > Apps, and selecting Push > Push to all. Dashboard users can manually queue install requests via the device page, or by pressing the Repush buttons on this page.
  • Install in foreground (Windows-only): Allow the installer to show user prompts, instead of silently installing in the background.
  • Installation arguments (optional): If the installer must be run with specific command line arguments, they can be listed here.
    The following list shows the actual install command run on the end-device, where [arguments] refers to the contents of the Installation arguments field in Dashboard:
    • EXE: application_installer.exe [arguments]
    • MSI: msiexec /quiet /i application_installer.msi [arguments]
    • PKG: /usr/sbin/installer [arguments] -pkg application_installer.pkg -target /
  • Command line (optional): Specifies a command to run after installation has completed. This is commonly used to reboot the machine after installation, using the following commands:
    • Windowsshutdown /r
    • OS X: shutdown -r now

    4. Click Save Changes. Unless auto-install is disabled, this will push out the application to all devices within the specified scope.

Example Configuration

The following example configuration will quietly install FileZilla from a Dropbox URL on all managed Windows clients with the "bginstall" tag. These clients will also reboot after installation has completed.

Monitoring Installation

The status of an installation can be checked via the Monitor > Clients page, by clicking on a particular client and navigating to the Event log or Activity log section.

Removing Applications from Devices

Certain .msi and .app programs can be remotely uninstalled via the Systems Manager > Monitor > Software page. To remove a specific application, search for the application under Software inventory and click uninstall.

Troubleshooting

If the software install command is issued and the application does not appear on the client device, check the Dashboard-side logging to see if the app install command errored out. If you see a 'Success' entry, this means the command successfully went through, but may not have completely executed on the client device. At this point, you should reference the agent logs on the device itself, and provide these to Meraki Support for troubleshooting assistance.

You must to post a comment.
Last modified
16:22, 8 Sep 2017

Tags

Classifications

This page has no classifications.

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community