Specifies the certificate that will be used to secure remote clients connectivity over HTTPS (in case of DirectAccess) or ...

Specifies the certificate that will be used to secure remote clients connectivity over HTTPS (in case of DirectAccess) or SSTP (in case of VPN)
1. SSL certificate changes are allowed only within the bounds of the current value of the ConnectTo address (configurable through the set-daserver cmdlet), i.e., the subject name of the new certificate should always match ConnectTo. All other certificates are rejected and the cmdlet errors out, even if all other criteria for an SSL certificate are satisfied. This behavior is applicable irrespective of whether NAT is deployed or not and whether the server has a single network adapter or two network adapters
2. In a network load balancing scenario the changes take effect on all nodes. Hence, the specified certificate is required to be present on all nodes in the cluster
       a. If the certificate is not found on one or more nodes then the cmdlet errors out
       b. If one or more nodes are down when changing the certificate then the change applies only on the nodes that are up. But the DirectAccess server Group policy object is updated to ensure that when these machines come up load balancing is in stopped state on them due to a certificate mismatch. For the certificate change to take effect, the admin needs to install a similar certificate on them and re-run this cmdlet