Skip to content

Commit a6f5f45

Browse files
authored
Merge pull request #142904 from axelgMS/patch-18
Update troubleshoot.md
2 parents 7525876 + d8c25d9 commit a6f5f45

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

articles/virtual-machines/extensions/troubleshoot.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -73,26 +73,30 @@ Once the extension has been removed, the template can be re-executed to run the
7373

7474
### Trigger a new GoalState to the VM
7575
You might notice that an extension hasn't been executed, or is failing to execute because of a missing "Windows Azure CRP Certificate Generator" (that certificate is used to secure the transport of the extension's protected settings).
76-
That certificate will be automatically re-generated by restarting the Windows Guest Agent from inside the Virtual Machine:
76+
That certificate will be automatically regenerated by restarting the Windows Guest Agent from inside the Virtual Machine:
7777
- Open the Task Manager
7878
- Go to the Details tab
7979
- Locate the WindowsAzureGuestAgent.exe process
8080
- Right-click, and select "End Task". The process will be automatically restarted
8181

8282

83-
You can also trigger a new GoalState to the VM, by executing an "empty update":
83+
You can also trigger a new GoalState to the VM, by executing a "VM Reapply". VM [Reapply](https://docs.microsoft.com/rest/api/compute/virtualmachines/reapply) is an API introduced in 2020 to reapply a VM's state. We recommend doing this at a time when you can tolerate a short VM downtime. While Reapply itself does not cause a VM reboot, and the vast majority of times calling Reapply will not reboot the VM, there is a very small risk that some other pending update to the VM model gets applied when Reapply triggers a new goal state, and that other change could require a restart.
8484

85-
Azure PowerShell:
85+
Azure portal:
86+
87+
In the portal, select the VM and in the left pane under the **Support + troubleshooting**, select **Redeploy + reapply**, then select **Reapply**.
88+
89+
90+
Azure PowerShell *(replace the RG Name and VM Name with your values)*:
8691

8792
```azurepowershell
88-
$vm = Get-AzureRMVM -ResourceGroupName <RGName> -Name <VMName>
89-
Update-AzureRmVM -ResourceGroupName <RGName> -VM $vm
93+
Set-AzVM -ResourceGroupName <RG Name> -Name <VM Name> -Reapply
9094
```
9195

92-
Azure CLI:
96+
Azure CLI *(replace the RG Name and VM Name with your values)*:
9397

9498
```azurecli
95-
az vm update -g <rgname> -n <vmname>
99+
az vm reapply -g <RG Name> -n <VM Name>
96100
```
97101

98-
If an "empty update" didn't work, you can add a new empty Data Disk to the VM from the Azure Management Portal, and then remove it later once the certificate has been added back.
102+
If a "VM Reapply" didn't work, you can add a new empty Data Disk to the VM from the Azure Management Portal, and then remove it later once the certificate has been added back.

0 commit comments

Comments
 (0)