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!
Create a XenServer catalog
Create machine catalogs describes the wizards that create a machine catalog. The following information covers details specific to XenServer (formerly Citrix Hypervisor) virtualization environments.
Note:
Before creating a XenServer catalog, you need to finish creating a connection to XenServer. See Connection to XenServer.
Create a machine catalog using a GPU-capable XenServer
GPU-capable machines require a dedicated master image. Those VMs require video card drivers that support GPUs. Configure GPU-capable machines to allow the VM to operate with software that uses the GPU for operations.
- In XenCenter, create a VM with standard VGA, networks, and vCPU.
- Update the VM configuration to enable GPU use (either Passthrough or vGPU).
- Install a supported operating system and enable RDP.
- Install Citrix VM Tools and NVIDIA drivers.
- Turn off the Virtual Network Computing (VNC) Admin Console to optimize performance, and then restart the VM.
- You are prompted to use RDP. Using RDP, install the VDA and then restart the VM.
- Optionally, create a snapshot for the VM as a baseline template for other GPU master images.
- Using RDP, install customer-specific applications that are configured in XenCenter and use GPU capabilities.
Create a machine profile-based machine catalog using PowerShell
When you create a catalog to provision machines using MCS, you can use a machine profile to capture the hardware properties from a virtual machine and apply them to newly provisioned VMs in the catalog. If the MachineProfile
parameter is not used, the hardware properties are captured from the master image VM or snapshot.
Note:
Currently, you can use only a snapshot as a machine profile input.
You can update the memory and disk cache sizes after creating the MCS catalogs when MCSIO is enabled. You can explicitly configure the following parameters to overwrite the values of the parameters in the machine profile input:
VMCpuCount
VMMemory
NetworkMapping
Create a catalog with a machine profile
- Open the PowerShell window.
- Run
asnp citrix*
. -
Create an identity pool. The identity pool is a container for the Active Directory (AD) accounts for the VMs to be created. For example:
New-AcctIdentityPool -Domain "citrix-xxxxxx.local" -IdentityPoolName "ExampleIdentityPool" -NamingScheme "abc1-##" -NamingSchemeType "Numeric" -Scope @() -ZoneUid "xxxxxxxx" <!--NeedCopy-->
-
Create the required AD computer accounts in Active Directory.
$password = "password123" | ConvertTo-SecureString -AsPlainText -Force New-AcctADAccount -IdentityPoolName "ExampleIdentityPool" -Count 10 -ADUserName "citrix-xxxxxx\admin1" -ADPassword $password Set-AcctAdAccountUserCert -IdentityPoolName "ExampleIdentityPool" -ADUserName "citrix-xxxxxx\admin1" -ADPassword $password <!--NeedCopy-->
-
Run the
New-ProvScheme
command to create a catalog. For example:New-ProvScheme -CleanOnBoot -HostingUnitName "ExampleHostingUnit" -IdentityPoolName "ExampleIdentityPool" -InitialBatchSizeHint 2 -CustomProperties '<CustomProperties xmlns="http://schemas.citrix.com/2014/xd/machinecreation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Property xsi:type="StringProperty" Name="UseManagedDisks" Value="true" /> </CustomProperties>' -MasterImageVM "XDHyp:\HostingUnits\ExampleHostingUnit\ExampleVDA.vm\ExampleVDA.snapshot" -ProvisioningSchemeName "ExampleCatalog" -Scope @() -SecurityGroup @() -MachineProfile "XDHyp:\HostingUnits\ExampleHostingUnit\ExampleMachineProfile.vm\ExampleSnapshot.snapshot" <!--NeedCopy-->
-
Register provisioning scheme as a broker catalog. For example:
$ConfigZone = Get-ConfigZone | Where-Object { $_.Name -eq "xxxxxx" } New-BrokerCatalog -Name "MPLT1" -AllocationType Random -Description "Machine profile catalog" -ProvisioningSchemeId fe7df345-244e-4xxxx-xxxxxxxxx -ProvisioningType Mcs -SessionSupport MultiSession -PersistUserChanges Discard -ZoneUid ($ConfigZone.Uid) <!--NeedCopy-->
- Add VMs to the catalog.
Update a catalog with a new machine profile
Note:
- The
Set-ProvScheme
command in this case does not change the machine profile of the existing VMs in the catalog. Only the newly created VMs added to the catalog have the new machine profile.- You cannot convert a machine profile-based machine catalog to non-machine profile-based machine catalog.
To update a catalog with a new machine profile:
-
Run the
Set-ProvScheme
command. For example:Set-ProvScheme -ProvisioningSchemeName "ExampleCatalog" -MachineProfile "XDHyp:\HostingUnits\ExampleHostingUnit\ExampleMachineProfileVm.vm\ExampleMachineProfileSnapshot.snapshot" <!--NeedCopy-->
For more information on the Set-ProvScheme command, see Set-ProvScheme.
Where to go next
- If this is the first catalog created, you are guided to create a delivery group.
- To review the entire configuration process, see Plan and build a deployment.
- To manage catalogs, see Manage machine catalogs and Manage a XenServer catalog.
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.