Home > Blogs > VMware vSphere Blog > Tag Archives: vSphere Web Client

Tag Archives: vSphere Web Client

vCenter Server 5.5 Update 1 Released

As hinted throughout most of the day, the vCenter Server 5.5 Update 1 has been publicly released this evening.

vCenter Server 5.5 Update 1 | 11 MAR 2014 | Build 1623101
vCenter Server 5.5 Update 1 Installation Package | 11 MAR 2014 | Build 1623099
vCenter Server Appliance 5.5 Update 1 | 11 MAR 2014 | Build 1624811

Whats New

  • vCloud® Hybrid Service™ vSphere® Client Plug-in, is now available in vSphere Web Client
  • vCenter Server is now supported on Windows Server 2012 R2
  • This release delivers a number of bug fixes

Full release notes can be found here

Download bits here

Getting ready to upgrade production to vCenter Server 5.5? Make sure you’re using the correct deployment option

Over the last few months, many customers have been testing and familiarizing themselves with vSphere 5.5 however deployment into a production environment is usually stalled until the availability of the first update or service pack. As we are nearing the typical time frame of when such an update or service pack may become available, I wanted to share some findings that may affect your deployment selection of vCenter Single Sign-On when deploying or upgrading to vCenter Server 5.5

During the installation of vCenter Single Sign-On server you are asked on the deployment option of the vCenter Single Sign-On instance. Below is the intended use case for each deployment option.

SSO#0

Continue reading

When to Centralize vCenter Single Sign-On Server 5.5

While VMware highly recommends the deployment of all vCenter Server components into a single virtual machine (excluding the vCenter Server database), large enterprise customers running multiple vCenter Server instances within a single physical location can simplify the vCenter Single Sign-On architecture and management by reducing the footprint and required resources and specify a dedicated vCenter Single Sign-On environment for all local resources in each physical location.

For vSphere 5.5 the VMware recommendation is to centralize vCenter Single Sign-On when you have 8 or more vCenter Server instances in a given location (this is a soft recommendation).

Centralized vCenter Single Sign-On Architecture


Figure 1: A Centralized vCenter Single Sign-On Server environment

There can be increased risk when centralizing a vCenter Single Sign-On server (to why it is not recommended for smaller environments) due to the increased number of components affected if the vCenter Single-Sign-On server was to become unavailable, in short all vCenter Server components of all vCenter Servers registered will incur authentication loss (when compared to  just the single vCenter Server instance when installed locally) and so availability of the vCenter Single Sign-On centralized server(s) is highly recommended. Continue reading

Load Balancing vCenter Single Sign-On

One question that we often get from customers is how to load balance SSO. While we do have documentation and support for setting up Apache to load balance SSO many customers already own a load balancer or do not wish to use Apache.
Continue reading

PM Research: Managing Content with vCenter(s) – Quick Survey

As an admin in the data center, you have to

  1. Ensure that your VM templates are up to date
  2. Maintain a set of scripts for customizing the guest OS’s, installing custom applications, etc.,
  3. Share all of them across sites and vCenter instances.

Therefore, we at VMware are trying hard to provide you with a simple and efficient solution to manage your VM templates, scripts, ISO images, etc. – collectively called “Content”.

We now need your input to ensure that we understand your current infrastructure, methodologies, and core use cases so that we build the right set of features and for the right scale.

We have kept this survey really short (7 questions) and we’d appreciate you taking the time to provide us your feedback. Thank you!

Survey link: http://bit.ly/vSContentMgmt (updated link)

Updated vCenter Server 5.5.0a Released

A minor update to the vCenter Server 5.5 has been released

VMware vCenter Server™ 5.5.0a | 31 OCT 2013 | Build 1378901
vCenter Server Appliance 5.5.0a | 31 OCT 2013 | Build 1398493

 Issues resolved with this release are as follows
  1. Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
  2. Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
  3. Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
  4. VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables
  5. Attempts to search the inventory in vCenter Server using vSphere Web Client with proper permissions might fail to return any results
  6. vCenter Server 5.5 might fail to start after a vCenter Single Sign-On Server reboot
  7. Unable to log in to vCenter Server Appliance 5.5 using domain credentials in vSphere Web Client with proper permission when the authenticated user is associated with a group name containing parentheses
  8. Active Directory group users unable to log in to the vCenter Inventory Service 5.5 with vCenter Single Sign-On
  9. Attempts to log in to vCenter Single Sign-On and vCenter Server might fail when there are multiple users with the same common name in the OpenLDAP directory service
  10. Attempts to log in to vCenter Single Sign-On and vCenter Server might fail for OpenLDAP 2.4 directory service users who have attributes with multiple values attached to their account
  11. Attempts to Log in to vCenter Server might fail for an OpenLDAP user whose account is not configured with a universally unique identifier (UUID)
  12. Unable to add an Open LDAP provider as an identity source if the Base DN does not contain an “dc=” attribute
  13. Active Directory authentication fails when vCenter Single Sign-On 5.5 runs on Windows Server 2012 and the AD Domain Controller is also on Windows Server 2012

