Estate_Master
asked on
Launching Apps via RDweb Access not working
I have created a Windows Server 2012 VM on Azure in its own Domain, running Active Directory.
It is also the host for:
It has been configured for Remote Desktop Session access to launch published apps.
Here is an overview of the deployment: http://screencast.com/t/NC
The issue I am facing is this:
While logged inside the Azure VM that is hosting the applications, I can:
Here is a video of me doing the above while logged onto the Azure VM: http://screencast.com/t/Px
However, if I attempt to do the above steps on any other PC, we can browse to the 'RD Web Access' URL and log in to the RD Web page BUT, when I attempt to launch the application, I get the error "Remote Desktop can’t connect to the remote computer for one of these reasons..........." (screenshot)
Here is a video of me doing the above on my local machine: http://screencast.com/t/zj
I have run the RD License Diagnoser and everything seems to be OK: http://screencast.com/t/3c
Can anyone provide any suggestions on what could be the problem, and how to fix it?
It is also the host for:
RD Gateway
RD Licensing
RD Web Access
RD Connection Broker
It has been configured for Remote Desktop Session access to launch published apps.
Here is an overview of the deployment: http://screencast.com/t/NC
The issue I am facing is this:
While logged inside the Azure VM that is hosting the applications, I can:
Browse to the 'RD Web Access' URL
Log in to the RD Web page
Successfully launch the published apps
Here is a video of me doing the above while logged onto the Azure VM: http://screencast.com/t/Px
However, if I attempt to do the above steps on any other PC, we can browse to the 'RD Web Access' URL and log in to the RD Web page BUT, when I attempt to launch the application, I get the error "Remote Desktop can’t connect to the remote computer for one of these reasons..........." (screenshot)
Here is a video of me doing the above on my local machine: http://screencast.com/t/zj
I have run the RD License Diagnoser and everything seems to be OK: http://screencast.com/t/3c
Can anyone provide any suggestions on what could be the problem, and how to fix it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the suggestion, ill give that a try.
We were under the impression that you can set the self-signed certificate to be 'trusted' by saving it into the trusted root directory on the PC connecting to the VM (which we already have done) - is this not the case?