MicrosoftHappy new year everyone!
JSteskal can you elaborate on your request of having a native client? Is there an item for this at aka.ms/wacfeedback, that describes the idea a bit more?
Theo_Tran gabrielluizbh LCKho3693 JamesvandenBerg
has anyone tried the following setup with the new gateway:
I've deployed a new web certificate via AD CS to the WAC VM. Then installed the new gateway with custom options.
The cert includes the DNS FQDN in the cert and cert SAN.
public port: 443
using existing certificate (opposited to create an self-signed one), entered the cert Thumbprint
use kerberos instead of http
allow access from domain joined computers
The problem is that i cannot reach the Gateway from my management machine via Edge. I can ping, rdp the WAC VM if necessary but the webaddress does not respond example https://wacgw.corp.contoso.com
I noticed that when I am using a self signed cert, the wizard will ask for the FQDN, but when using an existing cert, there is no question about the FQDN. I could imagine that this missing part is the reason for the issue, as the wizard ends with https://localhost:443 instead of using the FQDN.
A/B testing: using the self signed certificate, the new gateway works fine, but cannot be correctly registered to Azure apparently due to the incorrect FQDN.
Thanks for your time and double checking this behaviour and potential remediation.