The realese notes can be found here with full details, download now from www.vmware.com

vCenter Single Sign-On 5.5 – Backwards Compatible?

Part of my role at VMware is to  work closely with our customers and partners, sharing experiences and feedback with internal VMware Product Management and Engineers to help make our products better. One area that has been dominantly more focused than others over the last 12 months has obviously been vCenter Single Sign-On.

Due to this feedback, one of the drivers for the new vCenter Single Sign-On was to provide backwards compatibility and to highlight this, a recent Knowledge Base article released.

Supported vCenter Single Sign-On 5.5 configuration and interoperability with vSphere 5.1 (2059249)

Continue reading

VMworldTV have released the VMworld vCenter Server recorded breakout sessions

I was a little surprised how quickly these went live but can now share the VMworld vCenter Deep Dive and vSphere Upgrade series: Part 1 – vCenter Server breakout sessions from last weeks VMworld in Barcelona where my sessions were recorded and are now available for your viewing pleasure.

vCenter Deep Dive

vSphere Upgrade series Part 1: vCenter Server

enjoy

vCenter Server 5.5 – Simple vs Custom Installations

With the release of vSphere 5.5 now upon us, before jumping in and performing a fresh install or an upgrade I wanted to highlight the minor changes to the vCenter Server installer, specifically when to use the simple installer and when to use the individual custom install wizards.

With the new release, when you attach your ISO image you will be presented with the updated splash screen

Simple Install

Selecting this option which is now the default will give you an installation of the core components required for vCenter server with the default settings on too a single physical or virtual server. With vSphere 5.5 we have now added the vSphere Web Client into the mix to assist with setting up vCenter Single Sign-On if necessary. Simple Install will install the following core components in the required order specified.

Using the simple install, the components will be installed to the default C:\Program Files\VMware\Infrastructure destination folder or upgrade the existing version in the installed location. If you have distributed components with vSphere 5.1, this will install all components locally when ran, installing any components anew if not present which may affect you permission and accessibility (ie new vCenter Single SIgn-On instance)

Use case:
You will use the Simple Install option if you are installing or upgrading a single vCenter server with all of its components local to each other (VMware recommendation).

NOTE: If you are intending to install or upgrade multiple vCenter servers (ie for Linked Mode) then you can use the Simple Install for the first vCenter server to setup the vCenter Single Sign-On security domain and then use the custom installation options for the additional vCenter servers.

Custom Installation

The custom install provides the individual installer for each vCenter component which allows for additional options during install or upgrade. Each installer must be ran in the correct order (shown above) and allows for the following use cases

  1. Distribute components across multiple servers
    (although supported, customers have shared that this does add complexity with management and availability options of vCenter server)
  2. Install into a specific destination folder
    (eg D:\VMware)
  3. Install more than one vCenter server(s) in too the same vCenter Single Sign-On security domain
    (ie for Linked Mode as multiple vCenter Single Sign-On security domains (eg: vsphere.local) is not recommended)

As always please reference the VMware vSphere 5.5 Documentation Center for up to date documentation as well as the VMware Compatibility Guide and VMware Product Interoperability Matrixes prior to commencing any install or upgrade procedure.

VMware vCenter Server 5.1 Update 1 Released

There have been some rumors but I can now officially share the update release 1 for vSphere vCenter Server 5.1.

vCenter Server 5.1 Update 1 | Build 1064983
vCenter Server Appliance 5.1 Update 1 | Build 1065184

Download from VMware.com

What’s New

This release of VMware vCenter Server 5.1 Update 1 offers the following improvements:

  • vCenter Server is now supported on Windows Server 2012
  • Additional vCenter Server Database Support: vCenter Server now supports the following databases.
    • Microsoft SQL Server 2012
    • Microsoft SQL Server 2008 R2 SP2
  • Additional Guest Operating System Customization Support -vCenter Server now supports customization of the following guest operating systems:
    • Windows 8
    • Windows Server 2012
    • Ubuntu12.04
    • RHEL 5.9
  • vCenter Essentials no longer enforces vRAM usage limit of 192 GB
    With vSphere 5.1 Update 1, the Essentials and Essentials Plus licenses no longer restrict virtual machine power-on operations when the vRAM usage limit of 192 GB is met.
  • Resolved Issues – This release delivers a number of bug fixes that have been documented in the Resolved Issues section.

Click to review the complete VMware vSphere 5.1 Update 1 release notes

Continue reading