netsh wlan connect name=profile_name not working over SSH when Remote Desktop is enabled

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest version
• Search the existing issues.

Steps to reproduce

The issue occurs when you try to execute netsh wlan connect name=profile_name.

To reproduce the issue you need all three conditions:

• Calling netsh wlan connect over SSH
• Having remote desktop service enabled
• The profile you are connecting to is 802.1x (e.g. WPA2 Enterprise)

Only having two of the conditions it will work, e.g. disabling remote desktop, using WPA2 Personal, or calling netsh command direct from the terminal window.

Expected behavior

The netsh wlan connect command runs and the connection is established successfully.

Actual behavior

The command returns success but it does not connect.

Error details

If you look into the WLAN-AutoConfig logs in Event Viewer you see the error:
Reason: Unable to identify a user for 802.1X authentication.

Checking the OneX logs in Event Viewer you see the error:
Port(2): Error 0x3F0 in calling WTSQueryUserToken. Proposing machine authentication.

Environment data

Name                           Value                                           
----                           -----                                           
PSVersion                      5.1.22621.963                                   
PSEdition                      Desktop                                         
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                         
BuildVersion                   10.0.22621.963                                  
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Version

OpenSSH_for_Windows_8.6p1

Visuals

No response

Start by reproducing netsh wlan connect name=profile_name over SSH with Remote Desktop enabled and an 802.1X profile. Compare the WLAN-AutoConfig and OneX Event Viewer logs, including the WTSQueryUserToken error. Done means the command establishes the authenticated wireless connection instead of returning success without connecting.