Skip to content

Reset-Provvmdisk

Resets the OS disk of persistent VMs.

Syntax

Reset-ProvVMDisk [-ProvisioningSchemeName] <String> -VMName <String[]> -OS [-RunAsynchronously] [-PurgeJobOnSuccess] [-Force] [-LoggingId <Guid>] [-BearerToken <String>] [-TraceParent <String>] [-TraceState <String>] [-VirtualSiteId <String>] [-AdminAddress <String>] [-WhatIf] [-Confirm] [<CommonParameters>]<br><br>Reset-ProvVMDisk [-ProvisioningSchemeUid] <Guid> -VMName <String[]> -OS [-RunAsynchronously] [-PurgeJobOnSuccess] [-Force] [-LoggingId <Guid>] [-BearerToken <String>] [-TraceParent <String>] [-TraceState <String>] [-VirtualSiteId <String>] [-AdminAddress <String>] [-WhatIf] [-Confirm] [<CommonParameters>]

Detailed Description

Allows you to reset the disks of persistent VMs from Machine Creation Services and hypervisor.

Parameters

Name Description Required? Pipeline Input Default Value
ProvisioningSchemeName The name of the provisioning scheme from which VM disks will be reset. true true (ByPropertyName)
ProvisioningSchemeUid The unique identifier of the provisioning scheme from which VM disks will be reset. true false
VMName List of VM names that will be have the OS disk reset. true true (ByValue, ByPropertyName)
OS Indicates that the OS disk should be reset. true false
RunAsynchronously Indicates whether the command returns before it completes. If this is specified, the command returns an identifier for the task that was created. This task can be monitored using the get-ProvTask command. false false false
PurgeJobOnSuccess Indicates that the task history is removed from the database when the task completes. This cannot be specified for tasks that run asynchronously. false false
Force Suppresses prompts for confirmation before proceeding to reset the OS disk of the specified VMs. 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
TraceParent Specifies the trace parent assigned for internal diagnostic tracing use false false
TraceState Specifies the trace state assigned for internal diagnostic tracing user false false
VirtualSiteId Specifies the virtual site the PowerShell snap-in will connect to. false false
AdminAddress The address of a Citrix Virtual Apps and Desktops controller that the PowerShell snap-in connects to. You can provide this as a host name or an IP address. false false LocalHost. When a value is provided by any cmdlet, this value becomes the default.
WhatIf Shows what would happen if the cmdlet runs. The cmdlet is not run. false false
Confirm Prompts for confirmation before running the cmdlet. false false

Input Type

Citrix.Machinecreation.Sdk.Provisionedvirtualmachine

You can pipe an object containing parameters called 'VMName' and 'ProvisioningSchemeName' to Reset-ProvVMDisk.

Return Values

System.Guid

When the RunAsynchronously identifier is specified, this GUID is returned and provides the task identifier.

Notes

Only one long-running task for each provisioning scheme can be processed at a time.
In the 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. WorkflowHostUnavailable The task could not be started because the database connection is inactive. 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 ExceptionThrown An unexpected error occurred. For more details, see the Windows event logs on the controller being used or Citrix Virtual Apps and Desktops logs.
The cmdlet is associated with a task of type ResetVirtualMachine, and while active will move through the following operations (CurrentOperation field)
ValidatingInputs ResettingVirtualMachines

Examples

Example 1

c:\PS>,(Get-ProvVM -ProvisioningSchemeName "myProvScheme") | Reset-ProvVMDisk -ProvisioningSchemeName "myProvScheme" -OS<br><br>TaskId                 : 2706e50b-aff9-44c7-a3e3-8c8c7f1f4ac5<br><br>Active                 : False<br><br>Host                   : MY-DDC<br><br>DateStarted            : 5/24/2022 12:02:29 PM<br><br>Metadata               : {}<br><br>CurrentOperation       :<br><br>TaskProgress           : 100<br><br>LastUpdateTime         : 5/24/2022 12:02:41 PM<br><br>ActiveElapsedTime      : 10<br><br>DateFinished           : 5/24/2022 12:02:41 PM<br><br>TerminatingError       :<br><br>Type                   : ResetVM<br><br>Status                 : Finished<br><br>ResetVirtualMachines   : {XD\machine01$, XD\machine02$}<br><br>FailedVirtualMachines  : {}<br><br>ProvisioningSchemeName : myProvScheme<br><br>ProvisioningSchemeUid  : 3d79b132-22c5-40d3-9a99-7cb497924f9e<br><br>TaskState              : Finished<br><br>TaskStateInformation   :<br><br>WorkflowStatus         : Completed<br><br>TaskExpectedCompletion :

Description

Reset all VMs in provisioning scheme myProvScheme

Example 2

c:\PS>Reset-ProvVMDisk -ProvisioningSchemeName "myProvScheme" -VMName ("machine01","machine02") -OS<br><br>TaskId                 : 2706e50b-aff9-44c7-a3e3-8c8c7f1f4ac5<br><br>Active                 : False<br><br>Host                   : MY-DDC<br><br>DateStarted            : 5/24/2022 12:02:29 PM<br><br>Metadata               : {}<br><br>CurrentOperation       :<br><br>TaskProgress           : 100<br><br>LastUpdateTime         : 5/24/2022 12:02:41 PM<br><br>ActiveElapsedTime      : 10<br><br>DateFinished           : 5/24/2022 12:02:41 PM<br><br>TerminatingError       :<br><br>Type                   : ResetVM<br><br>Status                 : Finished<br><br>ResetVirtualMachines   : {XD\machine01$, XD\machine02$}<br><br>FailedVirtualMachines  : {}<br><br>ProvisioningSchemeName : myProvScheme<br><br>ProvisioningSchemeUid  : 3d79b132-22c5-40d3-9a99-7cb497924f9e<br><br>TaskState              : Finished<br><br>TaskStateInformation   :<br><br>WorkflowStatus         : Completed<br><br>TaskExpectedCompletion :

Description

Reset machine01 and machine02 in provisioning scheme myProvScheme

Example 3

c:\PS>Reset-ProvVMDisk -ProvisioningSchemeName "myProvScheme" -VMName "machine01" -OS<br><br>TaskId                 : 2706e50b-aff9-44c7-a3e3-8c8c7f1f4ac5<br><br>Active                 : False<br><br>Host                   : MY-DDC<br><br>DateStarted            : 5/24/2022 12:02:29 PM<br><br>Metadata               : {}<br><br>CurrentOperation       :<br><br>TaskProgress           : 100<br><br>LastUpdateTime         : 5/24/2022 12:02:41 PM<br><br>ActiveElapsedTime      : 10<br><br>DateFinished           : 5/24/2022 12:02:41 PM<br><br>TerminatingError       :<br><br>Type                   : ResetVM<br><br>Status                 : Finished<br><br>ResetVirtualMachines   : {XD\machine01$}<br><br>FailedVirtualMachines  : {}<br><br>ProvisioningSchemeName : myProvScheme<br><br>ProvisioningSchemeUid  : 3d79b132-22c5-40d3-9a99-7cb497924f9e<br><br>TaskState              : Finished<br><br>TaskStateInformation   :<br><br>WorkflowStatus         : Completed<br><br>TaskExpectedCompletion :

Description

Reset machine01 in provisioning scheme myProvScheme

Was this article helpful?