Tools

Not able to see UAC prompt when on a remote DRE session

This article shows how to resolve and remove the black screen that appears when the UAC prompts during a remote DRE session

First published date

3/31/2020 12:41 PM

Last published date

4/12/2020 2:06 PM

Overview

When connected to a remote session via DRE and you are log in to the remote host as domain admin or with elevated user privileges, performing tasks that require admin permission triggers the UAC to prompt normally on the screen of the user that has the higher privilege or on the "secure remote desktop". The registry entry in-charge of where the UAC prompt should show up, determines which screen it should appear. When that said registry gets corrupted or missing, it will only display on the native monitor and remote administration will be on a standstill until the remote user supplies the admin credentials.

By design, DRE agent service does not have the ability to elevate any domain user privileges and would depend deeply on the DRE technician's access level within the domain and remote host as a domain resource.

When performing a task that requires an admin permission during the DRE session, the selected value for "User Account Control: Switch to the secure desktop when prompting for elevation" determines where the prompt would appear:

- Enabled: (Default) All elevation requests go to the secure desktop regardless of prompt behavior policy settings for administrators and standard users

- Disabled, All elevation requests go to the interactive user's desktop. Prompt behavior policy settings for administrators and standard users are used.

Also, the UAC prompt will not appear on the secure desktop if the UAC switch registry is missing or corrupted.

Product section

Dameware Remote Everywhere

Cause

The registry key that controls whether prompting should occur on the secure desktop or on the user's desktop is missing or corrupted.

Resolution

1. Once connected to the remote machine thru DRE, Click on the Remote Registry tab

2. On the Registry Editor:

Locate and right-click HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorAdmin, and then click Delete.
Right-click HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System, point to New, and then click DWORD Value.
Type ConsentPromptBehaviorAdmin, and then press ENTER.
Right-click ConsentPromptBehaviorAdmin, and then click Modify.
In the Value data box, type 5, and then click OK.
Locate and right-click HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\PromptOnSecureDesktop, and then click Delete.
Right-click HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System, point to New, and then click DWORD Value.
Type PromptOnSecureDesktop, and then press ENTER.
Right-click PromptOnSecureDesktop, and then click Modify.
In the Value data box, type 1, and then click OK

4. Select the remote Remote Desktop tab to view

For additional information regarding UAC not showing on secure remote desktop, see https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee844168(v%3dws.10 © Microsoft 2020 available at https://docs.microsoft.com/
obtained on March 27, 2020)

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.