Windows Server Essentials 2016 Remote Web Access not working

I finally got some free time and decided to try and set up Anywhere Access inside Windows Server Essentials 2016. Didn't go good. Every time I go into the Dashboard and try and configure it I get a error message that "There is an issue with your Remote Desktop Services settings that cannot be automatically repaired. Please contact Product Support".

   I decided to take a look at Roles and noticed that only one role under Remote Desktop Services was installed (Remote Desktop Gateway) so I installed the Remote Desktop Web Access role. Still no luck. Do I need to install and other Remote Desktop roles?

  The only other error I am getting is that ports 80 and 443 are blocked which they aren't because the Windows Firewall is turned Off.

Any ideas?
LVL 15
LockDown32OwnerAsked:
Who is Participating?
 
LockDown32Connect With a Mentor OwnerAuthor Commented:
The issue actually turned out to be security on the C:\Windows\Temp folder. How it got changed after running fine for 6 months is beyond me. I have had the exact same thing happen in Windows 10. Leave it to Microsoft......
0
 
Hypercat (Deb)Commented:
I'm not experienced with Server Essentials, but on a standard server in order to configure remote desktop you have to install the following services:  RD Gateway, RD Session Host, RD Connection Broker and RD Licensing, as well as RD Web Access if you want to use Remote WebApps in addition to (or instead of) Remote Desktop.
0
 
LockDown32OwnerAuthor Commented:
Yep. Those are installed. I either get "Forbidden. Access Denied" or the IIS page. Something really wrong with IIS.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Hypercat (Deb)Commented:
Are your RD website virtual directories set to use SSL and do you have an SSL certificate appropriately configured and applied to the website and the various remote desktop components? In the standard RDS configuration it's strongly recommended that you use a public certificate authority (like GoDaddy, Verisign, etc.) rather than a self-signed certificate. Which are you using?

And what URL are you using?  Normally the URL would be something like: https://server.domain.com/rdweb.
0
 
LockDown32OwnerAuthor Commented:
Right now the SSL Cert is kind of moot. Even the url you suggested results in the same error as others I have tired. See the attached screen shot....
Capture.PNG
0
 
Hypercat (Deb)Commented:
Did you follow these instructions (or similar ones) on setting up the remote web access on Essentials Server?

https://docs.microsoft.com/en-us/windows-server-essentials/manage/manage-remote-web-access-in-windows-server-essentials

These instructions are quite different from the steps to set up a standard RDS server, and I'm sure (like the predecessor Small Business Server versions) that the Essentials experience uses built-in procedures to create the remote web site in IIS that are probably different from the standard setup. If you didn't use this "wizard" automated setup method, then there's undoubtedly something that was missed in the configuration during the installation of the RDS services and web configuration.
0
 
LockDown32OwnerAuthor Commented:
It was the definitive solution
0
 
LockDown32OwnerAuthor Commented:
It worked
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.