RDS 2016 Remote App issue
-
@dbeato said in RDS 2016 Remote App issue:
Hello All,
I have hit a wall (or it seems like it) with an RDS 2016 server that was deployed for a client. All servers are setup with Windows Server 2016 and are VMs.
The setup is as follows:
1- Server has RDGateway, RD Licensing and Remote Web Apps.
2- Server has The Connection Broker role
3- Server has the Remote Session Host role.The problem I am seeing is that Remote Apps do not work or open from Web Interface or RDP file. I can connect to any remote server via RDP externally or Internally through the RDGateway also Remote Apps RDP files previously deployed work.
The error I get is "Your computer was unable to connect to the remote computer" but there are no errors in either the RDGateway, RD Connection Broker or Session Host.
Any advice or recommendation is appreciated. I also would like to note that I have removed and recreated the collection to not avail.
Check the RDP files that you get from your Web site and see if it has the RD Gateway setting in there?
-
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
Hello All,
I have hit a wall (or it seems like it) with an RDS 2016 server that was deployed for a client. All servers are setup with Windows Server 2016 and are VMs.
The setup is as follows:
1- Server has RDGateway, RD Licensing and Remote Web Apps.
2- Server has The Connection Broker role
3- Server has the Remote Session Host role.The problem I am seeing is that Remote Apps do not work or open from Web Interface or RDP file. I can connect to any remote server via RDP externally or Internally through the RDGateway also Remote Apps RDP files previously deployed work.
The error I get is "Your computer was unable to connect to the remote computer" but there are no errors in either the RDGateway, RD Connection Broker or Session Host.
Any advice or recommendation is appreciated. I also would like to note that I have removed and recreated the collection to not avail.
Check the RDP files that you get from your Web site and see if it has the RD Gateway setting in there?
It doesn’t, that’s what I found out. I added it manually to the RDP file in the registry and still doesn’t work
-
@dbeato said in RDS 2016 Remote App issue:
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
Hello All,
I have hit a wall (or it seems like it) with an RDS 2016 server that was deployed for a client. All servers are setup with Windows Server 2016 and are VMs.
The setup is as follows:
1- Server has RDGateway, RD Licensing and Remote Web Apps.
2- Server has The Connection Broker role
3- Server has the Remote Session Host role.The problem I am seeing is that Remote Apps do not work or open from Web Interface or RDP file. I can connect to any remote server via RDP externally or Internally through the RDGateway also Remote Apps RDP files previously deployed work.
The error I get is "Your computer was unable to connect to the remote computer" but there are no errors in either the RDGateway, RD Connection Broker or Session Host.
Any advice or recommendation is appreciated. I also would like to note that I have removed and recreated the collection to not avail.
Check the RDP files that you get from your Web site and see if it has the RD Gateway setting in there?
It doesn’t, that’s what I found out. I added it manually to the RDP file in the registry and still doesn’t work
https://gitlab.com/dafyre/powershell-utils/raw/master/RAPPConfiguration.ps1
Here's a Powershell script I use to do it. (must be run as admin). From what I gather, this has to be done per collection...
./RAPPConfiguration.ps1 -collection "My collection" -gateway "rdgateway.mydomain.com"
Should get you going. I recommend running this from your connection broker.
-
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
Hello All,
I have hit a wall (or it seems like it) with an RDS 2016 server that was deployed for a client. All servers are setup with Windows Server 2016 and are VMs.
The setup is as follows:
1- Server has RDGateway, RD Licensing and Remote Web Apps.
2- Server has The Connection Broker role
3- Server has the Remote Session Host role.The problem I am seeing is that Remote Apps do not work or open from Web Interface or RDP file. I can connect to any remote server via RDP externally or Internally through the RDGateway also Remote Apps RDP files previously deployed work.
The error I get is "Your computer was unable to connect to the remote computer" but there are no errors in either the RDGateway, RD Connection Broker or Session Host.
Any advice or recommendation is appreciated. I also would like to note that I have removed and recreated the collection to not avail.
Check the RDP files that you get from your Web site and see if it has the RD Gateway setting in there?
It doesn’t, that’s what I found out. I added it manually to the RDP file in the registry and still doesn’t work
https://gitlab.com/dafyre/powershell-utils/raw/master/RAPPConfiguration.ps1
Here's a Powershell script I use to do it. (must be run as admin). From what I gather, this has to be done per collection...
./RAPPConfiguration.ps1 -collection "My collection" -gateway "rdgateway.mydomain.com"
Should get you going. I recommend running this from your connection broker.
I did do that as well since I have it but still
-
-
@dbeato said in RDS 2016 Remote App issue:
I am also leaning to do this:
https://social.technet.microsoft.com/Forums/windows/en-US/96cf9ef3-6ec2-4c7a-9e9f-21aeb6ef794d/remote-desktop-collection-is-missing-properties-i-would-like-to-add?forum=winserverTSThat's essentially why the powershell script does... So you ran the script and you're still not getting correct RDP files from the RD Web site?
-
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
I am also leaning to do this:
https://social.technet.microsoft.com/Forums/windows/en-US/96cf9ef3-6ec2-4c7a-9e9f-21aeb6ef794d/remote-desktop-collection-is-missing-properties-i-would-like-to-add?forum=winserverTSThat's essentially why the powershell script does... So you ran the script and you're still not getting correct RDP files from the RD Web site?
yeah, it didn't really work since it is not updating anything on the connection broker. I am going to redo it all...
-
@dbeato said in RDS 2016 Remote App issue:
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
I am also leaning to do this:
https://social.technet.microsoft.com/Forums/windows/en-US/96cf9ef3-6ec2-4c7a-9e9f-21aeb6ef794d/remote-desktop-collection-is-missing-properties-i-would-like-to-add?forum=winserverTSThat's essentially why the powershell script does... So you ran the script and you're still not getting correct RDP files from the RD Web site?
yeah, it didn't really work since it is not updating anything on the connection broker. I am going to redo it all...
Curious.
-
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
I am also leaning to do this:
https://social.technet.microsoft.com/Forums/windows/en-US/96cf9ef3-6ec2-4c7a-9e9f-21aeb6ef794d/remote-desktop-collection-is-missing-properties-i-would-like-to-add?forum=winserverTSThat's essentially why the powershell script does... So you ran the script and you're still not getting correct RDP files from the RD Web site?
yeah, it didn't really work since it is not updating anything on the connection broker. I am going to redo it all...
Curious.
You mean after I finish redoing it?
-
@dbeato said in RDS 2016 Remote App issue:
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
@dafyre said in RDS 2016 Remote App issue:
@dbeato said in RDS 2016 Remote App issue:
I am also leaning to do this:
https://social.technet.microsoft.com/Forums/windows/en-US/96cf9ef3-6ec2-4c7a-9e9f-21aeb6ef794d/remote-desktop-collection-is-missing-properties-i-would-like-to-add?forum=winserverTSThat's essentially why the powershell script does... So you ran the script and you're still not getting correct RDP files from the RD Web site?
yeah, it didn't really work since it is not updating anything on the connection broker. I am going to redo it all...
Curious.
You mean after I finish redoing it?
Just strange that it isn't working. I have Gateway, Web, and Connection Broker on same system here, so that could be part of it.