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 an AWS catalog
Manage machine catalogs describes the wizards that manage a machine catalog. The following information covers details specific to AWS cloud environments.
Note:
Before managing an AWS catalog, you need to finish creating an AWS catalog. See Create an AWS catalog.
Remove tags
When you create a catalog or a VM, tags are created on the following resources:
- Virtual machine
- Root disk volume
- Identity disk volume
- Elastic network interface (ENI)
- Root disk image (AMI)
- Launch template
- Snapshot of AMI or root disk
You can remove VMs and machine catalogs from Citrix database and remove Citrix-created tags. You can use:
-
Remove-ProvVM
withForgetVM
parameter to remove VMs and Citrix-created tags from a single VM or a list of VMs from a machine catalog.Note:
With the
ForgetVM
parameter, the VMs are removed from the Citrix’s provisioning scheme database, however, the VMs continue to remain in the hypervisor. -
Remove-ProvScheme
withForgetVM
parameter to remove a machine catalog from the Citrix database and resources from a machine catalog.
To do this:
- Open a PowerShell window.
- Run
asnp citrix*
to load the Citrix-specific PowerShell modules. -
Unlock the VM before removing the VMs. For example:
Unlock-ProvVM -ProvisioningSchemeName "<name>" -VMID "<id" <!--NeedCopy-->
-
Run one of the following commands to remove VMs, machine catalog, and Citrix-created tags from resources.
-
Run
Remove-ProvVM
withForgetVM
to remove VMs from Citrix database and Citrix-created tags from VMs. For example:Remove-ProvVM -ProvisioningSchemeName "<name>" -VMName "<name>" -ForgetVM <!--NeedCopy-->
-
Run
Remove-ProvScheme
to remove machine catalog from Citrix database and resources from a machine catalog. For example:Run Remove-ProvScheme -ProvisioningSchemeName "<name>" -ForgetVM <!--NeedCopy-->
-
-
Verify that the VM is removed from the Delivery Controller, but, not from the hypervisor.
- Run
Get-ProvVM -ProvisioningSchemeName "<name>" -VMName "<name>"
. This must return nothing. -
Go to AWS EC2 console. You must see the VMs, however, the Citrix-created tags are now removed. Citrix-created tags from the following resources are removed:
- Virtual machine
- Root disk volume
- Identity disk volume
- ENI
- Run
-
If you remove the machine catalog, verify that the catalog is removed from the Delivery Controller.
- Run
Get-ProvScheme -ProvisioningSchemeName "forgetvmdemo"
. This must return an error. -
Verify in AWS EC2 console that the following resources are removed.
- Root disk image (AMI)
- Launch template
- Snapshot of AMI or root disk
- Run
Identify resources created by MCS
Following are the tags that MCS adds to the resources on AWS platform. The tags in the table are represented as “key”:”value”.
Resource name | Tag |
---|---|
ID disk | “Name”: “VMName_IdentityDisk” |
“XdConfig”: “XdProvisioned=true” | |
“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
Image | “XdConfig”: “XdProvisioned=true” |
“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
ENI | “Description”: “XD Nic” |
“XdConfig”: “XdProvisioned=true” | |
“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
OS disk | “Name”: “VMName_rootDisk” |
“XdConfig”: “XdProvisioned=True” | |
“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
[when AwsCaptureInstanceProperties = true] “Citrix Resource”: “” | |
[when AwsCaptureInstanceProperties = true and AwsOperationalResourcesTagging = true] “CitrixOperationalResource”: “” | |
PrepVM | “Name”: “Preparation - CatalogName - xxxxxxxxxx” |
“XdConfig”: “XdProvisioned=true” | |
“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
[when AwsCaptureInstanceProperties = true] “Citrix Resource”: “” | |
[when AwsCaptureInstanceProperties = true and AwsOperationalResourcesTagging = true] “CitrixOperationalResource”: “” | |
Published snapshot | “XdConfig”: “XdProvisioned=true” |
If not a snapshot for Volume Worker AMI, then “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
Template | [when AwsCaptureInstanceProperties = true] “XdConfig”: “XdProvisioned=true” |
[when AwsCaptureInstanceProperties = true] “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
[when AwsCaptureInstanceProperties = true] “CitrixResource”: “” | |
[when AwsCaptureInstanceProperties = true and AwsOperationalResourcesTagging = true] “CitrixOperationalResource”: “” | |
VM in catalog | “XdConfig”: “XdProvisioned=true” |
“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
[when AwsCaptureInstanceProperties = true] “CitrixResource”: “” | |
[when AwsCaptureInstanceProperties = true] “aws:ec2launchtemplate:id”:”lt-xxxx” | |
[when AwsCaptureInstanceProperties = true] “aws:ec2launchtemplate:version”: “n” | |
[when AwsCaptureInstanceProperties = true and AwsOperationalResourcesTagging = true] “CitrixOperationalResource”: “” | |
Volume worker AMI | “XdConfig”: “XdProvisioned=true” |
Volume worker bootstraper | “Name”: “XenDesktop Temp” |
“XdConfig”: “XdProvisioned=true” | |
“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” | |
[when AwsCaptureInstanceProperties = true and AwsOperationalResourcesTagging = true] “CitrixVolumeWorkerBootstrapper”: “” | |
Volume worker instance | “Name”: “Citrix.XD.Volumeworker-xxxx-xx-xx-xx-xxxx” |
“XdConfig”: “XdProvisioned=true” |
Convert legacy MCS catalogs in AWS to machine profile-based catalogs
To convert a non-machine profile-based machine catalog to a machine profiled-based machine catalog, complete the following steps:
- On the Machine Catalogs page, right-click the Machine Catalog name that you want to convert, and then select Edit Machine Catalog.
- On the Edit Machine Catalog > Machine Profile page, select the Use a machine profile check box.
- Click Select a machine profile.
- On the Select a machine profile page, select a virtual machine or launch template to use as the machine profile.
- If some current settings differ from the new machine profile settings, select the required option for the settings you want to use and click Continue.
- Click Apply.
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.