XenMobile lets you configure devices that can be shared by multiple users. The shared devices feature lets, for example, clinicians in hospitals use any nearby device to access apps and data rather than having to carry around a specific device. You may also want shift workers in fields like law enforcement, retail, and manufacturing to share devices to reduce equipment costs.
As of the release of version 10.4, Worx Mobile Apps are renamed to XenMobile Apps. Most of the individual XenMobile Apps are renamed as well. For details, see About XenMobile Apps.
Key Points About Shared Devices
- Available on both iOS and Android tablets and phones. Basic device enrollment program (DEP) enrollment is not supported for a XenMobile Enterprise shared device. You must use an authorized DEP to enroll a shared device in this mode.
- Client certificate authentication, Citrix PIN, Touch ID, User Entropy, and two-factor authentication are not supported.
- Available only on iOS and Android tablets.
- Supported on XenMobile 10.3.x and above.
- MAM-only mode is not supported. The devices must enroll in MDM.
- Only WorxMail, WorxWeb, and the ShareFile mobile app are supported. HDX apps are not supported.
- Only AD username and password authentication is supported. Client certificate authentication, Worx PIN, Touch ID, User Entropy, and two-factor authentication are not supported.
- Active Directory users are the only supported users; local users and groups are not supported
- Re-enrollment is required for existing MDM-only shared devices to update to MDM+MAM mode.
- Users can share Worx apps and MDX-wrapped apps only; they cannot share native apps on the devices.
- Once downloaded during first-time enrollment, Worx apps are not downloaded again each time a new user signs on to the device. The new user can pick up the device, sign on, and get going.
- On Android, to isolate each user's data for security purposes, the Disallow rooted devices policy in the XenMobile console should be On.
Prerequisites for Enrolling Shared Devices
Before you can enroll shared devices, you must do the following:
Pre-requisites for MDM+MAM Mode
- Create an Active Directory group named something like Shared Device Enrollers.
- Add to this group Active Directory users who will enroll shared devices . If you want a new account for this purpose, create a new Active Directory user (for example, sdenroll) and add that user to the Active Directory group.
Shared Device Requirements
For the best user experience, including silent installation and removal of apps, Citrix recommends configuring shared devices on the following platforms:
- iOS 10
- iOS 9
- Android M
- Android 5.x
- Android 4.4.x
- Android 4.0.x (MDM-only mode)
Configuring a Shared Device
Follow these steps to configure a shared device.
- From the XenMobile console, click the gear in the upper-right corner. The Settings page appears.
- Click Role-Based Access Control, then click Add. The Add Role screen is displayed.
- Create a shared-device enrollment user role named Shared Device Enrollment User with Shared devices enroller permissions under Authorized Access. Be sure to expand Devices in Console features and then select Selective Wipe device. This setting ensures that the apps and policies provisioned through the shared devices enroller account are deleted through Worx Home, when the device is un-enrolled.
For Apply Permissions, keep the default setting, To all user groups, or assign permissions to specific Active Directory user groups with the To specific user groups.
Click Next to move to the Assignment screen. Assign the shared-device enrollment role you just created to the Active Directory group you created for shared device enrollment users in Step 1 under Pre-requisites. In the image below, citrix.lab is the Active Directory domain and Shared Device Enrollers is the Active Directory group.
4. Create a delivery group that contains the base policies, apps, and actions that you want to apply to the device when a user is not signed on, then associate that delivery group with the shared device enrollment user Active Directory group.
5. Install Worx Home on the shared device and enroll it in XenMobile using the shared device enrollment user account. You can now view and manage the device through the XenMobile console. For more information, see Enrolling Devices.
6. To apply different policies or to provide additional apps for authenticated users, you must create a delivery group associated with those users and deployed to shared devices only. When creating the groups, configure deployment rules to ensure that the packages are deployed to shared devices. For more information, see Configuring Deployment Rules.
7. To stop sharing the device, perform a selective wipe to remove the shared device enrollment user account from the device, along with any apps and policies deployed to it.
Shared Device User Experience
Users see only the resources available to them, and they have the same experience on every shared device. The shared device enrollment policies and apps always remain on the device. When a user who isn't enrolled in shared devices signs on to Worx Home, that person's policies and apps are deployed to the device. When that user signs off, the policies and apps that differ from those of the shared device enrollment are removed, while the shared-device enrollment resources remain intact.
WorxMail and WorxWeb are deployed to the device when enrolled by the shared device enrollment user. User data is maintained securely on the device. The data is not exposed to other users when they sign on to WorxMail or WorxWeb.
Only one user at a time can sign on to Worx Home. The previous user must sign off before the next user can sign on. For security reasons, Worx Home does not store user credentials on shared devices, so users must enter their credentials each time they sign on. To ensure that a new user cannot access resources intended for the previous user, Worx Home does not allow new users to sign on while the policies, apps, and data associated with the previous user are being removed.
Shared device enrollment doesn't change the process for upgrading apps. You can push upgrades to shared-device users as always, and shared-device users can upgrade apps right on their devices.
Recommended WorxMail policies
- For the best WorxMail performancel, set Max sync period based on the number of users that will share the device. Allowing unlimited sync is not recommended.
Number of users sharing device
Recommended max sync period
21 to 25
1 week or less
6 to 20
2 weeks or less
5 or fewer
1 month or less
- Block Enable contact export to avoid exposing a user’s contacts to other users who share the device.
- On iOS, only the following settings can be set per user. All other settings will be common across users who share the device:
Out of Office
Sync Mail Period