This parameter is used to enable/disable health checks for DirectAccess clients. It can take one of the following values ...

This parameter is used to enable/disable health checks for DirectAccess clients. It can take one of the following values
1. Enabled
2. Disabled
Following are important behavioral aspects for health checks:
1. In order to enable health checks machine certificate authentication should already be enabled, i.e., an IPsec root certificate should be deployed.
2. On disabling health checks if neither of the following is already enabled then machine certificate authentication is automatically disabled: 
    a. Multisite, i.e. multisite is not deployed/enabled
    b User authentication is not two-factor
    c. Support for down-level clients is not enabled
3. Healthcheck is a global configuration that applies to the entire DirectAccess deployment.

This parameter is applicable only in case of multisite deployment and represents the name to be used when creating the down-level ... This parameter is only applicable in case of a multi-site deployment and represent the names of one or more down-level client ... This parameter is used to change the configuration in which DirectAccess has been deployed. It can take one of the following ... This parameter is used to configure Teredo. It can take one of the following values 1. Enabled 2. Disabled Following are ... This parameter is used to enable/disable health checks for DirectAccess clients. It can take one of the following values ... This parameter is used to specify the time duration for which store should be emptied and indicates the start date. If no ... This parameter is used to specify the time duration for which the statistics of historical connections is to be retrieved ... This parameter is used to specify the time duration for which the statistics of historical connections is to be retrieved ... This parameter is used to specify the time duration for which the statistics summary of historical connections is to be retrieved ...