VMware View Agent uninstall Script?

Similar Questions

• VMware View Agent Direct-connection plug-in

  Hello

  Someone knows how can I get the plugin VMware View Agent direct connection?

  Thank you.

  This one is not publicly available, in order to get it you need to have compromised in place with VMware.

  I'd say contact your local VMware Salesteam and see if they can help.

  Linjo

• VMWare View Agent on the Terminal Server

  We are trying to install the Agent on a Server Terminal server view, and the view Agent service crashes. I looked in the VDM newspapers and see the following information.

  Anyone know why the view Agent cannot load jar files?

  17:42:13, INFO 337 < Service main Thread > [wsnm_desktop] DesktopManager Queue Server installed
  17:42:13, 337 INFO < MessageFrameWorkDispatch > [wsnm_desktop] Session CONNECTED after reboot wsnm: id = 0, KCDOM01\lbeardall, the client user = SPI-LBEARDALL
  17:42:13, INFO 337 < logloaded > [MessageFrameWork] "ws_filesystem - component of VMware View filesystem plugin" Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, INFO 337 < logloaded > [MessageFrameWork] Plugin 'wsnm_jmsbridge - VMware View framework JMS Bridge Controller' loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 353 INFO < logloaded > [MessageFrameWork] "ws_perfmon - VMware View Performance Monitor and counter shop" Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 353 INFO < logloaded > [MessageFrameWork] Plugin "ws_thinappmgmt - support for VMware View infrastructure Application Management" loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 353 INFO < Service main Thread > [wsnm] start the VMware View System Service
  17:42:13, 509 INFO < 7008 > [MessageFrameWork] 'wsnm_jms - VMware View framework JMS bridge' program began, version = 4.6.0 build-366101, pid = 7096, buildtype = release, usethread = 1, closeafterwrite = 0
  17:42:13, 541 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:42:13, 541 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 541 WARN] < main Thread > error occurred during initialization of VM
  17:42:13, 650 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute
  17:43:13, 724 < 5732 > INFO [MessageFrameWork] program 'wsnm_jms - VMware View framework JMS bridge' started, version = 4.6.0 build-366101, pid = 5952, buildtype = release, usethread = 1, closeafterwrite = 0
  17:43:13, 755 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:43:13, 771 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:43:13, 771 WARN] < main Thread > error occurred during initialization of VM
  17:43:13, 880 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute
  17:44:14, 064 < 3228 > INFO [MessageFrameWork] program 'wsnm_jms - VMware View framework JMS bridge' started, version = 4.6.0 build-366101, pid = 3160, buildtype = release, usethread = 1, closeafterwrite = 0
  17:44:14, 095 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:44:14, 095 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:44:14, 095 WARN] < main Thread > error occurred during initialization of VM
  17:44:14, 204 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute
  17:45:14, 388 INFO < 1292 > [MessageFrameWork] 'wsnm_jms - VMware View framework JMS bridge' program began, version = 4.6.0 build-366101, pid = 1288, buildtype = release, usethread = 1, closeafterwrite = 0
  17:45:14, 419 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:45:14, 419 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:45:14, 419 WARN] < main Thread > error occurred during initialization of VM
  17:45:14, 528 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute

  Looks like the Sun JVM, the portion of the agent running JMS integration crashes at startup. It's just a guess, but I've seen a similar case with another client where they were running XP virtual machines with large amounts of RAM and some third-party software that was loading DLLs in the middle of the address space of the process. The JVM tries to get a contiguous area of memory, it may be falling on this sequel to a similar problem. On large memory systems, the default behavior of the JVM seizes more than necessary (although it is normally not a problem), try to set the following in the registry to avoid this:

  [Manager\JVM of \VMware VDM\Node of HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc..]

  JVMOptions = - XX: + ForceTimeHighResolution-Xmx64m

  Note that I added only option - Xmx64m to the existing setting.

• The upgrade of VMware View Agent from 5.2 to 5.3 causes agent become inaccessible in Horizon administrator.

  Short throughout, I was unable to update several agents to 5.3, because the 5.2 msi could not be found.

  I followed the instructions on this page (KB VMware: UpgradingVMware View Agent and View Composer fails with the error: the component that you are trying to use is o...) and installed the agent 5.3

  It worked on the test systems 3. When I went to live 2 principles broke. I can RDP but you cannot use the Client to connect and get a response that says that the resource is not available.

  I looked into the Horizon view Admin and they are listed as inaccessible agent, matching State pairings.

  I did the following.

  Uninstalled agent 5.3.

  Uninstalled the tools.

  Reinstalled them both.

  The removed from the inventory of the pool and added them.

  This is Win7 systems.

  Any help would be much appreciated.

  Fred

  I could solve this problem by removing the pool, then adding back and then restarting the agent service. It sometimes took two reboots, but that's fine.

