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!
Connection to XenServer
Create and manage connections and resources provides detailed instructions using the wizard to create a connection. Before establishing a connection to XenServer (formerly Citrix Hypervisor), you need to first finish setting up your XenServer as a host. See Add a resource type or activate an unused domain in Citrix Cloud.
Create a connection to XenServer
When you create a connection to XenServer, you must provide the credentials for a Virtual Machine Power Administrator (VM Power Admin) or higher-level user.
Citrix recommends using HTTPS to secure communications with XenServer. To use HTTPS, you must replace the default TLS certificate installed on XenServer. For more information, see Install a TLS certificate on your server.
You can configure high availability if it is enabled on the XenServer server. Citrix recommends that you select all servers in the pool (from Edit High Availability) to allow communication with the XenServer server if the pool master fails.
Note:
If you are using HTTPS and want to configure high-availability servers, do not install a wildcard certificate for all servers in a pool. An individual certificate for each server is required.
When using local storage on one or more XenServer hosts for temporary data storage, make sure that each storage location in the pool has a unique name. (To change a name in XenCenter, right-click the storage and edit the name property.)
If you connect to the XenServer that supports vGPU, you can verify the GPU group and the GPU type in the Summary page of the wizard for creating a connection.
Use IntelliCache for XenServer connections
Using IntelliCache, hosted VDI deployments are more cost-effective because you can use a combination of shared storage and local storage. This enhances performance and reduces network traffic. The local storage caches the master image from the shared storage, which reduces the amount of reads on the shared storage. For shared desktops, writes to the differencing disks are written to local storage on the host and not to shared storage.
The important considerations are:
- Shared storage must be NFS when using IntelliCache.
- Citrix recommends that you use a high-performance local storage device to ensure the fastest possible data transfer.
To use IntelliCache, enable IntelliCache as detailed:
- When installing XenServer, select Enable thin provisioning. See Install the XenServer host for information on installing XenServer host from local media. Citrix does not support mixed pools of servers with some servers that have IntelliCache enabled and some servers that do not IntelliCache enabled.
- In Citrix DaaS, IntelliCache is disabled by default. You can change the setting only when creating a XenServer connection. You cannot disable IntelliCache later. When you create a XenServer connection:
- Select Shared as the storage type.
- Select the Use IntelliCache checkbox.
See IntelliCache for more information.
Required XenServer permissions
The XenServer permissions are role-based (RBAC). The Role-Based Access Control (RBAC) feature in XenServer allows you to assign users, roles, and permissions to control who has access to your XenServer and what actions they can perform. The XenServer RBAC system maps a user (or a group of users) to defined roles (a named set of permissions). The roles have associated XenServer permissions to perform certain operations.
For more information, see Role-based access control.
The role hierarchy, in order of increasing permissions is: Read-Only → VM Operator → VM Admin → VM Power Admin → Pool Operator → Pool Admin.
The following section summarizes the minimum role required for each provisioning task.
Creating a host connection
| Task | Minimum role required |
|---|---|
| Add a host connection using the information obtained from XenServer | Read-Only |
| View users and their assigned role | Read-Only |
Power management of VMs
| Task | Minimum role required |
|---|---|
| Power on or off the VMs | VM Operator |
Creating, updating, or deleting VMs
| Task | Minimum role required |
|---|---|
| Add or remove VMs to existing snapshots schedules | VM Power Admin |
| Add, modify, delete snapshot schedules | Pool Operator |
| Publish master image | Pool Operator (Requires switch-port locking) |
| Create a machine catalog | Pool Operator: Requires switch-port locking |
| Add or remove VMs (not GPU enabled VMs) | VM Admin |
| Add or remove VMs (GPU enabled VMs) | Pool Operator |
| Add, remove, or configure virtual disk or CD devices | VM Admin |
| Manage Tags | VM Operator |
For more information on RBAC roles and permissions, see RBAC roles and permissions.
For information on switch port locking, see Use switch port locking.
Where to go next
- If you’re in the initial deployment process, see Create machine catalogs.
- For XenServer specific information, see Create a XenServer catalog.
More information
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.