The latest version of XenMobile has these new features and improvements:
- Manage OS updates to Chromebook devices
- Chromebook device power management settings
- App Restrictions device policy for Chrome OS
- Manage bookmarks for Chromebook devices
- Fixed issues in XenMobile Service 10.18.4
Manage OS updates to Chromebook devices
You can now use the Control OS Update device policy to deploy OS updates to Chromebook devices. To configure the policy, go to Configure > Device Policies and add or edit the Control OS Update device policy.
Configure these settings:
- Update enabled: Specifies whether to update Chromebook devices automatically to a newly released version of Chrome OS. Default is Off.
- Reboot after update: Specifies whether to reboot a Chromebook device the next time that the user signs out after a successful automatic update. Default is Off.
- Target platform version prefix: If a device is on an older version, this setting specifies the prefix of the target version to update to. For Chrome platform versions, see https://chromereleases.googleblog.com/. If a device is already on a version with the given prefix, no update occurs. If the device is on a higher version, it remains on the higher version. Rollback isn’t supported. Default is empty.
Use one of the following version formats:
- ”” or unset: Update to latest version available.
- 10323.: Update to any minor version of 10323 (for example, 10323.58.0).
- 10323.58.: Update to any minor version of 10323.58 (for example, 10323.58.0).
- 10323.58.0: Update to this specific version only.
- Delay update period: Specifies how long a device can wait before downloading an update. The delay is counted from the time the update first deploys to the server. The device might wait a portion of this time in terms of wall clock time and the remaining portion in terms of the number of update checks. The maximum duration value is 14 days. Default is 0.
Chromebook device power management settings
You can control how Chromebook devices respond to idle periods when using AC or battery power. To manage power settings, go to Configure > Device Policies, add the Power Management device policy, and configure these settings.
The following settings appear for both AC and Battery.
- Idle delay: The length of time without user input before taking the idle action. Specify in milliseconds. Default is 0.
- Idle warning delay: The length of time without user input before showing a warning dialog. Specify in milliseconds. Default is 0.
- Screen dim delay: The length of time without user input before dimming the screen. Specify in milliseconds. Default is 0.
- Screen off delay: The length of time without user input before turning off the screen. Specify in milliseconds. Default is 0.
- Idle action: Action to take after reaching the idle delay: Suspend, Logout, Shutdown, Do Nothing. Default is Suspend.
App Restrictions device policy for Chrome OS
You use the App Restrictions device policy to specify allowed or blocked Chrome apps and Android apps running on Chrome OS. If you enable App Runtime for Chrome (ARC) in the Restrictions device policy, you configure Android app restrictions under Android apps in the XenMobile App Restrictions device policy.
To configure app restrictions, go to Configure > Device Policies, add the App Restrictions policy, and then configure these settings for Chrome OS.
Chrome app settings:
Chrome apps are both apps and extensions.
- App install allowed: A global setting to allow or block the installation of all Chrome apps on Chromebook devices. If you choose Allowed, you can create a list of specific blocked apps. If you choose Not allowed, you can create a list of specific allowed apps. To do that, click Add under Chrome apps. To use the settings specified in your Chrome account, select Unspecified. Default is Allowed.
- Chrome apps: To add Chrome apps that are exceptions to your selection for the App install allowed setting, click Add and then specify these settings:
- App name: A name used to identify an app in the XenMobile console.
- App ID: The unique identifier for a Chrome app. Don’t include the prefix “app:”.
To look up a Chrome app ID: Go to the Chrome store, https://chrome.google.com/webstore, and search for the app. Click the app to view the URL and app ID in the address bar. The last portion of the address is the app ID. For example, if the URL is https://chrome.google.com/webstore/detail/citrix-intranet/hjacpdaecmilhndcbllidcgaaicdlpff, the app id is “hjacpdaecmilhndcbllidcgaaicdlpff”.
You can look up Chrome apps only from Chromebook. You can look up Chrome extensions from any platform.
- App install allowed: Creates an exception to the global setting above. This setting allows or blocks the specified Chrome app.
- Installed: If On, forces the Chrome app to install for enrolled Chromebook users. If Off and an app is installed, the app is uninstalled. If Off and the app is no longer configured by the policy, the app remains installed. Default is Off.
- Pinned: If On, pins the app to the Chromebook task bar. Default is Off.
- URL: Specifies the URL from which users can download an app that isn’t hosted in the Chrome Web Store.
- Extension policy: Defines, in JSON format, the app-specific policy defined by this app. For information, see Manifest for storage areas.
Android app settings:
To enable enrolled Chromebook users to run Android apps, configure the Restrictions device policy as noted in the next section “Enable enrolled Chromebook users to run Android apps.” To configure ARC app restrictions, click Addunder Android apps and then specify these settings.
- App ID: A unique app identifier for an Android app running on Chrome OS. For example: com.android.camera. Don’t include the prefix “app:”.
To look up an Android app ID: Go to the Google Play store, https://play.google.com/store, and search for the app. Click the app to view the app ID in the address bar. The portion after “id=” is the app ID. For example, if the URL is https://play.google.com/store/apps/details?id=com.citrix.Receiver, the app id is com.citrix.Receiver.
- Installed: Specifies whether to force the Android app to install for enrolled Chromebook users. If Off and an app is installed, the app is uninstalled. If Off and the app is no longer configured by the policy, the app remains installed. Default is Off.
- Pinned: If On, pins the Android app to the Chromebook task bar. Default is Off.
Enable enrolled Chromebook users to run Android apps
To enable enrolled Chromebook users to run Android apps: Go to Configure > Device Policies and add a Restrictions device policy for Chrome OS with the setting Enable App Runtime for Chrome (ARC) enabled.
- Enable App Runtime for Chrome (ARC): If On, allows enrolled Chromebook users to run Android apps. Specify ARC apps in the XenMobile App Restrictions device policy. Requires G Suite Chrome configuration. ARC isn’t available if either Ephemeral mode or multiple sign-on is enabled in the current user session. If Off, enterprise Chromebook users can’t run Android apps. The default is On.
Manage bookmarks for Chromebook devices
You can deploy a folder of bookmarks to Chromebook devices. To manage the bookmarks, go to Configure > Device Policies, add the Managed Bookmarks policy, and then configure these settings:
- Folder name: The name of a bookmark folder to deploy to Chromebook devices.
- Name: The name of a bookmark.
- Bookmark: The URL for the bookmark.
Fixed issues in XenMobile Service 10.18.4
After you delete a Chromebook or Workspace hub device using the XenMobile action: The devices continue to show in the XenMobile console until after you refresh it.
When you change users to a different Active Directory security group: For enrolled iOS devices, XenMobile Service does not detect the change, update the delivery group membership, or push new policies to the devices.
After an update to XenMobile Service 10.18.2 or 10.18.3, the Export button is missing from the Manage > Users and Manage > Enrollment Invitations pages.