Tag: vsphere

vSphere Update Manager : This product can only be installed on Windows Server 2008 or above

You are trying to install vSphere Update Manager on Windows Server 2012 R2 (whether it is Standard or Datacenter edition) and error appears:

This product can only be installed on Windows Server 2008 or above

image

In addition to this, your environment meets the following prerequisites:

  • The Update Manager server requires a 64-bit Windows system.
  • CPU: Intel or AMD x86 processor with two or more logical cores, each with a speed of at least 2GHz
  • RAM: 2GB RAM if Update Manager and vCenter Server are on different machines
  • RAM: 8GB RAM if Update Manager and vCenter Server are on the same machine
  • Network: 10/100 Mbps
  • Network: For best performance, use a Gigabit connection between vCenter Update Manager and the ESX/ESXi hosts

Cause

Error says that you have the wrong type of OS , but in fact you have to check is your server domain controller or not. vSphere Update manager on a Microsoft Active Directory Domain Controller is unsupported scenario.

References

Installing VMware vSphere Update Manager fails with the error: This product can only be installed on Windows Server 2008 or above (2078069)

vSphere 6 UM: Supported Operating Systems and Database Formats

vCenter 503 Service Unavailable

1. You have just updated vCenter (in my case, VCenter Appliance with PSC 6.0 to 6.0U2)

2. You have restarted vCenter, waited for ~ 10 minutes and trying to open web sphere client

3. Unfortunately,error appears:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7fb16c058ad0]

_serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe)

OR Information message:

The vSphere Client web server is initializing

4. To fix it go to VAMI (https://<vcenter fqdn>:5480) and check overall health status.

vcenter appliance health status

5. To check services manually, enable SSH and BASH from html client

image

6. Or login to direct console (DCUI) and enable SSH/BASH from there

ssh console vcenter

7. Open Putty and connect to vCenter Appliance, type root password and shell

image

8. Check status of services again

image

9. Check vSphere web client service status

service vsphere-client status

10. Try to restart or start service and check status after manipulations

To restart:

service vsphere-client restart

To stop and start manually:

service vsphere-client stop
service vsphere-client start

11. vSphere Web Service should be running and overall health indicator status is green or, at least, yellow

image

vcenter appliance health status 2

12. Try to open vSphere Web Client

Note:  you also need to make sure that there are no issues with DNS and IP allocations in your network (DNS is available, there are no IP duplicates, firewall deny rules and etc.)

References: