After posting yesterday I spent several hours trying both the detailed procedure from Go Daddy for CRS request, download and installation, and trying the Remote Access Wizard certificate install routine. In all cases there was either a domain mis-match,
or the certicate indicated it was issued by the wrong certification authority. My decision was to shelve the idea of using my own domain and shift to one issued by Microsoft. Later I can try to change to my registered domain. One question in my post was resolved
-- I discovered using Remote Access setup to change domains.
The new Remote Access is to https://kielbaslink.homeserer.com. Remote Access from the Dashboard and from Launchpad both work. I did have to place the new certificate in the Trusted Certificates Store.
New problem:
Trying to use Remote Web Access from IE fails. When the browser "failure to connect" message appears, running diagnotics brings a result that says, in part: ".... the Remote Desktop Gateway server address requested and the certificate subject name do
not match."
Certificate Information:
In the certiciate details it says:
Issued to: kielbasalink.homeserver.com
Issued by: Go Daddy Secure Certficate Authority
Help! In the interest of moving beyond installation and setup to using WHS 2011, can someone please tell me how to resolve this certificate disparity. It seems that this should be a self-issued certicate, iniated by Microsft, that shows my domain, Kielbasalink,
as the issuer. Solving this problem will even make my wife happy! I am neglecting my chores.
A secondary question is about all of the bogus certicates that I have attempted to install. If they do not overwrite their predecessor, should the unused and useless certficates somehow be delected from the server? If the answer is "yes", can anyone tell
me what needs to done.
Thank you in advance for any help that you can offer.
Charlie
