dsdssd

Author: ScottAzure

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

@@ -130,7 +130,7 @@ at Microsoft.WindowsAzure.GuestAgent.ContainerStateMachine.HostGAPluginUtility.U
 
 These error entries indicate that the VM can't reach the WireServer IP address, 168.63.129.16.
 
-### Solution: Enable DHCP, and make sure that the server isn't blocked by firewalls, proxies, or other sources
+#### Solution: Enable DHCP, and make sure that the server isn't blocked by firewalls, proxies, or other sources
 
 1. Connect to the VM by using Remote Desktop, and then test connectivity to 168.63.129.16. See the [Troubleshoot connectivity](/azure/virtual-network/what-is-ip-address-168-63-129-16?tabs=windows#troubleshoot-azure-ip-connectivity) section of [Azure IP address 168.63.129.16 overview](/azure/virtual-network/what-is-ip-address-168-63-129-16).
 1. If you have only one private IP on your VM's network adapter, we highly recommend that you have DHCP enabled on the guest VM. If you need a static private IP address, you should configure it through the Azure portal or PowerShell, and make sure the DHCP option inside the VM is enabled. To make sure that the IP configuration always matches the configuration on the VM in Azure, [learn how to set up a static IP address](/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps) by using PowerShell.
@@ -156,11 +156,11 @@ at Microsoft.WindowsAzure.GuestAgent.AgentCore.AgentService.<>c__DisplayClass2.<
 
 These error entries indicate that the Azure VM Agent is stuck in the "Stopping" process.
 
-### Solution A: Start WaAppAgent.exe and stop WindowsAzureGuest.exe
+#### Solution A: Start WaAppAgent.exe and stop WindowsAzureGuest.exe
 
 Make sure that *WaAppAgent.exe* is running on the VM. If it isn't running, restart the RdAgent service, and then wait five minutes. After *WaAppAgent.exe* starts running, end the *WindowsAzureGuest.exe* process.
 
-### Solution B: Upgrade Azure VM Agent
+#### Solution B: Upgrade Azure VM Agent
 
 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).
 
@@ -176,7 +176,7 @@ The following error entries are logged in the *WaAppAgent.log* file:
 
 These error entries indicate that [Wireshark](https://www.wireshark.org) installed the packet capture ([Npcap](https://npcap.com)) loopback adapter of the Network Mapper ([Nmap](https://nmap.org)) Project on the VM. Wireshark is an open source tool for profiling network traffic and analyzing packets. Such a tool is often referred to as a network analyzer, network protocol analyzer, or sniffer.
 
-### Solution: Disable the Npcap loopback adapter
+#### Solution: Disable the Npcap loopback adapter
 
 Try to disable the Npcap loopback adapter, and then check whether the problem is resolved.
 
@@ -195,7 +195,7 @@ Microsoft.Cis.Fabric.CertificateServices.RdCertificateFactory.Shutdown()
 
 These errors probably occur because of Remote Procedure Call (RPC) issues. For example, the RPC endpoint might not be listening, or the RPC process might be missing on the opposite end.
 
-### Solution: Start the CNG Key Isolation service
+#### Solution: Start the CNG Key Isolation service
 
 Check whether the [Cryptography Next Generation (CNG) Key Isolation](/windows-server/security/windows-services/security-guidelines-for-disabling-system-services-in-windows-server#cng-key-isolation) (`CNGKEYISO`) Windows service is in the list of RPC endpoints. To do this, run the following [portqry](../../../windows-server/networking/portqry-command-line-port-scanner-v2.md) command:
 
@@ -218,7 +218,7 @@ PInvoke PFXImportCertStore failed and null handle is returned. Error Code: 86
 
 These errors probably occur because of a lack of permissions on the *Crypto* folders for the SYSTEM account. If you collect a [Process Monitor](/sysinternals/downloads/procmon) (ProcMon) trace while you restart the Guest Agent services (RdAgent or WindowsAzureGuestAgent), you should be able to see some "Access Denied" errors.
 
-### Solution: Add full control of Crypto folders to the SYSTEM account
+#### Solution: Add full control of Crypto folders to the SYSTEM account
 
 Make sure that the SYSTEM account has **Full Control** permissions on the following folders:
 
@@ -244,7 +244,7 @@ Most likely, these errors occur because a third-party application was installed
 
 A `BadImageFormatException` error occurs when a 64-bit application is loading a 32-bit DLL.
 
-### Solution: Set the Enable64Bit registry entry for .NET Framework and restart the VM
+#### Solution: Set the Enable64Bit registry entry for .NET Framework and restart the VM
 
 [!INCLUDE [Registry important alert](../../../includes/registry-important-alert.md)]
 
@@ -301,7 +301,7 @@ Exception Info: System.TypeInitializationException
 
 This issue might occur if the *C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\Config\\machine.config* file is missing or corrupted.
 
-### Solution: Copy a working Machine.config file to the VM, and then restart the Guest Agent services
+#### Solution: Copy a working Machine.config file to the VM, and then restart the Guest Agent services
 
 To resolve the issue, follow these steps:
 
@@ -320,7 +320,7 @@ To resolve the issue, follow these steps:
 
 If trying to install Guest Agent fails, make sure that all [prerequisites for Guest Agent](/azure/virtual-machines/extensions/agent-windows#prerequisites) are satisfied.
 
-### Uninstall and reinstall Windows Guest Agent
+#### Solution: Uninstall and reinstall Windows Guest Agent
 
 1. Check in Add/Remove Programs whether Guest Agent is installed. 
 
@@ -391,7 +391,7 @@ Event time="2019-12-12T12:49:05.123Z" category="INFO" source="GuestAgent"><SetRd
 
 The VM agent .msi file uses WMI StdRegProv to access the registry. If WMI isn't working correctly, the .msi file can't set the RdAgent service path from the registry. Therefore, the .msi file installation fails.
 
-### Solution
+#### Solution
 
 1. Open an elevated Command Prompt window.
 2. To test whether WMI StdRegProv is working, run the following WMIC command, and copy the output to a text file:
@@ -457,7 +457,7 @@ System event error 7031 or 7034 is logged, and the C:\WindowsAzure\logs\Transpar
 (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config line 242)
 ```
 
-### Solution
+#### Solution
 
 This issue might occur if Windows Communication Framework (WCF) profiling is enabled. WCF profiling should be enabled only while you debug a WCF issue. It shouldn't be left enabled while you run a production workload.