- What's new
- System requirements
- Provisioning Services product overview
- Upgrading a Provisioning Services farm
-
Installing and configuring Provisioning Services
- Pre-installation tasks
- Licensing
- Upgrading a Provisioning Services target device vDisk using in-place upgrade
- Configuring UEFI pre-boot environments
- Installing Provisioning Services Server software
- Configuring the farm
- Running the Configuration Wizard silently
- Installing Provisioning Services Console software
- Adding additional Provisioning Servers
- Preparing a master target device for imaging
- Using the Imaging Wizard to create a new vDisk
- Assigning vDisks to target devices
- Uninstalling Provisioning Services product software
- Configuring the bootstrap file from the console
- Getting the bootstrap file
- Using the Manage Boot Devices utility
- CIS Problem Reporting
- Enable SQL Server Always On multi-subnet failover
- About SAN policies
- Configure Linux Streaming
- Configure PVS-Accelerator
- Using the Provisioning Services Console
- Managing farms
- Managing sites
- Managing administrative roles
- Managing stores
-
Managing Provisioning Servers
- Provisioning Servers in the console
- Provisioning Server properties
- Overview of Provisioning Server tasks
- Copying and pasting Provisioning Server properties
- Deleting a Provisioning Server
- Starting, stopping, or restarting Provisioning Services
- Showing Provisioning Server connections
- Balancing the target device load on Provisioning Servers
- Checking for Provisioning Server vDisk access updates
- Configuring Provisioning Servers manually
- Disabling write cache to improve performance when using storage device drives
- Providing Provisioning Servers with access to stores
-
Managing target devices
- Configuring the BIOS-embedded bootstrap
- Adding target devices to the database
- Setting the target device as the template for this collection
- Copying and pasting target device properties
- Booting target devices
- Checking a target device's status from the console
- Sending messages to target devices
- Disabling a target device
- Deleting target devices
- Shutting down target devices
- Restarting target devices
- Using the Status Tray on a target device
- Managing target device Personality
- Moving target devices between collections
- Changing the device status to Down
- Target device properties
- Configuring target devices that use personal vDisks
-
Managing vDisks
- Creating vDisks
- Prerequisites for deploying vDisks
- Configuring the vDisk access mode
- Selecting the write cache destination for standard vDisk images
- Configuring a vDisk for Microsoft Volume Licensing
- Managing load balancing across servers
- Support for replicated vDisk storage
- Exporting and importing vDisks
- Releasing vDisk locks
- Copying and pasting vDisk properties
- Adding existing vDisks to a vDisk pool or store
- Backing up a vDisk
- Viewing vDisk usage
- Deleting cache on a difference disk
- vDisk properties
- Assigning vDisks and versions to target devices
- Updating vDisks
- Retiring or deleting vDisks
-
Managing device collections
- Device collection properties
- Creating a device collection
- Importing target devices into a collection
- Deleting a collection
- Refreshing a collection in the console
- Booting target devices within a collection
- Restarting target devices within a collection
- Shutting down target devices within a collection
- Sending messages to target devices within a collection
- Moving collections within a site
- Managing views
- Managing for highly available implementations
- Configuring vDisks for Active Directory management
- Network components
- Managing printers
- Using the Streamed VM Setup Wizard
- Deploying virtual desktops to VMs using the XenDesktop Setup Wizard
- Provisioning vGPU-enabled XenDesktop machines
- Configuring Personal vDisks
- Logging
- Auditing
- APIs
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
About the common vDisk image feature
December 28, 2018
| Contributed by:
The Common Image feature allows a single vDisk to simultaneously support multiple target device platforms, greatly reducing the number of vDisks an administrator must maintain. The procedure for creating a common image depends on the target device platform.
Supported target device platforms include:
- A combination of XenServer VMs and physical devices (virtual-to-virtual and virtual-to-physical). For details, refer to Create Common Images for use with XenServer VMs and Physical Devices, or Blade Servers.
- Multiple types of physical devices (different motherboards, network cards, video cards, and other hardware devices). For details, refer to Creating a Common Image for use with Multiple Physical Device Types
- Blade servers. For details, refer to Create Common Images for use with XenServer VMs and Physical Devices, or Blade Servers
The official version of this content is in English. Some of the Citrix documentation content is machine translated for your convenience only. Citrix has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Citrix product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Citrix, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Citrix will not be held responsible for any damage or issues that may arise from using machine-translated content.
Dieser Service enthält möglicherweise Übersetzungen, die von Google bereitgestellt werden. GOOGLE HAFTET KEINE GARANTIEN IM ZUSAMMENHANG MIT DEN ÜBERSETZUNGEN, AUSDRÜCKLICH ODER STILLSCHWEIGEND, EINSCHLIESSLICH GEWÄHRLEISTUNGEN DER GENAUIGKEIT, ZUVERLÄSSIGKEIT UND JEGLICHER GARANTIERUNG DER MARKTGÄNGIGKEIT, EIGNUNG FÜR EINEN BESTIMMTEN ZWECK UND UNGÜLTIGKEIT.
CE SERVICE PEUT CONTENIR DES TRADUCTIONS DE GOOGLE. GOOGLE DÉCLINE TOUTES LES GARANTIES RELATIVES AUX TRADUCTIONS, EXPRESSES OU IMPLICITES, Y COMPRIS TOUTES GARANTIES D'EXACTITUDE, DE FIABILITÉ ET TOUTE GARANTIE IMPLICITE DE QUALITÉ MARCHANDE, D'ADÉQUATION À UN USAGE PARTICULIER ET DE NON-INFRACTION.
ESTE SERVICIO PUEDE CONTENER TRADUCCIONES REALIZADAS POR GOOGLE. GOOGLE RECHAZA TODAS LAS GARANTÍAS RELACIONADAS CON LAS TRADUCCIONES, EXPRESAS O IMPLÍCITAS, INCLUYENDO CUALQUIER GARANTÍA DE EXACTITUD, FIABILIDAD Y CUALQUIER GARANTÍA IMPLÍCITA DE COMERCIABILIDAD, ADECUACIÓN PARA UN PROPÓSITO PARTICULAR Y NO FRECUENCIA.
本服务可能包含GOOGLE提供的翻译服务。 GOOGLE不承担与翻译有关的所有明示或暗示的担保，包括对准确性，可靠性以及对适销性，特定用途的适用性和不侵权的任何暗示担保的任何担保。
このサービスには、Googleによる翻訳が含まれている場合があります。 Googleは、正確性、信頼性、および商品性、特定の目的に対する適合性についての黙示の保証を含む、明示または黙示を問わず、翻訳に関連するすべての保証を否認します。
Support:
https://www.citrix.com/support
Feedback and forums:
https://discussions.citrix.com
Version