How to Configure a Persistent Static Route Print

Applies to: Windows Server 2019, Windows Server 2022, and Windows Server 2025.

A persistent route directs a specific destination network through an approved gateway after server restarts.

Prerequisites

• Administrative access and an approved change window.
• A verified backup and documented rollback plan.
• A pilot environment or low-risk target for validation.

Step-by-step procedure

1. Confirm the destination prefix, next hop, and interface index.
2. Test reachability before changing routing.
3. Create the route with an explicit metric.
4. Validate path and asymmetric-routing risk.

Commands

Get-NetIPInterface -AddressFamily IPv4
New-NetRoute -DestinationPrefix "198.51.100.0/24" -InterfaceIndex 12 -NextHop "192.0.2.1" -RouteMetric 50 -PolicyStore PersistentStore
Get-NetRoute -DestinationPrefix "198.51.100.0/24"

Verification

Test-NetConnection reaches an approved destination through the intended next hop after restart.

Rollback

Remove only the named route with Remove-NetRoute and verify the previous path returns.

Security notes

• Use least privilege and record the change.
• Review relevant event logs after implementation.
• Test before production rollout.

Related resources

Canadian Windows VPS and RDS hosting: networkmanager.info. Refer to Microsoft Windows Server documentation.