in "rds with existing AD" template, remove Public IP from RDGW VM and replace RDS deployment FQDN with DNS name of RDGW load balancer's public IP.

_From @cnicholson on January 30, 2017 19:52_

1. This reduces attack surface (there are currently 2 open ports to the RDGW VM)
2. is consistent with the HA GW template which will need to set the FQDN to the LB's DNS name

deployment FQDN is the one that is set in "Deployment Properties" dialog and is what is used in the published RDP file to connect to the RDGW.

Also noticed that the SSL certificate on the RDGW VM has the wrong name. It is currently the name of the public IP address connected directly to the VM rather than the name on the RDGWLB public IP.

_Copied from original issue: mmarch/rds-templates#23_

Start with the "rds with existing AD" template and inspect how the RDGW VM, RDGW load balancer public IP, deployment FQDN, and SSL certificate name are configured. Done means the VM no longer has a public IP, the deployment and certificate names use the load balancer's public DNS name, and the template remains deployable.

Written by the indexing model from the issue text.