If the second NIC cannot be configured for the domain profile for any reason, then the DirectAccess IPsec policy must be manually scoped to all profiles using the following Windows PowerShell commands: $gposession = Open-NetGPO -PolicyStore If the DirectAccess server has two or more network adapters (one classified in the domain profile and the other in a public/private profile), but you want to use a single NIC topology, then the recommendations are:Įnsure that the second NIC, and any additional NICs, are also classified in the domain profile. Join client computers and the DirectAccess server to the Active Directory domain.Ĭonfigure GPOs for the deployment, if required.Ĭonfigure security groups that will contain DirectAccess client computers, and any other security groups required in the deployment. TaskĬonfigure the server network settings on the DirectAccess server.Ĭonfigure routing in the corporate networkĬonfigure routing in the corporate network to make sure traffic is appropriately routed.Ĭonfigure additional firewalls, if required.Ĭonfigure DNS settings for the DirectAccess server. Before beginning the deployment steps, ensure that you have completed the planning steps described in Plan a Basic DirectAccess Deployment. This topic describes how to configure the infrastructure required for a basic DirectAccess deployment using a single DirectAccess server in a mixed IPv4 and IPv6 environment. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016
0 kommentar(er)
