Problem in installing VMware View Server connection

Similar Questions

• I can't install vmware view without a second server?

  I am really new to server management. When I tried to install VMware View Server connection I got an error. He said

  A controller of Active Directory (AD DC) domain to the "local" area could contacted could.

  Ensure that the domain name is typed correctly. If the name is correct, click details to correct that information.

  I also read somewhere that you can not install vmware view on the same Active Directory domain controller running server. Is it possible to install vmware view without going through a second server? If so, how?

  You may first have to install ESX/ESXi in your server.

  • After successful installation, connect to the respective client server using vShphere.
  • Try to create 3 virtual machines and install Microsoft 2 k 8 operating systems.
  • The first virtual machine, you can use it as Server Active directory micorsoft.
  • Then you can you use it to vCenter server.
  • Third one you can use for connection server vmware view.
  • You may need to create two more additional, as virtual machines VMware view comments and the other as a client of the view. You can either install windows XP/windows 7 for the VMS in the thesis.

  As already mentioned in messages, you can view VMware View Installation Guide for more details.

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

• Cannot install VMWare View connection Server 5

  Hello

  In order to try the VMWare View 5, I have the program installation and 2008 R2 SP1 virtual server on which I am trying to install VMWare View connection Server 5.

  The server is a complete new installation with only the Active directory (and DNS) installed.

  Everything I try, I keep having the following error:

  This product can only be installed on Windows 2003 or Windows Server 2008 64 - bit. Other operating systems are not supported

  I went through the community forum, but the I have not found my solution to the problem of the forums.

  Kind regards

  Nick

  The broker for connections cannot be installed on a server that is running the role of AD.

  Sent from my iPhone

• Problem with instalation VMware server 2 on Debian Lenny (linux-image - 2.6.30 - 1-686. bpo)

  Hello

  I have problem with instalation VMware server 2 on Debian Lenny (linux-image - 2.6.30 - 1-686. bpo). The problem appears in the last step of the instalation during construction of the vmmon module I installed VMware server 2 on Debian Lenny (linux-image - 2.6.26) according to http://www.howtoforge.com/how-to-install-vmware-server-2-on-debian-lenny and Vmware has worked well. Now, the instalation ends with the following output:

  Extract the sources of the vmmon module.

  The construction of the vmmon module.

  Using 2.6.x kernel build system.

  do: enter the directory ' / tmp/vmware-config1/vmmon-only '.

  do /lib/modules/2.6.30-bpo.1-686/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. modules of

  make [1]: Entering directory ' / usr/src/linux-headers-2.6.30-bpo.1-686'

  CC /tmp/vmware-config1/vmmon-only/linux/driver.o

  In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:31:

  /tmp/vmware-config1/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait '.

  /usr/src/linux-headers-2.6.30-BPO.1-common/include/Linux/poll.h:67: error: previous declaration of 'poll_initwait' is here

  /tmp/vmware-config1/vmmon-only/Linux/driver.c: in function 'LinuxDriverSyncCallOnEachCPU ':

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1423: error: too many arguments to function 'smp_call_function '.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c: in function 'LinuxDriver_Ioctl ':

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid '.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid '.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-config1/vmmon-only/Linux/driver.c:2007: error: too many arguments to function 'smp_call_function '.

  make [4]: * /tmp/vmware-config1/vmmon-only/linux/driver.o error 1

  make [3]: * error 2

  make [2]: * error 2

  make [1]: * error 2

  make [1]: leaving directory ' / usr/src/linux-headers-2.6.30-bpo.1-686'

  make: * http://vmmon.ko error 2

  make: leaving directory ' / tmp/vmware-config1/vmmon-only '.

  Unable to build the vmmon module.

  For more information about how to troubleshoot module, please

  visit our Web site at " " http://www.VMware.com/go/UNSUP-Linux-products "and "

  " http://www.VMware.com/go/UNSUP-Linux-tools ". "

  The execution is canceled.

  I appreciate all ideas of solution to this problem.

  Thank you Pavel

  Your kernel is NOT linux-image - 2.6.26 but (of output) 2.6.30 - bpo.1 - 686

  See this page for a fix possible (the problem is common also for workstation):

  http://www.insecure.WS/2008/10/20/VMware-specific-specific-55x-and-kernel-2627

  Or see this thread:

  http://communities.VMware.com/thread/188410?TSTART=0

  André

• 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

• Installation of the SDK to allow VMWare View to connect to VC - how?

  Hello

  I installed the server VMWare View connection, but when I try to add my VC, I get a connection error. I checked the firewall ports and traffic becomes to my VC so I don't think that's the problem. I checked the event log on the server VMWare View connection and try to connect to http:// < virtualcenter >: < port > /SDK

  I guess this way tells me that I need to install the SDK. I downloaded it, but the installation instructions are not clear, and I find nothing in the installation guide for VMWare View to help me.

  Can someone advise or give me a detailed guide on what do I do?

  There is nothing to install. The URL... / sdk will give a 404 error, it is not used as-is. For example, I've seen configured to point to the VC:

  Server address: vc.mpryor.int

  User name: administrator

  Password: *.

  Connect using SSL: true

  This will save the URL https://vc.mpryor.int:443 / sdk in ADAM and use it. Navigation it will give me a 404 error, but I assure you that I'm using without problem.  You must have a network issue - check firewall, proxy server (for the machine, not your user account) and DNS.

• Can VMware View - I connect with Microsoft RDP?

  Hello world

  Can I connect via the Microsoft's RDP client Vmware View environment? No view, just Microsoft RDP client. I have a thin client model and just support Microsoft RDP Protocol. I want to connect environment seen through this customer.

  Thank you.

  Grosbois

  You MUST have a client of VMware view. Then you can connect through it to view desktop using PCoIP or RDP Protocol.

  You will be able to connect to the desktop using RDP display if your thin client is located in the same subnet (and if RDP is enabled on the desktop to view server and you know its ip address) but would not use vmware view (if you want to connect directly to your desktop from RDP Why would you need to notice), which would also directly access to a machine as you access all the other Windows VM.

  And its always advisable to disable direct RDP on view desktops.

• You must use view client for windows to access view server connection"

  When I go to my security on the outside, I get a message in 5.1, but 5.0 would simply run the installation of the client.  Is this new 5.1?  "You must use view client for windows to access the server view connection."

  Well Yes new feature. Is VMware view Client unbundling

  Take a look at

  http://www.VMware.com/files/PDF/view/VMware-view-evaluators-Guide.PDF

  from pg 87

  On page 88, he says

  Portal of the view on the login server see the landing Page

  The URL root view connection server is hosting a view portal or download customer portal, as the default value, the destination page. The page contains instructions to launch an existing customer of the view and a link to a download page to the VMware.com website that contains a client compatible with the detected operating system version.

  The portal of the view is more directly initiates a Client installation view, but instead allows the user to manually call the installation process.

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

• Cannot install VMware vCenter Server on a virtual machine

  Hello world

  I'm new to the forum. I try to install the vcenter server in a virtual machine.

  Configuration of the VM: 10G VMDK, used 7G... 2G memory... guest operating system is win XP Pro.

  When I run the Setup it says:

  This installation package could not be opened!

  I have attached a JPG of the error. Can someone please!

  Kind regards.

  64 bit is not supported as a host to vCenter operating system, see the compatibility guide posted above.  I would try to mount the ISO using the client machine instead of starting from the ESX host, it could be that your DVD image is not good.

• Reconstructed View Composer databases, view server connection problems

  I had to go back to a previous snapshot on my SQL database server that was right before I installed the database to View Composer.  Mode to connect to the server, there is a pool for the related clones.  How can I remove the pool?  When I try to delete it, I get an error that I do not remember the hand, but basically it has to do with the fact that see connection to the server could not find the swimming pool in the database.  Any ideas?

  You would need to connect via ADSI Edit.    Check out this KB for instructions on how to remove obsolete work and clones, http://kb.vmware.com/kb/1008658positions.   This should give you an idea on how to connect to the ADAM database and navigate.

• Install VMware View Webclient

  Hello everyone,

  when a user tries to conenct the first time with our view security server (for example https://10.10.10.10) and connect, to say that he had to install the client from the view, when he gets prompted it to do so, the system to say, he needs to have administrive rights to install the client.

  How can it be installed as an admin on this machine?

  
  
  MCP, VCP

  Keep in mind if you upgrade after that users will be asked to upgrade their client or continue to use the former client.   It might be useful to inform users not upgrade.

  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 Server

  Hello

  My view Horizon 5.3.0 Server ws_TunnelService.exe uses ipv6 I did not allowed.

  I was wondering if I could disable or y at - it another way to deal with it?

  I tried to disable ipv6 setting in the windows registry, but ws_TunnelService.exe always uses ipv6 traffic.

  Hi all

  The question can be solved by editing the registry of Vmware---> JAVA_OPTS

  Add inDjava.net.preferIPv4Stack=true

  Kind regards

  HiangLeong