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!
User Enrollment Options
You can have users enroll their devices in XenMobile in several ways. Before considering the specifics, decide which devices you want to enroll in MDM+MAM, MDM, or MAM. For more information about those management modes, see Management Modes.
At the highest level, there are four enrollment options:
- Enrollment Invitation: Send an enrollment invitation or invitation URL to users. Enrollment invitations and URLs aren’t available for Windows devices.
- Self Help Portal: Set up a portal that users can visit to download Secure Hub and enroll their devices or send themselves an enrollment invitation.
- Manual Enrollment: Send out an email, handbook, or some other communication to let users know that the system is available for enrollment. Users then download Secure Hub and enroll their devices manually.
- Enterprise: Another option for device enrollment is through an Apple Deployment Program and Google Android Enterprise. Through each of these programs, you can buy devices that are pre-configured and ready for employees to use. For more information, see the Apple Deployment Program articles in Apple Support and Google Android Enterprise documentation on the Android Enterprise website.
Enrollment Invitation
You can email an enrollment invitation to users with iOS, macOS, Android Enterprise, and legacy Android devices. Enrollment invitations and URLs aren’t available for Windows devices.
You can also send an installation link through SMTP or SMS to users with iOS, macOS, Android, or Windows devices. For more information, see Enroll devices.
If you choose to use the enrollment invitation method, you can:
- Choose Invitation URL, Invitation URL + PIN, or Invitation URL + Password enrollment security modes.
- Use any combination of the modes.
- Enable or disable the modes from the Settings page.
For information on each enrollment security mode, see Configure enrollment security modes.
Invitations serve many purposes. The most common use of invitations is to notify users that the system is available, and that they can enroll. Invitation URLs are unique. After a user uses an invitation URL, the URL is no longer available. You can use this property to limit the users or devices enrolling to your system.
When configuring an enrollment profile, you can control the number of devices specific users can enroll, based on Active Directory groups. For example, you might allow your Finance division only one device per user.
Be aware of the extra costs and pitfalls of certain enrollment options. For example, sending invitations by using SMS requires extra infrastructure. For more information on this option, see Notifications.
Along with send invitations by email, make sure that users have a way to access email outside of Secure Hub. You can use a one-time password (OTP) enrollment security mode as an alternative to Active Directory passwords for MDM enrollment.
Self-Help Portal
You can request an enrollment invitation through the Self-Help Portal. For information about setting up the Self-Help Portal, see Configure enrollment security modes.
Manual Enrollment
With manual enrollment, users connect to XenMobile either through AutoDiscovery or by entering the server information. With AutoDiscovery, users log on with only their email address or Active Directory credentials in User Principal Name format. Without AutoDiscovery, they must enter the server address and their Active Directory credentials. For more information about setting up AutoDiscovery, see XenMobile AutoDiscovery Service.
You can facilitate manual enrollment in several ways. You can create a guide, distribute it to users, and have them enroll themselves. You can have your IT department manually enroll groups of users in certain time slots. You can use any similar method where users must enter their credentials, server information, or both.
User Onboarding
After you have your environment set up, you need to decide how to get users into your environment. An earlier section in this article discusses the specifics of user enrollment security modes. This section discusses the way that you reach out to users.
Open Enrollment versus Selective Invitation
When onboarding users, you can allow enrollment through two basic methods:
- Open enrollment. By default, any user with LDAP credentials and the XenMobile environment information can enroll.
- Limited enrollment. You can limit the number of users by only allowing users with invitations to enroll. You can also limit open enrollment by an Active Directory group.
With the invitation method, you can also limit the number of devices a user can enroll. In most situations, open enrollment is acceptable, but there are a few things to consider:
- For MAM enrollment, you can easily limit open enrollment through Active Directory group membership.
- For MDM enrollment, you can limit the number of devices that can enroll based on Active Directory group membership. If you only allow corporate devices in your environment, that limitation typically isn’t an issue. You might want to consider this method, however, in a BYOD workplace if you want to limit the number of devices in your environment.
Selective invitation is typically done less often because it requires a bit more work than open enrollment. For users to enroll their devices in your environment, you must send an invitation unique to each user. For information on how to send an enrollment invitation, see Sending an enrollment invitation.
While you can use Active Directory groups to create invitations in batches, you must carry out this approach in waves.
First Contact with Users
After you decide between open enrollment or selective invitation and then set up those environments, you must make users aware of their enrollment options.
If you use the selective invitation method, email and SMS messages are a part of the process. You can send emails through the XenMobile console for open enrollment as well. For details, see Sending an enrollment invitation.
In either case, keep in mind that for email, you need an SMTP server. For text messages, you need an SMS server. Those servers might be extra cost to consider when making your decision. Before you select a method, consider how you expect new users to access information, like email. If you want all users to access their email through XenMobile, sending them an invitation email would be problematic.
You can also send communications by another means outside of XenMobile for an open enrollment environment. For that option, be sure to include all the relevant information. Let users know where they can get the Secure Hub app and what method to use to enroll. If you have discovery turned off, also provide users the XenMobile Server address. To learn more about AutoDiscovery, see XenMobile AutoDiscovery Service.
Share
Share
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.