Merge pull request #8326 from MicrosoftDocs/main

Deland-Han · web-flow · commit 02ba15f70d79 · 2025-02-26T18:00:08.000+08:00
Auto push to live 2025-02-26 02:00:02
diff --git a/support/azure/.openpublishing.redirection.azure.json b/support/azure/.openpublishing.redirection.azure.json
@@ -6295,6 +6295,10 @@
       {
         "source_path": "azure-kubernetes/error-codes/vhdfilenotfound.md",
         "redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-vhdfilenotfound"
+      },
+      {
+        "source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
+        "redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
       }
   ]
 }
diff --git a/support/azure/virtual-machines/linux/linux-virtual-machine-cannot-start-fstab-errors.md b/support/azure/virtual-machines/linux/linux-virtual-machine-cannot-start-fstab-errors.md
@@ -4,7 +4,9 @@ description: Explains why Linux VM can't start and how to solve the problem.
 services: virtual-machines
 documentationcenter: ''
 author: saimsh-msft
+ms.author: saimsh
 manager: dcscontentpm
+ms.reviewer: divargas
 tags: ''
 ms.custom: sap:My VM is not booting, linux-related-content
 ms.service: azure-virtual-machines
@@ -13,8 +15,7 @@ ms.topic: troubleshooting
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: azurecli
-ms.date: 02/19/2025
-ms.author: saimsh
+ms.date: 02/26/2025
 ---
 
 # Troubleshoot Linux VM boot issues due to fstab errors
@@ -112,13 +113,17 @@ Azure Linux Auto Repair (ALAR) scripts are part of the VM repair extension descr
 The ALAR scripts use the repair extension `repair-button` to fix fstab issues by specifying `--button-command fstab`. This parameter triggers the automated recovery. Implement the following steps to automate fstab errors via the offline ALAR approach:
 
 ```azurecli-interactive
-az vm repair repair-button --button-command fstab --verbose rgtest --name vmtest
+az extension add -n vm-repair
+az extension update -n vm-repair
+az vm repair repair-button --button-command 'fstab' --verbose $RGNAME --name $VMNAME
 ```
 
 > [!NOTE]
-> - Replace the resource group name `rgtest` and VM name `vmtest` accordingly.
-> - The repair VM script, in conjunction with the ALAR script, will temporarily create a resource group, a repair VM, and a copy of the affected VM's OS disk. It backs up the original **/etc/fstab** file and modifies it by removing or commenting out data file system entries that aren't required to boot the system.
-> - After the OS starts successfully, review and edit the **/etc/fstab** file to fix any errors that might have prevented a proper reboot. Finally, the `repair-button` script will automatically delete the resource group containing the repair VM.
+> Replace the resource group name `$RGTEST` and VM name `$VMNAME` accordingly.
+
+* The repair VM script, in conjunction with the ALAR script, will temporarily create a resource group, a repair VM, and a copy of the affected VM's OS disk. It backs up the original `/etc/fstab` file and modifies it by removing or commenting out data file system entries that aren't required to boot the system.
+* After the OS starts successfully, review and edit the `/etc/fstab` file to fix any errors that might have prevented a proper reboot.
+* Finally, the `repair-button` script will automatically delete the resource group containing the repair VM.
 
 #### Use the manual method
 
diff --git a/support/azure/virtual-machines/linux/suse-public-cloud-connectivity-registration-issues.md b/support/azure/virtual-machines/linux/suse-public-cloud-connectivity-registration-issues.md
@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot connectivity and registration for SUSE SLES VMs
 description: Troubleshoot scenarios in which an Azure VM that has a SUSE Linux Enterprise Server image can't connect to the SUSE Subscription Management Tool (SMT) repository.
-ms.date: 02/04/2025
+ms.date: 02/26/2025
 author: rnirek
 ms.author: hokamath
 ms.reviewer: adelgadohell, mahuss, esanchezvela, scotro, v-weizhu, divargas
@@ -221,29 +221,15 @@ If instances aren't regularly updated, they can become incompatible with our upd
     ```bash
     sudo zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata SUSEConnect python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin libsuseconnect suseconnect-ruby-bindings docker libcontainers-common
     ```
