Merge pull request #8833 from MicrosoftDocs/main

Auto push to live 2025-04-29 10:02:10

Author: Deland-Han

support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md

@@ -13,7 +13,7 @@ ms.topic: troubleshooting
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: azurecli
-ms.date: 10/11/2021
+ms.date: 04/29/2025
 ms.author: genli
 ---
 
@@ -32,6 +32,7 @@ If your Linux virtual machine (VM) in Azure encounters a boot or disk error, you
 > * The maximum time a script can run is 90 minutes, after which it will time out.
 > * Do not modify the tags that are created on the repair VM. The tags are neccessary for the restore command to function correctly.
 > * For VMs using Azure Disk Encryption, only managed disks encrypted with single pass encryption (with or without KEK) are supported.
+> * The VM Contributor role doesn't provide enough permissions to run the scripts, as they require permissions to read, write, and delete resources in the resource group that includes the target VM. Therefore roles such as Contributor or Owner at that resource group level is required.
 
 ## Repair process overview
 

support/azure/virtual-machines/linux/serial-console-grub-single-user-mode.md

@@ -22,7 +22,7 @@ ms.author: genli
 
 [!INCLUDE [CentOS End Of Life](../../../includes/centos-end-of-life-note.md)]
 
-GRand Unified Bootloader (GRUB) is likely the first thing you see when you boot a virtual machine (VM). Because it's displayed before the operating system has started, GRUB isn't accessible via SSH. In GRUB, you can modify your boot configuration to boot into single-user mode, among other things.
+Grand Unified Bootloader (GRUB) operates at an early stage in a Linux virtual machine (VM) boot process. It operates before the Linux kernel is loaded and before any system services (such as networking or SSH) are started, so GRUB isn't accessible via SSH. You must use the Serial Console to access GRUB. In GRUB, you can modify your boot configuration to boot into single-user mode, among other things.
 
 Single-user mode is a minimal environment with minimal functionality. It can be useful for investigating boot issues, file system issues, or network issues. Fewer services can run in the background and, depending on the runlevel, a file system might not even be automatically mounted.
 
@@ -31,7 +31,7 @@ Single-user mode is also useful in situations where your VM might be configured
 > [!NOTE]
 > The Serial Console service allows only users with *contributor* level or higher permissions to access the serial console of a VM.
 
-To enter single-user mode, enter GRUB when your VM is booting, and modify the boot configuration in GRUB. See detailed instructions for entering GRUB in the next section. In general, if your VM has been configured to display GRUB, you can use the restart button within your VM's serial console to restart the VM and display GRUB.
+To enter single-user mode, enter GRUB when your VM is booting, and modify the boot configuration in GRUB. See detailed instructions for entering GRUB in the next section. If your VM is set up to display GRUB, you can use the restart button within your VM's serial console to restart the VM and display GRUB.
 
 :::image type="content" source="media/serial-console-grub-single-user-mode/restart-vm-button.png" alt-text="Screenshot of the Restart VM button displayed in the tool bar." border="false":::
 
