Best Practices Analyzer for Remote Access: Configuration (Section 2)
Applies To: Windows Server 2012 R2
The topics in this section can help you bring Remote Access running on Windows Server 2012 R2 into compliance with configuration best practices. Content in this section is most valuable when you have completed a Best Practices Analyzer scan of Remote Access and you want information about how to interpret and resolve scan results that identify areas of Remote Access that are noncompliant with configuration best practices.
Best Practices Analyzer and configuration rules
The Best Practices Analyzer applies configuration rules to identify settings that might require modification for Remote Access to perform optimally. Configuration rules can help prevent setting conflicts that can result in error messages or prevent Remote Access from carrying out its prescribed duties in an enterprise.
Topics in this section
This section includes the following topics.
RRAS: A static pool should be configured for IPv4 address assignment to the VPN client
RRAS: The static pool IPv4 addresses must be valid unicast IPv4 addresses
RRAS: The default route (IPv4 or IPv6) should not be advertised to the peers
RRAS: The default route (IPv4 or IPv6) should not be accepted from the peers
RRAS: The BGP peer IP address should not be assigned to a local network interface
RRAS: A local global IPv6 address must be configured on the BGP Router
RRAS: Multiple routes with different Next-Hop values and the same Destination prefix are configured
RRAS: The BGP peer's Hold-Timer should not be set to the value 0
RRAS: BGP peer's Hold-Timer should not be set to a very low value
RRAS: All the ingress route advertisements should not be dropped because of a routing policy
RRAS: All the egress route advertisements should not be dropped because of a routing policy
RRAS: BGP peers should not be configured for manual (passive) peering mode
RRAS: For BGP Peering over IPv6 addresses, IPv4 routes should not be configured for advertisement