Import a provisioning scheme into the site
Import-ProvScheme [-ProvisioningSchemeData <String>] [-LoggingId <Guid>] [-BearerToken <String>] [-AdminAddress <String>] [<CommonParameters>]
This cmdlet imports a provisioning scheme into the site, the data passed to this cmdlet should be obtained via the Export-ProvScheme cmdlet generally obtained form a different site
|Name||Description||Required?||Pipeline Input||Default Value|
|ProvisioningSchemeData||Json encoded string of a provisioning scheme||false||true (ByPropertyName)|
|LoggingId||Specifies the identifier of the high-level operation this cmdlet call forms a part of. Citrix Studio and Director typically create high-level operations. PowerShell scripts can also wrap a series of cmdlet calls in a high-level operation by way of the Start-LogHighLevelOperation and Stop-LogHighLevelOperation cmdlets.||false||false|
|BearerToken||Specifies the bearer token assigned to the calling user||false||false|
|AdminAddress||Specifies the address of a XenDesktop controller the PowerShell snap-in will connect to. You can provide this as a host name or an IP address.||false||false||Localhost. Once a value is provided by any cmdlet, this value becomes the default.|
This object provides details of the provisioning scheme and contains the following information:
The unique identifier for the provisioning scheme.
The name of the provisioning scheme.
The number of processors that VMs will be created with when using this scheme.
The maximum amount of memory that VMs will be created with when using this scheme.
The path within the hosting unit provider to the copy of the VM snapshot that the scheme uses.
The date and time that the copy was made of the VM snapshot used by the scheme.
The unique identifier of the identity pool (from the ADIdentity PowerShell snap-in) that the scheme uses.
The name of the identity pool (from the ADIdentity PowerShell snap-in) that the scheme uses.
The unique identifier of the hosting unit (from the Hosting Unit PowerShell snap-in) that the scheme uses.
The name of the hosting unit (from the Hosting Unit PowerShell snap-in) that the scheme uses.
Indicates whether the VMs that are created will be reset to a clean state on each boot.
The identifier of any current task that is running for the provisioning scheme.
The metadata associated with this provisioning scheme.
The DNS names of the controllers associated with this provisioning scheme for Quick Deploy purposes.
The opaque VM metadata block
True if the scheme will use personal vDisk storage.
The drive letter for the personal vDisk
The size of the personal vDisk in GB
The percentage of the personal vDisk to be used for profile data
Whether to use dedicated tenancy when creating machines in Cloud Hypervisors.
The unique identifier of the current master image used by the provisioning scheme. (See Get-ProvSchemeMasterVMImageHistory.)
True if the scheme will use the wrote back cache feature.
The size of the write back cache disk if specified in GB.
The size of the write back memory cache if specified in MB.
Indicates whether the machines are provisioned using the dedicated full disk clone feature.
In the case of failure, the following errors can result.
The query required to get the database was not defined.
The user does not have administrative rights to perform this operation.
The operation could not be performed because of a configuration logging error
An error occurred while communicating with the service.
The operation could not be completed because the database for the service is not configured.
Import-ProvScheme -ProvisioningSchemeData $provisioningSchemeData
Import the json encoded data that is in \$provisioningSchemeData