-
-    > [!IMPORTANT]
-    > The latest `cloud-regionsrv-client-10.3.11-150300.13.19.1` introduces new dependencies (`libcontainers-common` and `docker`). This causes dependency errors. When [cloud instance repos fail because of outdated packages](https://www.suse.com/support/kb/doc/?id=000021552), the latest packages are installed:
-    >```ouput
-    >cloud-regionsrv-client 10.3.11-150300.13.19.1
-    >cloud-regionsrv-client-plugin-azure 2.0.0-150300.13.19.1
-    >```
-
-4. If there are dependency errors from the latest package, `cloud-regionsrv-client-10.3.11-150300.13.19.1`, you must downgrade `cloud-regionsrv-client` and `cloud-regionsrv-client-plugin-azure`. Otherwise, skip this step.
-
-    ```bash
-    sudo zypper --no-refresh --no-remote --non-interactive  install --old-package cloud-regionsrv-client-10.3.7-150300.13.14.1.noarch.rpm
-    sudo zypper --no-refresh --no-remote --non-interactive  install --old-package cloud-regionsrv-client-plugin-azure-2.0.0-150300.13.14.1.noarch.rpm
-    ```
-5. Run the following commands:
+4. Run the following commands:
 
     ```bash
     sudo find /root/packages/ -type f -name "*.rpm" -exec cp {} /root/packages/rpms/ \;
     sudo cd /root/packages
     sudo tar -czvf suse-public-registration.tgz rpms
     ```
 
-6. Transfer `suse-public-registration.tgz` to the broken instance:
+5. Transfer `suse-public-registration.tgz` to the broken instance:
 
     ```bash
     sudo scp /root/packages/suse-public-registration.tgz user@targetip:/tmp
@@ -252,7 +238,7 @@ If instances aren't regularly updated, they can become incompatible with our upd
     > [!NOTE]
     > Replace `user` and `targetip` as appropriate.
 
-7. Sign in to the broken instance to extract and install the packages:
+6. Sign in to the broken instance to extract and install the packages:
 
     ```bash
     sudo cd tmp
@@ -261,11 +247,12 @@ If instances aren't regularly updated, they can become incompatible with our upd
     sudo zypper --no-refresh --no-remote --non-interactive install --force *.rpm
     ```
 
-8. Register the VM again:
+7. Register the VM again:
 
     ```bash
     sudo registercloudguest --force-new
     ```
+For more information, see [Cloud instance repos fail due to outdated packages](https://www.suse.com/support/kb/doc/?id=000021552).
 
 ## Scenario 3: General registration issues
 
diff --git a/support/azure/virtual-machines/linux/toc.yml b/support/azure/virtual-machines/linux/toc.yml
@@ -124,8 +124,8 @@
   items:
   - name: Can't restart after applying kernel changes
     href: kernel-related-boot-issues.md
-  - name: Linux VMs fail to boot due to Hyper-V driver issues
-    href: linux-vm-no-boot-hyper-v-driver-issues.md
+  - name: Troubleshoot LIS driver issues on Linux VMs
+    href: troubleshoot-lis-driver-issues-on-linux-vms.md
 
 - name: OS upgrades
   items:
diff --git a/support/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms.md b/support/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms.md
@@ -1,15 +1,15 @@
 ---
-title: Linux VMs fail to boot due to Hyper-V driver issues
-description: Provides solutions to Azure Linux VM boot failures that occur because Hyper-V drivers are missing or disabled.
+title: Troubleshoot LIS/Hyper-V Driver Issues on Linux Virtual Machines
+description: Provides solutions to Azure Linux VM issues that occur because Hyper-V drivers are missing or disabled.
 ms.date: 02/26/2025
 ms.reviewer: divargas, msaenzbo, v-weizhu
 ms.custom: sap:My VM is not booting, linux-related-content
 ---
-# Azure Linux virtual machines fail to boot due to Hyper-V driver issues 
+# Troubleshoot LIS/Hyper-V driver issues on Linux virtual machines
 
 **Applies to:** :heavy_check_mark: Linux VMs
 
-When you run a Linux Virtual Machine (VM) on Azure, the Hyper-V drivers, also known as Linux Integration Services (LIS) drivers, are crucial for proper VM operations. These drivers allow the VM to communicate with the underlying Azure hypervisor. If these drivers are missing or not properly loaded, the VM might fail to boot. This article provides solutions to boot failures due to Hyper-V driver issues in Azure Linux VMs.
+When you run a Linux Virtual Machine (VM) on Azure, the Hyper-V drivers, also known as Linux Integration Services (LIS) drivers, are crucial for proper VM operations. These drivers allow the VM to communicate with the underlying Azure hypervisor. If these drivers are missing or not properly loaded, the VM might fail to boot. This article provides solutions to LIS/Hyper-V driver issues in Azure Linux VMs.
 
 ## Prerequisites
 
@@ -94,7 +94,7 @@ dracut:/#
 
 ## Cause
 
-Here are some reasons for VM boot failures:
+If LIS/Hyper-V drivers are missing or not correctly loaded, the VM might not start because of the following reasons:
 
 - Missing disk and network drivers
 
@@ -199,7 +199,9 @@ Here are some reasons for VM boot failures:
 
 4. Rebuild the initial RAM disk image for your affected kernel by following the steps in [Regenerate missing initramfs manually](kernel-related-boot-issues.md#missing-initramfs-manual).
 
-## Verify the network driver is functional after a fresh boot or reboot
+## FAQ
+
+### If I'm experiencing some issues, such as connectivity, how can I make sure that the network driver, hv_netvsc, is working as expected after a fresh start or restart of the system?
 
 To confirm that the Hyper-V network driver (`hv_netvsc`) is active and functional, check the system logs and look for the following entry:
 
diff --git a/support/dynamics-365/supply-chain/procurement/purchase-order-line-deletion-restriction.md b/support/dynamics-365/supply-chain/procurement/purchase-order-line-deletion-restriction.md
@@ -3,7 +3,7 @@ title: Purchase Order Line Deletion Restriction
 description: Provides a workaround for the restriction on deleting purchase order lines under certain conditions in Dynamics 365 Supply Chain Management.
 ms.reviewer: shubhamshr
 ms.date: 02/25/2025
-ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orderss
+ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orders
 ---
 # Can't delete a purchase order line after it's confirmed
 
diff --git a/support/windows-server/active-directory/lds-service-startup-fails.md b/support/windows-server/active-directory/lds-service-startup-fails.md
@@ -1,7 +1,7 @@
 ---
 title: LDS service startup fails
 description: Introduce the solution for LDS Service startup failure after you manually change msDS-Behavior-Version attribute.
-ms.date: 01/15/2025
+ms.date: 02/26/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -10,16 +10,14 @@ ms.custom:
 - sap:active directory\ldap configuration and interoperability
 - pcy:WinComm Directory Services
 ---
-# LDS service startup fails after you manually change msDS-Behavior-Version in Windows Server 2019 and 2016
+# LDS service startup fails after you manually change msDS-Behavior-Version in Windows Server
 
-This article provides a solution to an error that LDS service startup fails after you manually change msDS-Behavior-Version.
+This article provides a solution to an error that the LDS service startup fails after you manually change the **msDS-Behavior-Version** attribute.
 
-_Applies to:_ &nbsp; Windows Server 2019, Windows Server 2016  
+_Applies to:_ &nbsp; All supported versions of Windows Server and Windows Client  
 _Original KB number:_ &nbsp; 4550446
 
-## Symptom
-
-In ADSI Edit, you change the **msDS-Behavior-Version** attribute of the Partitions container to **7** in order to raise the Active Directory (AD) Lightweight Directory Services (LDS) instance functional level to WIN2016.
+In ADSI Edit, you change the **msDS-Behavior-Version** attribute of the **Partitions** container to **7** in order to raise the Active Directory (AD) Lightweight Directory Services (LDS) instance functional level to **WIN2016**.
 
 :::image type="content" source="media/lds-service-startup-fails/attribute-editor.png" alt-text="Change the msDS-Behavior-Version attribute to 7.":::
 
@@ -51,81 +49,4 @@ Additionally, you receive the following error message:
 
 :::image type="content" source="media/lds-service-startup-fails/error-message.png" alt-text="Error 0xc0000025 Windows could not start the L D S service on Local Computer.":::
 
-## Cause
-
-Manually setting the **msDS-Behavior-Version** attribute value to **7** on LDS instances is not supported.
-
-## Resolution
-
-If the LDS instance contains only one server, you must restore the server from a backup to resolve the issue.
-
-If there are multiple replica servers in that instance (for example, LDSServer1 and LDSServer2), and if one server has not yet been restarted, follow these steps:
-
-1. If the LDS server on which the service that does not start (for example, LDSServer1) holds the LDS Roles (for example, Schema and Domain Naming FSMO), seize the roles by running ntdsutil:
-
-    > C:\Windows\system32> **ntdsutil**  
-    ntdsutil: **roles**  
-    fsmo maintenance: **connections**  
-    server connections: **connect to server LDSServer2:50000( 50000 is the port number in that example)**  
-    Binding to LDSServer2:50000 ...  
-    Connected to LDSServer2:50000 using credentials of locally logged on user.  
-    server connections: **q**  
-    fsmo maintenance: **seize schema master**
-
-    :::image type="content" source="media/lds-service-startup-fails/role-seizure-confirmation-dialog.png" alt-text="A role seizure confirmation dialog displays.":::
-
-2. Connect to the configuration partition of the server that still runs the LDS instance (for example, LDSServer2), and then roll back the functionality level version by reverting the **msDS-Behavior-Version** attribute value.
-
-3. Run a metadata cleanup of the LDS server (LDSServer1) by using **dsmgmt**:
-
-    > C:\Windows\system32> **dsmgmt**  
-    dsmgmt: **metadata cleanup**  
-    metadata cleanup: **connections**  
-    server connections: **connect to server LDSServer2:50000 ( 50000 is the port number in that example)**  
-    Binding to LDSServer2:50000 ...
-    Connected to LDSServer2:50000 using credentials of locally logged on user.
-    server connections: **q**  
-    metadata cleanup: **select operation target**  
-    select operation target: **list naming contexts**  
-    Found 3 Naming Context(s)
-    0 - CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    1 - CN=Schema,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-     2 - DC=LDS,DC=COM
-    select operation target: **select naming context2 ( 2 stands for the domain naming context )**  
-    No current site
-    No current domain
-    No current server
-    Naming Context - DC=LDS,DC=COM
-    select operation target: **list sites**  
-    Found 4 site(s)
-    0 - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    1 - CN=Site1,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    2 - CN=Site2,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-     3 - CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    select operation target: **select site3 (where 3 is the number of the site in which the server is located,** **matching output from previous step)**  
-    Site - CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    No current domain
-    No current server
-    Naming Context - DC=LDS,DC=COM
-    select operation target: **list servers in Site**  
-    Found 1 server(s)
-     0 - CN=LDSServer1,CN=Servers,CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    select operation target: **select Server0 (where 0 is the number of the server you wish to remove, matching output from previous step)**  
-    Site - CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    No current domain
-    Server - CN=LDSServer1,CN=Servers,CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    DSA object - CN=NTDS Settings,CN=LDSServer1,CN=Servers,CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    DNS host name - LDSServer1.CONTOSO.COM
-    Naming Context - DC=LDS,DC=COM
-    select operation target: **q**  
-    metadata cleanup: **remove selected server**
-
-    :::image type="content" source="media/lds-service-startup-fails/server-remove-confirmation-dialog.png" alt-text="Select Yes to remove the server object in the Server Remove Confirmation Dialog box.":::
-
-4. Log on to LDSServer1, and uninstall the instance:
-
-    :::image type="content" source="media/lds-service-startup-fails/uninstall-program.png" alt-text="Select the instance that you want to uninstall in Programs and features window.":::
-
-    :::image type="content" source="media/lds-service-startup-fails/select-skip-all.png" alt-text="Select Skip All in the Active Directory Lightweight Directory Services Removal Wizard.":::
-
-5. Run the Active Directory Lightweight Directory Services Setup (C:\Windows\ADAM\adaminstall.exe) on LDSServer1 to install a replica of the existing instance from LDSServer2.
+For Windows servers with monthly updates before the February 2025 update rollup installed, manually setting the **msDS-Behavior-Version** attribute value of LDS instances to **7** isn't supported. To resolve the issue, install the February 2025 update rollup or a later version.

Original file line number	Diff line number	Diff line change
`@@ -6295,6 +6295,10 @@`
`6295`	`6295`	`{`
`6296`	`6296`	`"source_path": "azure-kubernetes/error-codes/vhdfilenotfound.md",`
`6297`	`6297`	`"redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-vhdfilenotfound"`
	`6298`	`+ },`
	`6299`	`+ {`
	`6300`	`+ "source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",`
	`6301`	`+ "redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"`
`6298`	`6302`	`}`
`6299`	`6303`	`]`
`6300`	`6304`	`}`