Applies to: Windows Server 2019, Windows Server 2022 and Windows Server 2025, subject to the workload and edition requirements below.
Understand what NPS registration enables
Network Policy Server provides RADIUS authentication, authorization and accounting for supported network-access devices and VPN gateways. It can also act as a RADIUS proxy. Installing it does not automatically authorize users or turn every packet sender into a trusted RADIUS client. Those behaviours depend on registered clients, connection-request policy, network policy and the chosen authentication methods.
When NPS authorizes AD users, registering the server in Active Directory gives it the directory access needed to read relevant account dial-in properties. Registration adds the NPS computer account to the RAS and IAS Servers group in the appropriate domain. This is distinct from adding a VPN gateway as a RADIUS client inside NPS. Mixing those two registration concepts is a common reason a deployment looks complete in one console but cannot process a real login.
Prepare a domain member and secure network boundary
Use a supported Windows Server, current security updates and reliable domain DNS and time synchronization. Decide whether this NPS will authenticate locally, proxy requests or support both through carefully separated policies. Plan availability: a single NPS can become the shared failure point for Wi-Fi, VPN and switch access even when every individual access device is healthy.
Use administrative and delegated AD rights appropriate to the installation and group-membership change. Do not add broad domain privileges to the service merely to avoid a registration error. If users reside in other domains, evaluate registration and trust requirements for those domains explicitly. A local-domain membership does not automatically supply every permission needed across a forest or external trust.
Define the exact network devices that may send RADIUS traffic, their source addresses as seen by NPS, authentication and accounting ports, shared-secret ownership and log retention. Keep RADIUS on protected networks or an approved secured path. Do not expose UDP RADIUS broadly to the Internet or rely on the shared secret as if it encrypted all request contents.
Install the NPS role service
Open elevated Windows PowerShell on the intended NPS server and inspect feature state. Install the NPAS role service with management tools and review the returned installation result. This prepares the IAS service and the Network Policy Server console; it does not create a production network policy for your users.
Get-WindowsFeature NPAS
$result = Install-WindowsFeature -Name NPAS -IncludeManagementTools
$result | Format-List Success,RestartNeeded,ExitCode,FeatureResult
Get-Service -Name IAS
Get-NetConnectionProfilePerform a requested restart during the maintenance window. Check that the intended server is domain joined and has the correct active network profile. A domain member appearing on a Public profile may have a domain-location or DNS issue worth solving before it becomes an authentication dependency. Retain the installation result and baseline policy configuration as part of the change record.
Register the server in Active Directory
Open Network Policy Server, right-click the NPS local-server root and select Register server in Active Directory. Review the confirmation explaining the directory permissions. Perform this with an account authorized to make the required group-membership change. For another domain, follow the documented registration process for that domain rather than assuming the local-console operation covers it.
# On an administration system with the ActiveDirectory module:
Get-ADGroupMember -Identity 'RAS and IAS Servers' |
Select-Object Name,ObjectClass,SamAccountName
# Inspect the NPS computer identity separately:
Get-ADComputer -Identity 'NPS01' -Properties DNSHostName |
Select-Object Name,DNSHostName,EnabledConfirm that the intended NPS computer account appears, allowing for AD replication and token-refresh effects where applicable. Do not confuse the logged-on administrator account with the NPS computer account. If registration is denied, inspect delegated permissions, target domain and directory connectivity; repeatedly trying with unrelated privileged accounts makes the ownership problem harder to audit. Document which domains have been registered.
Add only known RADIUS clients and narrow firewall access
In RADIUS Clients and Servers, add the approved VPN gateway, access point controller or switch as a RADIUS client. Enter a descriptive name, the actual source IP or resolvable address, vendor settings where needed, and a strong shared secret delivered through the approved secure process. The RADIUS client is the network-access device, not the employee laptop that will authenticate through it.
Configure the same peer address, ports and secret on that access device. NPS commonly uses UDP 1812 for authentication and 1813 for accounting and can listen on legacy ports too. Review the actual listener and firewall rules, remove unnecessary exposure and scope the active ports to known peers. A TCP Test-NetConnection result does not prove a UDP RADIUS request reached NPS.
Apply current RADIUS hardening guidance, including Message-Authenticator handling and the relevant update requirements. Pilot compatibility with each client or proxy implementation rather than assuming an old appliance implements the attribute correctly. If enforcement drops packets, identify and update the incompatible peer; do not broadly disable integrity protection to restore every request without investigation.
Create a pilot policy with a clear match and method
Create a small approved AD pilot group and a network policy limited to the intended access scenario. Conditions should identify the relevant group and access type, and constraints should allow only the approved authentication method. For EAP-TLS or PEAP, select a suitable NPS server certificate and ensure clients validate the expected name and chain. Certificate-based designs also need correct client certificates and mapping.
Review connection-request policies first: they determine whether requests are processed locally or forwarded. Then review network-policy order, because an earlier matching policy can override the assumptions of a later pilot policy. Do not enable PAP, broad password methods or all-user access merely to obtain a success event. A policy match is meaningful only if it enforces the intended identity and security requirements.
Configure accounting and authentication logs with an approved retention and access policy. Decide how the service behaves when logging storage is full or accounting fails, and monitor that condition. Logs can include user identities, device details and access history, so keep them protected while ensuring operators can diagnose failures.
For AD-backed certificate authentication, verify strong certificate-to-account mapping under the current domain-controller enforcement requirements. A UPN that merely looks correct is not sufficient evidence of a strong mapping. Current updates no longer support the old compatibility-mode registry escape described in older deployment notes; correct certificate issuance or an approved strong explicit mapping and inspect domain-controller authentication events.
Verify a real grant and a real denial
Use the actual access device and a representative external or network client to generate a login request. A permitted pilot account should be granted through the intended policy. An account outside the group, an invalid credential or an unsuitable certificate should be denied as designed. Confirm accounting arrival if it is part of the service requirement.
Get-Service IAS
# Where NPS success/failure auditing is enabled:
Get-WinEvent -FilterHashtable @{LogName='Security';Id=6272,6273;StartTime=(Get-Date).AddHours(-1)} -MaxEvents 30
Get-WinEvent -FilterHashtable @{LogName='System';ProviderName='NPS';StartTime=(Get-Date).AddHours(-1)} -MaxEvents 30Record the selected policy, authentication method, device source and reason code. A running IAS service or AD group membership proves only one prerequisite. If no NPS event appears, check whether auditing is enabled and whether the request reaches the expected listener before concluding that the user’s account is wrong. Avoid repeated production login attempts that can trigger account lockout.
Troubleshoot and retire the service deliberately
For unknown-client or silently dropped traffic, check the source address after NAT, shared-secret agreement, UDP ports and Message-Authenticator compatibility. For a processed denial, inspect the NPS reason and selected policy, then check group membership, dial-in settings, certificate validation or the chosen EAP method. For cross-domain failures, verify trust, DNS, registration and directory access in the account domain.
Rollback a pilot by removing or disabling only its policy and client entries while preserving the baseline and logs. Unregister or remove the NPS computer’s directory membership only when no active service depends on it, and migrate RADIUS clients to another verified server before uninstalling. Document policy order, client inventory, secrets lifecycle, certificate renewal, logging and backup. A maintainable NPS deployment makes both acceptance and rejection understandable to the operator who must investigate the next failed login.
Related guidance and official references
Prepare RRAS; Configure IKEv2 remote access; Configure advanced auditing; Forward Windows events.