Skip to content

How to Install the Remote Access and RRAS Roles on Windows Server Print

  • 0

Applies to: Windows Server 2019, Windows Server 2022 and Windows Server 2025, subject to the workload and edition requirements below.

Choose the Remote Access role services you actually need

Windows Server Remote Access includes role services for VPN, routing and Web Application Proxy. Routing and Remote Access Service, usually called RRAS, supplies the VPN and router functions used in many traditional Windows deployments. Installing a role service makes its components available; it does not complete a secure VPN, publish a route or authorize users. Keep installation separate from the deliberate network and authentication configuration that follows.

This guide prepares a Windows Server for a defined RRAS deployment. It explains routing-only and VPN paths without pretending they are interchangeable. DirectAccess is a different deployment model, and a Remote Access installation command with DirectAccess parameters can change policy and dependencies that a simple RRAS router does not need. Select the intended purpose before running configuration commands, especially on a server that already provides network services.

Confirm platform support and network ownership

Use a supported physical server or virtualization platform and check the current platform support statement. Microsoft explicitly does not support deploying the Windows Server Remote Access role for VPN, DirectAccess or other Remote Access features inside an Azure VM. That limitation should not be generalized into a claim that every VM or every hosting platform is unsupported; RRAS can be deployed on supported Hyper-V VMs, subject to the network design.

On any hosted server, verify that the provider allows the intended routing, source addresses, protocols and forwarding behaviour. A role can install successfully while an upstream anti-spoofing or NAT policy prevents the design from working. Obtain a clear internal and external interface map, approved routes and firewall scope. Keep a console path available because routing changes can break the session used to administer the server.

A router or VPN gateway occupies a sensitive boundary. Avoid placing unrelated public applications or domain-controller duties on it. Decide who patches it, who owns its certificate and authentication policy, and how access is monitored. Availability requirements may require more than one gateway and a separate client or routing failover design.

Inventory addressing, routes and existing configuration

Before installation, record adapter identities, addresses, DNS servers, routes and active connection profiles. Confirm there is no overlapping internal, VPN-client or remote-site address range. Decide where the default gateway belongs; putting independent defaults on internal and external interfaces can create asymmetric traffic. DNS registration and domain communication on a multihomed server also need explicit review.

Get-NetAdapter | Select-Object Name,InterfaceDescription,ifIndex,MacAddress,Status
Get-NetIPConfiguration
Get-NetRoute -AddressFamily IPv4
Get-NetConnectionProfile
Get-WindowsFeature RemoteAccess,DirectAccess-VPN,Routing
Get-Service RemoteAccess -ErrorAction SilentlyContinue

If Remote Access is already configured, export and document it before changing role services. Do not reinitialize a production gateway simply because a tutorial starts with a blank server. Capture the existing VPN protocols, authentication providers, address pools, demand-dial interfaces and NAT mappings through the appropriate management tools. Retain that evidence outside the gateway so it remains available during an outage.

Install routing components or VPN components deliberately

Use elevated Windows PowerShell and choose the role services that match the approved function. For routing-only preparation, install Routing with management tools. For a VPN server, install DirectAccess-VPN; the role-service name covers the VPN components and is not itself an instruction to deploy DirectAccess. A combined design may need both.

# Routing-only component installation:
Install-WindowsFeature -Name Routing -IncludeManagementTools
# For an approved VPN deployment instead, install its components:
# Install-WindowsFeature -Name DirectAccess-VPN -IncludeManagementTools
Get-WindowsFeature RemoteAccess,DirectAccess-VPN,Routing

Review the result for Success and RestartNeeded, and perform any required reboot in the agreed maintenance window. The commented VPN line is an alternative, not a requirement to run every command. Do not install Web Application Proxy or other boundary services unless the architecture calls for them. Management tools can also be installed on an approved administration server for remote operation.

Initialize the intended service mode

After the components are installed, initialize only the selected mode. A routing-only server can use Install-RemoteAccess -VpnType RoutingOnly. Alternatively, use the Routing and Remote Access console to configure custom routing. A VPN server uses the VPN-specific workflow and requires protocol, certificate, authentication and client-address decisions that are intentionally not guessed here.

# Only for the routing-only design:
Install-RemoteAccess -VpnType RoutingOnly
Get-Service -Name RemoteAccess
Get-RemoteAccess

Do not run a second installation mode against an existing deployment without reviewing how configuration is reused. The RemoteAccess cmdlet family includes DirectAccess-specific behaviour, so ensure the parameters match RRAS rather than copying an example with DAInstallType or client-GPO settings. A Running service proves the process started; it does not prove packet forwarding, NAT or a VPN login works. Complete the corresponding task-specific configuration next.

Apply release-specific VPN security consciously

If this server will accept VPN clients, choose supported modern protocols and configure certificates and authentication before exposing the service. Windows Server 2025 changes defaults for new RRAS setups so PPTP and L2TP connections are not accepted by default. Earlier releases and existing configurations retain their own behaviour. An upgrade is therefore not evidence that an old weak protocol was automatically removed.

Inventory and explicitly disable protocols that the approved design does not use. IKEv2 and SSTP have different certificate, transport and client requirements; select them based on the actual deployment. Define authorization through a narrow group and appropriate NPS policy rather than allowing every domain user. If using external RADIUS, protect the shared secret and restrict traffic to the known RADIUS peers. Installing RRAS does not automatically provide MFA or a complete remote-access authorization policy.

Verify installation separately from end-to-end operation

Confirm the chosen features are installed and the RemoteAccess service state matches the configured mode. Review System and Remote Access events after startup. Then verify the actual function using a representative internal client, remote VPN client or remote-site gateway, depending on the deployment. A local ping from the router cannot establish that a client’s return path works.

Get-WindowsFeature RemoteAccess,DirectAccess-VPN,Routing
Get-Service RemoteAccess
Get-NetRoute -AddressFamily IPv4
Get-WinEvent -FilterHashtable @{LogName='System';StartTime=(Get-Date).AddHours(-1)} -MaxEvents 60

For routing, confirm traffic crosses between the intended subnets and unauthorized paths stay blocked. For VPN, test certificate validation, accepted and rejected users, assigned addresses, DNS and resource access. For NAT, check translated outbound traffic and absence of unintended inbound mappings. Record source, destination and expected result so future troubleshooting can distinguish a feature-installation problem from a policy or topology problem.

Troubleshoot and roll back without losing the network baseline

For installation failures, examine feature and servicing errors and verify the source matches the server release. For service-start failures, inspect dependencies and the exact RRAS event. For failed forwarding or VPN access, work through addressing, routes, firewall, upstream policies and authentication in order. Do not enable every protocol or disable the firewall merely to see whether connectivity improves.

If rollback is required, remove or disable the newly configured function during a maintenance window and restore the recorded routes, interface settings and policy. Do not uninstall a role used by another RRAS function or an active gateway without migrating its users and traffic. Preserve logs and configuration before cleanup. The handover should identify mode, interfaces, protocols, authorization owner, certificates, routing dependencies and recovery access, so the next operational change starts from evidence rather than rediscovering the boundary.

Related guidance and official references

Configure RRAS NAT; Configure IKEv2 remote access; Install and register NPS.


Was this answer helpful?

« Back