Poor performance VMWare View 4.6

We deployed a small VMWare View solution for administrative personnel, accounting and CAD / drafting of users. Currently, we have race 21 VM and received daily complaints about the performance, some days better than others but all well below the level of performance of a desktop computer configured in a way appropriate. We are either duty put an end to the use of the output of this system and return to the standard desktop computers or add an additional server to view VMWare and persevere, we can find the cause of the weak performance of hope.

Here is the specification of

The virtual computer running server:

Dell PE R510, 2 x 6 core Xeon 5670 CPU clocked at 2,933 ghz, 64 GB of memory, TB 1.81 storage Raid 5 using 6-disc 7200 tr / MIN SATA 6 g, NICs 4 x 1 Gbit

Configuration of the VM:

Windows 7 32 - bit, 2 CPU and 3 GB of memory by the system, we have 3 pools Clone related to the installation of specific software for accounting, Admin, and CAD.

I can't see were the loss of performance is. Sometimes the users sessions hang for a few seconds when they choose the various functions in the office or AutoCad, then the system is again significant. Other times the screen quality degrades a bit before clear. For some office programs take an excessive amount of time to load and become available. Sometimes to connect or general file / network access is slow, summary record lists taking extended periods to update or view the content. Sometimes of functions such as print and trace take excessive amounts of time before appear in their respective dialog boxes.

I've attached screenshots of our performance to review statistics. Any help would be welcome.

Hi Matt,

Please provide more information.

On a hardware RAID 5 type 6-pin, your number of IOP on a RAID 5 is about 130 IOPS / s based on an 80% writing / reading of 20% ratio.

You use 21 workstations more than 130 IOPS / s, then you're essentially allowing for 6 inputs/outputs by the office without any room for overhead.

Now, if you have moved to 15K SAS with the same amount of battery, you would end up with a result of 304 IOPS / s based on the same report.

21 offices spread over 304 is 14 inputs/OUTPUTS per desktop, but again, no overhead.

Essentially, simply by moving to 15 K SAS, you more than double your IO, but your RAID set is not optimal.

If you went hardware RAID 10 with the same number of PIN, your IOPS / s would rise to 555 based on the same ratios.

21 workstations more IOPS 555 / s 26 IOPS / sec per desktop computer that comes close to the 30-40 recommended for VDI.

If you can afford to go 8 x 600 GB 15 K on your R510, surprise you pleasently with performance - he would net you have a 740 IOP account

21 offices on 740 IOPS / IOPS 35 s / s by the office which is more in line with the recommendation of VDI.

I mine with a range 40 IOPS / sec per office more overhead, and we have no problem on our end here.

Do not give up, with a little more work and planning, you could end up with a great platform - we use the R510 is there as well and love them.

I hope that helps you, it's a great place to ask questions and get answers.

I'm also on Twitter if you want to ask more questions, more than happy to help you!

See you soon!

Tags: VMware

