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à))
Assign roles to users and groups
All XenServer users must have an RBAC role. In XenServer, you must first assign a role to the newly created user before they can use the account. Note that XenServer does not automatically assign a role to the newly created user. As a result, these accounts will not have any access to the XenServer pool until you assign them a role.
Before you can assign a role to a user or group, you must add the user or group’s Active Directory account to XenServer after joining the associated domain as described in Join a domain and add RBAC users.
You can assign a user a different role by one of the following methods:
- Change the role assigned to the user in the Select Roles dialog in XenCenter. This requires the Assign/modify role permission, which is only available to a Pool Administrator.
- Modify the user’s containing group membership in Active Directory (so that the user becomes part of a group that is assigned a different role).
If, on separate occasions, an administrator indirectly applies multiple roles to a user (for example, by the user being a member of multiple groups), XenServer grants the user the permissions from the highest role to which he or she was assigned.
- In the Resources pane, select the pool or server that contains the user or group.
- Click the Users tab.
- In the Users and Groups with Access pane, select the user or group to which you want to assign permissions.
- Click Change Role.
In the Select Roles dialog, select the role you want to apply and click Save. For information about the permissions associated with each role, see Definitions of RBAC roles and permissions.
When you are assigning a role, you can select multiple users simultaneously by pressing the CTRL key and selecting the user accounts.
(Optional.) When changing a role, if the user is currently logged on to the pool and you want them to receive their new permissions immediately, click Logout User. This disconnects all of the user’s sessions on the pool so the user receives a new session with the modified role.
When changing a role, for the new role to take effect, the user must log out and log back in again. You can force this log out by clicking the Logout User button. (Forcing logouts requires the Logout active user connections permission, which is available to a Pool Administrator or Pool Operator).
In XenServer v6.1.0 and earlier, when new users are added, they are automatically assigned the Pool Administrator role. In XenServer Enterprise and higher, when you add new users, XenServer does not assign newly added user accounts roles automatically. You must assign roles to new accounts separately.
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.