How To: XenMobile MDM 8.5 Deployment Part 5: Deployment Packages

In the last part of my series (Applications) we went over how to package external apps for distribution either via push or offering in our EAS (Enterprise App Store). We can’t wrap our own apps without XenMobile App Edition or Enterprise Edition and this series is focusing strictly on Mobile Device Manager or “MDM” version. We are almost to the point now that we can get a device under our control…ALMOST. Our policies are in place, our applications are packaged and prepped, it’s time to put together a “Deployment Package” which is what I will show you how to do in this piece.

A deployment package is basically a grouping of selected policies and applications that you have made, which will be pushed out to a device. You can have multiple deployment packages but only one “default” deployment per platform. However, there is a decent rules engine available in your deployment’s which I’ll show below where you can fine tune who gets what based on certain criteria. I would recommend you have your base “default” deployment with the subset of applications and settings that are applicable to your entire device user base. From there, carve up sub packages based on either AD groups or as I’ll be showing below, device type (i.e., iPad).

If you would like to read the other parts in this article series please go to:

Step 1: Login to your XenMobile MDM management console and go to the “Deployment” tab then click “iOS Base Package” that should already be there to open it.


Step 2. We’ll leave the name as is, so click “Next”


Step 3. We want this to be our default deployment for all iOS devices so we’ll leave it checked as default deployment for groups of users. You could however sort on any AD group you’ve made MDM aware of.


Step 4. On this page is where we select what policies/apps we want to include in this deployment. You’ll see a few already present such as the software inventory task which inventories a device, the enterprise app store (MyAppStore), an app push of Worx Home (denoted by the preceding “Push:”), and our passcode policy. Now lets add some of the additional policies and apps we’ve been working on.


Step 5. Browse through and move to the right pane our wrapped “Office Mobile” app, note this is a PUSHED app denoted by the “Push:”. Lets also make SalesForce Classic *available* to everyone via our EAS, denoted by the preceding “EAS:”. This will NOT push the app but it can be self subscribed via the EAS by the user. Lets also push our policies for forbidden apps notification, forbidden apps Out of Compliance, and our Cloud Storage Policy. Once its all over, click “Next”.


Step 6. We want to check this on every connection, starting now, and deploy it if it is not deployed. Click Next.


Step 7. Here is our summary for our package, lets click “Finish”.


Step 8. Now lets create a sub-package for iPad since I have an iPad only app I want to push for collaboration. Select “New Package” then “New iOS Package”.


Step 9. We’ll name this one iPad Base Policy or any name that will make sense of what it contains/is used for. Pick a convention and stick to it. I missed step 2 on my screenshots but select an applicable group of users and click next there also.


Step 10. Browse to our Talkboard by Citrix and set it to Push. It is currently only an iPad app so we’ll filter for that. Click Next.


Step 11. Same thing, check on every connection and push package if not already deployed.


Step 12. We want a new simple rule here, “Deploy only on devices iPad”. In the second screenshot below I show the various rule criteria we can use to setup our rules. Click Next



Step 13. There we have it. An iOS Base Package and a sub-package for our iPad’s that pushes an iPad only app out.


Granted this is all very basic, but I hope you can see the flexibility and power in this. I mentioned in earlier articles how “Policies” and “Applications” roll up into “Deployments” and I hope that is now clear. You can have NUMEROUS policies here delineated by AD Group or device types and properties to meet the needs of the various types of users in your org. One note, remember that we are pushing apps..if we push the app we control it, we can remove it, etc but if that user already has the app we can’t push “over” it..the end user has to remove the publicly loaded app so we can push ours. Obviously not ideal but I wanted to point that out. I don’t personally see this as a big issue but to some it may be.

As with all my articles I hope this helps someone out there. Stay tuned for part 6 where we (finally) ACTUALLY enroll an end user device!

If you would like to read the other parts in this article series please go to:


8 thoughts on “How To: XenMobile MDM 8.5 Deployment Part 5: Deployment Packages

  1. We’re a bunch of volunteers and starting a brand new
    scheme in our community. Your site provided us with helpful information to work on. You’ve done an impressive activity and our entire community
    might be thankful to you.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s