Skip to content

Commit 41b7c8a

Browse files
ScottAzureScottAzure
committed
sdsds
ssddsds
1 parent 4cecf1c commit 41b7c8a

2 files changed

Lines changed: 12 additions & 66 deletions

File tree

‎support/azure/virtual-machines/windows/windows-azure-guest-agent-tools-vmassist.md‎

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ You can run the tool in any of the following manners.
4242
### 1. Download from GitHub and run within the VM
4343

4444
Download the scripts from GitHub, and then run them manually. To access the scripts, follow the resource links in the previous sections.
45-
Please see the GitHub page to see the latest instruction for how a customer can [install VM assist](https://github.com//azure/azure-support-scripts/blob/master/vmassist/windows/README.md).
45+
Please see the GitHub page to see the latest instruction for how a you can [install VM assist](https://github.com//azure/azure-support-scripts/blob/master/vmassist/windows/README.md).
4646

4747
RDP into the VM and from an elevated PowerShell window run the following to download and run the script:
4848
```powershell
@@ -99,36 +99,32 @@ If you open a support request, please include both of the above files to aid you
9999

100100
## Current list of findings/checks
101101

102-
Here are the current list of checks/findings along with any potential internal articles that can help in case the customer needs further assistance.
102+
Here are the current list of checks/findings along with any potential documentation to help understand the issue being detected.
103103

104104
| Checks | Details |
105105
|--------|---------|
106106
| Check for Folder| Validates that the folder C:\WindowsAzure folder exists and is also used to help determine that the Guest Agent was installed.<br><br>If this doesn't exist then its likely that the guest agent needs to be installed. |
107107
| Check for binaries | Validates that the guest agent .exes (WindowsAzureGuestAgent.exe and WaAppAgent.exe) exist and is also used to help determine that the Guest Agent was installed.<br><br>If this doesn't exist then its likely that the guest agent needs to be installed. |
108108
| Status of agent services | Validates that the guest agent services (WindowsAzureGuestAgent and RdAgent) exist and is also used to help determine that the Guest Agent was installed.<br><br>If this doesn't exist then its likely that the guest agent needs to be installed. If they do exist then ensure they're set to `Running` and ideally their StartType will be set to `Automatic` |
109109
| Status of `winmgmt` service | Validates that the winmgmt service is running. |
110-
| Status of `KeyIso` service | Validates that the `KeyIso (CNG Key Isolation)` service is running.<br><br> See this [Needs to be Public](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/1551510/RPC-Issues_AGEX) for more details. |
110+
| Status of `KeyIso` service | Validates that the `KeyIso (CNG Key Isolation)` service is running.<br><br> See this [Needs to be Public](windows-azure-guest-agent#remote-procedure-call-rpc-issues---rdcrypt-initialization-failed) for more details. |
111111
| Check if agent services/processes have crashed | This checks if the Guest Agent services/processes have crashed in the last day. If its just a one off crash, then it may not be important unless it happens right when the issue is reported. On the other hand, if its constantly crashing then it needs to be investigated.<br><br>First look in the WaAppAgent.log and System/Application event logs. |
112-
| Checks if `stdregprov` is working | The VM agent MSI uses WMI StdRegProv to access the registry. If WMI is not working properly the MSI cannot set the RdAgent service path from the registry and the MSI install fails. <br><br> See this [Needs to be Public](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/1595962/WinGA-failing-to-install-due-broken-WMI_AGEX) for more details. |
112+
| Checks if `stdregprov` is working | The VM agent MSI uses WMI StdRegProv to access the registry. If WMI is not working properly the MSI cannot set the RdAgent service path from the registry and the MSI install fails. <br><br> See this [Guest Agent installation fails because of faulty WMI](windows-azure-guest-agent#guest-agent-installation-fails-because-of-faulty-wmi) for more details. |
113113
| Agent is installed | Returns True if the guest Agent is installed. If its not installed then the guest agent needs to be installed. |
114114
| Installed by PA or MSI | This checks if the Guest Agent was installed by the provisioning agent or manually via .MSI. Neither of these options are `wrong`, but its included for informational purposes. |
115115
| Supported version | Checks that they are using an up to date, supported version of the Guest Agent. |
116-
| Proxy | Checks for netsh proxies. This doesn't check for the existance of *all* type of proxy on the system. For example, it doesn't check if there is a `3rd party proxy application` installed. <br><br>If there are wireserver connectivity issues you can start troubleshooting with the [Troubleshooting 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16#troubleshoot-connectivity). If you need to specifically look into proxy then see [Needs to be Public](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/1566544/Proxy-Issues_AGEX). |
117-
| CRP cert exists and is valid | Checks that the CRP "Windows Azure CRP Certificate Generator" certificate exists. This certificate is there to secure the communication with the host, and transfer protected settings used by extensions.<br><br> See this [public article](troubleshoot-extension-certificates-issues-windows-vm.md) for more details. |
118-
| WCF debugging | This may occur if Windows Communication Framework (WCF) profiling is enabled. WCF profiling should only be enabled while debugging a WCF issue. It should not be left enabled while running a production workload.<br><br> See this [Needs to be Public](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/1630419/Crashing-Due-to-WCF-Profile-Enabled_AGEX) for more details. |
119-
| Wireserver (168.63.129.16) connectivity on 80, 32526, and REST API | If there are wireserver connectivity issues you can start troubleshooting with the [Why is this here and the proxy check above](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/1027820/WireServer-Troubleshooting_AGEX). |
120-
| IMDS connectivity | IMDS connectivity is not required for the Guest Agent to work, but the Guest Agent does try to connect so you may see errors in the logs. Additionally VM assist itself gets information on the VM from IMDS to populate some sections of the .HTML file.<br><br>So not having connectivity to IMDS will not break the Guest Agent, start with the [Needs to be Public](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/495850/Basic-Workflow_IMDS). |
121-
| Third-party modules in WaAppAgent and WindowsAzureGuestAgent | Other applications occasionally inject their .dlls into the Guest Agent process. Most of the time it will not cause the Guest Agent to fail. However, it is possible that these .dlls can cause unexpected failures in the Guest Agent that are difficult to debug. Although it is relatively rare that these cause an issue, if any of these .dlls are from unexpected applications and you've exhausted [Needs to be Public - rare--](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/495025/Guest-Agent-Workflow_AGEX) then consider having the customer remove/reconfigure the application so that it no longer injects its .dlls into the Guest Agnet process(es). As this scenario is pretty rare, you may want to check with a SME/TA first. |
122-
| Checks permissions on machineKeys folder | Checks to see that the default permissions are in place on `C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys`. If improper permissions are applied that block access then the Guest Agent itself may be 'Ready', but extensions that use protected settings won't work.<br><br> See this [Needs to be Public](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/1986524/Crypto-or-Certificate-Errors-with-Windows-Guest-Agent_AGEX) for more details. |
116+
| Proxy | Checks for netsh proxies. This doesn't check for the existance of *all* type of proxy on the system. For example, it doesn't check if there is a `3rd party proxy application` installed. <br><br>If there are wireserver connectivity issues you can start troubleshooting with the [Troubleshooting 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16#troubleshoot-connectivity). |
117+
| CRP cert exists and is valid | Checks that the CRP "Windows Azure CRP Certificate Generator" certificate exists. This certificate is there to secure the communication with the host, and transfer protected settings used by extensions.<br><br> See this [Troubleshoot extension certificate issues on a Windows VM in Azure](troubleshoot-extension-certificates-issues-windows-vm.md) for more details. |
118+
| WCF debugging | This may occur if Windows Communication Framework (WCF) profiling is enabled. WCF profiling should only be enabled while debugging a WCF issue. It should not be left enabled while running a production workload.<br><br> See this [Windows Azure Guest Agent service or the RdAgent service stops responding on startup (WCF)](windows-azure-guest-agent#windows-azure-guest-agent-service-or-the-rdagent-service-stops-responding-on-startup) for more details. |
119+
| Wireserver (168.63.129.16) connectivity on 80, 32526, and REST API | If there are wireserver connectivity issues you can start troubleshooting with the [Troubleshooting 168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16#troubleshoot-connectivity). |
120+
| IMDS connectivity | IMDS connectivity is not required for the Guest Agent to work, but the Guest Agent does try to connect so you may see errors in the logs. Additionally VM assist itself gets information on the VM from IMDS to populate some sections of the .HTML file.<br><br>So not having connectivity to IMDS will not break the Guest Agent, start with the [Troubleshooting tool for Azure VM Instance Metadata Service issues](windows-vm-imds-tool.md). |
121+
| Third-party modules in WaAppAgent and WindowsAzureGuestAgent | Other applications occasionally inject their .dlls into the Guest Agent process. Most of the time it will not cause the Guest Agent to fail. However, it is possible that these .dlls can cause unexpected failures in the Guest Agent that are difficult to debug. Although it is relatively rare that these cause an issue, if any of these .dlls are from unexpected applications injected, consider remove/reconfigure the application so that it no longer injects its .dlls into the Guest Agnet process(es). |
122+
| Checks permissions on machineKeys folder | Checks to see that the default permissions are in place on `C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys`. If improper permissions are applied that block access then the Guest Agent itself may be 'Ready', but extensions that use protected settings won't work.<br><br> See this [PInvoke PFXImportCertStore failed and null handle is returned. Error Code: 86](windows-azure-guest-agent#pinvoke-pfximportcertstore-failed-and-null-handle-is-returned-error-code-86) for more details. |
123123
| Checks permissions on `C:\WindowsAzure` and `C:\Packages` | Validates that the System account has access to these directories. These directories are what the Guest Agent and extensions use for their binaries, config files, and log files, so its important the System account has access. |
124-
| Sufficient disk space |This checks for available disk space. If the disk space is completely filled then the Guest Agent may not be able to write its status file, update, install extensions, etc. The customer would either need to delete files or expand their disk. |
124+
| Sufficient disk space |This checks for available disk space. If the disk space is completely filled then the Guest Agent may not be able to write its status file, update, install extensions, etc. Please either need to delete files or expand their disk. |
125125
| DHCP IP | If there is one private IP on the VM's NIC, then we highly recommend having DHCP enabled in the guest VM. If they need a static private IP address, they should [configure it through the Azure portal or PowerShell](/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps), and make sure the DHCP option inside the VM is enabled. This will ensure that the IP configuration will always match what is configured on the VM in Azure.<br><br>If they have multiple private IPs assigned to their VM's NIC, then ensure that they followed the steps to [statically assign the IPs correctly](/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal#os-config). After this, if the Guest Agent isn't able to communicate with 168.63.129.16, then check that the primary IP in Windows [matches the primary IP in their VM's NIC in Azure](no-internet-access-multi-ip.md). |
126126

127127

128-
### **Additional resources**
129-
130-
- [xxxxx](/azure/virtual-machines/windows/no-internet-access-multi-ip)
131-
132128
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
133129

134130
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

‎support/azure/virtual-machines/windows/windows-azure-guest-agent.md‎

Lines changed: 0 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -109,9 +109,6 @@ Compare any errors that you find to the following common scenarios that can caus
109109

110110
### Can't connect to WireServer IP (168.63.129.16)
111111

112-
<details>
113-
<summary>Click here for troubleshooting details</summary>
114-
115112
The following error entries are logged in the *WaAppAgent.log* file:
116113

117114
```output
@@ -141,13 +138,8 @@ These error entries indicate that the VM can't reach the WireServer IP address,
141138
1. Check for any issues that a firewall, a proxy, or another source might cause that could block access to IP address `168.63.129.16`.
142139
1. Check whether Windows Firewall or a third-party firewall is blocking access to ports `80` and `32526`. For more information about why this address shouldn't be blocked, see [What is IP address 168.63.129.16?](/azure/virtual-network/what-is-ip-address-168-63-129-16)
143140

144-
</details>
145-
146141
### Guest Agent is stuck in the "Stopping" process
147142

148-
<details>
149-
<summary>Click here for troubleshooting details</summary>
150-
151143
The following error entries are logged in the *WaAppAgent.log* file:
152144

153145
```output
@@ -172,13 +164,8 @@ Make sure that *WaAppAgent.exe* is running on the VM. If it isn't running, resta
172164

173165
If Solution A doesn't resolve the issue, remove the currently installed version, and then [install the latest version of the agent manually](/azure/virtual-machines/extensions/agent-windows#manual-installation).
174166

175-
</details>
176-
177167
### The Npcap loopback adapter is installed
178168

179-
<details>
180-
<summary>Click here for troubleshooting details</summary>
181-
182169
The following error entries are logged in the *WaAppAgent.log* file:
183170

184171
```output
@@ -193,13 +180,8 @@ These error entries indicate that [Wireshark](https://www.wireshark.org) install
193180

194181
Try to disable the Npcap loopback adapter, and then check whether the problem is resolved.
195182

196-
</details>
197-
198183
### Remote Procedure Call (RPC) issues - RdCrypt Initialization failed
199184

200-
<details>
201-
<summary>Click here for troubleshooting details</summary>
202-
203185
The following error entries are logged in the *WaAppAgent.log* file:
204186

205187
```output
@@ -223,13 +205,8 @@ portqry -n <VMName> -e 135
223205

224206
If you don't see the `CNGKEYISO` process, start it from the Windows Services console (CNG Key Isolation = `KeyIso`), and then restart *WaAppAgent.exe* or *WindowsAzureGuestAgent.exe*.
225207

226-
</details>
227-
228208
### PInvoke PFXImportCertStore failed and null handle is returned. Error Code: 86
229209

230-
<details>
231-
<summary>Click here for troubleshooting details</summary>
232-
233210
Windows Guest Agent is running, but extensions aren't working. The following error entries are logged in the *WaAppAgent.log* file:
234211

235212
```output
@@ -251,13 +228,8 @@ Make sure that the SYSTEM account has **Full Control** permissions on the follow
251228

252229
- *C:\\ProgramData\\Microsoft\\Crypto\\SystemKeys*
253230

254-
</details>
255-
256231
### System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
257232

258-
<details>
259-
<summary>Click here for troubleshooting details</summary>
260-
261233
The following error entries are logged in the *WaAppAgent.log* file to indicate that Guest Agent isn't responding:
262234

263235
```output
@@ -282,13 +254,8 @@ If the **Enable64Bit** registry entry is set to **0**, then 64-bit .NET applicat
282254

283255
The solution is to set the **Enable64Bit** key to **1**, and then restart the VM.
284256

285-
</details>
286-
287257
### Windows Guest Agent doesn't start because of a ConfigurationErrorsException or TypeInitializationException error
288258

289-
<details>
290-
<summary>Click here for troubleshooting details</summary>
291-
292259
Windows Guest Agent stops responding upon startup, and the following application log entries are logged:
293260

294261
```output
@@ -349,13 +316,8 @@ To resolve the issue, follow these steps:
349316
net start WindowsAzureGuestAgent
350317
```
351318

352-
</details>
353-
354319
### Installing Guest Agent fails
355320

356-
<details>
357-
<summary>Click here for troubleshooting details</summary>
358-
359321
If trying to install Guest Agent fails, make sure that all [prerequisites for Guest Agent](/azure/virtual-machines/extensions/agent-windows#prerequisites) are satisfied.
360322

361323
### Uninstall and reinstall Windows Guest Agent
@@ -392,13 +354,8 @@ If trying to install Guest Agent fails, make sure that all [prerequisites for Gu
392354
- C:\Windows\Panther\msiexec.log
393355
- C:\Windows\Panther\VmAgentInstaller.xml
394356
395-
</details>
396-
397357
### Guest Agent installation fails because of faulty WMI
398358
399-
<details>
400-
<summary>Click here for troubleshooting details</summary>
401-
402359
1. Download the latest [.msi file](https://github.com/Azure/WindowsVMAgent/releases) from the GitHub Releases for Windows Guest Agent.
403360
1. Install Guest Agent by using the msiexec command line + arguments
404361
@@ -490,13 +447,8 @@ wmic service rdagent list brief
490447
491448
10. At this point, if the **WMIC** command fails or still doesn't show that **RdAgent** is running, send the **C:\Windows\Panther\VMAgentInstall.xml** file to Microsoft Support for review.
492449
493-
</details>
494-
495450
### Windows Azure Guest Agent service or the RdAgent service stops responding on startup
496451
497-
<details>
498-
<summary>Click here for troubleshooting details</summary>
499-
500452
System event error 7031 or 7034 is logged, and the C:\WindowsAzure\logs\TransparentInstaller.log shows the following entry:
501453
502454
```
@@ -544,8 +496,6 @@ net start WindowsAzureGuestAgent
544496

545497
- In some cases, the VM might have to be restarted for the WCF disablement to take effect.
546498

547-
</details>
548-
549499
## Next steps
550500

551501
Other known issues that are associated with the Azure VM Agent are listed in its [GitHub repository](https://github.com/Azure/WindowsVMAgent/wiki/Known-Issues).

0 commit comments

Comments
 (0)