Connections of VDI to AD

Similar Questions

• IEAK error when connect to VDI Desktop in vWorkspace 8

  Hello

  as a previous mistake of kerberos ticket post I do several tests in order to implement vWorkspace 8.

  When I connect to VDI desktop (without kerberos, or with the initial only, not SSO) pops up an error IEAK. Sorry for the attached screenshoot and some descriptions are in Spanish

  The guest operating system is company Win 7 SP1 with the latest patches, active RDP8 and Explorer 9. Guest operating system is Spanish localized.

  

  Detailed description:

  Firma con problemas:

  Number del problema evento: BEX

  Application number: rundll32.exe_iedkcs32.dll

  Application version: 6.1.7600.16385

  Marca of tiempo of the application: 4a5bc637

  Number del modulo con errores: PNMicSrv.dll_unloaded

  Version del modulo con errores: 0.0.0.0

  Tiempo del modulo Marca con errores: 513eb9a9

  Exception offset: 7502d6a1

  Exception code: c0000005

  Exception data: 00000008

  Led operating system version: 6.1.7601.2.1.0.256.4

  ID of regional config: 3082

  Additional information 1: 0a9e

  Additional information 2: 0a9e372d3b4ad19135b953a78882e789

  Additional information 3: 0a9e

  Additional information 4: 0a9e372d3b4ad19135b953a78882e789

  LEA nuestra declaracion privacy online:

   http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0C0A

  I have the same problem. I opened a folder with support and they are studying.

  Meanwhile, I have found a workaround. It seems that the problem is related to pnmicsrv.dll for vworkspace versions superior to 7,6 GA at least the question seemed to us after application of a patch for this version and it reappeared after upgrade to v8. In both cases I solved it replaces the pnmicsrv.dll file in our model with the dll version 7.6 of GA

• W7 64 bit VMWare View client do not connect with VDI

  Hi guys, I installed the x 64 client vmware view on a W7, and I'm not trying to connect to a VDI from him. When I try to open the connection with the view server I have the following error

  "vmware client view server returned an invalid or unrecognized response".

  I took a quick glance to vmware \AppData\Local\VMware\VDM\log files and I saw the following error codes

  2012-12-27 09:43:58, 936 DEBUG < MessageFrameWorkDispatch > [wswc_http] ErrorCode WININET is 12152

  Anyone know why this error occurs for the 64-bit client?

  Thanks in advance

  Hello..

  Yes! You can.

  This is for you - compatibility matrix

  http://pubs.VMware.com/view-50/index.jsp?topic=/com.VMware.view.upgrade.doc/GUID-E9BB81A4-1054-4BBB-A43B-CB60A6EF909E.html

  Concerning

  Faisal

• See DR with Broker for Replica connections

  We are eager to have some DR in our environment view and thought that if I have a Connection Broker in each of our data centers, one being the "main" and the other being a replica. Whereas in cases or the other sites in descending us would point users to the other Broker pools for the connections and VDI in this DC.

  -What looks like a plausible idea to anyone? Or how everyone does not DR for different domain controllers.

  See you soon

  A.

  Front view 6 having brokers connection across different data centers would not be supported.   Now that view 6 is out you can use the architecture of pod to accomplish a DR form for the environment.

  http://blogs.VMware.com/EUC/2014/04/VMware-horizon-6-introducing-cloud-pod-architecture.html

• VWorkspace Reporting and licensing

  Hello

  I'm trying to find out how many people have connected to VDI over a certain period. It comes to the current report. Manager, it will use to determine how many licenses we need and what is the use (Sessions, licenses). For the moment, I know people are connected, but I don't know how to put together the date.

  Another question is if I go to the Management Console > license file I see 0 In Use licenses even though people are connected. Is this supposed to show the use of the current license?

  Hello Dejan,

  I suggest to study further why it shows 0 licenses and has nothing to do with M & D. M & d works correctly, you farm should behave properly first. You receive error popups when you access licenses screen? 0 sessions/licenses may indicate a malfunction of the broker for connections. For starters, you can check if the quest Connection Broker, database management and the registry services are running. Broker listed in the GPMC vWorkspace, rentals, location 1, list of connection brokers?

