Due to the recent *RemoteWebAccess.com fiasco, I recently changed over to a new certificate (using the "Get a free Let's Encrypt SSL Certificate...) Dynamic DNS, etc.. I believe I followed the process and wizards correctly to import and apply the new certificate for my IIS and VPN. I have removed the old *remotewebaccess.com certificates. I uninstalled and reinstalled the Connector on all Clients. I noticed that at time of reinstall of the Connector, the Server did NOT create a new VPN connection on each of the Clients. Instead I created a new VPN connection on each Client. Everything with one small "housekeeping exception" appears to be working perfectly..... despite deleting the old *remotewebaccess.com VPN connection from the Clients, It keeps reappearing on the clients when they connect to the Server network. The connection is no longer valid but I can't figure-out why or where from the Server keeps issuing the VPN Connection... Any suggestions? Thanks!!!
Did you release the old domain from within the Access Anywhere wizard from the Essentials Dashboard?
Yes. In fact the wizard even now shows that "the domain is setup manually." After much digging I found the problem. For whatever the reason/problem, the two registry keys: "Connection Name" & "Internet Address" on the server at: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\RemoteAccess\VPNSettings, seem to responsible. They were still showing the name and address of the removed *Remotewebacccess domain. I updated the two keys with the new name and address and all is good now. When clients connect the Server will add now add the proper VPN profile to the client IF it is missing.
Thanks Joe! Good catch :)