Management and Security powered by Landesk

Distributing content to MDM managed devices

Tools > Distribution > Distribution packages

Use Mobility Manager to distribute links, documents, and apps to managed devices by creating distribution packages then scheduling them for deployment.

Distributing links and documents

To receive link or document packages, the device user must have both the Ivanti Agent and either Ivanti Portal Manager or Ivanti Workspaces installed.

Universal link packages. Links are shortcuts to applications. You can link to a distribution package, an executable, or a URL. Links can appear in LaunchPad, on the desktop, or in the Start menu.

Universal streamed document packages. Streamed documents are viewable with the new Ivanti Portal Manager on managed devices. A streamed document must be hosted on a UNC or HTTP share that managed devices can access. The streamed document file extension must have an application associated with it that can display that document type. Streamed documents aren't cached locally. Streamed documents are generally used with package bundles to provide users with additional instructions or information.

For information about scheduling a deployment, see Distribute a package.

Distributing software

When distributing software, the package that is sent to the device does not contain the app, it only contains the location of the app. When the device receives the package, the device contacts the server (either the app store or your server) that hosts the app and downloads it. If the app server is unavailable (for example, if the app server is only available on the domain and the device is not currently on the domain), the device will attempt to download the app the next time that it checks in with the core server.

NOTE: Mobility Manager does not use the preferred server information. Even if the app is stored on a preferred server, you must specify a URL to the server, and that is the only server the device will attempt to download the app from. If the server requires a password to access the app, the download will fail.

Software packages are specific to an operating system. You cannot have one package that delivers the same app to both Android and iOS devices. However, you can create one package for each operating system and then put them in the same bundle.

When you need to distribute a new version of an app that has already been distributed, create a software package with the new app, increment the version number, and use the same package ID. The device will detect that it is a new version of an app it already has, and update the app rather than uninstalling and re-installing.

ClosedTo create a software package for Android or iOS

Distribute free apps from the Google Play store or the Apple App Store, or distribute apps that you have the .apk or .plist and .ipa files for.

1.Click Tools > Distribution > Distribution packages.

2.Choose the folder where you are creating the package and click the New button in the toolbar.

3.Select Mobile then the type of package you want to create.

4.On the Package information page, type a description of the app.

5.Select the method for distributing the app.

App store. Use the search box to find the app. When you select an app through the search, the Location, Package ID and Package version fields are populated. You can only distribute free apps from an app store.

Manifest URL. Provide the path to the app (either the .apk file, or the .plist and .ipa files) on a web server. This must be an address to a web server that the device can reach. You also need to provide the Package ID and the Package version for the app. You can get this information from the app developer.

VPP (iOS only). Select an existing Token alias and then click the arrow icon. This presents a list of all apps associated with the VPP token. This option is only available for iOS and Macintosh MDM packages. If no tokens appear, see Using a VPP Account.

6.Click Save.

For information about scheduling a deployment, see Distribute a package.

ClosedTo create a software package for Mac

Distribute free apps from the the Apple App Store, or distribute apps that you have the .plist and .ipa files for.

1.Click Tools > Distribution > Distribution packages.

2.Choose the folder where you are creating the package and click the New button in the toolbar.

3.Select Macintosh > Macintosh MDM.

4.On the Package information page, type a description of the app.

5.Select the method for distributing the app.

Manifest URL. Provide the path to the app ( the .plist and .ipa files) on a web server. This must be an address to a web server that the device can reach. You also need to provide the Bundle ID and the Bundle version for the app. You can get this information from the app developer.

VPP. Select an existing Token alias and then click the arrow icon. This presents a list of all apps associated with the VPP token. This option is only available for iOS and Macintosh MDM packages. If no tokens appear, see Using a VPP Account.

6.Click Save.

For information about scheduling a deployment, see Distribute a package.

ClosedTo create a software package for Windows 10

Create an MSI software distribution package then distribute it to MDM managed Windows devices. For more information about MSI packages, see Using MSI distribution packages. Currently, MDM software distribution for Windows devices only supports one MSI at a time and silent installation. All other configurations will not apply unless the Agent is used.

1.Click Tools > Distribution > Distribution packages.

2.Choose the folder where you are creating the package and click the New button in the toolbar.

3.Select Windows > MSI.

4.On the Package information page, type a description of the software.

5.Locate and select the primary file.

6.Click Save.

For information about scheduling a deployment, see Distribute a package.

WARNING: If you lack sufficient app licenses to distribute apps to all enrolled devices, Mobility Manager will deliver software packages until all licenses are used up. All remaining devices will display as a failed deployment.


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other