• VMware View Agent 5.2.0 PCoIP over WAN fails

  Recently, I did an upgrade on VMware View VMware view horizon 5.2 4.6 square.

  After the upgrade the 4.6.0 view agent in virtual machines of my parents to view agent 5.2.0 and rebuild the office pools, external PCoIP does not work. Can I open a session in the 5.2 Client view, see the list of office pools, select a pool, the desk at work close and try to open remotely. After 1 second, this error appears:

  Error: Overview of VMware View Client: The connection to the remote computer has ended.

  What does not work:

  • External/WAN via PCoIP for workstations with the view Agent 5.2.0

  What does not work:

  • Internal/LAN via PCoIP for workstations with the view Agent 5.2.0
  • Internal/LAN via RDP for workstations with the view Agent 5.2.0
  • External/WAN via RDP for workstations with the view Agent 5.2.0
  • External/WAN via PCoIP for workstations with the Agent View 5.1.3 or lower (tested up to 4.6.0 Agent view)

  I even tried to build a new pool of desktop Windows 7 in a new OU in the active without optimizations VDI directory or group policy. I tried with and without the firewall Windows is activated. In any case, this new office pool works externally via any Agent from view but the view Agent 5.2.0.

  Is it the 5.2.0 Agent view have the same firewall/port that the Agent View 5.1.3 requirements? What else can I test or try to get external PCoIP for desktop computers to work with the view Agent 5.2.0?

  Finally, we discovered the problem / solution. We on a security apparatus of Palo Alto Networks that blocked traffic PCoIP 5.2.0 but not PCoIP 5.1.3 traffic.

  According to a backline Vmware engineer:

  "A change was made to the ephemeral TLS connection that is used to establish trust and to negotiate parameters for subsequent UDP traffic network. This change allows the customer to use their own certificate for TLS server for this connection. For more details of what happens during the installation of PCoIP, and how this changed view 5.2, see KB 1038762. »

  It seems that Palo Alto Networks did not like this change. When we removed our Palo Alto of WAN device, PCoIP 5.2.0 connections could be created. We finally had create a rule to allow the category: private-ip-addresses and URL: pcoip - by default-sni. Once this change has been made, connections WAN PCoIP 5.2.0 started working.