• Slow logon due to errors with PNShell

  Hello

  I'm in the process of slow logon caused bij pnshell when I was able to connect a VDI. The versions that I use are:

  • Looking for immediate Provisioning Service x 64 8.0.306.1427
  • Tools of quest for the managed desktop (64-bit)

  I have generated a log file, see below. What can be the cause and what is the solution?

  October 10, 2014 10:49:55 - 4884:1116 -! === !
  October 10, 2014 10:49:55 - 4884:1116 - Log PnShell
  October 10, 2014 10:49:55 - 3408:1804 -! === !
  October 10, 2014 10:49:55 - 4884:1116 - user: [VDI-CL-TEST002\Administrator]
  October 10, 2014 10:49:55 - 3408:1804 - Log PnShell
  October 10, 2014 10:49:55 - 4884:1116 - Version of the operating system: [6.2.9200]
  October 10, 2014 10:49:55 - 3408:1804 - user: [mydomain\VDI-CL-TEST002$]
  October 10, 2014 10:49:55 - 4884:1116 - Machine Name: [VDI - CL - TEST002.mydomain.local]
  October 10, 2014 10:49:55 - 3408:1804 - Version of the operating system: [6.2.9200]
  October 10, 2014 10:49:55 - 4884:1116 - PnShell Version: [8.0.306.1427]
  October 10, 2014 10:49:55 - 3408:1804 - Machine Name: [VDI - CL - TEST002.mydomain.local]
  October 10, 2014 Parent 10:49:55 - 4884:1116 - process: [winlogon.exe]
  October 10, 2014 10:49:55 - 3408:1804 - PnShell Version: [8.0.306.1427]
  October 10, 2014 10:49:55 - 4884:1116 -! === !
  October 10, 2014 Parent 10:49:55 - 3408:1804 - process: [pnsenapp.exe]
  October 10, 2014 10:49:55-4884:1116 - PNShell.cpp - does not not as a user [SYSTEM]. As a [Director]
  October 10, 2014 10:49:55 - 3408:1804 -! === !
  October 10, 2014 10:49:55 - 4884:1116 - CShellConfigFile - ERROR: not open xml file! The XML file name: C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml
  October 10, 2014 10:49:55-3408:1804 - PNShell.cpp - we run as the SYSTEM user.
  October 10, 2014 10:49:55 - 4884:1116 - PNShell.cpp - XML file was empty
  October 10, 2014 10:49:55 - 3408:1804 - CShellConfigFile - ERROR: not open xml file! The XML file name: C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml
  October 10, 2014 10:49:55-4884:1116 - PNShell - [PNSHELL_USERINIT_2] events successfully created
  10 October 2014 10:49:55-3408:1804 - PNShell - open the [PNSHELL_USERINIT_2] event successfully
  October 10, 2014 10:49:55 - 4884:1116 - PNShell - wait event [PNSHELL_USERINIT_2]
  October 10, 2014 10:49:55 - event - PNShell - 3408: 1804 [PNSHELL_USERINIT_2] setting
  October 10, 2014 10:49:55-4884:1116 - PNShell - [PNSHELL_COMPLETE_2] events successfully created
  October 10, 2014 10:49:55 - 3408:4916 - CShellConfigFile - ERROR: not open xml file! The XML file name: C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old.
  October 10, 2014 10:49:55 - 4884:1116 - PNShell - wait event [PNSHELL_COMPLETE_2]
  October 10, 2014 10:49:55-3408:4916 - PNShell.cpp - content reading of the shell configuration file.
  October 10, 2014 10:49:55 - 3408:4916 - CShellConfigFile - ERROR: not open xml file! The XML file name: C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml
  10 October 2014 10:49:55-3408:4916 - PNShell - open the [PNSHELL_COMPLETE_2] event successfully
  October 10, 2014 10:49:55 - event - PNShell - 3408: 4916 [PNSHELL_COMPLETE_2] setting
  October 10, 2014 10:49:55-3408:4916 - PNShell - [PNSHELL_SESSION_COMPLETE_2] events successfully created
  October 10, 2014 10:49:55-4884:1116 - Running USERINIT. EXE.
  October 10, 2014 10:49:55 - 3408:4916 - PNShell - wait event [PNSHELL_SESSION_COMPLETE_2]
  October 10, 2014 10:49:55 - 4884:1116 - launch [C:\WINDOWS\system32\USERINIT. [EXE] as a current user.
  October 10, 2014 10:50:11 - 4884:1116 - PNShell - ERROR: failed to copy 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml' to 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.cleanshorts', error code = (3)
  October 10, 2014 10:50:11 - 4884:1116 - PNShell - ERROR: failed to copy ' C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old. ' to ' C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old... cleanshorts ', error code = (3)
  October 10, 2014 10:50:11 - 4884:1116 - PNShell - ERROR: failed to copy 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml' to 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netdrive', error code = (3)
  October 10, 2014 10:50:11 - 4884:1116 - PNShell - ERROR: failed to copy ' C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old. ' to 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netdrive', error code = (3)
  October 10, 2014 10:50:11 - 4884:1116 - PNShell - ERROR: failed to copy 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml' to 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netprint', error code = (3)
  October 10, 2014 10:50:11-4668:4180 - assessment command line arguments.
  October 10, 2014 10:50:11-4460:4440 - assessment command line arguments.
  October 10, 2014 10:50:11 - 4884:1116 - PNShell - ERROR: failed to copy ' C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old. ' to 'C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netprint', error code = (3)
  October 10, 2014 10:50:11 - 4668:4180 - PNShell - ParseCommandLineArgs2, args = ["" / netdrive, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netdrive,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netdrive ""]
  October 10, 2014 10:50:11 - 4460:4440 - PNShell - ParseCommandLineArgs2, args = [' / cleanshorts, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.cleanshorts,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old cleanshorts "]
  October 10, 2014 10:50:11 - 3408:1804 - WM_SETTINGCHANGE
  10 October 2014 10:50:11-4884:1116 - PNShell - open the [PNSHELL_SESSION_COMPLETE_2] event successfully
  October 10, 2014 10:50:11 - 4668:4180 - PNShell - ParseCommandLineArgs2, argv [0] = [/ netdrive, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netdrive,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netdrive]
  October 10, 2014 10:50:11-4464:4728 - assessment command line arguments.
  October 10, 2014 10:50:11 - 4460:4440 - PNShell - ParseCommandLineArgs2, argv [0] = [/ cleanshorts, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.cleanshorts,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old cleanshorts]
  October 10, 2014 10:50:11 - events - PNShell - 4884: 1116 [PNSHELL_SESSION_COMPLETE_2] setting
  October 10, 2014 10:50:11-4668:4180 - PNShell - assessment command-line argument [/ netdrive, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netdrive,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netdrive]
  October 10, 2014 10:50:11 - 4464:4728 - PNShell - ParseCommandLineArgs2, args = ["" / netprint, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netprint,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netprint ""]
  October 10, 2014 10:50:11-4460:4440 - PNShell - assessment command-line argument [/ cleanshorts, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.cleanshorts,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old cleanshorts]
  October 10, 2014 10:50:11 - 3408:4916 - cannot rename the file [C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml] [C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old.]. Error code [3]
  October 10, 2014 10:50:11 - 4668:4180 - CShellConfigFile - ERROR: not open xml file! The XML file name: C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netdrive
  October 10, 2014 10:50:11 - 4464:4728 - PNShell - ParseCommandLineArgs2, argv [0] = [/ netprint, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netprint,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netprint]
  10:50:11-4460:4440 - CRegistryPerformer - October 10, 2014 has no query string value: could not open key ' Software\Provision Networks\Manage-IT ' under HKCU: the system kan het opgegeven bestand niet vinden.
  October 10, 2014 10:50:11 - 4668:4180 - NetworkDriveOperator.cpp - impossible to locate the configuration file PNShell. Cannot set up network drives.
  October 10, 2014 10:50:11-4464:4728 - PNShell - assessment command-line argument [/ netprint, C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netprint,C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netprint]
  October 10, 2014 10:50:11-4460:4440 - CShortcutCleaner - setting last run to [Fri Oct 10 10:50:11 2014]
  ]
  October 10, 2014 10:50:11-4464:4728 - NetworkPrinterOperator - cutting existing printer connections.
  October 10, 2014 10:50:11-4460:4440 - error opening registry key [Software\Provision network]
  October 10, 2014 10:50:11 - 4464:4728 - CShellConfigFile - ERROR: not open xml file! The XML file name: C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old..netprint
  October 10, 2014 10:50:11-4460:4440 - CRegistryPerformer - cannot write the string value: could not open key "Software\Provision Networks\Manage-IT ' under HKCU: the system kan het opgegeven bestand niet vinden.
  October 10, 2014 10:50:11 - 4464:4728 - NetworkPrinterOperator.cpp - impossible to locate the configuration file PNShell. Cannot configure network printers.
  October 10, 2014 10:50:11-4460:4440 - CShortcutCleaner - cleaning of the shortcuts created during the first time connection.
  October 10, 2014 10:50:11-4464:4728 - NetworkPrinterOperator - new connections to printer connection.
  October 10, 2014 10:50:11-4460:4440 - CRegistryPerformer - cannot delete the value: cannot delete the value PnShell_Shortcuts: the system kan het opgegeven bestand niet vinden.
  October 10, 2014 10:50:11 - 4464:4728 - CShellConfigFile - ERROR: not open xml file! The XML file name: C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.netprint
  October 10, 2014 10:50:11-4460:4440 - CShortcutCleaner - [C:\Users\Administrator\AppData\Local\Quest Software\vWorkspace\] directory does not exist. Cannot delete existing shortcuts.
  October 10, 2014 10:50:11 - 4464:4728 - NetworkPrinterOperator.cpp - impossible to locate the configuration file PNShell. Cannot configure network printers.

  Hi all

  We found that if you do not use Metaprofiles in your environment, you can save a fair few seconds off your time of connection by installing is not the part of the user of PNTools in your main image profiles.

  We did it here and it made a big difference.

  Thank you, Andrew

• Problem with USB Redirection on Horizon View Client v2.3.0 for Linux

  I had a problem on the USB Redirection when connecting to the Server of VMware View by Horizon View Client v2.3.0.

  1. Here is our configuration:
     1. Server:
        1. Horizon View Server 5.5 + Windows 7 Enterprise VDI
     2. Client:
        1. Thin client (TI ARM platform - 8148)
        2. Horizon View Client v2. 3 for Linux
        3. USB Flash: Kingston 8 GB USB 2.0, FAT32
  2. The issue: USB flash can not redirect to VDI successfully.
  3. Some status on our test:
  • The USB is plugged USB port on workstation before connecting to Horizon view Server 5.5
  • Light client can recognize and use USB flash to the local site.
  • When we connect to VDI, we can see the USB driver is responsible for research and installation, but windows VDI() reports fail to install the USB driver finally. It seems that VDI trying to acknowledge the failure of USB flash but finally.
  • It is held even Let's restart the workstation and VDI.
  • Attached file is the log of the Horizon of the VMware View Client.

  
  All welcomed to this topic?

  Unfortunately the newspapers show much... (note: they do not contain client-side logs)

  one thing I thought well... since he is a computer thinClient - we have seen the questions that manufacturers computer thinClient some of their own 'management' software install on the client. He often tries to do things with usb devices (maybe try to share them between a receiver client citrix application and view client app or maybe just there is a citrix receiver application installed too). In our experience, we've seen these apps interfere between them as they try to hang the bottom of usb devices down into the kernel.

  as such, could you try stop any 3rd party services - either citrix or your provider of thin client and then try again.

  If the problem persists, can you be sure to also collect these log files from the computer thinclient:

  Windows client

  • %ProgramData%\VMware\VDM\logs\debug-*.txt
    AND
  • C:\Windows\Temp\vmware-SYSTEM\vmware-usbarb-*.log

  Linux client

  • default /tmp/vmware-root/VMware-view-Usbd-*.log
    AND
  • / Library/Logs/VMware/vmware-usbarbitrator -.log

  for reference, the Agent-side usb connects:

  • %ProgramData%\VMware\VDM\logs\debug-*.txt

  see you soon

  peterB

• ThinShell 2.5.3 does not connect to Windows 8.1 VDI

  I'll put up ThinShell 2.5.3 on some older Windows 7 PC. It's on an AD domain using fully patched vWorkspace 8.5 (8.5.308.2004 connector). Try to install ThinShell 2.5.3 results in an error indicating the connector has not been detected on the PC.

  I then uninstalled this version and installed the 8.5.308.1991 connector. Then tried to reinstall ThinShell 2.5.3. It has installed.

  I have installation ThinShell in Native Mode, set EnableKerberos true and EnableSSO to True. When users open a session on the PC ThinShell launches the VDI. It connects, but then stops on the log on screen for Windows 8.1. Users must again enter their credentials and connect to the VDI. If the user already has a VDI session but is simply disconnected, opening a session on the PC ThinShell records all the way to the desktop.

  I also uninstalled the connector and then installed the 8.5.308.2004 (without messing with ThinShell). The results are the same.

  Hello

  I think it is because you have enabled EnableKerberos and EnableSSO.  EnableSSO will allow the credentials cached and you don't need this option while EnableKerberos.  Looks like you want to use Kerberos, then please try to set EnableSSO to false.

  I would also recommend that you use the configurator... http://en.community.Dell.com/TechCenter/virtualization/vWorkspace/b/vWorkspace-blog/archive/2013/10/17/thinshell-Configurator-2-0

  See you soon

  Paul

• vWorkspace 8 - VDI Windows 7 "Error cannot connect to the server '.

  Hello

  We are soon about to begin the deployment of our vWorkspace VDI solution. We have Windows 7 Client s connection to Win 7 Pro 32 Bit VM on Hyper-V.

  Sometimes when the user intiates a connection to the desktop of Windows 7 VDI published the vWorkspace Client launch and are trying to connect, and then an error will be presented "Error cannot connect to the server. We do not understand all the time and it is random.

  Go it is addressed urgently as it's going to cause some major headaches with our users.

  Someone at - it ideas?

  Cool, thanks Dan.

  I'll find the case of Mike and send the info from there.

• Connection to a VDI with PCoIP desktop shows a black screen and little disconnects

  I have an image of the mother and the pools built from this image. They work well. I created a new pool from this image with VDIs 10 gold. When I assigned people to this pool, they complained on black screen and when I looked at the papers I found some possible solutions to this problem.

  We are on view 5.3

  Operating system: WIN 7 32-bit.

  So far, I have these patches:

  (1) replace connect via GPO DNS

  (2) increases vram and no monitors

  Nothing has worked so far. Any help with this well really much appreciated. I have attached the log file. Ask if you need more info or newspapers on this subject.

  Kind regards

  Anoop.

  I found the problem. I tried to upgrade the agent from the view and then reinstalled 5.3. But the pilot svga not to downgrade to 8,15 and so the error. I uninstalled the tools and agent and reinstalled the VMware tools and the former agent of view in good order and he got the old svga driver (7.14) and now its work. Thank you to all who responded.

• MMR does not not on a direct connection VDI

  Hello

  According to the view release notes 6.0.2 ROR Horizon is supported on VADC (Agent direct connection), but so far I was not able to make it work. Strange thing is that when I connect to one of these workstations via the broker, ROR works. I use a VDI in Win 7 x 64 with the latest VMware Agents installed. Also, servers connection view and view composer have installed the latest versions and the client has the latest version of the Client view installed. There is no firewall rule that block traffic MMR no more, because for testing purposes, I've disabled the firewall on server side, client-side AND the VDI side. Anyone any idea what I am doing wrong?

  Thank you

  Chris

  Did you apply the group policy setting to enable it? Unlike the full connection agent, there is no UI admin to set this policy at the time of the connection, so it must be configured by GPOS. From view_agent_direct_connection.adm:

  Multimedia redirection (MMR) activated

  Determines if the MMR is enabled for client systems. ROR is a Microsoft's DirectShow filter that transfers multimedia codecs-specific data on view offices directly via a TCP socket to the client system. The data are then decoded directly on the client system, where it is played. The default value is disabled.

  MMR does not work correctly if the client system's video display hardware is not supported for recovery. Client systems may have insufficient resources to deal with a local multimedia decoding.

• VDI Session disconnects when you connect to the VPN

  I'm trying to find out why a VDI session log when you try to open a VPN session inside the virtual machine. My organization requires us to use two-factor authentication to access certain resources on the network (including the console in vCenter feature). The solution that we use is the Juniper Net Connect. Right when the VPN starts to open the session is disconnected and the only way to get screw is to restart the virtual machine. Thoughts?

  Yes, its quite simple, the VPN client closes all traffic that is not via the vpn.

  You must configure address. "split tunneling" on your VPN client.

  Linjo

• VDI Client cannot connect after windows updates 7

  Hello

  I did the updates on my windows workstations 7. After the updates when installed, I can not connect with my client of vdi for the connection to the server.

  Anyone have an idea? It works without these updates.

  BR

  Andreas

  It is a well known problem.

  A version of patch from view4.5 (353760) is available for this problem.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1034262

• Average time it takes to connect to a VDI

  I would like to know what the average length of time that it takes other people to connect on a VDI on the Internet. A connection using RDP, which connection via a security server, it takes our approxamately 2 minutes from the moment users wherever they select the pool Id in the list to the point their office is usable.

  All VDI are powered and put in service in advance.

  Any information that would establish if my installation is normal or that it needs futher investigation would be appreciated.

  Paul

  It should take<5 seconds="" to="" get="" your="" desktop.="" if="" it="" is="" taking="" more,="" there="" are="" probably="" issues="" in="" your="" environment="" somewhere.="" i="" would="" recommend="" checking="" speeds="" from="" the="" site="" experiencing="" the="" slowness="" to="" your="" view="" site="">

  ____________

  blog.eeg3.net | Useful links related to VMware

  If you have found this device or any other post useful, please consider the use of buttons useful/correct for award points.

• VDI connect to the virtual computer with multiple NICs, use wrong address

  Strange question, we are the double of a VM to autoguiding.  Each NIC is on a different network, and it works very well.  Except when you sign out of the VM with a zero client.  If both network adapters is enabled through the vsphere, zero client the client tries to connect to the virtual machine using a wrong address.  He will try to use the address 172.16.x.x, but the life of the virtual machine and is stored on 192.168.x.x network.  Is there a way to make the NETWORK on 192.168.x.x address network card that zero the client tries to connect?

  Using the network-> Advanced-> advanced-> tab connections maps and links, move the 192.168.x.x network adapter to the top of the list of connections.

  Linjo