-
-
Migrate workloads between resource locations using Image Portability Service
-
-
-
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!
Manage a XenServer catalog
Manage machine catalogs describes the wizards that manage a machine catalog. The following information covers details specific to XenServer virtualization environments.
Note:
Before managing a XenServer catalog, you need to finish creating a XenServer catalog. See Create a XenServer catalog.
Identify resources created by MCS
When the Machine Creation Services (MCS) generates resources like disks, it assigns a ProvisioningScheme ID tag for better utilization of those resources.
Tags are helpful to administrators as they can better manage and organize the resources. For example, if resources, like unused disks, are tagged, then administrators can easily identify where the resource is created, making the cleanup process efficient.
Following are the tags that MCS adds to the resources on XenServer platform. The tags in the table are represented as “key”:”value”.
Resource name | Tag |
---|---|
Copy of disk on each network or local storage (on-prem only) | “CitrixProvisioningSchemeId” : “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
ID disk | “CitrixProvisioningSchemeId” : “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
OS disk | “CitrixProvisioningSchemeId” : “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
Preparation VM | “CitrixProvisioningSchemeId” : “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
VM in catalog | “CitrixProvisioningSchemeId” : “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
WBC disk | “CitrixProvisioningSchemeId” : “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
Retrieve information about provisioning scheme
To retrieve detailed information about the provisioning scheme, you can execute the following PowerShell commands. Replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
with the actual Provisioning Scheme ID:
-
Replace the placeholder ID with your actual Provisioning Scheme ID
$provisioningSchemeId = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" <!--NeedCopy-->
-
Retrieve detailed information about the provisioning scheme:
Get-ProvisioningScheme -Id $provisioningSchemeId <!--NeedCopy-->
Retrieve list of resources created by MCS
Run the following commnds to get a comprehensive list of resources created by MCS.
-
Replace the placeholder ID with your actual Provisioning Scheme ID.
$provisioningSchemeId = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" <!--NeedCopy-->
-
Retrieve the entire list of resources created by MCS.
Get-ProvResource -ProvisioningSchemeUid $provisioningSchemeId | ConvertTo-JSON -Depth 6 <!--NeedCopy-->
After execution, you get the following output:
- The name and ID of the provisioning scheme.
- A list of provisioning image versions within the provisioning scheme. Each entry includes:
- The image name and ID.
- The Disk ID and Storage ID of the disk.
- A list of provisioning VMs. Each entry includes:
- The OS disk ID and parent disk ID of the OS disk .
- The Storage ID of the OS disk.
- The Identity disk and its Storage ID.
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.