• DST and vmware view = weird questions

  This is the 3rd time that when the time comes or goes we get questions of kind of weird in our very frequent floating pools, VMs stuck in starting up, wait for connection etc.

  If you look at the log below you will see that the virtual machine has been one hour before, and then she came back at the right time.

  Anyone else seen elsewhere?

  2014 03-18 T 16: 06:36.553 - 04:00 INFO (016 C-0390) < Service main Thread > [wsnm_desktop] DesktopManager queue server is installed

  2014 03-18 T 16: 06:36.585 - 04:00 INFO 016c - 082 C < logloaded > [MessageFrameWork] "ws_filesystem - component of VMware View filesystem plugin" Plugin loaded, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:36.595 - 04:00 INFO (016 C-0830) < logloaded > [MessageFrameWork] Plugin 'wsnm_jmsbridge - VMware View framework JMS Bridge Controller' loaded, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:36.612 - 04:00 INFO (016 C-0838) < logloaded > [MessageFrameWork] 'ws_klog - plugin VMware View Kernel Log' Plugin loaded, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:36.642 - 04:00 INFO (016c-0390) < Service main Thread > [wsnm] System Service VMware View begins

  2014 03-18 T 16: 06:36.642 - 04:00 INFO (016c-0840) < logloaded > [MessageFrameWork] "ws_perfmon - VMware View Performance Monitor and counter shop" Plugin loaded, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:36.643 - 04:00 INFO (016 C-0850) < logloaded > [MessageFrameWork] Plugin ' ws_vhub - Service USB virtual VMware View framework "support, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:36.643 - 04:00 INFO (016 C-0848) < logloaded > [MessageFrameWork] Plugin "ws_thinappmgmt - support for VMware View infrastructure Application Management" loaded, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:36.644 - 04:00 INFO (016 C-0854) < PluginInitThread > [ws_vhub] vhublib: initialized, VMware View virtual USB Hub API (64-bit) version: 5.5.0 build-966253, exit: unknown

  2014 03-18 T 16: 06:36.782 - 04:00 INFO (C 088-0890) < 2192 > program [MessageFrameWork] 'wsnm_jms - VMware View framework JMS bridge' began, version = 5.2.0 build-987719, pid = 0x88C, buildtype = release, usethread = 1, closeafterwrite = 0

  2014 03-18 T 16: 06:36.806 - 04:00 INFO (C 088-0890) < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\commonutils.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-9.2.1.jar VMware; C:\Program View\Agent\lib\\jmswrapper.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-9.2.1.jar VMware; C:\Program View\Agent\lib\\v4v-msgserver.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;

  2014 03-18 T 16: 06:36.818 - 04:00 INFO (088 C-08E4) < logloaded > [MessageFrameWork] "ws_javaview - VMware View Java Diagnostics Framework" Plugin, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:37.001 - 04:00 INFO (C 088-0938) < logloaded > [MessageFrameWork] Plugin "ws_java_bridgeDLL - VMware View Java Bridge Framework" loaded, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:37.002 - 04:00 INFO (C 088-0934) < logloaded > [MessageFrameWork] Plugin ' ws_java_native - Framework Java native Support of VMware View "load, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 16: 06:37.208 - 04:00 INFO (C 088-0890) < main Thread > [ws_java_bridgeDLL] JavaBridge installed service EventLoggerService

  2014 03-18 T 16: 06:37.208 - 04:00 INFO (C 088-0890) < main Thread > [] JavaBridge queue server is installed

  2014 03-18 T 16: 06:37.209 - 04:00 INFO (C 088-0890) < main Thread > [] View Composer agent has completed the customization

  2014 03-18 T 16: 06:37.737 - 04:00 INFO (0624-0628) < 1576 > [VMwareView-RdeServer] program "VMwareView-RdeServer - VMware View RDE 32-bit Server" began, version = e.x.p build-1190491, pid = 0 x 624, buildtype = release, usethread = 0, closeafterwrite = 0

  2014 03-18 T 16: 06:39.567 - 04:00 INFO (C 088-0890) < main Thread > [] View Composer personalization state 0 (0 seconds)

  2014 03-18 T 16: 06:39.673 - 04:00 INFO (C 088-0890) < main Thread > [java] bridge exe started ok.

  2014 03-18 T 15: 38:45.288 - 04:00 INFO (016 C-0128) < main Thread > [wsnm_desktop] Session created in WAIT state: id = 1, winStation = Console

  2014 03-18 T 15: 38:45.350 - 04:00 INFO (0488-0978) < 2424 > [MessageFrameWork] 'wssm - VMware View framework Session Manager' program began, version = 5.2.0 build-987719, pid = 0 x 488, buildtype = release, usethread = 1, closeafterwrite = 0

  2014 03-18 T 15: 38:45.397 - 04:00 INFO (0488-0550) < logloaded > [MessageFrameWork] Plugin 'wssm_desktop - VMware View framework Office Manager Instance' loaded, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 15: 38:45.397 - 04:00 (0488-07 D 0) INFO for < logloaded > [MessageFrameWork] Plugin 'ws_winauth - taken in charge of VMware View infrastructure Windows Authentication", version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 15: 38:45.475 - 04:00 (0488-05 D 0) INFO for < logloaded > [MessageFrameWork] Plugin 'ws_thinappmgmt - taken in charge of VMware View infrastructure Application Management", version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 15: 38:45.631 - 04:00 INFO (0488-0978) < main Thread > [wssm] Session Manager has begun for the session 1

  2014 03-18 T 15: 38:45.631 - 04:00 INFO (0488 - 0 to 28) < logloaded > [MessageFrameWork] 'wssm_uimanager - VMware View Host UI Framework' Plugin support, version = 5.2.0 build-987719, buildtype = output

  2014 03-18 T 15: 38:45.631 - 04:00 INFO (0488 - 0 B 40) < logloaded > [MessageFrameWork] Plugin 'wssm_ui - VMware View UI framework' loaded, version = 5.2.0 build-987719, buildtype = output

  I was on the phone with VMware for 5 hours Tuesday last with this same problem.  I ended up solving the problem without their help.  You must initialize your model, let the time updated, shut it down, take a new snapshot and recompose your pool.

  Re: View 5.3 - desktop blocked at startup

