We have some VMs that have 2 IPs, and are managed by vWorkspace. They weren't created by vWorkspace, just imported into the console.
They have 2 IPs, a 172.x, and a 10.x. The 10.x IP is one we need to use, but vWorkspace seems to try and connect to the 172.x address, and then fails
You can see in the screenshot. For some reason APDDWIAP122 uses the correct IP, but the others don't. We can't figure out what the difference is between 122 and the other VMs.
A new configuration option is available to support virtual machines that have multiple IP addresses. Typically this configuration is not required, but can be useful in some cases (e.g. VM has multiple network adaptors, user starts a client VPN connection, a USB video camera adds a network adaptor when plugged in). This new configuration option allows an administrator to specify the IP address range vWorkspace should use for communication with the VM. This configuration would usually be performed on the template VM and would include the entire range of IP addresses that may be assigned to VMs created from the template VM. This option can be configured via a registry key on the VDI machine as described below.
On 32-bit computers, navigate to HKLM\Software\Provision Networks\Common
On 64-bit computers, navigate to HKLM\Software\Wow6432Node\Provision Networks\Common
Create the following keys:
IPRange - REG_SZ - Enter one of the IP addresses in the IP address range that should be used (e.g.10.1.1.1) IPMask - REG_SZ - Enter the sub-net mask for the IP address range that should be used (e.g. 255.255.255.0)
The example configuration above results in an IP address range of 10.1.1.1-10.1.1.255. For a computer multiple IP addresses, if one of the IP address is in the configured range vWorkspace will use that IP address for management and remote desktop communication. If none of the IP addresses are in the configured IP address range, the first IP address based on binding order will be used.
Note: Dell Software does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
I suspect this is more a DNS issue than a vWorkspace issue but let's see what we can find out.
When you import VMs into the console, the connection broker(s) will use the DNS-resolved IP address of the VMs and will attempt to initialise (copy data collector service binary to VM, run a remote command to start the data collector service and brand the VM with the correct registry values). The data collector service then reads the registry values and starts sending heartbeat packets to the connection broker.
So if initialisation was successful, the LLMServerList value should have your connection broker names.
For x64 VMs, check the LLMServerList value under HKLM\SOftware\Wow6432Node\Provision Networks\Common. For x86 VMs, check the LLMServerList value under HKLM\Software\Provision Networks\Common.
If the name(s) are there, the next step is that the data collector service on the VM needs to be able to resolve the IP address of one of the connection brokers. I would guess the connection broker is on the 10.202.4. network.
Vms on the 172.21.202 network (DHCP?) would need to be able to do a DNS lookup on the connection broker name, and depending on the IP address, would then use the appropriate network interface to talk to that network. If the data collector service can't resolve the connection broker IP address, then the VM will appear to be offline (not sending heartbeats to connection broker).
If you log on to the console of one of the offline VMs, use nslookup to look up the connection broker name. If it doesn't resolve, you've found your problem.
However I am curious as to why one of the VMs worked. If they've got 2 NICs, is it possible you've got DHCP enabled on both networks? If they have different DNS servers and default gateways, then I could speculate a degree of randomization in the end result.
If the IP address of the connection broker is resolved, then the VM would be sending heartbeats with a 10.202.4 IP address and the connection broker would update accordingly. If not, the VM would be offline.
There is no Provision Networks entry in the registry at all, so it doesn't even get to this stage.
We can see a bunch of entries in our firewall logs where the CB is trying to access the VM on the 172.x IP address, but it gets blocked (which is expected behaviour).
Both IPs are static, no DHCP is at play here.
In the VMWare console, I can see both IPs listed, so VMWare knows about both IPs. I guess when I import the VM from VMWare, VMWare either tells vWorkspace about both IPs, then vWorkspace picks tho 172.x address and it fails, or VMWare only tells vWorkspace about the 172.x address, and it fails.
If I NSLookup the CB from the VM, it works and gets the correct IP. the CB is not on the 10.202.x network, it's on the 10.1.x network.
You didn't mention static IP addresses so I (wrongly) assumed that DHCP could be at fault.
If there is no Provision Networks entry, then the vWorkspace "agent", PNtools hasn't been installed. So no latency reduction, no universal printing, flash redirection, user profile management etc.
However even without PNTools installed on the VMs, the connection broker HAS to be able to initialize the VMs when you import them. That involves copying a file, pndcsvc.exe to c:\windows system32 (x64 or syswow64 for x86), and running a remote command which installs pndcsvc.exe as a service and creates the registry settings under HKLM...\Provision Networks\Common that the data collector service needs to send a heartbeat packet to the connection broker.
No heartbeat packet=OFFLINE.
You are going to have to create a firewall exclusion for the connection broker, because if it can't communicate with the virtual machines, they won't be available.
This is analogous to what you have if you forget to install VMware tools on to a VM, it'll be crippled.
You have to set this on the VM manually. Normally the registry entries would be put into your master template (Hence being a range instead of a specific ip)
Then when you deployed from that template, during provisioning we'd inject the rest of the registry keys needed for the VM to talk to the Connection Broker. The DataCollector service would then send the correct IP to use to the Broker as part of it's heartbeats.
As you've manually imported these VMs, rather than provisioning them through vWorkspace, you do have a unique issue as you say in your last sentence.
To get around this, either
1. Temporarily disable the other nic, so that your Hypervisor will report the correct IP address to our Broker and we'll then be able to do the initialize and get the VM setup.. As long as you have the registry key in place for which IP to use, you'll then be able to re-enable the other network card.
2. You may be able to fix this by changing the binding order of your NICs. I think if you make the NIC with the correct IP the first network card in the binding order, it will be this IP address that gets reported to the Hypervisor. We asked the Hypervisor for the IP so this should also fix the issue.
Is this only for VDI or does it work for RDSH as well? I have a 2012R2 RDSH server running vWorkspace 8.01 which worked fine until I added a second NIC. As soon as this was added, clients failed to connect via the web interface or AppPortal. Direct connections using PNTSC worked fine.
Looking at resource monitor on the secure gateway server I can see that connections are trying to connect to the wrong IP address. If I disable the 2nd NIC, things start working again.
I installed the hotfix and added the IPRange value as the servers IP address and IPMask value as 255.255.255.255. It made no difference. I also confirmed that the NIC I want to use is first in the binding list.
We have Server 2008R2 RDSH servers with similar configurations which don't have this issue.
DELL-Andrew W1
378 Posts
2199
0
Posted August 18th, 2014 03:00
Hi Nick,
We have a hotfix to allow VDI to work with Multiple NICs.
You need to install https://support.software.dell.com/vworkspace/kb/122723
A new configuration option is available to support virtual machines that have multiple IP addresses. Typically this configuration is not required, but can be useful in some cases (e.g. VM has multiple network adaptors, user starts a client VPN connection, a USB video camera adds a network adaptor when plugged in). This new configuration option allows an administrator to specify the IP address range vWorkspace should use for communication with the VM. This configuration would usually be performed on the template VM and would include the entire range of IP addresses that may be assigned to VMs created from the template VM. This option can be configured via a registry key on the VDI machine as described below.
On 32-bit computers, navigate to HKLM\Software\Provision Networks\Common
On 64-bit computers, navigate to HKLM\Software\Wow6432Node\Provision Networks\Common
Create the following keys:
The example configuration above results in an IP address range of 10.1.1.1-10.1.1.255. For a computer multiple IP addresses, if one of the IP address is in the configured range vWorkspace will use that IP address for management and remote desktop communication. If none of the IP addresses are in the configured IP address range, the first IP address based on binding order will be used.
Note: Dell Software does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Thanks, Andrew.