VIBSearch Finding VIB versions

VIBSearch is a simple PowerShell script with a GUI that will search for a specified VIB or all the VIBS installed on the ESXi hosts. A VIB stands for vSphere Installation Bundle (VIB). VIBs are used to package and distribute ESXi software such as drivers. The GUI is designed with SAPIEN PowerShell Studio 2014.

With VIBSearch it is easily to verify that all the ESXi host in the cluster have the same VIB versions installed. VIBSearch can be used for example to easily identify the HP-AMS driver version on all the ESXi hosts.

Requirements

VIBSearch is tested with:

  • PowerShell 4.0
  • PowerCLI 5.8 Release 1
  • For the Out-GridView cmdlet, PowerShell ISE is needed. Install ISE by using the following PowerShell commands:
    • Import-Module ServerManager
    • Add-WindowsFeature PowerShell-ISE

Installing and executing VIBSearch

  • Download VIBSearch.txt, link
  • Rename the *.txt  file to *.ps1
  • Open PowerShell and execute:
    • Set-ExecutionPolicy  unrestricted
    • ./vibsearch.ps1

After executing the script the following GUI appears:

0

  • To connect enter the FQDN or IP address of the vCenter name (1) and click on Connect (2) button

1

  • A credential window appear, enter the credentials for authenticating (administrator) to the vCenter Server. For a domain login use: user user@domainname  or domainname\username

5

  • After successfully authenticating to the vCenter Server there are two options to choose:
    • List All the VIBS:  List all the ESXi hosts in the vCenter Server
    • Search VIB: specify a VIB name for example “HP-AMS”

6

If authentication to the vCenter Server fails the following error is displayed in the PowerShell window:

authen

Example output:

HP-AMS VIB versions

hpams

Intel NIC VIB “net-igb” versions

Intel

NVIDIA VIB versions:

nvidia

Thanks to Francois-Xavier Cat (@LazyWinAdm) for helping me with the VIBSearch tool.

 

Identify the Single Sign-On (SSO) deployment method for the vCenter Server

With vSphere 5.5 you have the following deployment methods for Single Sign-On (SSO):

  • vCenter Single Sign-On for your first vCenter Server
  • vCenter Single Sign-On for an additional vCenter Server in an existing site (formerly HA Cluster)
  • vCenter Single Sign-On for an additional vCenter Server with a new site (formerly Multisite)

Once SSO is installed it can be usefull to identify what deployment options are used for example in a Site Recovery Manager (SRM) deployment. The following steps can be used to identify what deployment option are used for SSO on a vCenyter Server 5.5:

  • Browse to the following directory on the vCenter Server: C:\ProgramData\VMware\VMware VirtualCenter
  • Use a type command to display  the “LS_ServiceID.prop” file. The file contains the site name and indentifier.  For example:  SiteName1:10b042be-9b7a-467c-aa05-047a895c60fb
  • Repeat the above steps on the other vCenter Server(s)

If the string is the same in both sites SSO has deployed as:  “vCenter Single Sign-On for an additional vCenter Server in an existing site”. If the string is different, the vCenter Single Sign-On instance is deployed as:  “vCenter Single Sign-On for an additional vCenter Server with a new site”.

Microsoft Virtual Machine Converter 3.0 multiple disks bug

When converting a Windows 2008 R2 VM that contains multiple disks (VMDKs), the converting process with Microsoft Virtual Machine Converter (MVMC) 3.0 fails with the following error:

Microsoft Virtual Machine Converter encountered an error while attempting to convert the virtual machine. Log 

Details: A task may only be disposed if it is in a completion state (RanToCompletion, Faulted or Canceled).

This is a bug that was already available in MVMC version 2.0 and fixed in MVMC 2.1.  MVMC 2.1 is hard to find so here is a link to my OneDrive.

 

Hurry-up for the VCP5-DCV Delta Exam

VMware has released a new delta exam to recertify current VCP5-DCV holders. This delta exam focusses on material between vSphere 5.0/5.1 and vSphere 5.5 exams. This exam must be done before the end of the month!

Here are some details of the exam:

  • Based on new material between the vSphere 5.0/5.1 and vSphere 5.5 exams
  • The VCP5-DCV Exam consists of 65 questions and a short pre-exam survey consisting of 8 questions
  • In the VMware Education portal check when the VCP5-DCV certification expires:

vcp

  • The passing score is 300 (scale from 100-500)
  • The exam is available in English and Japanese
  • Exam time limit is 75 minutes and 15 minutes for the survey questions. (30 minutes additional time for countries where English is not a primary language)
  • Available online and you can take it from any location
  • The cost of the VCP5-DCV delta exam is:  €90,00
  • The exam must be completed within 2 days of your registration with PearsonVUE
  • If a candidate fails an exam on the first attempt, he or she must wait seven calendar days from their Original appointment time before he or she can register to retake the exam
  • The exam will only be offered until November 30, 2014. Update: VMware extending the period to take the exam, it  will be available through March 10, 2015.
  • The blueprint can be found here, link
  • The exam code is: VCP550D
  • A free 1-hr online eLearning  “VMware vSphere: What’s New Fundamentals of V5.5″  is available. This self-paced online training covers many new enhancements. This eLearning course does not fulfill certification requirements necessary for VCP5-DCV.   The eLearning can be found here, link
  • The VCP5-DCV Recertification website can be found here, link

vcp1

Let me know your experience with the VCP5-DCV Delta (VCP550D) Recertification Exam.

Tips for Installing Update Rollup 4 for System Center 2012 R2 Virtual Machine Manager

Update Rollup (UR) 4 for System Center 2012 R2 Virtual Machine Manager is released this week. The update contains a huge list of issues that are fixed and support for the following Linux systems is added:

  • Red Hat Enterprise Linux 7 (64 bit)
  • Oracle Linux 7 (64 bit)
  • CentOS Linux 7 (64 bit)

Here are some tips for installing Update Rollup (UR) 4 for System Center 2012 R2 Virtual Machine Manager:

  • Install the VMM Server and Administrator Console package by using Microsoft Update, WSUS or manual download

ur4

  • After the update of UR4 the SCVMM host must be rebooted
  • Before Update Rollup 4, you had to run an SQL script after you installed an update package to make sure Update Rollups function correctly. As of Update Rollup 4, this step is NO longer required
  • Update the VMM agents of all the SCVMM components such as Hyper-V hosts, VMM Server, Library and WSUS server. The SCVMM UR4 agent version is: 3.2.7768.0
  • The System Center Virtual Machine Manager DHCP Server (x64) component must be manually updated on all VMM Hyper-V hosts. To update the agent, first uninstall the old version by running the following command from an elevated PowerShell Command Prompt:
(Get-WmiObject -Class Win32_Product -Filter 'Name = "Microsoft System Center Virtual Machine Manager DHCP Server (x64)"' -ComputerName . ).Uninstall()
  • Copy the DHCPExtn.msi from SCVMM server (default installed in C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\SwExtn) to the Hyper-V host and execute the MSI. No restart of the Hyper-V host in needed
  • Check if the version of the DHCP Server component. The version must match 3.2.7768.0. Use the following PowerShell command:
Get-WmiObject -Class win32_product -Filter 'Name = "Microsoft System Center Virtual Machine Manager DHCP Server (x64)"'

dhcpclient

  • Update the UR4 System Center Virtual Machine Manager Console on all servers for example the SCVMM admin workstations and Citrix Delivery Controllers

More information can be found here.