# Qualify RDS IP virtualization for an application compatibility issue

> When should an RDS application be tested with per-session or per-program IP virtualization?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-209-qualify-rds-ip-virtualization-for-an-application-compatibility-issue/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:42+00:00
- Modified: 2026-09-08T18:29:33+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

When should an RDS application be tested with per-session or per-program IP virtualization?

## Potentially affected

Administrators investigating IP-address-related compatibility for Winsock applications on on-premises RDS session hosts.

## DSE recommendation

Choose a representative application and a small set of concurrent test users.

## Article

## Source facts

Microsoft documents per-session and per-program IP virtualization for Winsock applications on Remote Desktop session hosts. The cited IP-virtualization procedure applies only to on-premises environments. The feature assigns individual addresses to sessions to address compatibility problems when multiple users otherwise share one address. The documented configuration supports a single selected network adapter, even when more than one adapter is enabled. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/internet-protocol-virtualization).

## Applicability

Establish the actual application symptom and confirm that the vendor’s requirements involve the network identity of sessions or programs. Review the session-host version and selected adapter against the source. Keep this compatibility assessment separate from granting users additional network access.

## DSE recommendation

Choose a representative application and a small set of concurrent test users. Record the original network and application behavior, the intended virtualization scope, and the chosen adapter. Ask the application and network owners to agree on address allocation and expected observations. Preserve the original configuration and avoid applying a host-wide compatibility change before the symptom is reproducible.

## Verification

Run the affected transaction concurrently in the approved pilot sessions. Compare observed addresses, application behavior, and any failure messages with the baseline. Test an unrelated application to detect unintended effects. Retain the exact scope and adapter configuration with the results, and expand only after the original compatibility problem is demonstrably resolved.

## Official references

[Microsoft Learn: Remote Desktop IP virtualization in Windows Server](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/internet-protocol-virtualization). Source reviewed September 8, 2026.

## Primary reference

- Name: Remote Desktop IP virtualization in Windows Server
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/internet-protocol-virtualization
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Qualify RDS IP virtualization for an application compatibility issue,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-209-qualify-rds-ip-virtualization-for-an-application-compatibility-issue/
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.