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à))
XenCenter 2023.x.x is currently in preview and is not supported for production use. Note that any future references to production support apply only when XenCenter 2023.x.x and XenServer 8 go from preview status to general availability.
You can use XenCenter 2023.x.x to manage your XenServer 8 and Citrix Hypervisor 8.2 CU1 non-production environments. However, to manage your Citrix Hypervisor 8.2 CU1 production environment, use XenCenter 8.2.7. For more information, see the XenCenter 8.2.7 documentation.
You can install XenCenter 8.2.7 and XenCenter 2023.x.x on the same system. Installing XenCenter 2023.x.x does not overwrite your XenCenter 8.2.7 installation.
When you first install XenServer, a user account is added to XenServer automatically. This account is the local super user (LSU), or
root, which the XenServer system authenticates locally. You can create extra users by adding Active Directory accounts from the Users tab in XenCenter.
The term “user” refers to anybody with a XenServer account, that is, anyone administering XenServer hosts, regardless of the level of their role.
If you want to have multiple user accounts on a server or a pool, you must use Active Directory user accounts for authentication. This feature allows XenServer users to log in to the servers in a pool using their Windows domain credentials.
Mixed-authentication pools are not supported. That is, you cannot have a pool where some servers in the pool use Active Directory and some don’t.
When you create a user in XenServer you must first assign a role to the newly created user before they can use the account. XenServer does not automatically assign a role to the newly created user. As a result, these accounts do not have any access to the XenServer pool until you assign them a role.
Using the Role Based Access Control (RBAC) feature, you can assign the Active Directory accounts different levels of permissions depending on the user’s role. If you do not use Active Directory in your environment, you are limited to the LSU account.
Even though the XenServer servers are Linux-based, XenServer lets you use Active Directory accounts for XenServer user accounts. To do so, it passes Active Directory credentials to the Active Directory domain controller.
You can enable LDAP channel binding and LDAP signing on your AD domain controllers. For more information, see Microsoft Security Advisory.
When added to XenServer, Active Directory users and groups become XenServer subjects, called users in XenCenter. When a subject is registered with XenServer, users and groups are authenticated with Active Directory on login. These users and groups do not need to qualify their user name with a domain name.
To qualify a user name, you must enter the user name in Down-Level Logon Name format, for example,
By default, if you don’t qualify the user name, XenCenter attempts to log users in to Active Directory authentication servers using the domain to which it is joined. The exception to this rule is the LSU account, which XenCenter always authenticates locally (that is, on XenServer) first.
The external authentication process works as follows:
- The credentials supplied when connecting to a server are passed to the Active Directory domain controller for authentication.
- The domain controller checks the credentials. If they are invalid, the authentication fails immediately.
- If the credentials are valid, the Active Directory controller is queried to get the subject identifier and group membership associated with the credentials.
- If the subject identifier matches the one stored in XenServer, the authentication is completed successfully.
When you join a domain, you enable Active Directory authentication for the pool. However, when a pool is joined to a domain, only users in that domain (or a domain with which it has trust relationships) can connect to the pool.
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.