Merge pull request #9172 from MicrosoftDocs/main

Auto push to live 2025-06-20 10:01:51

Author: Deland-Han

support/azure/virtual-machines/linux/leapp-upgrade-process-rhel-7-and-8.md

@@ -2,7 +2,7 @@
 title: Upgrade RHEL PAYG virtual machines using Leapp
 description: Provides steps to upgrade virtual machines that use RHEL pay-as-you-go images from RHEL 7 to RHEL 8 or RHEL 8 to RHEL 9.
 ms.reviewer: divargas, msaenzbo, v-weizhu
-ms.date: 09/14/2024
+ms.date: 06/20/2025
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
 ms.topic: how-to
@@ -91,16 +91,18 @@ You can perform an in-place upgrade from RHEL 7 to the following RHEL 8 minor ve
 You can perform an in-place upgrade from RHEL 8 to the following RHEL 9 minor versions.
 
 
-| Source OS version| Target version  | End of support      |
-|------------------|-----------------|---------------------|
-| RHEL 8.8         | RHEL 9.2        | May 31, 2025 (EUS)  |
-| RHEL 8.10        | RHEL 9.4        | May 31, 2026 (EUS)  |
-| RHEL 8.10        | RHEL 9.5        | May 31, 2026        |
+| Source OS version| Target version | End of support      |
+|------------------|----------------|---------------------|
+| RHEL 8.10        | RHEL 9.4       | April 30, 2026 (EUS)|
+| RHEL 8.10        | RHEL 9.6       | April 31, 2027 (EUS)|
+
 
 
 > [!NOTE]  
 > If you locked the VM to a minor release, remove the version lock. For more information, see [Switch a RHEL 8.x VM back to non-EUS](/azure/virtual-machines/workloads/redhat/redhat-rhui?tabs=rhel8#switch-a-rhel-server-to-non-eus-repositories).
 
+
+
 1. If you restricted packages to a specific version using the `yum-plugin-versionlock` command, remove the restriction:
 
     ```bash
@@ -152,6 +154,7 @@ Replace `<target_os_version>` with the target OS version, for example, `8.10`.
 
 ### [RHEL 8.*x* to RHEL 9.*x*](#tab/rhel8-rhel9)
 
+
 Run the following `leapp preupgrade` command:
 
 ```bash
@@ -205,7 +208,7 @@ Continue the Leapp upgrade process after the Leapp pre-upgrade report shows no e
     ```
     
     > [!NOTE]
-    > - Replace `<target_os_version>` with the target OS version, for example, `9.4` or `9.5`. 
+    > - Replace `<target_os_version>` with the target OS version, for example, `9.4` or `9.6`. 
     > - If you want to perform an automatic reboot, which is needed during the upgrade process, add the `--reboot` option to the `leapp upgrade` command.
 
 2. If the `--reboot` option wasn't included in the previous command, monitor the Serial Console. Once the upgrade process shows that a reboot is required to continue the process as follows, manually reboot the VM:

support/windows-server/windows-security/windows-laps-troubleshooting-guidance.md

@@ -1,7 +1,7 @@
 ---
 title: Windows LAPS troubleshooting guidance
 description: Provides troubleshooting guidance for Windows LAPS using Windows events.
-ms.date: 01/15/2025
+ms.date: 06/20/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -144,7 +144,7 @@ LAPS failed to find the currently configured local administrator account
 
 Windows LAPS reads the local administrator's name from Group Policy or the Intune setting **Name of administrator account to manage**. If this setting isn't configured, it will look for the local account with a security identifier (SID) ending with 500 (administrator). If Windows LAPS can't find the account, Event ID 10013 is logged.
 
-In the current version of Windows LAPS, there's no feature to create the managed user.
+Starting with Windows 11, version 24H2 and Windows Server 2025, a feature to create the managed user has been added. For more information, see [Windows LAPS account management modes](/windows-server/identity/laps/laps-concepts-account-management-modes). For earlier versions, the account must already exist.
 
 ### Resolution
 
@@ -193,7 +193,7 @@ The device (Microsoft Entra joined or hybrid joined) that's configured with Wind
 
 ### Resolution
 
-1. Verify that you can connect successfully to the registration endpoint (`https://enterpriseregistration.windows.net`). If you open Microsoft Edge or Google Chrome and connect to the registration endpoint (`https://enterpriseregistration.windows.net`), you get a message "Endpoint not found". This message means you can connect to the Enterprise Registration Endpoint.
+1. Verify that you can connect successfully to the registration endpoint (`https://enterpriseregistration.windows.net`). If you open Microsoft Edge or Google Chrome and connect to the registration endpoint (`https://enterpriseregistration.windows.net`), you get a message "Unsupported method or endpoint." This message means you can connect to the Enterprise Registration Endpoint.
 2. If you're using a proxy server, verify that your proxy is configured under the system context. You can open an elevated command prompt and run the `netsh winhttp show proxy` command to display the proxy.
 
 ## Event ID 10026
@@ -437,7 +437,7 @@ This issue can also occur if you move the machine to a different organizational
 1. If you haven't run the Windows LAPS PowerShell cmdlet to assign the Self Permission to the computer account, run the following cmdlet:
 
     ```PowerShell
-    Set-LapsADComputerSelfPermission -identity <OU Name>
+    Set-LapsADComputerSelfPermission -Identity <OU Name>
     ```
 
     For example: