Overview of VMware View Server

Similar Questions

• Overview of VMware View Client 3.0.0 - cloud icons missing?

  Overview of VMware View Client 3.0.0 build 1887158 - missing icons of cloud?

  After you have installed the Client of the view and adding a new server we do not see the icon 'cloud' over the connection to the server. The link to server connection works and connects - lack just the cloud chart

  

  Any ideas?

  Should look like this...

  

  OK, that explains it. Its a known problem when running in a terminal services session.

  Have no ETA on when it will be fixed.

  Linjo

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

• 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

• Problem in installing VMware View Server connection

  Hello

  As the first step to install the VMware View Manager, I tried to install the connection to the VMware View server on a virtual machine to Windows 2003 Server SP2. This machine is added to a domain under our Windows Active Directory. I can connect to the machine using user accounts that are on the directory to active directory. My problem is that when I try to install the view connection server, I get an error message indicating

  "The computer is a member of a domain, but no server connection was found. Please make sure that the computer is properly connected to a domain and that a domain controller is available before to perform this installation again'.

  Because I can log into the machine using accounts in active directory, I assume that the computer is properly connected in the field. I also confirmed that there is a domain controller in active directory. I tried to do the installation under an account that has administrative privileges for the object active directory, but also a local administrator account. Could someone suggest where I could go wrong?

  Thanks in advance

  Concerning

  Varun

  You have validated that DNS and WINS are configured correctly on the server you are trying to intall the broker for connections on?

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

• Overview of VMware View 5.2 Load Balancing

  Hi guys,.

  I use VMware view Horizon 5.2 and my infrastructure is as follows:

  2 view x servers security

  2 view connection x servers

  Can anyone please guide me how to configure load balancing and what are the best practice Horizon of VMware View load balancer configuration.

  See you soon

  http://pubs.VMware.com/view-52/topic/com.VMware.ICbase/PDF/horizon-view-52-architecture-planning.PDF

  Simply place your load balancer in front of the two security servers. This is indicated on page 70 - figure 5-2.

  If you also want to allow access by internal users, and then add two replicas more connection to the server. This is indicated on page 71 - figure 5-3.

  Your reviews will connect to the alias balanced appropriate load.

  Mark

• Overview of VMware View Client 2.1 crash during the connection to the pool offices

  To Horizon View Client updated to version 2.0 2.1, whenever I try to connect to the pool of offices after the connection to the login server, it remains on the 'connection '. "message for a bit before it crashes. This has been the case regardless of which server the connection that I use. Are there others who is to have this similar problem with the new version of the OS X client?

  Thank you, solgae. Team may have found the cause, so there is a patch which includes patches, could help you to check?

  1. backup of the libpcoip_client.dylib in the directory "/ Applications/Horizon of VMware View Client.app/Contents/PlugIns/PCoIPVMView.bundle/Contents/MacOS.

  2. replace by the task libpcoip_client.dylib.

  3. If this patch does not work, please provide the journal.

  -zhanglin

• 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

• 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

• Problems with the module supplier of personalized identification information and overview of VMware View Client working together

  I have a Horizon of VMware View client that connects me HVD Windows 7. So when I give view client Vmware Horizon my credentials, it auto logs me. I also created a custom credential provider that works on Windows 7 PC. When I install the custom in the HVD credentials provider, it works if I am already connected to HVD and I simulate CTRL + ALT + DELETE. Can I use my credential provider to "unlock" in. However, if I disconnect of HVD and try to connect using VMware Horizon View client to connect to Windows 7 of HVD, it gets stuck on the screen of the tile. I see the VMware SSO user tile but nothing happens when I click it. Then, I use my provider of customized credentials to connect. I expect to bypass my ISP credentials on the first connection and self as before.

  Anyone have any ideas?

  Thanks for your help.

  OK, I did some more troubleshooting and discovered that it was a problem with auto connection set to TRUE on my side of custom credentials provider (I pbAutoLogonWithDefault to TRUE). Since I still like it TRUE, I had originally set it to FALSE and then change for REAL once my credential provider was used.

  Thank you!

• The installation of VMWare View Server program

  Hello

  I have a solution of ESXi, vSphere 5 where I host all my virtual servers with a virtual vCenter Management Standard.  I'm working on that I need for a configuration of VMWare View and I was hoping someone here could help me.

  I have 12 physical blades to host my VMWare View solution (according to the calculations of number of jobs) and I have VMWare View Bundle licenses.

  Ive been reading through the notes and he says that this set comes with an edition of vCenter.

  A few questions:

  My existing vCenter instance should be used to manage the VMWare View host or do I need to install a separate instance of vCenter VMWare View and use the license in the bundle?

  I guess I should install ESXi instances in the beam that will allow me to supply only desktop computers?

  If I have servers connection and composer, should they be hosted in Clusters VMWare View or the cluster of servers existing vsphere 5?

  If this is the case, I also have a question about the network configuration.  When I install the ESXi for VMWare View, will I still have a requirement for a management console, the vmkernel, and the 'Front End' (for users IP address) vnic to the vswitch?

  Another question about the round rbin DNS.  I try to also install Connection 2 and 2 servers of composer whose load is balanced.  Anyone has any info on setting up of Robin DNS?

  Thank you very much

  We use a 6 with network storage based physical NETWORK adapter configuration.

  You will have a default port for management.  vMotion is split to its own IP address, and these two vmkernel ports are on the same vSwitch, with natachasery used by one and waiting for the other.

  iSCSI must be separated from its own vSwitch and pair of NICs as well supported by linked vmkernel ports for redundancy and load balancing.

  This leaves at least another vSwitch and pair of natachasery to the actual traffic of vm.

  -KjB

  Post edited by: kjb007: said vSwitch

• VMware View Server vCentre

  Hello

  I am designing a VDI solution and I have a question about the vCentre server that comes with the view license first.  This is a license fully functional vCentre or a watered-down version that allows to manage only the ESX hosts running vSphere for desktops.  I would have a few regular vSphere ESX hosts to the server infrastructure, vSphere for hosting desktops to virtual desktops, but manage all hosts of the vCentre even.

  Thank you!

  The vCenter Server you get with a view is a regular version, which can be used to display the VM client as well as view (connecting to server.) server infrastructure Use is limited to the above by the EULA (license agreement).

  If you plan to use a vCenter Server as well as your non-View server infrastructure, you need to obtain a separate license for vCenter Server and hosts for non-View systems to be licensed. However, technically, you can manage everything through one instance of vCenter.

  André

• Overview of VMware View Client shows "USB redirection is not available on this desktop computer.

  Hi all

  We try to connect to an RDS Server with std R2 2012 Windows via the PCOIP Protocol, but we get the above error. Does anyone know why this might be?

  Thank you

  James.

  When you installed the agent view you choose the song "USB redirection '? In my view, it is not selected by default in the standard installation and when you activate this feature, he throws a warning that you must accept too much security.

• What NAT ports in the firewall for VMware View Server Security?

  We have a Cisco ASA and I wonder what are the ports I need NAT from the outside to the Security Server?  I'm assuming that port 443, but don't know if this is correct or if maybe other ports must be open.

  Thank you!

  Brian

  This KB should help you, http://kb.vmware.com/kb/1027217.

• Overview of VMWare View 2.3.0 build 1551379 password cached?

  We use HP T510 Thin Windows Embedded Clients joined our network.

  With Horizon view 2.3.0 build 1551379 installed.

  When a user enables its information network identification expires and then changes its Horizon view password then fails Auto connect by using stored credentials.

  If you turn off Auto Connect using the new credentials manually, everything works fine.  If you select then again auto reconnect the logon fails.

  If you change your password before expiration, everything works fine.

  It's only a problem with users who leave passwords expire.

  Is there a way to clear the cached password?

  Or, what is the solution to this problem.

  Thank you

  Dale

  you said "If you disable the automatic connection and manually using the new credentials, everything works fine. If you select then again auto reconnect the logon fails. »

  Indeed, at the time of the automatic deactivation connect and enter the new password, the new password must replace the old copy cached stored password.

  but I think that this replaces only once you have managed to establish a new connection to the virtual desktop. at this point if you disconnect (CTRL_ALT_F12) I think, you should be able to activate auto connect, which will already have the new credentials stored?

  This is the process that you follow, and the new password is not overwriting the old?

  -Chile-