When designing a topology for DirectAccess, you should consider which resources need to be available to clients. The location of those resources within the network is also vital for designing a DirectAccess topology. For example, if certain internal resources can’t work with DirectAccess, you might need to look to a different topology than if you have a native Windows Server 2012 data center.
Table 3-3 lists three scenarios for DirectAccess deployment.
TABLE 3-3 DirectAccess deployment scenarios
DirectAccess uses IPv6 for communication between clients and endpoints. Most topologies involve some type of transition technology, such as Intra-Site Automatic Tunnel Addressing Protocol (ISATAP). Applications and operating systems participating in DirectAccess also need to be IPv6-capable. For environments, applications, or operating systems limited to IPv4 only, NAT64/DNS64 service must be provided.
