-
-
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 VMware catalog
Manage machine catalogs describes the wizards that manage a machine catalog. The following information covers details specific to VMware virtualization environments.
Note:
Before managing a VMware catalog, you need to finish creating a VMware catalog. See Create a VMware catalog.
Update provisioned VMs to current provisioning scheme state
The Set-ProvScheme
command changes the provisioning scheme. However, it does not affect existing VMs. Using the PowerShell command Set-ProvVMUpdateTimeWindow
, you can apply the current provisioning scheme to an existing persistent or non-persistent VM or set of VMs. This feature is applicable to machine profile and non-machine profile-based machine catalog.
You can update the following:
- VMCpuCount: Provisioning scheme property
- VMMemoryMB: Provisioning scheme property
- Folder ID: Custom property
- Subnet mapping: Provisioning scheme property
- Hardware version of VM: Only for machine profile-based machine catalog
- Machine profile: Only for machine profile-based machine catalog
You can update:
- A single VM
- A list of specific VMs or all existing VMs associated with a provisioning scheme ID
- A list of specific VMs or all existing VMs associated with a provisioning scheme name (machine catalog name)
Before updating the existing VMs
-
Check the configuration of the existing VMs. For example:
Get-ProvScheme | select ProvisioningSchemeName, ProvisioningSchemeVersion <!--NeedCopy-->
-
Update the provisioning scheme. For example:
$customProperties=<CustomProperties xmlns="http://schemas.citrix.com/2014/xd/machinecreation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Property xsi:type="StringProperty" Name="FolderId" Value="FOLDER_ID"/></CustomProperties> $memoryMb=<DOUBLE THE "UPDATE" MACHINE PROFILE> Set-ProvScheme -ProvisioningSchemeName my-catalog -VMCpuCount 4 -VmMemoryMb $memoryMb -CustomProperties $customerProperties -NetworkMapping @{"1" = "<A_NETWORK_PATH_FROM_THE_HOSTING_UNIT>"} -MachineProfile "<PATH_TO_UPDATE_MACHINE_PROFILE>" <!--NeedCopy-->
-
Check if the current property of the VM matches the current provisioning scheme, and if there is any pending update action on the VM. For example:
Get-ProvVM | select VMName, ProvisioningSchemeUpdateRequested, ProvisioningSchemeVersion <!--NeedCopy-->
You can also find VMs with a particular version. For example:
Get-ProvVM -Filter "ProvisioningSchemeVersion -eq 1" | select VMName, ProvisioningSchemeVersion <!--NeedCopy-->
Request updates for existing VMs to apply at the next restart
-
Run the following commands to update existing VMs and have the updates apply at the next restart.
-
To update all the existing VMs. For example:
Set-ProvVMUpdateTimeWindow -ProvisioningSchemeName my-catalog -StartsNow -DurationInMinutes -1 <!--NeedCopy-->
-
To update a list of specific VMs. For example:
Set-ProvVMUpdateTimeWindow -ProvisioningSchemeName my-catalog -VMName <List-Of-Vm-Names> -StartsNow -DurationInMinutes -1 <!--NeedCopy-->
-
To update VMs based on the output of
Get-ProvVM
. For example:Get-ProvVM -ProvisioningSchemeName "my-catalog" | Set-ProvVMUpdateTimeWindow -ProvisioningSchemeName my-catalog -StartsNow -DurationInMinutes -1 <!--NeedCopy-->
Note:
- The
StartsNow
indicates that the scheduled start time is the current time. - The
DurationInMinutes
with a negative number (for example, –1) indicates no upper bound on the schedule’s time window.
-
-
Find VMs with an update scheduled. For example:
Get-ProvVM -Filter "ProvisioningSchemeUpdateAfter" | select VMName, ProvisioningSchemeUpdateAfter <!--NeedCopy-->
-
Restart the VMs. At the next power-up, property changes are applied to the existing VMs. You can check the updated status using the following command. For example:
Get-ProvVM | select VMName, ProvisioningSchemeUpdateRequested, ProvisioningSchemeVersion <!--NeedCopy-->
Cancel the configuration update
You can also cancel a configuration update of a single VM, multiple VMs, or an entire catalog. To cancel a configuration update:
-
Run
Clear-ProvVMUpdateTimeWindow
. For example:-
To cancel the configuration update scheduled for a single VM:
Clear-ProvVMUpdateTimeWindow -ProvisioningSchemeName “ my-catalog “ -VMName “vm1” <!--NeedCopy-->
-
To cancel the configuration update scheduled for multiple VMs:
Clear-ProvVMUpdateTimeWindow -ProvisioningSchemeName "my-catalog" -VMName "vm1","vm2" <!--NeedCopy-->
Note:
The VMs must be from the same catalog.
-
Update the folder ID of a machine catalog
You can update the folder ID of an MCS machine catalog by specifying the FolderId
in the custom properties of Set-ProvScheme
command. The VMs created after updating the folder ID are created under this new folder ID. If this property is not specified in CustomProperties
, then VMs are created under the folder where the master image is located.
Perform the following steps to update the folder ID of a machine catalog.
- Open a Web browser and enter the URL for the vSphere Web Client.
- Enter the credentials and click Login.
- Create a VM placement folder in vSphere Web Client.
- Open a PowerShell window.
- Run asnp citrix* to load the Citrix-specific PowerShell modules.
-
Specify the
FolderID
in theCustomProperties
ofSet-ProvScheme
. In this example, the folder ID value isgroup-v2406
.Set-ProvScheme -ProvisioningSchemeUid "50bb319c-2e83-4a37-9ea1-94f630687372" -CustomProperties "<CustomProperties xmlns=""http://schemas.citrix.com/2014/xd/machinecreation"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance""><Property xsi:type=""StringProperty"" Name=""FolderId"" Value=""group-v2406"" /></CustomProperties>" <!--NeedCopy-->
- Add a VM to the machine catalog using Studio.
- Check the new VM on vSphere Web Client. The new VM is created under the new folder.
Find the folder ID using PowerShell commands
Use the PowerShell command Get-HypConfigurationDataForItem
to find the folder ID for an existing folder in a VMware Hypervisor.
Create a hosting connection and resource group for a VMware Hypervisor. Then, perform the following steps to find the folder ID of a folder on that hypervisor.
-
Determine the
XDHyp
path to the root of the VM folder tree. For example:XDHyp:\Connections\VMwareConn\Datacenter.datacenter <!--NeedCopy-->
-
Use
Get-HypConfigurationDataForItem
to retrieve the tree structure. For example:Get-HypConfigurationDataForItem -LiteralPath XDHyp:\Connections\VMwareConn\Datacenter.datacenter <!--NeedCopy-->
-
Run the following command to identify the folder ID from the output XML. In this example, look for the folder ID of
ExampleFolder
in the XML output.$result = Get-HypConfigurationDataForItem -LiteralPath XDHyp:\Connections\VMwareConn\Datacenter.datacenter $result.VmPlacementFolder <!--NeedCopy-->
XML output:
<?xml version="1.0" encoding="utf-16"?> <CtxVmPlacementFolder xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Name>vm</Name> <Id>group-v4</Id> <SubFolder> <CtxVmPlacementFolder> <Name>vCLS</Name> <Id>group-v75</Id> <SubFolder /> </CtxVmPlacementFolder> <CtxVmPlacementFolder> <Name>MyOtherFolder</Name> <Id>group-v1110</Id> <SubFolder /> </CtxVmPlacementFolder> <CtxVmPlacementFolder> <Name>ExampleFolder</Name> <Id>group-v4658</Id> <SubFolder /> </CtxVmPlacementFolder> </SubFolder> </CtxVmPlacementFolder> <!--NeedCopy-->
Find the folder ID in vSphere
Access the MOB on any ESXi or vCenter server system to find the folder ID of the VMs.
The Managed Object Browser (MOB) is a web-based server application available inbuilt in all ESX/ESXi and vCenter server systems. This vSphere utility allows you to view detailed information about objects like VMs, datastores, and resource pools.
- Open a web browser and enter
http://x.x.x.x/mob
, where x.x.x.x is the IP address of the vCenter Server or ESX/ESXi host. For example, https://10.60.4.70/mob. - On the Home page of MOB, click the value of the property content.
- Click the value of the rootFolder.
- Click the value of the childEntity.
- Click the value of the vmFolder.
- You can find the folder ID in the value of the childEntity.
Identify resources created by MCS
Following are the tags that MCS adds to the resources on VMware platform. The tags in the table are represented as “key”:”value”.
Resource name | Tag |
---|---|
Preparation VM | “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
“XdConfig:”XdProvisioned=True” | |
VM in catalog | “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” |
“XdConfig:”XdProvisioned=True” |
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.