So ran across this one today.
IF you are using StoreFront 2.0 AND auto-subscribe apps to your users (KEYWORDS:Auto in description) AND you see an event ID of 5 in the Citrix Delivery Services log on one of your StoreFront servers that is failing and the description is “The auto provisioned app with id “FarmName.AppName” has not bee subscribed during the last enumeration.”
Supposedly it manifests around 700+ subscriptions, although I have seen it hit as low as the 500 mark. (Calculate by <users> x <subscribed apps per user>)
This is particularly nasty because it defeats your load balancing even if you have a properly setup NetScaler utilizing StoreFront monitors..it will keep sending connections to the effected server rendering you with a random and nasty bug.
To check if this might be your issue go to a StoreFront server that is presenting the Event ID 5 with the above text and open PowerShell, Set-ExecutionPolicy Unrestricted, change to C:\Program Files\Citrix\Receiver StoreFront\Scripts and run .\ImportModules.ps1. Once complete, run a store subscription export by running Export-DSSStoreSubscriptions -StoreName <store> -FilePath c:\blah\subscriptions.csv and then open that CSV and see how many lines you have. If its in the hundreds then you might be effected by this bug.
Open a Citrix Support case and reference SR 61125582 for the private hot fix. Word is this will be included in StoreFront 2.1.
Happy <bug> hunting
In XenMobile MDM Edition 8.5 we can get applications down to our devices based on a multitude of criteria that we will cover in the “Deployment” part of this series. In this specific article I want to show you how we can bring in and distribute apps to our users via MDM. I should point out that the “MDX Toolkit” that is used to wrap custom, in-house apps is not included in the MDM Edition and is only available in App Edition and Enterprise Edition. The limitations of this are that we can only distribute “External” apps, i.e. apps from the respective platforms App Store (iOS, Google Play, and Windows Phone. Blackberry is out of luck).
In this 3rd part of my 7 part series on XenMobile MDM 8.5 we will focus on policies. Policies within MDM allow you to control a multitude of features on your end users mobile devices, including: WiFi, Email, VPN, Location Services, most all functionality of the device (camera, FaceTime, etc), AppStore access, etc. Most configuration variations you do to control and limit/restrict/configure your end users devices will be done from this tab. This tab is also the location where we can create some automated actions that include notifying your users when they have fallen out of compliance.
In late 2012 Citrix announced they had purchased a 7-year-old startup company called Zenprise that was a hot player in the mobile device security market. Up until that time, Citrix was positioning for that sector with its CloudGateway Enterprise product and focusing mostly on apps and data management..not really the device. Zenprise helped them flesh out their offering, which is now known as “XenMobile”. Although it’s gone through a few iterations it has finally reached a final “form” if you will of three editions: MDM, App, and Enterprise.
The purpose of this article series will be to walk through the installation and basic setup of the MDM (Mobile Device Management) Edition which focuses almost exclusively on managing the device, and not necessarily so much the data or apps. Although it is capable of application pushes and the like… a feature comparison can be found on Citrix’ website HERE. I encourage you to view that. One major difference to note is MDM does not sandbox apps/data, but App Edition does, and Enterprise Edition can.
In they first part of my XenMobile series we covered the (albeit slightly) boring initial install..with this next article we will cover the basic configuration steps that will start inching us closer to actually managing a device. By the end of this article I will have shown how to configure XenMobile MDM for LDAP integration, assign a group for Administration, a regular “Users” group, setup an email notification server to send out your deployment invitations that we’ll be covering in a later article, and some minor details on the Notification Templates..