Part I of this blog post series describes what Remote Desktop IP Virtualization is all about, illustrates the scenarios where it can add value, lists the requirements for configuring a server in Remote Desktop IP Virtualization mode and details the steps involved in configuring per-program and per-session Remote Desktop IP Virtualization through RD Session Host Configuration MMC snap-in.
This post explains how to do all this automatically on managed computers by using Group Policy (GP) objects.
If Remote Desktop IP Virtualization is enabled but virtual IP addresses are not available (i.e. DHCP server runs out of virtual IP addresses), the default behavior is for the session to fall back to using the IP address of the Remote Desktop Session Host server. If you wish to disallow this behavior and force unique IP addresses to be used for individual sessions or specified applications, you can configure this through the “Do not use Remote Desktop Session Host server IP address when virtual IP address is not available” policy setting.
So, if virtual IP addresses are not available, with this policy enabled:
At no time is a session force disconnected or force logged off.
To configure the above policy setting, double click or right click “Do not use Remote Desktop Session Host server IP address when virtual IP address is not available” and select ‘Edit’ option to bring up GP dialog.
a. Select “Enabled” to enable this GP i.e. the IP address of the RD Session Host server is not used if a virtual IP is not available.
b. Select “Disabled” to disable this GP i.e. the IP address of the RD Session Host server is used if a virtual IP is not available.
c. Optional: Enter any comment for the setting in the comment field.
d. Click OK or Apply to accept the settings.
In addition to RD Session Host Configuration MMC snap-in and GPO, Remote Desktop IP Virtualization can also be configured through RDS Provider for Windows PowerShell and WMI.
Part III (coming soon) of this blog post series has information on configuring RD IP virtualization through RDS Provider for Windows PowerShell.
The requirement for specifying the NIC using the server IP address in Classless Inter-Domain Routing notation means that you can't use ONE AD group policy to manage VIPA for your estate, you need to either define it in local group policy on EVERY server or create a group policy for EVERY server?
Surely you guys have a way of managing this from ONE AD group policy???