-
-
-
-
-
-
-
-
-
-
-
New-ProvScheme
-
-
-
-
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!
New-Provscheme
Creates a new provisioning scheme.
Syntax
New-ProvScheme [-ProvisioningSchemeName] <String> -HostingUnitName <String> -IdentityPoolName <String> -MasterImageVM <String> [-VMCpuCount <Int32>] [-VMMemoryMB <Int32>] [-CleanOnBoot] [-UsePersonalVDiskStorage] [-UseWriteBackCache] [-Scope <String[]>] [-NoImagePreparation] [-NetworkMapping <Hashtable>] [-Metadata <Hashtable>] [-ServiceOffering <String>] [-SecurityGroup <String[]>] [-DedicatedTenancy] [-TenancyType <String>] [-VhdTemplateSource <String>] [-VhdResultDestination <String>] [-AppScanResultsFile <String>] [-CustomProperties <String>] [-ResetAdministratorPasswords] [-FunctionalLevel <String>] [-UseFullDiskCloneProvisioning] [-RunAsynchronously] [-PurgeJobOnSuccess] [-InitialBatchSizeHint <Int32>] [-LoggingId <Guid>] [-BearerToken <String>] [-VirtualSiteId <String>] [-AdminAddress <String>] [<CommonParameters>]
New-ProvScheme [-ProvisioningSchemeName] <String> -HostingUnitUid <Guid> -IdentityPoolUid <Guid> -MasterImageVM <String> [-VMCpuCount <Int32>] [-VMMemoryMB <Int32>] [-CleanOnBoot] [-UsePersonalVDiskStorage] [-UseWriteBackCache] [-Scope <String[]>] [-NoImagePreparation] [-NetworkMapping <Hashtable>] [-Metadata <Hashtable>] [-ServiceOffering <String>] [-SecurityGroup <String[]>] [-DedicatedTenancy] [-TenancyType <String>] [-VhdTemplateSource <String>] [-VhdResultDestination <String>] [-AppScanResultsFile <String>] [-CustomProperties <String>] [-ResetAdministratorPasswords] [-FunctionalLevel <String>] [-UseFullDiskCloneProvisioning] [-RunAsynchronously] [-PurgeJobOnSuccess] [-InitialBatchSizeHint <Int32>] [-LoggingId <Guid>] [-BearerToken <String>] [-VirtualSiteId <String>] [-AdminAddress <String>] [<CommonParameters>]
<!--NeedCopy-->
Detailed Description
Lets you create a new provisioning scheme. The creation process makes a copy of the hard disk attached to a virtual machine snapshot or VM template and stores it in every storage location that the hosting unit referenced by the provisioning scheme defines. This is a long-running task and typically takes several minutes to complete (depending on the size of the hard disk that is being copied and the number of snapshots that the hard disk consists of).
A snapshot or VM template must be used rather than a VM, so that the content of the hard disk for the provisioning scheme can be easily determined.
Because the snapshot or VM template are specified using a path into the Citrix Host Service PowerShell Provider, the Citrix Host Service PowerShell snap-in must also be loaded for this cmdlet to be used.
This cmdlet requires information to be provided that is retrieved using other snap-ins that form part of the Citrix Machine Creation Services: Hosting Unit Service Snapin The snap-in that provides information about the hypervisors. AD Identity Service Snapin The snap-in that provides information about the identity pools.
The provisioning scheme is a collection of all of the data that is required to form a template against which virtual machines can be created. It therefore requires the following: Hosting Unit A reference to an item defined in the Host Service that defines the hypervisor, the network, and the storage to be used. Identity Pool A reference to the collection of Active Directory accounts that is used for virtual machines created from the provisioning scheme.
Related Commands
Parameters
Input Type
Return Values
System.Guid
When the RunAsynchronously identifier is specified, this GUID is returned and provides the task identifier.
System.Management.Automation.PSCustomObject
This object provides details of the task that was run and contains the following information:
TaskId <Guid>
The identifier for the task that was performed.
Active <Boolean>
Indicates whether the task is still processing or is complete.
Host <string>
The name of the host on which the task is running or was run.
DateStarted <DateTime>
The date and time that the task was initiated.
Type <Citrix.XDInterServiceTypes.JobType>
The type of task. For new provisioning scheme tasks, this is always NewProvisioningScheme.
Metadata <Citrix.MachineCreation.Sdk.Metadata[]>
The list of metadata stored against the task. For new tasks, this is empty until metadata is added.
WorkflowStatus <System.Workflow.Runtime.WorkflowStatus>
Indicates the status of the workflow that is used to process the task.
ProvisioningSchemeName <string>
The name of the provisioning scheme that the task was for.
ProvisioningSchemeUid <Guid>
The unique identifier of the provisioning scheme that the task was for.
MasterImage <string>
The path (in the hosting unit provider) of the virtual machine snapshot or VM template that was used as the master VM image for the task.
IdentityPoolName <string>
The name of the identity pool (from the ADIdentity PowerShell snap-in) that the new provisioning scheme uses.
IdentityPoolUid <guid>
The unique identifier name of the identity pool (from the ADIdentity PowerShell snap-in) that the new provisioning scheme uses.
HostingUnitName <string>
The name of the hosting unit (from the Hosting Unit PowerShell snap-in) that the new provisioning scheme uses.
HostingUnitUid
The unique identifier of the hosting unit (from the Hosting Unit PowerShell snap-in) that the new provisioning scheme uses.
PersonalVDiskDriveLetter
The drive letter on which a personal vDisk is mounted (blank if the personal vDisk feature was not selected).
PersonalVDiskDriveSize
The size of any personal vDisk (zero if the personal vDisk feature was not selected).
WriteBackCacheDiskSize
The size of any write back cache disk (zero if the write back cache feature was not selected).
WriteBackCacheMemorySize
The size of the write back cache (zero if the write back cache feature was not selected).
Scopes <Citrix.Fma.Sdk.ServiceCoreScopeReference[]>
The delegated administration scopes to which the scheme will belong.
NetworkMap <Citrix.MachineCreation.Sdk.NetworkMap>
The list of NIC to network associations, if specified.
UseFullDiskCloneProvisioning <Boolean>
Indicates whether the machines are provisioned using the dedicated full disk clone feature.
ProvisioningSchemeMetadata <Dictionary<string, string>>
The metadata to apply to the provisioning scheme, if specified.
TaskState <Citrix.MachineCreation.Sdk.NewProvisioningSchemeState>
The state of the task. This can be any of the following:
Processing
The task has begun but has not done anything yet.
LocatingResources,
The workflow is locating resources from other services.
HostingUnitNotFound
The task failed because the required hosting unit could not be located.
VirtualMachineSnapshotNotFound
The task failed because the required VM snapshot or VM template could not be located.
ConsolidatingMasterImage
The task is consolidating the master image.
ReplicatingConsolidatedImageToAllStorage
The task is replicating the consolidated master image.
StoringProvisioningScheme
The task is storing the provisioning scheme data in the database.
Finished
The task completed with no errors.
ProvisioningSchemeAlreadyExists
The task failed because a provisioning scheme with the same name already exists.
IdentityPoolNotFound
The task failed because the specified identity pool could not be found.
MasterVMImageIsNotPartOfProvisioningSchemeHostingUnit,
The task failed because the hosting unit from which the master image originated is not the same hosting unit that the provisioning scheme is using.
MasterVmImageIsNotASnapshot
The task failed because the master VM path does not refer to a snapshot or VM template item.
ProvisioningSchemeNotFound
The task failed because it could not find a provisioning scheme with the specified name.
TaskAlreadyRunningForProvisioningScheme
The task failed because a task for a provisioning scheme with the same name is already running.
InvalidMasterVMConfiguration
The task failed because the VM snapshot or VM template specified as the master has an invalid configuration.
InvalidMasterVMState
The task failed because the VM snapshot or VM template specified as the master is currently in an invalid state.
InsufficientResources
The task failed because the hypervisor did not have enough resources to complete the task.
DiskConsolidationFailed
The disk consolidation task failed. Details are in the task state information string.
StorageNotFound
The task failed because no associated storage was found in the hosting unit.
ConfigurationError
The task failed because the service is unable to contact one of the other services. This is because not all appropriate Configuration Service registrations have been performed.
RequestedFeatureNotEnabled
The task failed because a requested feature is not enabled.
Canceled
The task was stopped by user intervention (using Stop-ProvTask).
TaskStateInformation
Additional information about the current task state.
TaskProgress
The progress of the task 0-100%.
DiskSize
The size of the master image in GB
DedicatedTenancy
Whether to use dedicated tenancy when creating machines in Cloud Hypervisors.
TenancyType
Type of tenancy Shared, Instance or Host wheen creating machines in Cloud Hypervisors.
Notes
Only one long-running task for each provisioning scheme can be processed at a time.
In case of failure, the following errors can result.
Error Codes
———–
JobCreationFailed
The requested task could not be started.
DatabaseError
An error occurred in the service while attempting a database operation.
DatabaseNotConfigured
The operation could not be completed because the database for the service is not configured.
ServiceStatusInvalidDb
An error occurred in the service while attempting a database operation. Communication with the database failed for
for various reasons.
MachineCreationServiceDoesNotSupportPersonalDisk
The service instance being used has not been upgraded to support the personal vDisk feature.
DatabaseMissingCapabilites
The database supporting the service instance being used has not been upgraded to support the personal vDisk feature.
CommunicationError
An error occurred while communicating with the service.
InvalidParameterCombination
Both PurgeJobOnSuccess and RunAsynchronously were specified. When running asynchronously, the cmdlet terminates before the job does, so it cannot clean up the completed job.
PermissionDenied
The user does not have administrative rights to perform this operation.
ConfigurationLoggingError
The operation could not be performed because of a configuration logging error.
ScopeNotFound
One or more of the scopes nominated for the new provisioning scheme do not exist.
WorkflowHostUnavailable
The task could not be started because the database connection is inactive.
ExceptionThrown
An unexpected error occurred. To locate more details, see the Windows event logs on the controller being used, or examine the XenDesktop logs. VhdParametersMustBeSupplied
When parameter VhdTemplateSource or VhdResultDestination is supplied, both parameters are required to be supplied. ServiceDoesNotSupportFullDiskClone
The full disk clone parameter is being used when the service does not support the full disk clone feature. Upgrade the service or remove the parameter. FullDiskCloneDoesNotSupportCleanOnBootVMs
The full disk clone functionality is applicable to dedicated provisioned machines only. FullDiskCloneDoesNotSupportPvdVMs
The full disk clone functionality is only applicable to dedicated provisioned machines that do not use Personal VDisks.
The cmdlet is associated with a task of type NewProvisioningScheme, and while active will move through the following operations (CurrentOperation field)
ValidatingInputs
ConsolidatingMasterImage
PreparingMasterImage
ReplicatingMasterImage
CommittingScheme
Examples
Example 1
C:\PS> New-ProvScheme -ProvisioningSchemeName XenPS -HostingUnitName XenHu -IdentityPoolName idPool1 -CleanOnBoot -MasterImageVM XDHyp:\HostingUnits\XenHU\Base.vm\Base.snapshot
TaskId : 90e93b9d-a225-4701-ad50-fa1546af35ac
Active : False
Host : MyHost
DateStarted : 17/05/2010 08:22:22
Type : NewProvisioningScheme
Metadata : {}
WorkflowStatus : Completed
ProvisioningSchemeName : XenPS
MasterImage : /Base.vm/Base.snapshot
IdentityPoolName : idPool1
IdentityPoolUid : 03743136-e43b-4a87-af74-ab71686b3c16
HostingUnitName : XenHU
HostingUnitUid : 01a4a008-8ce8-4165-ba9c-cdf15a6b0501
PersonalVDiskDriveLetter :
PersonalVDiskDriveSize : 0
ProvisioningSchemeUid : 7585f0de-192e-4847-a6d8-22713c3a2f42
CurrentOperation :
TaskState : Finished
TaskStateInformation :
TaskProgress : 100
DiskSize : 24
<!--NeedCopy-->
Description
Creates a new provisioning scheme with the name “XenPS” using the hosting unit “XenHu” and the identity pool “idPool1” from the master VM snapshot called “Base.snapshot”.
Example 2
C:\PS> New-ProvScheme -ProvisioningSchemeName XenPS -HostingUnitName XenHu -IdentityPoolName idPool1 -CleanOnBoot -MasterImageVM XDHyp:\HostingUnits\XenHU\Base.vm\Base.snapshot -RunAsynchronously
Guid
----
6dd85fec-96cf-46b1-9cd4-d8ba7d06e85b
<!--NeedCopy-->
Description
Creates a new provisioning scheme with the name “XenPS” using the hosting unit “XenHu” and the identity pool “idPool1” from the master VM snapshot called “Base.snapshot” asynchronously. To get the task details, use Get-ProvTask -TaskID <task id><br>i.e.<br>C:\PS>Get-ProvTask -TaskID 6dd85fec-96cf-46b1-9cd4-d8ba7d06e85b<br>TaskId : 6dd85fec-96cf-46b1-9cd4-d8ba7d06e85b<br>Active : False<br>Host : MyHost<br>DateStarted : 17/05/2010 08:22:22<br>Type : NewProvisioningScheme<br>Metadata : {}<br>WorkflowStatus : Completed<br>ProvisioningSchemeName : XenPS<br>MasterImage : XDHyp:\HostingUnits\XenHU\Base.vm\Base.snapshot<br>IdentityPoolName : idPool1<br>IdentityPoolUid : 03743136-e43b-4a87-af74-ab71686b3c16<br>HostingUnitName : XenHU<br>HostingUnitUid : 01a4a008-8ce8-4165-ba9c-cdf15a6b0501<br>PersonalVDiskDriveLetter :<br>PersonalVDiskDriveSize : 0<br>ProvisioningSchemeUid : 7585f0de-192e-4847-a6d8-22713c3a2f42<br>TaskState : Finished<br>TaskStateInformation :<br>TaskProgress : 100<br>DiskSize : 24
Example 3
C:\PS>$provScheme = New-ProvScheme -ProvisioningSchemeName XenPS2 -HostingUnitName XenHu -IdentityPoolName idPool1 -CleanOnBoot -MasterImageVM XDHyp:\HostingUnits\XenHU\Base.vm\Base.snapshot -UsePersonalVDiskStorage -PersonalVDiskDriveSize 17 -PersonalVDiskDriveLetter x
<!--NeedCopy-->
Description
Creates a new provisioning scheme with the name “XenPS2” using the hosting unit “XenHu” and the identity pool “idPool1” from the master VM snapshot called “Base.snapshot”; apply a 17GB personal vDisk. The personal vDisk is mapped as drive X. The operation runs synchronously, and the return value contains the task details<br>For example:<br>C:\PS>$provScheme<br>TaskId : d726222a-04b5-4098-b9ac-db85ed9d351b<br>Active : False<br>Host : MyHost<br>DateStarted : 12/09/2011 09:30:04<br>Type : NewProvisioningScheme<br>Metadata : {}<br>ProvisioningSchemeName : XenPS2<br>IdentityPoolName : idPool1<br>IdentityPoolUid : 03743136-e43b-4a87-af74-ab71686b3c16<br>HostingUnitName : XenHU<br>HostingUnitUid : 01a4a008-8ce8-4165-ba9c-cdf15a6b0501<br>PersonalVDiskDriveLetter : X<br>PersonalVDiskDriveSize : 17<br>WorkflowStatus : Completed<br>MasterImage : XDHyp:\HostingUnits\XenHU\Base.vm\Base.snapshot<br>ProvisioningSchemeUid : 7585f0de-192e-4847-a6d8-22713c3a2f42<br>TaskState : Finished<br>TaskStateInformation :<br>TaskProgress : 100<br>DiskSize : 24
Share
Share
In this article
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.