diff --git a/support/azure/virtual-machines/windows/windows-azure-guest-agent-tools-vmassist.md b/support/azure/virtual-machines/windows/windows-azure-guest-agent-tools-vmassist.md index b26764f40b0..176d7cc8c27 100644 --- a/support/azure/virtual-machines/windows/windows-azure-guest-agent-tools-vmassist.md +++ b/support/azure/virtual-machines/windows/windows-azure-guest-agent-tools-vmassist.md @@ -44,25 +44,13 @@ Set-ExecutionPolicy Bypass -Force (Invoke-WebRequest -Uri https://aka.ms/vmassist -OutFile vmassist.ps1) | .\vmassist.ps1 ``` -Alternatively, you can specify the full URL instead of the aka.ms short link: - -```powershell -(Invoke-WebRequest -Uri https://raw.githubusercontent.com//azure/azure-support-scripts/master/vmassist/windows/vmassist.ps1 -OutFile vmassist.ps1) | .\vmassist.ps1 -``` - ### Option 2: Manually download and run Download: ```powershell [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 -Invoke-WebRequest -Uri https://raw.githubusercontent.com//azure/azure-support-scripts/master/vmassist/windows/vmassist.ps1 -OutFile vmassist.ps1 -``` - -Alternatively, you can specify the full URL instead of the aka.ms short link: - -```powershell -Invoke-WebRequest -Uri https://raw.githubusercontent.com//azure/azure-support-scripts/master/vmassist/windows/vmassist.ps1 -OutFile vmassist.ps1 +Invoke-WebRequest -Uri https://aka.ms/vmassist -OutFile vmassist.ps1 ``` Run the script: @@ -72,16 +60,6 @@ Set-ExecutionPolicy Bypass -Force .\vmassist.ps1 ``` -### Option 3: Download from browser - - 1. Download the ```vmassist.ps1``` file [from a web browser](https://github.com//azure/azure-support-scripts/blob/master/vmassist/windows/vmassist.ps1). - 1. In an elevated PowerShell window, make sure that you're in the same directory that you downloaded the script to, and then run the following code to run the script: - - ```powershell -Set-ExecutionPolicy Bypass -Force -.\vmassist.ps1 - ``` - ## Analyzing output The script runs a series of checks to analyze the health of the VM Guest Agent and look for various known configurations that could cause issues. Each check either passes or fails in the PowerShell window.