Merge pull request #8077 from MicrosoftDocs/main

Auto push to live 2025-01-21 18:00:03

Author: Deland-Han

support/azure/azure-storage/files/security/files-troubleshoot-linux-nfs.md

@@ -3,7 +3,7 @@ title: Troubleshoot NFS file shares - Azure Files
 description: Troubleshoot issues with NFS Azure file shares.
 ms.service: azure-file-storage
 ms.custom: sap:Security, linux-related-content
-ms.date: 10/11/2024
+ms.date: 01/21/2025
 ms.reviewer: kendownie
 ---
 
@@ -24,6 +24,76 @@ This article lists common issues related to NFS Azure file shares and provides p
 | Standard file shares (GPv2), GRS/GZRS | :::image type="icon" source="media/files-troubleshoot-linux-nfs/no-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-linux-nfs/no-icon.png" border="false"::: |
 | Premium file shares (FileStorage), LRS/ZRS | :::image type="icon" source="media/files-troubleshoot-linux-nfs/no-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-linux-nfs/yes-icon.png" border="false":::|
 
+## Use the Always-On Diagnostics tool
+
+You can use the Always-On Diagnostics (AOD) tool to collect logs on NFSv4 and SMB Linux clients. The daemon runs in the background as a system service and can be configured to detect anomalies in a variety of sources such as dmesg logs, debug data, and error and latency metrics. It can capture data from tcpdump, nfsstat, mountstsat, and other sources, along with the system's CPU and memory usage. The tool can be useful for collecting debug information on field issues that can be hard to reproduce.
+
+AOD is currently compatible with systems running SUSE Linux Enterprise Server 15 (SLES15) and Red Hat Enterprise Linux 8 (RHEL8). Follow the appropriate installation steps.
+
+### [RHEL](#tab/RHEL)
+
+Follow these instructions to install the Always-On Diagnostics tool on Red Hat Enterprise Linux 8.
+
+1. Download the repo config package.
+   
+```
+curl -ssl -O https://packages.microsoft.com/config/rhel/8/packages-microsoft-prod.rpm
+```
+
+2. Install the repo config package.
+   
+```
+sudo rpm -i packages-microsoft-prod.rpm
+```
+
+3. Delete the repo config package after installing and updating the package index files.
+
+```
+rm packages-microsoft-prod.rpm
+sudo dnf update
+```
+
+4. Install the package.
+
+```
+sudo dnf install aod
+```
+
+### [SLES](#tab/SLES)
+
+Follow these instructions to install the Always-On Diagnostics tool on SUSE Linux Enterprise Server 15.
+
+1. Add the Microsoft repo. You might need to add the Microsoft repository key to your list of trusted keys.
+
+```
+sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
+sudo zypper addrepo --check --refresh --name 'Microsoft' https://packages.microsoft.com/sles/15/prod microsoft
+```
+
+2. Refresh the repositories.
+
+```
+sudo zypper refresh
+```
+
+3. Check if the repo has been added and the aod package is available for installation.
+
+```
+zypper search aod
+```
+
+4. Install the package.
+
+```
+sudo zypper install aod
+```
+
+### [Ubuntu](#tab/Ubuntu)
+
+The Always-On Diagnostics tool is not yet available for Ubuntu.
+
+---
+
 ## chgrp "filename" failed: Invalid argument (22)
 
 ### Cause 1: idmapping isn't disabled

support/azure/azure-storage/files/security/files-troubleshoot-linux-smb.md

@@ -11,8 +11,6 @@ ms.reviewer: kendownie, v-weizhu
 
 This article lists common issues that can occur when using SMB Azure file shares with Linux clients. It also provides possible causes and resolutions for these problems.
 
-You can use [AzFileDiagnostics](https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFileDiagnostics/Linux) to automate symptom detection and ensure that the Linux client has the correct prerequisites. It helps set up your environment to get optimal performance. You can also find this information in the [Azure file shares troubleshooter](https://support.microsoft.com/help/4022301/troubleshooter-for-azure-files-shares).
-
 > [!IMPORTANT]
 > This article only applies to SMB shares. For details on NFS shares, see [Troubleshoot NFS Azure file shares](/azure/storage/files/files-troubleshoot-linux-nfs).
 
@@ -24,6 +22,80 @@ You can use [AzFileDiagnostics](https://github.com/Azure-Samples/azure-files-sam
 | Standard file shares (GPv2), GRS/GZRS | :::image type="icon" source="media/files-troubleshoot-smb-authentication/yes-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-smb-authentication/no-icon.png" border="false"::: |
 | Premium file shares (FileStorage), LRS/ZRS | :::image type="icon" source="media/files-troubleshoot-smb-authentication/yes-icon.png" border="false"::: | :::image type="icon" source="media/files-troubleshoot-smb-authentication/no-icon.png" border="false"::: |
 
+## Run diagnostics
+
+Diagnostics tools can be helpful for ensuring that clients have the correct prerequisites and for collecting debug information on field issues that can be hard to reproduce.
+
+### Use AzFileDiagnostics
+
+You can use [AzFileDiagnostics](https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFileDiagnostics/Linux) to automate symptom detection and ensure that the Linux client has the correct prerequisites. It helps set up your environment to get optimal performance.
+
+### Use the Always-On Diagnostics tool
+
+You can also use the Always-On Diagnostics (AOD) tool to collect logs on SMB and NFSv4 Linux clients. The daemon runs in the background as a system service and can be configured to detect anomalies in a variety of sources such as dmesg logs, debug data, and error and latency metrics. It can capture data from tcpdump, nfsstat, mountstsat, and other sources, along with the system's CPU and memory usage.
+
+AOD is currently compatible with systems running SUSE Linux Enterprise Server 15 (SLES15) and Red Hat Enterprise Linux 8 (RHEL8). Follow the appropriate installation steps.
+
+#### [SLES](#tab/SLES)
+
+Follow these instructions to install the Always-On Diagnostics tool on SUSE Linux Enterprise Server 15.
+
+1. Add the Microsoft repo. You might need to add the Microsoft repository key to your list of trusted keys.
+
+```
+sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
+sudo zypper addrepo --check --refresh --name 'Microsoft' https://packages.microsoft.com/sles/15/prod microsoft
+```
+
+2. Refresh the repositories.
+
+```
+sudo zypper refresh
+```
+
+3. Check if the repo has been added and the aod package is available for installation.
+
+```
+zypper search aod
+```
+
+4. Install the package.
+
+```
+sudo zypper install aod
+```
+
+#### [RHEL](#tab/RHEL)
+
+Follow these instructions to install the Always-On Diagnostics tool on Red Hat Enterprise Linux 8.
+
+1. Download the repo config package.
+   
+```
+curl -ssl -O https://packages.microsoft.com/config/rhel/8/packages-microsoft-prod.rpm
+```
+
+2. Install the repo config package.
+   
+```
+sudo rpm -i packages-microsoft-prod.rpm
+```
+
+3. Delete the repo config package after installing and updating the package index files.
+
+```
+rm packages-microsoft-prod.rpm
+sudo dnf update
+```
+
+4. Install the package.
+
+```
+sudo dnf install aod
+```
+
+---
+
 ## <a id="timestampslost"></a>Time stamps were lost when copying files
 
 On Linux/Unix platforms, the `cp -p` command fails if different users own file 1 and file 2.

support/power-platform/power-automate/desktop-flows/how-to-get-power-automate-desktop-installer-logs.md

@@ -1,54 +1,52 @@
 ---
-title: Power Automate for desktop installation logs
-description: Introduces the locations that contain Power Automate for desktop installation logs.
-ms.reviewer: quseleba, guco
-ms.date: 09/13/2024
+title: Power Automate for desktop logs
+description: Introduces the locations that contain Power Automate for desktop logs.
+ms.reviewer: quseleba, guco, madiazor, johndund
+ms.date: 01/22/2025
 ms.custom: sap:Desktop flows\Working with Power Automate for desktop
 ---
-# Power Automate for desktop installation logs
+# Power Automate for desktop logs
 
-If your Power Automate for desktop installation fails, you can use the logs described in this article to diagnose and resolve issues. If you need to contact [Microsoft Support](https://www.microsoft.com/power-platform/products/power-automate/support) for assistance with installation issues, collect the following logs in a .zip file and include them in the support request to expedite the investigation.
+When troubleshooting issues with Power Automate for desktop, you might need to collect logs for customer support to analyze. These logs can be for a failed installation, problems running desktop flows, or issues with Power Automate or the machine runtime application.
 
 _Applies to:_   Power Automate  
 _Original KB number:_   4555577
 
 ## Installer logs
 
-These logs can be found in the _%temp%_ folder of the user who performed the installation. You can find them by typing _%temp%_ in the address bar of File Explorer. The files of interest are:
+The easiest way to get installer logs is to export them using the link provided at the end of a failed installation. When your installation fails and displays "There's a problem installing," select the **installation log files** link located under the **Troubleshooting tips** section.
+
+:::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/installation-log-files.png" alt-text="Screenshot of the page that contains the installation log files link that you can use to export the installer logs.":::
+
+If you need to get the installer files manually, they can be found in the _%temp%_ folder of the user who performed the installation. You can find them by typing _%temp%_ in the address bar of File Explorer to locate the following files:
 
 - _Power Automate for desktop\_*.log_
 - _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_
 
-The _Power Automate for desktop\_*.log_ file contains the general reason why the installation failed. The _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_ file has more detailed information.
+The _Power Automate for desktop\_*.log_ file contains the general reason for the installation failure. The _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_ file provides more detailed information.
 
 :::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/power-automate-installer-logs.png" alt-text="Screenshot of the Power automate for desktop installer logs.":::
 
-### How to export the Installer logs
+## On-premises product logs
 
-If your installation encounters an error and displays the message "There's a problem installing," you can find more details by selecting the "installation log files" link located under the **Troubleshooting tips** section. This will allow you to export the installer logs.
+For issues with creating flows, [using the Runtime Application to register](/power-automate/desktop-flows/manage-machines#register-a-new-machine) or configure your machine, or issues during cloud runtime, you might need to gather on-premises logs.
 
-:::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/installation-log-files.png" alt-text="Screenshot of the page that contains the installation log files link that you can use to export the installer logs.":::
+The easiest way to do this is to use the Power Automate machine runtime application. If you have the application installed, you can [use it to export logs automatically](/power-automate/desktop-flows/troubleshoot#collect-machine-logs).
 
-## Program data logs
-
-These are logs of the components installed on your machine. You can find them by typing the path _%programdata%\Microsoft\Power Automate\Logs_ in the address bar of File Explorer.
+If you need to collect on-premises logs manually, they can be found in _%programdata%\Microsoft\Power Automate\Logs_.
 
 > [!NOTE]
 > You need administrator privileges to read or copy these files to another folder. After copying them to a different folder, non-administrator users can open them.
 
 ## Event Viewer logs
 
-These logs are helpful when a Windows service fails to start.
+Event Viewer application logs are helpful when an application crashes or a Windows service fails to start.
 
 Follow these steps to view and save the logs:
 
 1. Open the Windows Event Viewer.
-2. Go to **Windows Logs** > **Application**, find the error, and review the information in the **General** and **Details** tabs.
-3. If needed, use the **Filter Current Log** menu to filter by **Event level** or **Logged** time (such as the last hour).
+2. Go to **Windows Logs** > **Application**, and look for an error with the source corresponding to the application that experienced the problem.
+3. Use the **Filter Current Log** menu to filter by **Event level** or **Logged** time (such as the last hour) if needed.
 4. To save the filtered log file, select **Save Filtered Log File As** and save it as an event file.
 
 :::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/power-automate-event-viewer-logs.png" alt-text="Screenshot of an example error logged in the Event Viewer.":::
-
-## More information
-
-[Troubleshoot installation issues in Power Automate for desktop](power-automate-desktop-installation-issues.md)

support/power-platform/power-automate/desktop-flows/power-automate-desktop-installation-issues.md

@@ -2,7 +2,7 @@
 title: Installation issues in Power Automate for desktop
 description: Helps troubleshoot stallation issues in Power Automate for desktop.
 ms.reviewer: guco, johndund
-ms.date: 09/12/2024
+ms.date: 01/20/2025
 ms.custom: sap:Desktop flows\Installation issues
 ---
 # Troubleshoot installation issues in Power Automate for desktop
@@ -29,7 +29,7 @@ For a complete list of prerequisites, see [Prerequisites and limitations](/power
 
 ## Gather diagnostic information
 
-Installation logs can provide useful details about the installation and help you diagnose and fix issues. For more information about where to find the logs, see [Power Automate for desktop installation logs](how-to-get-power-automate-desktop-installer-logs.md).
+Installation logs can provide useful details about the installation and help you diagnose and fix issues. For more information about where to find the logs, see [Power Automate for desktop installation logs](how-to-get-power-automate-desktop-installer-logs.md#installer-logs).
 
 ## Known issues and workarounds
 

support/power-platform/power-automate/desktop-flows/troubleshoot-direct-connectivity-issues.md

@@ -2,8 +2,8 @@
 title: Direct connectivity issues in Power Automate for desktop
 description: Provides more information about how to solve the direct connectivity issues in Power Automate for desktop.
 ms.reviewer: guco, madiazor, johndund, qliu
-ms.date: 11/21/2024
-ms.custom: sap:Desktop flows\Power Automate for desktop errors
+ms.date: 01/22/2025
+ms.custom: sap:Desktop flows
 ---
 # Direct connectivity issues in Power Automate for desktop
 
@@ -14,7 +14,7 @@ _Original KB number:_   5016345
 
 ## Symptoms
 
-Consider the following scenarios when using direct machine connectivity (not the data gateway, which has been deprecated for desktop flows):
+When attempting to run your desktop flows from a cloud flow or manage your desktop flow machines, you might encounter one of the following issues:
 
 #### Scenario 1
 
@@ -27,15 +27,19 @@ Consider the following scenarios when using direct machine connectivity (not the
 
 #### Scenario 2
 
-- Desktop flows run on a registered machine as long as a user session is running (attended runs) or even for some minutes after the last user has logged off (unattended runs).
+- Desktop flows run on a registered machine as long as a user session is running (attended runs) or even for some minutes after the last user signs out (unattended runs).
 - The connection to the machine is lost after some minutes (for example, 15 minutes).
-- The connection is re-established once a user logs back on to the machine.
+- The connection is re-established once a user signs back in to the machine.
+
+#### Scenario 3
+
+When you sign out of your Windows computer, the machine status in the Power Automate portal shows as disconnected.
 
 ## Cause
 
-Direct to machine connectivity uses Azure WCF relays to allow the Microsoft cloud to connect to on-premises machines and schedule desktop flow runs. The Power Automate Windows service that runs on-premises opens a relay listener that connects to the Azure cloud by opening web sockets.
+Direct to machine connectivity uses [Azure WCF relays](/azure/azure-relay/relay-what-is-it#wcf-relay) to allow the Microsoft cloud to connect to on-premises machines and schedule desktop flow runs. The Power Automate Windows service that runs on-premises opens a relay listener that connects to the Azure cloud by opening web sockets.
 
-The most common cause of relay connectivity issues is the machine losing connection to the network. This can be caused by your machine not being powered on or losing network when no user is signed in to the machine for instance.
+The most common cause of relay connectivity issues is the machine losing connection to the network. This can be caused by your machine not being powered on or losing network when no user is signed in to the machine.
 
 The Power Automate service runs under its own Windows account (NT Service\UIFlowService by default) which must have access to the network and be able to connect to _*.servicebus.windows.net_ (for more information, see [network requirements](/power-automate/ip-address-configuration#desktop-flows-services-required-for-runtime).)
 
@@ -54,13 +58,16 @@ You can refer to [Proxy setup](https://support.microsoft.com/topic/power-automat
 
 2. Understand the topology of the network: what network devices does the traffic hop through before being handed off to the public internet: NAT, firewalls, proxies and so on. Get logs from these devices during impacted runs, and logs from the outermost network device attesting that the traffic to _*.servicebus.windows.net_ is handed off to the public internet.
 
-3. Get WCF logs from UI flow service. For more information, see the [Enable WCF tracing](#enable-wcf-tracing) section below.
+3. If your network traffic runs though a proxy, attempt to mitigate the issue by [changing the on-premises account](/power-automate/desktop-flows/troubleshoot#change-the-on-premises-service-account) with which the Power Automate service (UIFlowService) runs.
+
+4. Get WCF logs from the Power Automate service (UIFlowService). For more information, see the [Enable WCF tracing](#enable-wcf-tracing) section below.
 
-4. Make sure your network configuration allows web socket traffic and long-running connections: a common pattern is proxies or other network devices killing connections after a set time.
+5. Make sure your network configuration allows web socket traffic and long-running connections: a common pattern is proxies or other network devices killing connections after a set time.
 
 ## What information to include when opening a support ticket
 
 - Your network topology: what are the devices that traffic goes through. (see the step 2 in the section above)
+- Whether the Power Automate service (UIFlowService) on your machine is running as the default account (NT Service\UIFlowService) or if it has been changed to run as a different account.
 - Logs from your network devices showing that the traffic is indeed handed off to the public internet. Include times of the issues and the time zones used by the logs.
 - WCF traces from the impacted machines. (see the [Enable WCF tracing](#enable-wcf-tracing) section below)
 - Desktop flow run IDs of impacted runs.