Command 'az network bastion rdp' does not work in admin powershell window
See original GitHub issueRunning the following command in an admin powershell window results in the below error on multiple machines. It works just fine in a normal / non-admin window.
az network bastion rdp --subscription [MySubID] --target-resource-id [MyTargetResourceID] --resource-group [MyResourceGroup] --name [MyBastionName]
Error: ‘Invalid connection file (C:\Windows\System32/conn.rdp) specified’
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Azure Bastion Native Client Support With the Windows RDP ...
It's important that you run Windows Terminal as an administrator, otherwise the 'az network bastion rdp' command will fail with a permissions ...
Read more >az network bastion rdp command does not recongize valid VM ...
I am attempting to use the az network bastion rdp command to connect to an Azure Windows VM using the native RDP client...
Read more >Connect to a VM using a native client and Azure Bastion
Connect to a VM using the az network bastion tunnel command. This lets you do the following: Use native clients on non-Windows local ......
Read more >Cannot connect with RDP to a Windows VM in Azure - Virtual ...
The issue can be with the Remote Desktop service on the VM, the network connection, or the Remote Desktop client on your host...
Read more >An internal error occurs when you try to connect to an Azure ...
First, check to see whether the network security group for RDP port 3389 is unsecured (open). If it's unsecured and it shows *...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just wanted to add that I was able to reproduce this issue. The RDP connection fails with the above error when running Powershell as Admin. The RDP connection is successful when running Powershell as a normal / non-admin session.
@PramodValavala-MSFT I’m not the original commenter but I tested your work around and it does resolve the issue. I changed the directory to just the C:/ and was able to run the command in an admin powershell window. I appreciate your input!