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 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.
Storage migration of VMs
You can move the disk storage of existing VMs from an old storage to a new storage. During migration, MCS retains the VM capabilities such as power management, reset OS disk, and so on. You can also add new VMs to the machine catalog using the new disk storage. To do this, use the PowerShell command Move-ProvVMDisk
.
Currently, you can only migrate full clone persistent VMs.
The new storage must satisfy the following conditions:
- It must be within the same cluster of the old storage.
- The host on which the VM is running must have access to both the old and new datastores.
You can do the following tasks:
- Migrate the disk storage
- Deprecate the old storage
Migrate the disk storage
To migrate the disk storage:
-
Add a new storage to an existing hosting unit. Change the old storage to Superseded. You can do this using Studio or PowerShell commands.
- If using Studio, see Edit storage.
- If using PowerShell commands:
- Run
Add-Hyphostingunitstorage
to add the new storage to the existing hosting unit. - Run
Set-Hyphostingunitstorage
with Superseded as true to disable new VM creation in the old storage.
- Run
- Turn off the VMs and turn on the Maintenance Mode.
-
Move disk storage of the VMs to the new storage and update the storage information. For example:
Move-ProvVMDisk -ProvisioningSchemeName "myFullCloneProvScheme" -VMName ("VMware-TestVM01", "VMware-TestVM02") -DiskType OS,Identity -DestinationStorageId datastore1,datastore1 <!--NeedCopy-->
-
Get the task ID of the migration. For example:
,(Get-ProvVM -ProvisioningSchemeName xxxxx) | Move-ProvVMDisk -ProvisioningSchemeName xxxxx -DiskType OS,Identity -DestinationStorageId datastore1,datastore1 <!--NeedCopy-->
-
Check the status of the migration.
-
(Get-ProvTask -TaskID xxxxxxxxx).DiskMovedVirtualMachines
: Provides the list of VMs with successful disk migration, including the VMs that are already migrated to the new storage. -
(Get-ProvTask -TaskID xxxxxxxxx).DiskMoveFailedVirtualMachines
: Provides the list of VMs with failed migration. -
(Get-ProvTask -TaskID xxxxxxxxx).NotStartedVirtualMachines
: Provides the list of VMs whose migration has not yet started. -
Get-ProvVM -ProvisioningSchemeName xxxxx -VMName "VMware-TestVM01
: Provides the updated VM properties after the migration. Check the properties such asStorageId
,AssignedImage
,BootedImage
,IdentityDiskId
,IdentityDiskStorage
, andLastBootTime
.
-
After migrating the disks of MCS created VMs with snapshot, you might see the warning Consolidation is required in the VSphere Client. To consolidate and avoid data loss:
- Take a VMware VM backup. For example, transfer all VM files into another folder on a datastore.
- After you see the warning, click Consolidate, and then click OK to confirm the consolidation.
Deprecate the old storage
To deprecate the old storage after VMs disk migration:
-
Get the information about the base disks and machine count in each disk storage of the hosting unit. For example:
$result=Get-ProvSchemeResourceInStorage -ProvisioningSchemeName xxxxx $result $result.ProvResourceInStorage | Format-List -Property * <!--NeedCopy-->
After a successful migration, MCS automatically removes the stale base disk and there are no machines in the old storage. Therefore, after running the command, make sure that there are no machines and base disk in the old storage.
-
Run
Remove-Hyphostingunitstorage
to entirely remove the old storage from the hosting unit. You can also use Studio to remove the old storage.
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.