大网数据广告活动
远程桌面与会话

Prerequisites for Deploying DirectAccess

· 52CE 我爱测

This topic provides prerequisites for DirectAccess deployment in Windows Server 2016.

The following table lists the prerequisites necessary for using the configuration wizards to deploy DirectAccess.

Scenario Prerequisites
Deploy a Single DirectAccess Server Using the Getting Started Wizard - Windows Firewall must be enabled on all profiles- Only supported for clients running Windows 10®, Windows® 8, and Windows® 8.1 Enterprise.- A public key infrastructure is not required.- Not supported for deploying two-factor authentication. Domain credentials are required for authentication.- Automatically deploys DirectAccess to all mobile computers in the current domain.- Traffic to the Internet does not go through DirectAccess. Force tunnel configuration is not supported.- DirectAccess server is the network location server.- Network Access Protection (NAP) is not supported.- Changing policies by using a feature other than the DirectAccess management console or Windows PowerShell cmdlets is not supported.- For a multisite configuration, now or in the future, first follow the guidance in Deploy a Single DirectAccess Server with Advanced Settings.
Deploy a Single DirectAccess Server with Advanced Settings - A public key infrastructure must be deployed. For more information, see Test Lab Guide Mini-Module: Basic PKI for Windows Server 2012.- Windows Firewall must be enabled on all profiles.The following server operating systems support DirectAccess.- You can deploy all versions of Windows Server 2016 as a DirectAccess client or a DirectAccess server.- You can deploy all versions of Windows Server 2012 R2 as a DirectAccess client or a DirectAccess server.- You can deploy all versions of Windows Server 2012 as a DirectAccess client or a DirectAccess server.- You can deploy all versions of Windows Server 2008 R2 as a DirectAccess client or a DirectAccess server.The following client operating systems support DirectAccess.- Windows 10® Enterprise- Windows 10® Enterprise 2015 Long Term Servicing Branch (LTSB)- Windows® 8 and 8.1 Enterprise- Windows® 7 Ultimate- Windows® 7 Enterprise- Force tunnel configuration is not supported with KerbProxy authentication.- Changing policies by using a feature other than the DirectAccess management console or Windows PowerShell cmdlets is not supported.- Separating NAT64/DNS64 and IPHTTPS server roles on another server is not supported.

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 08/07/2020
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。