Implementacao Vmware View

Similar Questions

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

• Installation of VMWare view client issues with 64 bit Win8

  Hello

  I am trying to install VMware view client to access my VDI but I get the error message below... tried to install different products VMware, that nothing has worked... pls help.

  

  Its best you post your question in the following forums:

  Welcome | VMware Communities

• Test environment for VMware View 7 - PCoIP Protocol does not work properly

  We test VMware View 7 with as many Thin Clients and customers zero (Teradici)

  When we try to connect via RDP Protocol, it works fine. When we try to connect via the PCoIP Protocol, desktop display seems to blink (about 2 times per second) and display resolution is not acceptable. So, there is a problem with the Protocol (broker or Office VM)

  There are no firewall in the middle.

  Desktop virtual has a clean install.

  So... anyone have the same number? or similar?

  How much video Ram?

  You can increase the video Ram.

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

• VMware VIew 6 (PCOIP): Windows Client and web browser connects, Android and Ubuntu - don't

  Hello colleagues!

  VMware Horizon Client 3.4.0 build-2769709

  VMware View 6.1.1 construction-2769403

  VMware vSphere 6.0.0 2776511

  That's what's wrong: used SecurityServer and connecting to the server. External connection - via a router. When it is connected to a vmware PCOIP Protocol (Internet) outside of the view with a Windows client and a web browser, it works fine. But when connecting from Android or Linux (Ubuntu 14) load the desktop does not occur. Android immediately displays the message 'connection to server lost', Ubuntu delivers all messages - I'll be back on the screen to select a pool table.

  Which connection via MS RDP connection protocol is correctly to all customers.

  In the settings ConnectionServer in PCOIP Security Gateway set up the external address of the router.

  Redirect them router ports:

  -TCP 80,443,8443,4172,32111

  -UDP 4172,32111

  Any ideas?

  In security settings server in 'URL of PCOIP' was FQDN, but it must be the IP address.

• Names of certificate VMware View 6.1

  Hello world!

  I intend to install vmware view 6.1 with two connection on the LAN Server and security server on the DMZ.

  I wonder what names I need on the certificate?

  my login server names will be VDI1. MyDomain.Local, VDI2. MyDomain.Local

  my security server will be VDI3 (not domain joined server)

  my file on my public DNS is seen. Mydomain.com that guide to the Security server.

  I have internal CA server that can issue the certificate for VDI1. MyDomain.Local and VDI2. MyDomain.Local.

  I have a wildcard certificate for *. Mydomain.com (it does not contain one of my internal server names)

  
  

  1. can I use my wildcard certificate to connect to security without needing a server error?

  
  

  2. where should I install the generic cert? on the Security Server and all servers connection?

  
  

  3. what happens if I want to connect to internal network VDI do I have to install my certificate of internal CA with the internal names to my connection servers?

  
  

  4. because my login server will be connected both internal external, it uses internal cert (VDI1/2.MyCompany.local) for internal connection and external cert (*.) Mydomain.com) for external connection?

  
  

  
  

  Thank you.

  
  

  Taylor.

  I do not recommend to use a certificate with wildcards on connection servers.

  Instead, you can issue a certificate for each connection to the server: VDI1. MyDomain.Local and VDI2. MyDomain.Local

  In this way, the connection will be reliable when connection from inside.

  On the internet you connect on the server for security only, so you only need a trusted certificate installed on the Security server.

  If you issue a certificate from your CA, it will work but the clients that connect from the internet will not approve this certificate.

  If you want a certificate approved by anyone connecting from the internet, you must purchase a certificate of a CA like verisign etc.

  In both cases, the certificate must be issued with name: see . Mydomain.com and installed on the server for security only.

  Hope this helps

  Kind regards

  Claudio

• VMware View vGPU pool remote control software

  Hello!

  Normally, we used Dameware for remote control of our CAD user. But in a pool of VMware View, Dameware should not be used, the support has informed us.

  All other pools we used the VMware console, but it does not work with a vGPU.

  What is ofically supported and tested by VMware?

  Best regards

  Joerg

  News Info: Vmware supported Dameware, now!

• Disable the protocols and encryption algorithms in VMware View connection server and security

  Hello

  In my recent deployment, I had a customer request to disable some protocols and encryption at the Server VMware View connection and security. I read some articles and found that this has been achieved by editing the locked.properties file. But when we have edited and replaced the file, users could not connect to the virtual desktop, so came back to us backwards and desktop computers worked fine.

  I found a few articles that we don't need to edit the locked.properties file in VMware view Horizon 6. If someone has done this please guide me through. Here are the details of the protocols and encryption algorithms that should be disabled

  Diffie-Hellman key

  Enable SSL v2/V3 and TLS 1.1 and 1.2

  Disable the RC4 encryption algorithm

  Select the secret of transfer (if possible)

  
  

  VMware view 6 is the connection to the server and security server.
  

  
  

  Thank you.
  

  Hello

  I implemented the following steps (from the manual):

  1. update the JCE policy files to take in charge the high-strength Cipher Suites

  You can add some cipher suites of high resistance for greater assurance, but first you must update the local_policy.jar and US_export_policy.jar files to each server instance and the security strategy for JRE 7 see connection to the server. You update these policy files by downloading the files to extend JCE (Java Cryptography) unlimited strength political jurisdiction from the Oracle Java SE download site 7.

  If you include some high-strength cipher suites in the list and you do not replace the policy files, you cannot restart the VMware view Horizon connection to the Server service.

  Policy files are located in the directory C:\Program View\Server\jre\lib\security from VMware.

  For more information on the download of the JCE unlimited strength jurisdiction policy 7 files, see the Oracle Java SE download site: http://www.oracle.com/technetwork/java/javase/downloads/index.html.

  After you update the policy files, you need to create backups of the files. If you upgrade the instance of the view connection server or security server, any changes you have made to these files can be replaced, and you may need to restore the backup files.

  2. the changes that policies of global acceptance with ADSI Edit

  • Start the ADSI utility on your computer see connection to the server.
  • In the console tree, select Connect to
  • In the selection or type a unique name text box or a naming context, type the unique name
    DC, DC = vdi is vmware, DC = int.
  • In the type or select a text field or the server box, select or type localhost: 389 or the name of a fully qualified domain (FQDN) of the server computer to connect to port 389 followed view.

  For example: localhost: 389 or mycomputer.mydomain.com:389

  • Expand the tree of the ADSI Editor, OU = properties, select OU = Global, then select OU = common in the right pane.
  • On the object CN = common, Global = UO, UO = properties, select each attribute that you want to change and enter the new list of security protocols or cipher suites.
    I used the following settings:

  EAP-ServerSSLCipherSuites: \LIST:TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256

  EAP-ServerSSLSecureProtocols_ \LIST:TLSv1.1,TLSv1.2

  It is not the highest possible, but they work with all the features of our customers.

  • Restart the service of VMware view Horizon connection server (server connection and security).

  This is not Activate secret transfer (if possible) , but other points are covered.

  If anyone can give a tip to activate the transfer secret, I would be grateful.

• 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

• Overview of VMware VIew Client for Linux

  Hey everybody

  Is there a table of software compatibility for VMware View Client and Linux Horizon? We would like to use the client on devices based on linux, but we do not know what linux operating systems are currently supported.

  Dou you have a formal link or are you aware of the compatibility?

  Best regards

  Documentation (https://www.vmware.com/pdf/horizon-view/horizon-client-linux-document.pdf):

  Operating systems: Horizon customer 3.2 supports the following operating systems.

  Operating system	Version
  Ubuntu Linux	12.04 or 14.04
  Red Hat Enterprise Linux (RHEL)	6.5
  SUSE Linux Enterprise Desktop (SLED)	11 SP3
  CentOS	6.5

  IMPORTANT only 32-bit systems are supported.

  * Horizon customer 3.1: 32-bit Ubuntu Linux 12.04 or 14.04

  * Display Client 2.x: Linux 32 bit Ubuntu 12.04

  * View Client 1.6 and 1.7: 32-bit Ubuntu Linux 10.04 or 12.04

  * Display Client 1.5: 32-bit Ubuntu Linux 10.04 or 10.10

  VMware customer Horizon for Linux Release Notes

• Installing the Server VMware View Composer

  Hi team,

  Need help,

  I'm trying to install VMware View Composer server but I can not create my ODBC connector, can you pls help me to do this task.

  I get this error message

  

  (1) to connect to the database and the new query

  use 'ViewcomposerDbName '.

  exec Sp_changedbowner 'viewservice.

  (2) the right of the database and allow the sql and windows Authetication

  See the screenshot

  (3) lFailing Stil? Go to, click on Sql Server for management (on the left side) > Sql Server Logs > current view them if it connects

  It should be

• VMware vs vmware view vs. horizon wdm

  Hi dear friends

  I need to know what is withholding wdm of vmware with vmware view with view horizon (features, tools and technical sheet)

  If there is this a document please show me

  They are essentially the same product, with more recent versions (which contain additional features) coming out under a slightly different name - the order you listed them is also the order of the liberation. VMware VDM has been renamed to VMware View, and when it is included in the Suite of the Horizon, it was changed to Horizon of VMware View. Why do you specifically, the licensing options?

• Several areas in the Horizon of VMware View AD

  Hi guys, I want to test creating Pools with 2 Active Directory domains. I have set up my environment as follows:

  
  

  Domain A

  
  

  1. connecting to the server

  Server 2-composer

  3-Security Server

  4 - vCenter Server

  
  

  Domain B

  1. connecting to the server

  2. created a separate account to View Composer

  For now seen Horizon 5.3.2 is fully functional on the field. But I need your help deployment pool using domain B. After you have configured the connection Server (joined to Domain B), I tried to add domain B by using view composer account by logging in to view Admin(Domain A) > Edit vCenter Server > change display composer settings > check server information (under Domain) but I'm 'Bad domain name.

  
  

  You guys please help or send me a link of approval one way of installation which is required for VMware View, so that I can deploy Pool using domain B.

  
  

  Without creating confidence, I added redirector conditional field B on the field which allow me to add domain B without "Bad domain name" pop up. But I don't know what to do next. Anyone can guide me please.

  
  

  Concerning

  Hello

  I've done below the configuration to create 2 different pools where VM is joined to 2 different domains.

  I have Domain A and domain B, having 2 confidence way configured by the AD team.

  I sent 3 win 2 k 8 Server and added to the field.-a. On a single server, I installed vCenter & composer on one server I installed the login server & the other I did the Server fall back to the existing connection server.

  In connect to server, I added vCenter & composer. I have 2 different users who have domain join rights in Domain A and domain B.

  Domain-A\abcUser

  Domain-B\xyzUser

  I added above 2 users in the view composer under domain settings. PFA.

  When creating a pool, in the comments tab customization for users of domain-A, I chose identifier of domain-A\abcUser machine Domain-A and the AD container, which is present in Domina-A place machines.

  for domain B user created another pool, and tab customization of comments, I chose domain-B\xyzuser and the AD container that belongs to the domain B to place machines.

  If you want to add a different machines, you must not deploy a connection/replica server in each domain. Just add the ID domain user under domain composer view tab and choose the right ID when creating the pool.

• Is it possible to remove the disposable disc to a pool configuration in VMware View?

  I would like to remove the option of disposable disc several persistent pools in VMware View Horizon 5.3.1 (where virtual machines are already using disposable disks); However, there doesn't seem to be a way to do this in the options of the pool. Is it possible to remove the disk otherwise option or should I remove the old pool and create a completely new without this option enabled?

  I used disposable disk option seems to be to save storage space, but I discovered that disposable disks have been updated only when displaying launched a turning off the virtual machines in the pool (which never happens). I thought that disposable records updated each time that a client shutdown/restarted the VM... but which is not the case. Given this information, I would like to stop using disposable disks as they really may not confer any advantage the way our persistent virtual machines are configured.

  Thanks in advance for any help!

  OK, you're right... only the drive letter customization is allowed.

  Now to answer your question, the one and only formally is to remove the pool by archiving all disks persistent (user data disk), and then create a pool with the same name (but without SDS).

  In addition, select all the archived UDD and then click on, "recreate". All new desktop computers will be recreated with the new spec,

  Another way (not officially committed / not sure of its effects)

  EAP-SVIVmPersistentDiskSpec entry will be there to ADAM OR = database server groups (VMware KB: connecting to the Database View ADAM)

  This entry will be there for disposable system that has a parameter "DiskUsage is SystemDisposable".

  Upron deleting the corresponding entry * may * end configuring don't not the SSD for the supply of others.