Similar Questions

  • VMware View 4.6 and vSphere Client performance

    Hello world

    I prepare a demo for VMware View 4.6, a small, with internal disks (3 x 600 GB, 6 GB/s SAS, 10 k RPM RAID 5), network: 100 MB (it was never a problem demos), within IBM x 3650 M3, 32 GB of RAM, 2 x xeon 4 c E5620 2.4 GHz.

    There are 3 virtual machines of Windows 2008 R2 (4 GB RAM and 20 GB disks) and 6 virtual desktops (2 GB RAM) and 30 GB drive XP

    In 10 k RPM there is 150 IOPS / s, so 3 drives x 150 = 450 IOPS / s-> 450 / 9 mV = 50 IOPS / s p/vm. I know that if IOPSp/vm is over 30, it's good, so this seems like a good script.

    I don't know what should I look to find the cause of poor performance.

    VI Client is really slow, and worse even desktop computers.

    Can you guide me to find the problem please?

    Thank you!

    Your latency of storage time seems a bit high, how the store looks like it? Possible alignment issues?

    You have a lot of CPU resources, I'd give workstations an another vCPU.

    Linjo

  • 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

  • With VMware View Server using LDAPS (port 636)

    I've been responsible for something that seems impossible/not supported.

    VMware View Server uses port 389 for LDAP.  My task is to do view to use instead the port 636 (LDAP over SSL).  The accusation is that the replicated servers in VMware View data not encrypted between other on port 389.

    So far in my quest, I did no progress in this project.  However, I was able to test that manual connections can now be performed (with ADSI Edit) with port port SSL 636 other replicated servers view.  Problem is that the view seems to have hard-coded to use port 389 and cannot be moved to use LDAPS.

    There are instructions to do something like this in vCenter (http://www.vstable.com/2012/01/27/vcenter-5-active-directory-web-services-error-1209/) (Security Virtual Lab: & amp; nbsp;) Architecture - Blog - proSauce), but nothing related to the sight of the surfaces in a Google search.

    Someone at - it have a Yes or whinny if possible?

    EDIT: Moved to the correct community.

    It is not easy being responsible for something impossible!

    Connection view servers have an AD LDS instance, and replication between servers using the AD LDS replication. This is a replication mechanism secure by using the replication RPC, LDAP and Kerberos and secure without having to implement LDAP over SSL on 636.

    The articles you refer to are actually on the definition of a port number unused LDAPS access of Web Active Directory Services with vCenter Server to get rid of an event without danger. It does nothing to do with replication between LDAP servers. View prevents remote access Active Directory Web services anyway with a specific firewall rule so that remote users have no access to it.

    The only reason why you can use LDAPS with AD LDS is if you support simple LDAP connections. The use of SSL would mean that the simple bind passwords are not sent in the clear. In the case of the view, simple LDAP connections are not enabled in any case.

    In summary, what you're trying to do is useless.

    Mark

  • VMware View with mixed processors on hosts

    Hello

    I have a client with an existing vmware view environment. the hosts are of 3 years older AMD servers, which will be replaced in the coming years.

    because of performance, we will move from AMD to Intel.

    We have a picture of office of parent in a floating pool automated with linked clones.

    When you start windows on a new processor architecture, you will receive a message that the hardware has changed a you must restart.

    So the question how it reacts, when using quickprep.

    everyone experiences with that? This working group or failure of deployment process?

    Greetings from vmworld Barcelona

    Ah, I see. Yes, once the Parent virtual machine was launched on the new hardware, the two processors exist in Windows. Windows clean up one old is why it stays in place which prevents the message from appearing again.

    -Mike

  • Overview of VMware View PCoIP

    Hello

    We have a test lab test view VMware Horizon on a test environment however we find that the following questions.

    When is connected through the vmware view client, enter the user name and then select on the desktop, we find that the following two errors:

    he tries to connect to the desktop computer, then we get a black screen, then a prompt that shows the end of the connection to the remote computer.

    The other mistake that we get is "the Protocol to display for this office is currently unavailable, so if we click try again we get the black screen and then the same error message ended with the connection to the remote computer.

    If we choose RDP, it works.

    This configuration is configured as follows:

    (material f/w)                                      (Win7) (Windows Firewall)

    Client application VMware > > > Firewall > > > > connect to server > > > > Virtual Office

    Firewall hardware ports 443 has sent to the login server

    Hardware firewall has ports open 4172 server to connect to the virtual desktop

    Virtual office has ports open virtual desktop to connect to the server of 4172

    am I missing something?

    What we are seeing with RDP, is that she's bad performance on YouTube and by displaying the web

    Hello

    Looks like your firewall rules are not configured correctly.

    Please refer to this doc and set the rules http://communities.vmware.com/docs/DOC-14974

    Concerning

    Noble

  • Problemas con vmware view 4.1 y terminales EVGA 'pcoip '.

    Hola todos,

    I hope to be escuentren very well

    Tengo una consulta en mi tengo vmware virtual center 4.1 entorno y vmware view 4.6

    Estoy put changing Terminal wyse working RDP por q a q el performance pcoip terminals are mucho mejor

    Tengo problemas con some las teminales cuando intentan a1 pcoip an Office Máquinas con esta version of vmware tools "vmware, Inc. product version: 8.3.17.15269, en todas estoy using esta version of officer discovers 4.6.0.366101.

    El problema're q despues el usuario type is the clave para a1 al servidor view appears una pantalla negra como por 5 segundos y despues devuelva has the pantalla inicio donde No. conectamos con el conexion server.

    If yo misma pcoip terminal uso para conectarme a otra Máquina virtual q tiene otra lower vm tools version has the 8.3.17.15269 TR conecta sin problemas. por lo q the diff q veo unica are the vmtools una Máquina a otra... pero todas no is como eso porq I have did a cluster con unas 60 vm con esa version of vm tools. Esto solo pasa con las pcoip terminals porq TR uso una wyse normal con esta version of vm tools 8.3.17.15269 if works

    Saludos,

    Hola Warrenjc

    Te cuento than amendments nosotros y paso el tema esta originado in el orden en what instalan drivers, vmware tools y officer see.

    Well as h. para y no tengas problemas you recommend respetes a raja tabla el orden of deployment of same segun lo indica vmw.

    ES decir.

    1. Instalar the vm.
    2. Instalar vmware tools.
    3. Agent view instalar.

    Fijate if asi you works adecuadamente.

    If haces algun cambio a nivel parches, plots etc, to be replaced by Recomiendan desinstalar todos los compontentes y volver a instalarlos en orden.

    Espero esto resuelva you question.

    Diego Quintana

  • VMWare View slow slide windows when you use two monitors

    I am experiencing very slow slide of windows from one monitor to the other when using VMWare View Client. I followed all the documentation on configuring dual monitors in VMWare View and I removed the background images, Windows 7 Setup, configure the video settings for better performance. Not sure if I'm missing something. Help, please.

    Hi Joshua,.

    Here are KB which may help you if you have not seen that.

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

    Concerning

    Mohammed

  • Deleting events in VMware View administrator

    Hello

    How can I remove events in the administrator of the display (here I have the version 4.6)?

    Due to a configuration problem now I have the same error over 3,000 events, and I'd be happy if I can delete them.

    Kind regards

    André

    You might be able to delete directly from SQL, using the events and event_data tables in the case of database.   I found th informaton below on page 10 of the guide to integration of VMware View.  I want to backup my database of events before performing any manipulation.

    VMware View provides details on all tables of database events. After a certain period of time elapsed

    Since writing to event record, VMware View deletes the record of the event, and event_data tables. You can

    Administrator display allows you to configure the period for which the database maintains a register to the event and

    tables of event_data. See the

    Installation of VMware View document for more information.

  • 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.

  • 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

  • Migrate to VMware View 4.6

    Hello

    What are the exact differences between VMware View 4.6 and 4.5.

    What operating system supports VMware View 4.6?

    Do we get the best performance with VMware View 4.6 on WAN?

    Note that 4172 between the connection to the server and security server is not necessary. The correct rules are here - http://www.vmware.com/pdf/view-46-architecture-planning.pdf - there is an entire section detailing "for servers security DMZ Firewall rules. See also http://communities.vmware.com/docs/DOC-14974 for the three steps needed to implement.

    Also note that https is the default value for the configuration of the Security server for interaction with the normal client and the secure tunnel (https).

    Select this option.

  • VMware view Administrator console... increase timeout

    Hi guys

    just migrated to view 4.5 and everything was fine...

    Is it possible to increase the limit of the Vmware view admin console timeout? I would have the dashboard always on my 2nd screen without going all day logon due to delays...

    Thanks

    Very well, you can do this by following these steps:

    Go to: Display Configuration > global settings > check Activate the automatic updates.

    You'll notice that the heading aid next to him said: "the idle session timeouts not happen when automatic updates are enabled, causing the Administrator display to remain active until the browser is closed or an explicit logout is performed."

    This will allow you to follow the Administrator display without waiting times. (And you don't forget to lock your workstation when you leave your desk anyway, so you should be fine. )

  • Android apps have poor performance

    I have several applications created for Android and all my folios seem poor performance on android devices. It takes a long time for any article to focus on the text (all sheets are built using PDF), and there is a significant for interactivity in a Folio delay, if it does not crash the app entirely. Has anyone else had problems with Android apps? I have not read a lot of useful information on them.

    All my applications are built for android with the dimensions of 2048 x 1536 to make them readable on the Nexus-10. All applications have been rebuilt with v27 and PDFS.

    I'd appreciate comments you can give.

    Thank you

    One thing that can help with the Active Viewer is to design to a smaller size (1024 x 768, for example), use a PDF object and the viewer intensify folios to fit larger screens. Put scale up to adjustment is supported in our 28 Viewer version of AIR and it makes a big difference in performance while maintaining the reasonable quality of the assets.

    Neil

  • VMware View 3.1 &amp; WYSE V10L - display refresh problem

    Hello world

    We are just in the middle of a VMware View 3; 1 deployment using new WYSE V10L thin client. We seem to have a bit of a problem with the screen refresh rate. Let me explain better (and just to the preface, the dorsal VMware environment runs VI 3.5 on 5 nine HP blades and a NetApp SAN.) The entire network is running Gigabit as well)...

    I don't know if it's just a limitation of the RDP Protocol, but a few of us working on the project need some checks. Basically, a session running on one of these WYSE Terminals it looks like the screen is choppy and the refresh rate of the screen is mediocre. Just regular browsing (scrolling up and down on a Web page) seems to be quite rough as well. Just to give you a comparison, if he were an ordinary PC, I would say that it didn't install the correct display driver. Even simply minimize windows seem to be trolling and the display seems wrong to draw images of the session. You would think that we ran in a remote office WAN, hundreds of miles away. But they were just on a local network (with no sign of any claim/network latency that we see).

    I hope I explained it well enough for you guys to understand. We expected just the performance to be a bit better from a point of view to display. But maybe we ask too through a regular session of the RDP. I'm hoping that someone has faced a similar problem and then I help (or tell us that this is the best we can expect). Of course, it is difficult to really see what I want to say without seeing the problem with your own eyes. Any help would be appreciated.

    Thank you, guys.

    gqstyles55

    gqstyles55, any update?

Maybe you are looking for