sasasa

Author: ScottAzure

support/azure/virtual-machines/windows/windows-vm-ghostednic-tool.md

@@ -1,15 +1,17 @@
 ---
-title: Azure VM Ghosted Nic Cleanup Script
-description: Azure VM Ghosted Nic Cleanup Script
+title: Azure VM Ghosted Nic Validation and Cleanup Tools
+description: Azure VM Ghosted Nic Validation and Cleanup Tools
 ms.service: azure-virtual-machines
 ms.date: 06/04/2024
 ms.custom: sap:Cannot create a VM, H1Hack27Feb2017
 ms.reviewer: macla, scotro, glimoli, jarrettr, azurevmcptcic
 ---
-# Troubleshooting tools for Azure VM Ghosted Nic issues
+# Azure VM Ghosted Nic Validation and Cleanup Tools
 
 **Applies to:** :heavy_check_mark: Windows VMs
 
+## Overview
+
 When an Azure Virtual Machine running Windows Server or Windows Client with **Accelerated Networking** enabled is **deallocated**, the following may occur:
 
 - Connectivity issues may occur for the active NIC
@@ -21,19 +23,13 @@ When an Azure Virtual Machine running Windows Server or Windows Client with **Ac
 
 `Ghosted nics` can happen to Azure virtual machines (VMs) causing connectivity, performance, Windows Update, and other issues. Microsoft provides a script-based tool to help diagnose and clean-up the ghost-nic issues.
 
-## Tool overview
-
-### Azure VM Ghosted Nic Validation and Cleanup Scripts
-
-**Purpose**  
+## Purpose
 There two scripts that can be used to detect if there are 'ghosted nics' inside of the VM. A VM that has one ore more could experience issues.This script detects ghosted (disconnected) network interface cards (NICs) and remove them from the registry.
 
 - [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
 - [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
-
-
-**Key features**  
+## Key features  
 
 * Detects for Ghosted Nics
 * Removes Ghosted Nics
@@ -79,7 +75,7 @@ For more information, see [Run scripts in your Windows VM by using action Run Co
 1. Run **[Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)** to verify activation status and detect common issues.
 2. If ghost-nics are detected, run [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal) to remove them.
 
-### **Additional resources**
+## Additional resources
 
 - [Troubleshooting: Multiple Mellanox Ethernet Adapters After VM Deallocation (Ghost NICs)](./windows-vm-ghostednic-troubleshooting.md)
 - [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)

support/azure/virtual-machines/windows/windows-vm-imds-tool.md

@@ -1,28 +1,24 @@
 ---
-title: Azure VM Instance Metadata Service Verification Script
-description: Azure VM Instance Metadata Service Verification Script
+title: Azure VM Instance Metadata Service Verification Tool
+description: Azure VM Instance Metadata Service Verification Tool
 ms.service: azure-virtual-machines
 ms.date: 06/04/2024
 ms.custom: sap:Cannot create a VM, H1Hack27Feb2017
 ms.reviewer: macla, scotro, glimoli, jarrettr, azurevmcptcic
 ---
-# Troubleshooting tool for Azure VM Instance Metadata Service issues
+# Azure VM Instance Metadata Service Verification Tool
 
 **Applies to:** :heavy_check_mark: Windows VMs
 
-
 The Azure Instance Metadata Service (IMDS) is a REST API that's available at a well-known, non-routable IP address (`169.254.169.254`). You can only access it from within the VM. Communication between the VM and IMDS never leaves the host. HTTP clients must bypass web proxies within the VM when querying IMDS. IMDS IP address (`169.254.169.254`) must be handled in the same manner as the `168.63.129.16` IP address. For additional information, read about the [Azure Instance Metadata Service (IMDS)](/azure/virtual-machines/instance-metadata-service)
 
 IMDS problems on Azure virtual machines (VMs) can occur because of configuration, certificate, or connectivity issues. Microsoft provides a script-based tool to help diagnose and resolve most activation-related problems.
 
-## Tool overview
-
-### Azure Instance Metadata Service certificate check
+## Overview
 
-**Purpose**  
 This PowerShell script verifies the attestation signature provided by the Azure Instance Metadata Service (IMDS). It ensures that the certificate used in attestation is valid and trusted by attempting to build a complete certificate chain. This process helps confirm the integrity and authenticity of an Azure VM’s identity. The script is also available via Run Command.
 
-**Key features**  
+## Key features  
 
 - Confirms that `169.254.169.254` is reachable.
 - Validates IMDS certificate presence and correctness.
@@ -67,7 +63,7 @@ For more information, see [Run scripts in your Windows VM by using action Run Co
 1. Run **IMDS Cert Check** to verify activation status and detect common issues.
 2. Apply the suggested fixes or refer to the official documentation for advanced troubleshooting.
 
-### **Additional resources**
+## Additional resources
 
 - [Azure Instance Metadata Service (IMDS)](/azure/virtual-machines/instance-metadata-service)
 - [Azure Instance Metadata Service-Attested data TLS: Critical changes are here](https://techcommunity.microsoft.com/t5/azure-governance-and-management/azure-instance-metadata-service-attested-data-tls-critical/ba-p/2888953)

support/azure/virtual-machines/windows/windows-vm-ipu-tool.md

@@ -11,6 +11,7 @@ ms.reviewer: macla, scotro, glimoli, jarrettr, azurevmcptcic
 **Applies to:** :heavy_check_mark: Windows VMs
 
 ## Overview
+
 This PowerShell script scans **CBS logs** for known Windows Servicing error codes that indicate issues requiring an **In-Place Upgrade (IPU)** or repair. It counts occurrences of each error code and provides a summary at the end. If any errors are found, a remediation link to Microsoft documentation is displayed.
 
 ## Features

support/azure/virtual-machines/windows/windows-vm-osupgradeassessment-tool.md

@@ -1,12 +1,12 @@
 ---
 title: Azure Virtual Machine (VM) Windows OS Upgrade Assessment Tool
-description: Azure VM Windows OS Upgrade Assessment Tool
+description: Azure Virtual Machine (VM) Windows OS Upgrade Assessment Tool
 ms.service: azure-virtual-machines
 ms.date: 06/04/2024
 ms.custom: sap:Cannot create a VM, H1Hack27Feb2017
 ms.reviewer: macla, scotro, glimoli, jarrettr, azurevmcptcic
 ---
-# Azure VM Windows OS Upgrade Assessment Tool
+# Azure Virtual Machine (VM) Windows OS Upgrade Assessment Tool
 
 **Applies to:** :heavy_check_mark: Windows VMs
 

support/azure/virtual-machines/windows/windows-vm-wureset-tool.md

@@ -12,9 +12,7 @@ ms.reviewer: macla, scotro, glimoli, jarrettr, azurevmcptcic
 
 ## Overview
 
-This article offers you steps to run a script that resets the Windows Servicing stack for a virtual machine running in Azure. Running the tool can fix most general problems that prevent Windows Update from installing successfully. 
-
-This script is designed for troubleshooting update failures on Windows Server or Windows client systems.
+This PowerShell script is designed to resets the Windows Servicing stack for a virtual machine running in Azure. This article offers you steps to run a script that resets the Windows Servicing stack for a virtual machine running in Azure. Running the tool can fix most problems that prevent Windows Updates from installing successfully. 
 
 > [!NOTE]
 > This article is intended for use with support agents and IT professionals. If you're a home user and looking for more information about fixing Windows update errors, see [Fix Windows Update errors](https://support.microsoft.com/help/10164).