During the installation of vCenter 5.1 on a Windows server 2012 I ran into an issue where the installation of the vCenter failed. The prerequisite services installed without problems but the vCenter service failed to install. The installation stopped with a Failed to install VMware vSphere Profile-Driven Storage error.
Looking at the services I noticed that the vCenter services was already installed but not running. When I tried to manually start the vCenter server service it failed with an error regarding a dependency service not being available.
Integrating Hyperic within VCOPS is fairly simple and similar to integrating other solutions. VCOPS uses adapters to establish this integration.
First step is to install the Hyperic adapter, this process is the same as updating the VCOPS installation. Open the update tab in the administration portal.
Point the update field to the Hyperic adapter .pak package you downloaded earlier and hit update. VCOPS will now install the Hyperic adapter. Installling an adapter is the same as updating VCOPS.
After the installation of the latest vSphere 4.1 patches all our hosts showed a warning regarding the Tech Support Modes being enabled. I took the time to write a script to start/stop theses services on the hosts in the vCenter server.
# # .SYNOPSIS # Start or Stop Local & Remote TSM # .VERSION # 1.0 # .DESCRIPTION # Script to start or stop Local & Remote Tech Support Mode on all the # vSphere severs located in vCenter.
One of our vSphere host showed as disconnected in vCenter. Connecting directly to the host with the vSphere client wouldn’t work neither. When restaring the services on the host I was able to connect directly but within one minute the connection between the client and the host would be lost.
As I had already encountered something similar before I checked the partitions on the hosts.
The vdf -h command shows that the hostdstats partitiion has filled up.
After the installation of the latest vSphere 4.1 patches all hosts displayed a warning about Local & Remote Tech Support Mode being enabled. As I didn’t file like manually stopping the services on every host I took the time to write a script which can start/stop Local and Remote Tech Support mode on all hosts in a vCenter.
# .SYNOPSIS # Start or Stop Local & Remote TSM # .
One of the new features in vSphere 4.1 is the ability to configure Host affinity rules for DRS. These enable you to split your vSphere cluster in several groups of hosts and assign assign a subset of your VMs to one of these groups.
There are plenty of use cases for this:
Applications licensed based on CPUs
performance sensitive applications
VMware just released vSphere 4.1, Site Recovery Manager 4.1 and VMware vCenter Server Heartbeat 6.3.
What’s new in vSphere 4.1.
The downloads can be found at:
ESX 4.1 - Release Notes
ESXi 4.1 - Release Notes
Site Recovery Manager 4.1 – Release Notes
vSphere PowerCLI 4.1
vSphere CLI 4.1
vSphere Management Assistant (vMA) 4.1
VMware vCenter Server Heartbeat 6.3
Release Notes Both vCenter 4.1 and SRM 4.
Notepad++ supports Powershell from version v5.6 but the VMware PowerCLI cmdlets aren’t included.
So I created PowerCLI Language definition file for syntax highlighting. It contains the cmdlets available in vSphere PowerCLI 4 Update 1 and vCenter Update Manager PowerCLI 4 Update 1.
I had to configure additional portgroups based on vlanids on a vSphere cluster. I couldn’t use host profiles to apply the configuration on all hosts.
$vCenter = Connect-VIServer -server(Read-Host "Please enter the name of your vCenter Server.") $Cluster = Get-Cluster -Name (Read-Host "Please enter the name of the cluster whose servers need to be reconfigured.") $vSwitch = Read-Host "Please enter the name of the vSwitch on which the portgroups need to be created.
VMware opened the registration for VMworld 2010.
More Labs - Self Paced
All Labs are self-paced so you have more freedom and options to choose from.
No Session Registration
No need to pre-register this year. You’ll have ample opportunity to attend the sessions of your choice as each one will be repeated at least twice.
Collaborate with industry leading subject matter experts in sessions, discussions and one-on-one meetings.