-
Release notes for Rolling Patches
-
Release notes for XenMobile Server 10.15
-
Release notes for XenMobile Server 10.15 Rolling Patch 4
-
Release notes for XenMobile Server 10.14
-
Release notes for XenMobile Server 10.13
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Release Notes for XenMobile Server 10.15 Rolling Patch 4 Release
These release notes describe enhancements and fixed and known issues for XenMobile Server 10.15 Rolling Patch 4.
What’s new
-
Access to Devices & Apps reports
Previously, the Devices & Apps reports page displayed the information about all the devices and apps for all the users irrespective of their user group even if the role-based access control (RBAC) is applied.
Starting from XenMobile Server 10.15 Rolling Patch 4 release, the Devices & Apps reports page displays the devices and apps specific to the user groups defined in the To specific user groups configuration that the RBAC role has permission to manage. For more information about configuring roles with RBAC, see Configure roles with RBAC.
-
Support for resetting Control OS Updates device policy to system default
Starting from XenMobile Server 10.15 Rolling Patch 4 release, a new value Default is added in the System update policy drop-down list in the Control OS Updates page for Android Enterprise. This feature allows you to reset the System update policy to system default. For more information, see Control OS Updates device policy.
-
Added new fields OAuth sign-in URL and OAuth token request URL in the Exchange device policy settings for iOS
Starting from XenMobile Server 10.15 Rolling Patch 4 release, OAuth sign-in URL and OAuth token request URL fields are added under the Exchange Policy > iOS > Use OAuth radio button. For more information, see Exchange device policy.
-
Support to sync or override Synced Exchange Services for iOS
Starting from XenMobile Server 10.15 Rolling Patch 4 release, you can choose whether to sync or override the following synced Exchange Services for iOS by enabling the relevant settings.
- Calendars
- Contacts
- Notes
- Reminders
For more information, see Exchange device policy.
-
Support for eSim on iOS devices
XenMobile Server has a new property
ios.esim.support
, which enables the XenMobile Server to get the eSim information from the iOS devices and displays the eSim related device properties on the user interface. The default value of this property is True. For more information, see Server properties.
For information about previous rolling patches for XenMobile Server 10.15.0, see Release notes for Rolling Patches.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.