Virtual IP and loopback not working in Windows server 2019 w/wo Xenapp 1811

[Martin Gråtrud]

Hi,

I’m trying to do this:

 

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/virtual-ip-virtual-loopback.html

 

However, having trouble getting this feature to function in the latest build of Windows server. I tried all kinds of configurations ranging from Local group policy, to registry editing.

 

The commands (with 2 sessions running):

 

ipconfig

Get-WmiObject -Namespace root\cimv2\TerminalServices –query "select * from Win32_TSVirtualIP" 

Returns:

ipconfig

Windows IP Configuration


Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : 
   Link-local IPv6 Address . . . . . : fe80::1d6a:4fc5:d03d:1cb1%6
   IPv4 Address. . . . . . . . . . . : 172.16.134.149
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   Default Gateway . . . . . . . . . : 172.16.134.1
Get-WmiObject -Namespace root\cimv2\TerminalServices -query "select * from Win32_TSVirtualIP"


__GENUS                            : 2
__CLASS                            : Win32_TSVirtualIP
__SUPERCLASS                       : CIM_Setting
__DYNASTY                          : CIM_ManagedSystemElement
__RELPATH                          : Win32_TSVirtualIP.VirtualIPActive=1
__PROPERTY_COUNT                   : 17
__DERIVATION                       : {CIM_Setting, CIM_ManagedSystemElement}
__SERVER                           : 10715V-TST002
__NAMESPACE                        : root\cimv2\TerminalServices
__PATH                             : \\10715V-TST002\root\cimv2\TerminalServices:Win32_TSVirtualIP.VirtualIPActive=1
Caption                            :
Description                        :
InstallDate                        :
Name                               :
NetworkAdapterDescription          :
NetworkAdapterDescriptionList      : {Microsoft Hyper-V Network Adapter}
NetworkAdapterMacAddress           :
NetworkAdapterMacList              : {00-15-5D-41-E5-0D}
PolicySourceNetworkAdapter         :
PolicySourceProgramList            : 0
PolicySourceVirtualIPActive        : 1
PolicySourceVirtualIPMode          : 1
ProgramList                        : {}
Status                             :
VirtualIPActive                    : 1
VirtualIPMode                      : 0
VirtualizeLoopbackAddressesEnabled : 0
PSComputerName                     : 

 

 

 

We deployed a Windows server 2016 with the exact same registry settings in the same VLAN, and the same commands (with 2 sessions running) returns the following:

ipconfig
Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : 
   Link-local IPv6 Address . . . . . : fe80::e549:aab5:8a01:54be%2
   IPv4 Address. . . . . . . . . . . : 172.16.134.148
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   IPv4 Address. . . . . . . . . . . : 172.16.134.140
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   IPv4 Address. . . . . . . . . . . : 172.16.134.152
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   Default Gateway . . . . . . . . . : 172.16.134.1

Tunnel adapter isatap.intra:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
Get-WmiObject -Namespace root\cimv2\TerminalServices -query "select * from Win32_TSVirtual IP"


__GENUS                            : 2
__CLASS                            : Win32_TSVirtualIP
__SUPERCLASS                       : CIM_Setting
__DYNASTY                          : CIM_ManagedSystemElement
__RELPATH                          : Win32_TSVirtualIP.VirtualIPActive=1
__PROPERTY_COUNT                   : 17
__DERIVATION                       : {CIM_Setting, CIM_ManagedSystemElement}
__SERVER                           : 10715V-TST001
__NAMESPACE                        : root\cimv2\TerminalServices
__PATH                             : \\10715V-TST001\root\cimv2\TerminalServices:Win32_TSVirtualIP.VirtualIPActive=1
Caption                            :
Description                        :
InstallDate                        :
Name                               :
NetworkAdapterDescription          :
NetworkAdapterDescriptionList      : {Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)}
NetworkAdapterMacAddress           :
NetworkAdapterMacList              : {00-15-5D-41-E0-5D}
PolicySourceNetworkAdapter         :
PolicySourceProgramList            : 0
PolicySourceVirtualIPActive        : 1
PolicySourceVirtualIPMode          : 1
ProgramList                        : {}
Status                             :
VirtualIPActive                    : 1
VirtualIPMode                      : 0
VirtualizeLoopbackAddressesEnabled : 0
PSComputerName                     : 

Notice the multiple ip adresses on the windows server 2016 ipconfig.

 

 

Anyone tried configuring this in Windows server 2019?

[Martin Gråtrud]

No one  so stupid trying this out?

 

We logged a case with Microsoft trying to figure it out.

[Martin Gråtrud]

Microsoft has now confirmed that this is a "Known Issue" (not a bug)..

[Martin Gråtrud]

https://support.microsoft.com/en-us/help/4501072/remote-desktop-ip-virtualization-does-not-work

[Nicholas Staab1709157778]

Martin, have you heard back from Microsoft on this? Or is it still not working with Server 2019?

[Kai-Olaf Pieth]

Does anyone have an update? Will this be fixed for Windows Server 2019 or is it fixed already?

[Wing Ling Lui]

Microsoft has update the following article

https://docs.microsoft.com/en-us/troubleshoot/windows-server/remote/remote-desktop-ip-virtualization

but it still not work. 

May your guys can try and let me know