• Two monitors configured using PCoIP does not cover both monitors for VMware View

  Occasionally, I've experienced the symptoms described in KB1027899, when usually the first time of connection for the day that I select multiscreen and the screen is divided in the Middle the 2 monitors using PCoIP. I end up disconnecting and reconnecting to the virtual machine a few times, which is a valid solution, but I'm still curious about why this is happening.

  I am running VMware View 5.0.0 build-481677, on a Wyse R90L with Windows XP Embedded, I use VMware View Client 5.0.0 build 481677 and VMWare View agent on a box of Windows 7 5.0.0 build 481677. We lack vCenter and ESXi 5.0.0 in all areas as well.

  According to the article, this happens because there is not enough video memory configured for the virtual computer. The problem I have is that if I force the pool offices use PCoIP and 128 MB of video memory, I can't RDP to the workstation as the Protocol is locked, I need to still be able to do. I tried manually increase the memory video, but view reconfigures to match the settings of the pool.

  Is there a way to increase the video memory without changing the required logon Protocol? Or is there a fix in a different way to this question?

  Thanks a lot guys.

  Joe

  Have you tried to change the configuration video pool to be 2 monitors with 2560 x # instead of the default resolution to see if that solves the problem?

  Datto

• personalization operation timed out VMware View 4.5

  I'm quite new to Vmware view and this is my first time setting up, please bare with me.

  I get the above error when trying to automatically create a related pool.

  I also spent review the previous post that says abot ensuring that:

  • DHCP is enable on the master image
  • VMware view agent is installed
  • VMware tools is installed
  • The firewall is disabled

  The new virtual machines are created and when I connect to Vsphere is to see that they connect to the field, receive IP from the DHCP server. But I don't see their name in my DNS.

  I hope to have provided enough information and you will appreciate any help.

  To the first just nslookup query, and check whether or not the host of clones name is resolved. Also select al virtual machines to see the Administrator page and perform a reset and see<--  if="" both="" these="" actions="" resolve="" your="" issue="" then="" it="" was="" due="" to="" a="" minor="" network="" outage="" happened="" during="" the="" provisioning="">

  Otherwise,.

  1. If the DNS server is a server active directory integrated one or not? If this is not the case, check the permission to register for this DNS server.

  2. the question of whether the DNS entry received from the DHCP server to clone is directed to the right DNS server? and same DNS / domain name cannot be resolved vcenter server?

  3. have you used Sysprep customization? If Yes, be aware that the domain setting is not levied custom specification but DNS settings will be taken from custom spec. In this case the definition given in the spec custom DNS should resolve the field added in vcenter configuration Admin display page

• VMware VI3, VMware View with Novell eDirectory integration

  Hello

  We are a COMPUTER consulting company and we have a lot of colleges and universities using Novell looking at VMware VI3 and VMware VIew.

  (1) for VMware VI3 tabs of permissions must be able to connect to an LDAP server to Active Directory only.

  (2) for VMware VIew 3, the VMware Agent should be integrated into the Novell Client for Windows...

  We did a little proof of concept with VMware View, and each time that the Novell Client are causing a lot of problems with VMware View Agent. It's bad because these 2 projects has been more than 10000 thin clients. They decided to Citrix XenDesktop used instead.

  It'll be great if you can built your product with the architecture of Novell.

  Best regards

  Eric Champagne

  IT Director

  Adaris Technologies / www.adaris.ca

  Yes, it would be nice

  a question: you say that a decision was made to use XenDesktop: are you still using VMware VI3? or XenServer?

  Jose

