After months of running the vSphere 5.1 appliance in my lab, I decided to install the 5.5 appliance to see just how far this little gem has come. So, I downloaded and deployed the OVA, and moved onto initial configuration. After the initial configuration was completed, I decided to tweak some values in the interface. First and foremost - the DHCP configuration had to go. Followed by setting the host FQDN, which was strangely omitted from the initial configuration. This made running AD authentication a little difficult since AD integration requires that the appliance have an FQDN before it will accept the configuration.
Deploying pools can be done using the VMware View Administrator. The Add Pool wizard in the Administrator takes us through a series of steps which include user assignment, pool Identification, provisioning settings, advanced storage options etc. (refer to the figure below). In this article we will learn a different approach to deploying pools - using a powerCLI cmdlet.
In this article, we will discuss how to prepare Visual Studio to perform various VMware tasks. VMware PowerCLI is a Windows PowerShell interface for managing and automating various vSphere tasks. Using VMware PowerCLI cmdlets in Visual Studio we can create, customize, or manage vSphere inventory objects.
Released on April 4, 2013, vCenter Operations Manager makes the next step forward in managing your vSphere environment.
During the installation of vCenter Single Sign On (SSO), the installer will attempt to detect the Active Directory (AD) domain for the logged in user and add it as an Identity Source. For the most part, this works fine; however, I’ve run into a couple of instances so far deploying vSphere 5.1 to customers where they either want to add a second AD Identity Source or for one reason or another (running the installer as the local administrator is a typical case), the installer didn’t properly add a non-System-Domain Identity Source.
I was recently looking for a step-by-step guide for creating vSphere DRS rules and groups for a customer implementing a vSphere Storage Metro Cluster with EMC VPLEX and had trouble finding a comprehensive article, so I decided to write one. Without further ado:
As of November 29, 2012, all vSphere customers, even down to those who purchased Essentials bundles, are entitled to vCenter Operations Foundation 5.6. While not as fully featured as the other vCenter Operations Management Suite editions, it’s a great place to gain some insight into your vSphere environment that you may not have previously had. Some of the features you get with vCenter Operations Foundation 5.6, described as vSphere Performance and Health, are: