Skip to content

Commit d795aa8

Browse files
authored
minor changes
1 parent e470ceb commit d795aa8

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Session creation error codes in unattended desktop flow runs
33
description: Solves error codes related to session creation during unattended desktop flow runs in Power Automate.
44
author: johndund
55
ms.author: johndund
6-
ms.date: 06/06/2024
6+
ms.date: 02/07/2025
77
ms.reviewer: madiazor, guco, fredg
88
ms.custom: sap:Desktop flows\Unattended flow runtime errors
99
---
@@ -53,7 +53,7 @@ To solve the issue:
5353
- Ensure that you can remote desktop to the machine from another machine on your network. If you're using Windows Server, you can try to remote desktop to "localhost" from the local machine itself when logged in as another account. If these actions fail, see [General Remote Desktop connection troubleshooting](../../../windows-server/remote/rdp-error-general-troubleshooting.md).
5454
- If you have a legal notice enabled for login, work with your system administrator to try disabling it. To see if the legal notice is activated, open Registry Editor and go to `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System`. If `legalnoticecaption` or `legalnoticetext` isn't empty, work with your system administrator to disable the legal notice.
5555
- Ensure that no third-party software is installed that might affect login or interfere with creating a remote desktop connection.
56-
- If you are connecting using a domain account (DOMAIN\user), connectivity problems to your domain controller may be causing the session not to properly open. Please work with your system administrator to examine connectivity logs. If you are on an Microsoft Entra ID joined or Entra hybrid joined device, please try using a UPN ([email protected]) to see if this resolves the problem. You can find out if you can use a UPN by going to start > run and running `dsregcmd /status`. If under "Device State" you see "AzureAdJoined: YES", then try changing the user specified the connection to the form [email protected].
57-
56+
- If you're connecting using a domain account (DOMAIN\user), connectivity problems to your domain controller might be causing the session not to properly open. Work with your system administrator to examine connectivity logs.
57+
- If you're on a Microsoft Entra joined or Entra hybrid joined device, try using a UPN (`[email protected]`). To see if you can use a UPN, go to **Start** > **Run**, and run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command. If you see `AzureAdJoined: YES` under `Device State`, try changing the user specified in the connection to the `[email protected]` format.
5858

5959
[!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]

0 commit comments

Comments
 (0)