• Cannot start the VMWare host agent service

  I worked on this issue for awhile with no resolution.  Initially, I had a problem running VMWare Server Home Page so I installed the VMWare Server Console and the error when trying to launch the Console VMWare Server on the same server VMWare Server is installed and connect locally:

  501 command overall GLOBAL Server-vmdb targets no host agent not supported.

  Came to the conclusiong that it was the result of the function of Agent Host VMware is not able to start.

  Environment:

  IBM BladeCenter HT chassis

  IBM eServer HS21 - 8853AC1

  NetXtreme Broadcom5704S

  2 x Quad Core Intel Xeon E5440 2.83 GHz

  Initially, I installed VMWare Server 2.0 and then upgraded to 2.0.1 to see if that would solve the issue but always without success.

  Event Viewer message:

  Host VMware Agent service terminated with service specific error 4294967295 (0XFFFFFFFF)

  Not tried so far:

  1. I tried uninstalling and reinstalling several times without success

  2. Tried to manually start the VMWare host Agent

  3. Tried the upgrade to VMWARE 2.0 VMWARE 2.0.1

  4. Tried to uninstall and reinstall

  5. Tried to launch the service as ADMINISTRATOR

  It is the only VMWare Server service that does not start... I Googled, and I can't find a resolution to this problem.

  Post edited by: RDPetruska

  Emoticon removed from the subject line.

  Check this solution or search the Internet: "panic error: not well formed (invalid token)" (sorry, I don't have the time to search for you now).

  BTW. If IIS is installed and running, try to stop and start the vmware agent

  J.

  If you have found this device or any other answer useful please consider the use of buttons useful or Correct to award points.

  Post edited by: janlib

• ThinPro with VMware View USB Redirection

  Hi all:

  I'm trying to configure my workstation (t620 ThinPro 5.1 running) to start required services necessary for USB with VMware View forwarding at startup.  I tried to add the command to /etc/rc.local and created my own init.d script, but none of these options automatically launch services.  Run manually /etc/rc.local and the custom init.d script launches the services successfully.

  Has someone managed to get the necessary USB redirection services running at the start?  Any guidance is appreciated.

  Thank you.

  Solved my problem... changed under USB Manager Remote Protocol of VMware View.  Updated this setting caused VMware services to run at startup.

• Direct connection to the view Agent Linux?

  Is there an implementation linux plugin for direct connection from the view of the PicoIP client (I use VMware View on Mac) on a Linux desktop?

  I just wanted to put in place a set of virtual machines Linux to be accessible by customers to view, Mac. Also intend to do not use a view connection server. I installed a virtual machine to test with Ubuntu top end and configure the Agent as well.

  Direct connection is not supported. You must configure a login server in your environment.

• How to fix VMware View Server certificate revocation check connection error?

  Dear community,

  For about 2 weeks, I feel a revocation of the certificate check error in our environment Horizon see 6.2. The strange thing is that, within 12 hours about two (replication) connection servers and the vCenter Server / server of composer (on the same machine) are considered as having invalid certificates, even if, in fact, they are valid (CA certificates). We use no security servers.

  The view admin console shows the following for servers connection:

  The server certificate is not approved.

  The server certificate cannot be verified.

  For the vCenter, he said (that I have validated manually the certificate):

  No problems found.

  Certificate is not approved, but the thumbprint of the certificate is accepted.

  With the connection series on 'full', States that the login server logs for the vCenter server:

  TRACE (B 17-0 - 0E98) < VCHealthUpdate > [NativeKeyVault] validateCertificateChain response: {result = FAIL, EndEntityReasons = cantCheckRevoked, ChainReasons = invalid, SelfSigned = false, EndErrorCode = 16777280, EndInfoCode = 258, ChainErrorCode = 16777280, ChainInfoCode = 256, PolicyErrorCode =-2146885613}

  As far as I can see there no similar entries for login server certificates in the newspaper.

  At the moment I am under the environment with composer and vCenter certificates manually valid and invalid connection (red) server certificates (as view clients and browsers are not disabled).

  I already checked that I am able to do everything 'green' again via setting the registry key 'CertificateRevocationCheckType'2 (as described here Configure the server certificates certificate revocation check). This brings me to the conclusion that one of the intermediate certificates cannot be validated. So, I had the information a "version" of an intermediate (intermediate certification authority) certificate has been revoked. There seems to be no coincidence - like the time point is as well, but this particular version does not appear to be used in the servers of my connection.

  However, even with full logging enabled, I can't information which (intermediate) certificate cannot be validated and why. I expected to see something like 'OCSP verification' or 'check the CRL' but I can't find it in the newspapers. However, I noticed that one of the intermediate certificates lacked the OCSP URL (even if the field "Authority Information Access" existed). Of course I updated the certificate with a version that contains the OCSP URL, but it has not changed anything.

  In addition, I checked manually all of the certificates in the chain with openssl (for OCSP) and CRLs as well, but everything seems to be OK (all URLS are accessible and no opportunity of certificate has been revoked). Actually, I do not interpret the error as "that the connection to the server is an invalid certificate because it has been revoked", but "it cannot check if it has been revoked. The servers do not need a proxy and nothing configured, so (I checked the proxy settings system context, also).

  For now, the problem is not critical, such as 'red' status connection server has no effect on our customers and so I could turn off certificate revocation check (or switch to check that the certificate of the server (2)). But of course, I would really solve the problem.

  Is there someone who can give me a hint on what to check, for example, how do I know which certificate cannot be controlled and why? Someone had the same or a similar problem? Support VMware is working on the problem as well, but they seem don't know is not the problem, either.

  I appreciate the thoughts and responses! Thank you!

  Best regards

  Fabian

  Dear community,

  During this time, I was able to correct the error described at the beginning of this thread. Jump to the end to see what could probably help you...

  1. At first, I installed an additional standalone VMware View Server connection in order to check the following related certificates:
     1. VMware support always told me to renew my certificates because they "were not valid" etc. - even if in fact they were (like external URL calls and attested manual verification and tests).
     2. That's why I created new additional certificates for the login server and configured to include the vCenter even as my production environment - only difference was I didn't inlcude the composer who runs the server vCenter himself.
     3. The result was that the server was "green" including both the vCenter Server certificate which could be 'not reliable' by the environment of production - strange, huh?
  2. After I reset the additional server to a turned wink where connection to the server was not yet installed (before that, I uninstalled the connection to the server in case there is information in vCenter thereon) and reinstalled as a replica of the production environment server. Somehow I expected this, but still quite strange the vCenter Server (and composer) now again was considered "invalid", even if the certificate of the server connection itself considered still valid and green. For test purposes, so I put certifice revocation checking on '2' (only one server certificate check) - but only on the 'old' production servers' and 'magical' everything has been considered valid. So as I see it, there seems to be some sort of information stored on the 'old' connection servers that makes them believe that invalid certificates and that the information is replicated on the third server unless I lower the revocation of the certificate controls on these servers. Altervative explanation could be that VMware View does not accept certificates with aliases that do not include the 'real' server name - that is / was in fact certificates the old servers connection. The new server certificate connection included the real name and the alias. I understand if this is the case, but then I expect that it be documented somewhere (I have not found this information) and also wouldn't understand why it worked without problem for several years before.
  3. After finding that out, I created new certificates for the 'old' connection servers, including aliases and real names and replaced the certificate on one of the servers (and restarted the login server) - only a few successfully. Once I put the revocation checking on '4' again on this server, the login server certificate was still considered valid, but not the vCenter and certificate of composer.
  4. Now, I've uninstalled the old login server (removed from the view) and reinstalled completely (including an update of the 2008 R2 2012 R2 OS) and after I have it reintegrated into the environment, everything remained green - as long I have will activate revocation checking on the second login server "old." This is why I did the same with this (completely reinstalled and reinstated it) and now everything is green with the revocation checking enabled on all replicas of server connection.
  5. The next step I uninstall the additional replica because I created only for troubleshooting purposes.

  So what will no doubt help in similar cases:

  • Reinstall the servers of connection one by one, including:
  • Uninstalling html access (if used), uninstall the login server to view, uninstall 'VMware' AD LDS Instance.
  • Removal of the connection to the server of replication group: run "s - r s uninstalled_ vdmadmin.exeservername" on one of the servers connection remaining.
  • Reinstall/Update OS (may not be necessary, but I did not test that)
  • Reininstall, return to the login server replica. If you used the certificates which included only the alias of the server I recommend you to create new ones, including the name of the server as well, but maybe it's not necessary as well. If you want to keep the certificates which only inlcude the alias it will be necessary to install this certificate after the first replication of the servers (see below).

  My question for technicians of VMware/developers: It is supported to use certificates include only the server alias. Otherwise why it worked before and where is it documented? Where are certificate cached information so that simply replace the certificate was only some, and not a complete success (see above). FYI - when I paired initially replicas that I had to install the CA (including only the pseudonym) after the first replication - now with certificates (including the server name and the alias), I could install the certificate before you replicate (= the login server installation).

• Horizon view Agent 6.0.2 Windows 8.1 desktop - size setting display scale causes mouse which will be pasted in the top left corner

  Hello

  I am having some problems when I try to adjust the size to the scale option in the Virtual Office Windows 8.1 with view agent 6.0.2. When I try to change the scale via Control Panel -> display -> option to change the size of all the items ( view failover control settings is disabled by VMware KB: Settings tab is not available in the display panel of a Horizon view desktop locally when t...). After that, the mouse pointer gets suddenly blocked until the upper-left corner, and I'm unable to move the mouse pointer on this corner that the mouse pointer continues new jump in him. When I change the scale to the original (use the keyboard to change the setting), the behavior of mouse pointer returns to normal.

  Anyone else having this problem?

  Found the solution by adding a registry entry:

  Location: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Teradici\PCoIP\pcoip_admin_defaults

  Name: pcoip.disable_cursor_jumping

  Type: REG_DWORD

  Data: 1

  After that it is defined on the parent image and recomposed (or reboot if you want to set this on a persistent desktop computer), there is no more mouse pointer jumps after changing the scale of the fonts/AC.

  This was indeed listed in KB here — not exactly the problem listed in the KB, but it is quite similar:

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

• VMware View 6.1 Zero-Client disconnect

  We have recently updated our platform VDI of VMWare View 6.1 using vSphere 6.0 and Nvidia vGPU (K1 grid). (HP T310 ZeroClient 4.7.1)

  Some of our users complain disconnects, some users have this error more than others.

  The mouse stops and a disconnect after 30 seconds.

  Here are a few journal entries:

  25/03/2015, 08:42:41.131 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: = > new connection request < =.

  25/03/2015, 08:42:41.131 > LVL:2 RC: AGENT 0: tera_agent_read_external_udp_address: RegQueryValueEx couldn't find the value of pcoip.external_udp_address in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to the server.

  25/03/2015, 08:42:41.131 > LVL:2 RC: AGENT 0: tera_agent_read_external_udp_address: RegQueryValueEx couldn't find the value of pcoip.external_udp_port in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to the server.

  25/03/2015, 08:42:41.131 > LVL:2 RC: 0 AGENT: customer address is 0.0.0.0:0 (order of the host)

  25/03/2015, 08:42:41.132 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: for gentle host: using Version 1 Tag

  25/03/2015, 08:42:41.132 > LVL:2 RC: PRI 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} for gentle host ID of Session: Tag: "W/AenY + In + UA" value: 5bf01e9d8f889fe5

  25/03/2015, 08:42:41.132 > LVL:2 RC: AGENT 0: server_listen_on_addr is 0.0.0.0:0 (order of the host)

  25/03/2015, 08:42:41.132 > LVL:1 RC: AGENT 0: pcoip_agent_connect_req: type = 2

  25/03/2015, 08:42:41.132 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} ID of Session = 4; Codec = 2.

  25/03/2015, 08:42:41.132 > LVL:1 RC: AGENT 0: pcoip_agent_connect_req: backtrace Journal 1

  25/03/2015, 08:42:41.133 > LVL:2 RC: AGENT 0: tera_agent_launch_server: {s_tag:0x5bf01e9d8f889fe5} pcoip_server_win32 launch

  25/03/2015, 08:42:41.133 > LVL:2 RC: AGENT 0: tera_agent_launch_server: path to the logfile {s_tag:0x5bf01e9d8f889fe5} optional specified as "C:\ProgramData\VMware\VDM\logs\".

  25/03/2015, 08:42:41.133 > LVL:2 RC: AGENT 0: tera_agent_launch_server: {s_tag:0x5bf01e9d8f889fe5} use_vmware_launcher = true.

  25/03/2015, 08:42:41.135 > LVL:2 RC: AGENT 0: create_session_process: open pcoip server process handle 00000000000003DC

  25/03/2015, 08:42:41.135 > LVL:2 RC: AGENT 0: tera_agent_launch_server: code {s_tag:0x5bf01e9d8f889fe5} Launcher using VMWare: worked [system is vista or newer, windows session id: 0 x 1, pid: 0x1e4, handful of proc: 0x3dc].

  25/03/2015, 08:42:41.381 > LVL:2 RC: AGENT 0: sSERVER_SESSION::agent_receiver_callback: A:srvr4 message; B:srvr0004 to A:srvr4, message = 00 00 00 00, len = 144

  25/03/2015, 08:42:42.135 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] waiting for ready message.

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] Got ready message.

  25/03/2015, 08:42:42.236 > LVL:2 RC: 0 AGENT: selected server_addr is 0.0.0.0:4172 (order of the host)

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] to connect to the mailbox on the server.

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] sending the session tag.

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 136 bytes

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] sending session option #0 key ='pcoip.enable_tera2800 "value =" 1 ".

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 48 bytes

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] sending session option #1 key ='pcoip.priority_level "value =" 4 ".

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} bytes 47

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] sending session option #2 key = 'pcoip.server_fqdn' value ='PS-VDI-01. PROJECTSERVE.local'.

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 71 bytes

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] end of options: sending message null-option

  25/03/2015, 08:42:42.236 > LVL:2 RC: AGENT 0: sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 26 bytes

  25/03/2015, 08:42:42.362 > LVL:2 RC: AGENT 0: sSERVER_SESSION::agent_receiver_callback: A:srvr4 message; B:srvr0004 to A:srvr4, message = 05 00 00 00, len = 136

  25/03/2015, 08:42:42.388 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] session to add to the list.

  25/03/2015, 08:42:42.388 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] the number of active sessions = 1

  25/03/2015, 08:42:42.388 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] sending ok connection response.

  25/03/2015, 08:42:42.388 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x5bf01e9d8f889fe5} [4] connection_response (end), 0

  25/03/2015, 08:42:42.580 > LVL:2 RC: AGENT 0: sSERVER_SESSION::agent_receiver_callback: A:srvr4 message; B:srvr0004 to A:srvr4, message = 0 b 00 00 00, len = 16

  25/03/2015, 08:42:42.602 > LVL:2 RC: AGENT 0: monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} MBX_CON_COMPLETE

  25/03/2015, 08:42:42.602 > LVL:2 RC: AGENT 0: monitor_soft_hosts: connection_complete {s_tag:0x5bf01e9d8f889fe5}: SOFT - MBX_CON_COMPLETE

  25/03/2015, 08:42:43.645 > LVL:2 RC: AGENT 0: monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} thread of control: connection_complete (MBX_CON_COMPLETE) callback is successful

  25/03/2015, 08:42:43.646 > LVL:2 RC: AGENT 0: mb_send_acknowledgement: {s_tag:0x5bf01e9d8f889fe5} send ACK.

  25/03/2015, 08:42:43.646 > LVL:2 RC: AGENT 0: sSERVER_SESSION::send_message: {s_tag:0x5bf01e9d8f889fe5} 8 bytes

  25/03/2015, 08:42:43.748 > LVL:2 RC: AGENT 0: mb_send_acknowledgement: {s_tag:0x5bf01e9d8f889fe5} srvr0004 Succeeded

  25/03/2015, 08:52:46.565 > LVL:2 RC: AGENT 0: monitor_soft_hosts: {s_tag:0x5bf01e9d8f889fe5} server is dead.

  25/03/2015, 08:52:46.666 > LVL:2 RC: 0 AGENT: tera_agent_disconnect [guest]: close the agent code: 6, disconnect reason: 0

  25/03/2015, 08:52:46.666 > LVL:2 RC: AGENT 0: tera_agent_disconnect: {s_tag:0x5bf01e9d8f889fe5} sign out is * NOT * pending (hndl: 4 pid: process handle 484,: 000003dc)

  25/03/2015, 08:52:46.666 > LVL:2 RC: AGENT 0: tera_agent_disconnect: {s_tag:0x5bf01e9d8f889fe5} server process already stopped (hndl: 4 pid: process handle 484,: 000003dc)

  25/03/2015, 08:52:46.666 > LVL:2 RC: AGENT 0: tera_agent_finish_disconnect_thread: connection_closed 6

  25/03/2015, 08:52:46.939 > LVL:2 RC: AGENT 0: sSERVER_SESSION: ~ sSERVER_SESSION: {s_tag:0x5bf01e9d8f889fe5} closing pcoip server process handle 00000000000003DC

  25/03/2015, 08:53:01.517 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: = > new connection request < =.

  25/03/2015, 08:53:01.518 > LVL:2 RC: AGENT 0: tera_agent_read_external_udp_address: RegQueryValueEx couldn't find the value of pcoip.external_udp_address in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to the server.

  25/03/2015, 08:53:01.518 > LVL:2 RC: AGENT 0: tera_agent_read_external_udp_address: RegQueryValueEx couldn't find the value of pcoip.external_udp_port in the Software\Policies\Teradici\PCoIP\pcoip_admin_defaults key, sending no value to the server.

  25/03/2015, 08:53:01.518 > LVL:2 RC: 0 AGENT: customer address is 0.0.0.0:0 (order of the host)

  25/03/2015, 08:53:01.518 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: for gentle host: using Version 1 Tag

  25/03/2015, 08:53:01.518 > LVL:2 RC: PRI 0: pcoip_agent_connect_req: {s_tag:0x3c5d2733bc4b5aa} for gentle host ID of Session: Tag: "A8XSczvEtaoA" value: 03c5d2733bc4b5aa

  25/03/2015, 08:53:01.518 > LVL:2 RC: AGENT 0: server_listen_on_addr is 0.0.0.0:0 (order of the host)

  25/03/2015, 08:53:01.518 > LVL:1 RC: AGENT 0: pcoip_agent_connect_req: type = 2

  25/03/2015, 08:53:01.518 > LVL:2 RC: AGENT 0: pcoip_agent_connect_req: {s_tag:0x3c5d2733bc4b5aa} ID of Session = 5; Codec = 2.

  25/03/2015, 08:53:01.518 > LVL:1 RC: AGENT 0: pcoip_agent_connect_req: backtrace Journal 1

  New Windows driver is GA and the ESX pilot remained the same so, fortunately, only an update of the Windows driver.

  Link is here.

  NVIDIA DRIVERS NVIDIA GRID VGPU SOFTWARE VERSION 346.68/348.27 WHQL