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à))
An enrollment profile specifies the following:
- Device management enrollment options for Android and iOS devices. For Android, the enrollment options available for the MDM+MAM (ENT) server mode differ from the options for MDM mode.
- App management enrollment options for Android and iOS devices.
- Other enrollment options:
Whether to limit the number of devices a user can enroll.
If the device limit is reached, an error message lets the user know that they exceeded the device registration limit.
Whether to allow a user to decline device management.
You can use enrollment profiles to combine multiple use cases and device migration paths within a single XenMobile Server console. Some use cases include:
- Mobile Device Management (MDM only)
- MDM+Mobile Application Management (MAM)
- MAM only
- Corporate-owned enrollments
- BYOD enrollments (the ability to opt out of MDM enrollment)
- Migration of Android Device Administrator enrollments to Android Enterprise enrollments (fully managed, work profile, dedicated device)
When you create a delivery group, you can use the default enrollment profile named Global or specify a different enrollment profile.
Enrollment profile features by platform include the following.
For Android devices: You specify the device owner mode. For example: Fully managed, fully managed with work profile, and BYOD work profile. The Dedicated device option appears only when you have an Enterprise or Advanced license for XenMobile. New devices enroll in Android Enterprise and app management by default. The enrollment security modes User name + PIN, Invitation URL, Invitation URL + PIN, and Invitation URL + Password aren’t available for Android Enterprise.
For iOS devices: You specify the device enrollment type: Device enrollment or don’t manage devices. The iOS settings appear only when you have an Enterprise or Advanced license for XenMobile. New devices enroll in Apple device management and app management by default.
If you don’t need to enroll dedicated devices for Android devices or MAM-only enrollment for Android or iOS devices, you can disable the server property
enable.multimode.xms. However, keeping this property enabled means you need only one XenMobile Server to handle all types of enrollment profiles. See Server properties.
When you disable
enable.multimode.xms, only the settings in this screenshot are available:
For more details about these settings, see Android Enterprise.
The default enrollment profile is named Global. The Global profile is useful for testing until you have a chance to create enrollment profiles.
The following screenshots show the default settings for the Global enrollment profile.
Enrollment profiles and delivery groups interact as follows:
You can attach an enrollment profile to one or more delivery groups.
If a user belongs to multiple delivery groups that have different enrollment profiles, the name of the delivery group determines the enrollment profile used. XenMobile Server selects the delivery group that appears last in an alphabetized list of delivery groups. For example, suppose that you have the following:
- Two enrollment profiles, named “EP1” and “EP2”.
- Two delivery groups, named “DG1” and “DG2”.
- “DG1” is associated with “EP1”.
- “DG2” is associated with “EP2”.
If the enrolling user is in both the “DG1” and “DG2” delivery groups, XenMobile Server uses the “EP2” enrollment profile to determine the enrollment type for the user.
Deployment order applies only to devices in a delivery group that has an enrollment profile configured for MDM (device management).
After a device enrolls, some changes to an enrollment profile require re-enrollment:
- Adding MAM to an enrollment profile that’s configured for MDM.
- Moving a device that’s enrolled in MDM to a delivery group configured for MDM+MAM. That change impacts new device enrollments only. Existing device enrollments aren’t impacted.
- Adding MDM to an enrollment profile that’s configured for MAM.
Switching to a different enrollment profile does not affect existing enrolled devices. However, users must unenroll and then reenroll those devices for the changes to take effect.
In the XenMobile Server console, go to Configure > Enrollment Profiles.
On the Enrollment Info page, type a descriptive name for the profile. By default, a user can enroll unlimited devices. Select a value to limit the number of devices per user. The limit applies to the sum of MAM or MDM managed Android and iOS devices that a user enrolls.
Complete the platform pages. For information about enrollment settings specific to the platforms, see:
On the Assignment page, attach one or more delivery groups to the enrollment profile.
A user might belong to multiple delivery groups that have different enrollment profiles. In that case, the name of the delivery group determines the enrollment profile used. XenMobile selects the delivery group that appears last in an alphabetized list of delivery groups. To create delivery groups, go to Configure > Delivery Groups.
A list of your enrollment profiles appears on the Configure > Enrollment Profiles page. To edit the Global profile or reset it to the original defaults, select the row for the Global profile and click Reset. You can’t delete the Global profile.
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 Do Not Agree to exit.