Summary
Windows Server 2008 R2 introduced the ability to assign IP addresses to individual sessions on a Per-Session or Per-Application basis. These IP Addresses can be assigned either via a network DHCP server or from a Static DHCP Pool.When a user connects to a Windows Server 2008 R2 Session Host they may have a Startup (Initial) program which requires the assignment of an IP address for proper function of the application.
In limited instances, delays in DHCP IP address assignment may cause session process start to fail, affecting the session start process.
In limited instances, delays in DHCP IP address assignment may cause session process start to fail, affecting the session start process.
More Information
Remote Desktop IP Virtualization allows IP addresses to be assigned to remote desktop connections on a per-session or per-program basis. Remote Desktop IP Virtualization is configured on the RD IP Virtualization tab of the RD Session Host Configuration tool.
If you assign IP addresses for multiple programs, they will share a session IP address. If you have more than one network adapter on the computer, you must also choose one network adapter for Remote Desktop IP Virtualization.
Normally each Remote Desktop Session Host server has a single IP address, which is shared among all the Remote Desktop Services (RDS) users. This makes the RDS experience different from regular desktops and breaks some application compatibility. RDS partners and competitors already provide the ability to assign an IP-Address to an application.
The Remote Desktop IP Virtualization service depends on a valid DHCP Server being active on the subnet. A valid pool of static IP addresses can also be configured manually. In some cases this was shown to have a much lower failure rate than standard DHCP services.
Testing is highly recommended for any application which will be run on a Remote Desktop Session Host with Remote Desktop IP Virtualization turned on, to determine if the environment will experience session startup failures due to Remote Desktop IP Virtualization delays.
ADDITIONAL INFORMATION:
Deploying Remote Desktop IP Virtualization Step-by-Step Guide
http://technet.microsoft.com/en-us/library/ee308290(WS.10).aspx
Using Static IP Addresses for Remote Desktop IP Virtualization
http://technet.microsoft.com/en-us/library/ee382306(WS.10).aspx
If you assign IP addresses for multiple programs, they will share a session IP address. If you have more than one network adapter on the computer, you must also choose one network adapter for Remote Desktop IP Virtualization.
Normally each Remote Desktop Session Host server has a single IP address, which is shared among all the Remote Desktop Services (RDS) users. This makes the RDS experience different from regular desktops and breaks some application compatibility. RDS partners and competitors already provide the ability to assign an IP-Address to an application.
The Remote Desktop IP Virtualization service depends on a valid DHCP Server being active on the subnet. A valid pool of static IP addresses can also be configured manually. In some cases this was shown to have a much lower failure rate than standard DHCP services.
Testing is highly recommended for any application which will be run on a Remote Desktop Session Host with Remote Desktop IP Virtualization turned on, to determine if the environment will experience session startup failures due to Remote Desktop IP Virtualization delays.
Workaround:Configure RDS Session Initial Program (Startup program) to run with a startup script (logon script) and introduce a 1-3 second delay into the execution of any process which has a requirement of a separate IP Address for the program to start and run.
ADDITIONAL INFORMATION:
Deploying Remote Desktop IP Virtualization Step-by-Step Guide
http://technet.microsoft.com/en-us/library/ee308290(WS.10).aspx
Using Static IP Addresses for Remote Desktop IP Virtualization
http://technet.microsoft.com/en-us/library/ee382306(WS.10).aspx