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 configure Teredo. It can take one of the following values
1. Enabled
2. Disabled
Following are the behavioral aspects of Teredo State
1. Teredo can be enabled only if two consecutive IP addresses are present on the Internet interface of the server. 
2. In a load balancing scenario 
    a. If a 3rd party load balancer is being used and Teredo has to be enabled then the load balancer should have two consecutive IP addresses
    b. If Teredo needs to be enabled in a cluster then the cluster should be destroyed first and two consecutive IPs should be configured on the DirectAccess server
3. The Teredo configuration is applicable per-computer or per-site (in the case of multisite deployments)

This parameter has relevance only when the Dialect parameter exists, and its value is specified as Association. Otherwise ... 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 ...