When the RunAsynchronously identifier is specified, this GUID is returned and provides the task identifier.
This object provides details of the task that was run and contains the following information:
The identifier for the task that was performed.
Indicates whether the task is still processing or is complete.
The name of the host on which the task is running or was run.
The date and time that the task was initiated.
The type of task. For new provisioning scheme tasks, this is always NewProvisioningScheme.
The list of metadata stored against the task. For new tasks, this is empty until metadata is added.
Indicates the status of the workflow that is used to process the task.
The name of the provisioning scheme that the task was for.
The unique identifier of the provisioning scheme that the task was for.
The path (in the hosting unit provider) of the virtual machine snapshot that was used as the master VM image for the task.
The name of the identity pool (from the ADIdentity PowerShell snap-in) that the new provisioning scheme uses.
The unique identifier name of the identity pool (from the ADIdentity PowerShell snap-in) that the new provisioning scheme uses.
The name of the hosting unit (from the Hosting Unit PowerShell snap-in) that the new provisioning scheme uses.
The unique identifier of the hosting unit (from the Hosting Unit PowerShell snap-in) that the new provisioning scheme uses.
The drive letter on which a personal vDisk is mounted (blank if the personal vDisk feature was not selected).
The size of any personal vDisk (zero if the personal vDisk feature was not selected).
The delegated administration scopes to which the scheme will belong.
The list of NIC to network associations, if specified.
ProvisioningSchemeMetadata <Dictionary<string, string>>
The metadata to apply to the provisioning scheme, if specified.
The state of the task. This can be any of the following:
The task has begun but has not done anything yet.
The workflow is locating resources from other services.
The task failed because the required hosting unit could not be located.
The task failed because the required VM snapshot could not be located.
The task is consolidating the master image.
The task is replicating the consolidated master image.
The task is storing the provisioning scheme data in the database.
The task completed with no errors.
The task failed because a provisioning scheme with the same name already exists.
The task failed because the specified identity pool could not be found.
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.
The task failed because the master VM path does not refer to a Snapshot item.
The task failed because it could not find a provisioning scheme with the specified name.
The task failed because a task for a provisioning scheme with the same name is already running.
The task failed because the VM snapshot specified as the master has an invalid configuration.
The task failed because the VM snapshot specified as the master is currently in an invalid state.
The task failed because the hypervisor did not have enough resources to complete the task.
The disk consolidation task failed. Details are in the task state information string.
The task failed because no associated storage was found in the hosting unit.
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.
The task was stopped by user intervention (using Stop-ProvTask).
Additional information about the current task state.
The progress of the task 0-100%.
The size of the master image in GB
Whether to use dedicated tenancy when creating machines in Cloud Hypervisors.