@@ -51,7 +51,7 @@ You can also restart your VM by running a SysRq "b" command if [SysRq](./serial-
 
 ## General single-user mode access
 
-You might need manual access to single-user mode when you haven't configured an account with password authentication. Modify the GRUB configuration to manually enter single-user mode. After you've done this, see the "Use single-user mode to reset or add a password" section for further instructions.
+You might need manual access to single-user mode when you haven't configured an account with password authentication. Modify the GRUB configuration to manually enter single-user mode. After doing this, see the "Use single-user mode to reset or add a password" section for further instructions.
 
 If the VM is unable to boot, distributions often automatically drop you into single-user mode or emergency mode. Other distributions, however, require additional setup, such as setting up a root password, before they can drop you into single-user or emergency mode automatically.
 
@@ -63,10 +63,6 @@ After you're in single-user mode, add a new user with sudo privileges by doing t
 1. Run `sudo usermod -a -G sudo <username>` to grant the new user root privileges.
 1. Use `passwd <username>` to set the password for the new user. You can then sign in as the new user.
 
-## Access for Red Hat Enterprise Linux (RHEL)
-
-If RHEL can't boot normally, it drops you into single-user mode automatically. However, if you haven't set up root access for single-user mode, you don't have a root password and can't sign in. There is a workaround (see the "Manually enter single-user mode in RHEL" section), but we suggest that you set up root access initially.
-
 ### GRUB access in RHEL
 
 RHEL comes with GRUB enabled out of the box. To enter GRUB, reboot your VM by running `sudo reboot`, and then press any key. The GRUB pane should be displayed. If it isn't, ensure that the following lines are present in your GRUB file (`/etc/default/grub`):
@@ -93,21 +89,9 @@ GRUB_CMDLINE_LINUX="console=tty1 console=ttyS0,115200n8 earlyprintk=ttyS0,115200
 > [!NOTE]
 > Red Hat also provides documentation for booting into Rescue Mode, Emergency Mode, or Debug Mode, and for resetting the root password. For instructions, see [Terminal menu editing during boot](https://aka.ms/rhel7grubterminal).
 
-### Set up root access for single-user mode in RHEL
-
-The root user is disabled by default. Single-user mode in RHEL requires the root user to be enabled. If you need to enable single-user mode, use the following instructions:
-
-1. Sign in to the Red Hat system via SSH.
-1. Switch to root.
-1. Enable the password for the root user by doing the following:
-    * Run `passwd root` (set a strong root password).
-1. Ensure that the root user can sign in only via ttyS0 by doing the following:
-    a. Run `vi /etc/ssh/sshd_config`, and ensure that PermitRootLogIn is set to `no`.
-    b. Run `vi /etc/securetty file` to allow sign-in only via ttyS0.
-
-Now, if the system boots into single-user mode, you can sign in with the root password.
+### Single-User mode in RHEL 6.9+ and 7.4+
 
-Alternatively, for RHEL 7.4+ or 6.9+, to enable single-user mode in the GRUB prompts, see [Booting into single-user mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/installation_guide/s1-rescuemode-booting-single).
+For RHEL 7.4+ or 6.9+, to enable single-user mode in the GRUB prompts, see [Booting into single-user mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/installation_guide/s1-rescuemode-booting-single).
 
 ### Manually enter single-user mode in RHEL
 
@@ -274,7 +258,6 @@ To enable single-user mode in Oracle Linux, follow the earlier instructions for
 To learn more about Serial Console, see:
 
 * [Linux Serial Console documentation](serial-console-linux.md)
-* [Use Serial Console to enable GRUB in various distributions](https://linuxonazure.azurewebsites.net/why-proactively-ensuring-you-have-access-to-grub-and-sysrq-in-your-linux-vm-could-save-you-lots-of-down-time/)
 * [Use Serial Console for NMI and SysRq calls](serial-console-nmi-sysrq.md)
 * [Serial Console for Windows VMs](../windows/serial-console-windows.md)
 * [Boot diagnostics](../windows/boot-diagnostics.md)

support/azure/virtual-machines/windows/serial-console-windows.md

@@ -11,7 +11,7 @@ ms.collection: windows
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 03/11/2025
+ms.date: 04/29/2025
 ms.author: mbifeld
 ms.custom: sap:VM Admin - Windows (Guest OS)
 ---
@@ -33,18 +33,9 @@ For serial console documentation for Linux, see [Azure Serial Console for Linux]
 > [!NOTE]
 > Serial Console is compatible with a managed boot diagnostics storage account.
 
-## Prerequisites to access the Azure Serial Console
+## Prerequisites
 
-To access the Serial Console on your VM or virtual machine scale set instance, you will need the following:
-
-- Boot diagnostics must be enabled for the VM.
-- A user account that uses password authentication must exist within the VM. You can create a password-based user with the [reset password](/azure/virtual-machines/extensions/vmaccess#reset-password) function of the VM access extension. Select **Reset password** from the **Help** section.
-- The Azure account accessing Serial Console must have [Virtual Machine Contributor role](/azure/role-based-access-control/built-in-roles#virtual-machine-contributor) for both the VM and the [boot diagnostics](boot-diagnostics.md) storage account.
-- Classic deployments aren't supported. Your VM or virtual machine scale set instance must use the Azure Resource Manager deployment model.
-- Serial Console is not supported when the storage account has **Allow storage account key access** disabled.
-
-> [!IMPORTANT]
-> Serial Console is now compatible with [managed boot diagnostics storage accounts](boot-diagnostics.md) and custom storage account firewalls.
+The prerequisites to access the Azure Serial Console can be found [here](serial-console-overview.md#prerequisites-to-access-the-azure-serial-console).
 
 ## Enable Serial Console functionality for Windows Server
 

support/power-platform/power-automate/desktop-flows/troubleshoot-session-creation-errrors.md

@@ -3,7 +3,7 @@ title: Session creation error codes in unattended desktop flow runs
 description: Solves error codes related to session creation during unattended desktop flow runs in Power Automate.
 author: johndund 
 ms.author: johndund 
-ms.date: 02/11/2025
+ms.date: 04/29/2025
 ms.reviewer: madiazor, guco, fredg 
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
@@ -36,11 +36,13 @@ You can find the full list of credential providers (many of which are built-in)
 
 `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers`
 
-Each subkey represents an installed credential provider. The following table lists the credential providers that Power Automate currently doesn't support. If you have the following registry key, work with your system administrator to uninstall the corresponding software.
+Each subkey represents an installed credential provider. The following table lists the credential providers that Power Automate currently doesn't support. If you have any of the following subkeys, work with your system administrator to uninstall the corresponding software.
 
 | Name | Subkey name |
 | :------------------------ | ---------------- |
 | SailPoint Technologies Desktop Password Reset | 0094A34B-0BF0-4789-8B2D-8339E469D756 |
+| SIDCredentialProvider | 36ED98C6-02FF-47e8-B7FE-957A411CEA16 |
+| CGWinLogon | BDA6DA5B-7E7E-482C-9B3E-67AFF0C838C0 |
 
 ## SessionCreationError
 

support/power-platform/power-automate/desktop-flows/ui-automation/cannot-access-java-application-elements.md

@@ -2,7 +2,7 @@
 title: Can't access elements of a Java application
 description: Troubleshoot the issue that Power Automate for desktop can't access the elements of a Java desktop application.
 ms.reviewer: pefelesk
-ms.date: 10/29/2024
+ms.date: 04/29/2025
 ms.custom: sap:Desktop flows\UI or browser automation
 ---
 # Can't access the elements of a Java application
@@ -18,6 +18,18 @@ Power Automate for desktop can't access the UI elements of a Java desktop applic
 
 ## Troubleshooting steps
 
+To solve this issue, try the [troubleshooter](/power-automate/desktop-flows/troubleshooter) first.
+
+1. In Power Automate for desktop, navigate to **Help** > **Troubleshooter**, and then run the [troubleshooter](/power-automate/desktop-flows/troubleshooter).
+
+2. In the **Troubleshooter** window, select **Run** on the **Troubleshot UI/Web automation issues** panel.
+
+3. If an issue is found for **Java Automation**, expand the panel to see the details.
+
+4. If a **Fix** button is available, select it to apply the fix. Ensure all running **Java** applications are closed before applying the fix.
+
+If the issue persists after using the troubleshooter, follow these steps to manually troubleshoot the issue:
+
 1. Ensure that you have Java installed on your machine:
 
    - Open the Command Line tool (cmd) and run the following command:
@@ -34,7 +46,7 @@ Power Automate for desktop can't access the UI elements of a Java desktop applic
 
    Go to **Control Panel** > **Ease of Access** > **Optimize visual display** > **Java Access Bridge from Oracle, Inc. Providing Assistive Technology access to Java applications**, and then disable the **Enable Java Access Bridge** option.
 
-   :::image type="content" source="media/cannot-access-java-application-elements/enable-java-access-bridge-option.png" alt-text="Screenshot of the Enable Java Access Bridge option in the Windows Control Panel.":::
+   :::image type="content" source="media/cannot-access-java-application-elements/enable-java-access-bridge-option.png" alt-text="Screenshot of the Enable Java Access Bridge option in the Windows Control Panel." lightbox="media/cannot-access-java-application-elements/enable-java-access-bridge-option.png":::
 
 3. Ensure that specific files exist in one or more Java folders of the machine after the Power Automate for desktop installation.
 

support/windows-server/certificates-and-public-key-infrastructure-pki/apps-forcibly-closed-tls-connection-errors.md

@@ -35,9 +35,9 @@ If you enabled [SChannel logging](/previous-versions/windows/it-pro/windows-serv
 
 ## Cause
 
-Windows 10, version 1511 and later versions of Windows, including Window Server 2016 or Windows 10, version 1607 that has updates released on Feb 25thor later updates installed, contains a leading zero update. Meanwhile, all Windows versions that released before that don't contain the leading zero updates.  
+Windows 10, version 1511 and later versions of Windows, including Window Server 2016 or Windows 10, version 1607 that has updates released on February 25, 2020, or later updates installed, contains a leading zero update. Meanwhile, all Windows versions that released before that don't contain the leading zero updates.  
 
-The TLS client and server need to calculate keys exactly the same way otherwise they get different results. TLS connections randomly fail if leading zeros are computed differently by the TLS client and TLS Servers.  
+The TLS client and server need to calculate keys exactly the same way, otherwise they get different results. TLS connections randomly fail if leading zeros are computed differently by the TLS client and TLS Servers.  
 
 When a [Diffie-Hellman key exchange](https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange) group has leading zeros, unpatched computers may incorrectly compute the mac by not accounting for the padded zeros. This issue is typically seen when interacting with non-Windows-based crypto implementations and can cause intermittent negotiation failures.