# Follow the NPS dependencies after an address or name change

> What must be rechecked when an NPS server or proxy is renamed or readdressed?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-222-follow-the-nps-dependencies-after-an-address-or-name-change/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:29+00:00
- Modified: 2026-09-08T18:29:34+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

What must be rechecked when an NPS server or proxy is renamed or readdressed?

## Potentially affected

Administrators changing the name or IP address of NPS RADIUS servers and proxies.

## DSE recommendation

Prepare a dependency checklist with the old and new endpoint, the owner of each access device or proxy, and the corresponding update step.

## Article

## Source facts

Microsoft directs administrators to verify that an address change preserves authentication, authorization, and accounting paths. For a multihomed proxy bound to a specific address, the NPS port settings must be updated with the new address. After a name change, remote RADIUS server groups configured with computer names must be updated. When certificate-based authentication is deployed, renaming NPS invalidates its server certificate and requires obtaining a new certificate. The page also calls for checking SQL logging connectivity after an address change. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-verify).

## Applicability

Inventory consumers of the old server name and address before scheduling the change. Distinguish direct-IP device settings from name-based remote-server-group entries. Include accounting and logging dependencies rather than limiting acceptance to a successful sign-in.

## DSE recommendation

Prepare a dependency checklist with the old and new endpoint, the owner of each access device or proxy, and the corresponding update step. Preserve current bindings and remote-server-group settings. Ask the logging owner to identify the expected post-change records and a way to detect a silent loss. Coordinate the change window so the related endpoints are not updated independently without a shared plan.

## Verification

Trace an authorized test request through each relevant device or proxy after the change. Verify the selected NPS endpoint and the expected accounting or SQL logging result. Check that configuration no longer depends on the retired name or address. Record remaining exceptions and investigate each before closing the migration.

## Official references

[Microsoft Learn: Verify Configuration After NPS Changes](https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-verify). Source reviewed September 8, 2026.

## Primary reference

- Name: Verify Configuration After NPS Changes
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-verify
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Follow the NPS dependencies after an address or name change,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-222-follow-the-nps-dependencies-after-an-address-or-name-change/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.