Home > Blogs > Support Insider > Tag Archives: installing

Tag Archives: installing

How to install Windows in VMware Fusion using Easy Install

This video demonstrates how to install Windows guest operating system using the Easy Install feature in VMware Fusion.

Before creating a virtual machine, you must obtain the operating system and any necessary product keys for installation in that virtual machine. VMware Fusion does not come with any operating systems to install in virtual machines you create.

This method assumes that you are using a physical CD or a disk image (.iso / .cdr /.dmg file). You cannot create a Windows virtual machine by using .exe files downloaded from Microsoft, as those files need to be run on a Windows PC.

Installing VMware Workstation Pro 12 on Windows

This video tutorial quickly demonstrates how VMware Workstation Pro 12 can be installed on your Windows PC or laptop.

Before starting with the installation ensure that your physical machine meets all of the system requirements for VMware Workstation. See Getting Started with VMware Workstation 12.x for further details.

For instructions regarding how to download the software and additional information concerning the installation sequence see VMware Knowledge Base article Downloading and installing VMware Workstation (2057907).

How to install vSphere 6 ESXi using the Interactive Installer

Interactive installations are recommended for small deployments of four or less hosts. Installation using this method involves booting from the ESXi 6.0 installation media by inserting the media in to the host and following the prompts from the installation wizard to choose a destination disk in the host and begin the installation. Our video today demonstrates how to install vSphere 6 ESXi using the Interactive Installer.

The ESXi installation media can be connected to the host in a few different ways:

  • Inserting the CD/DVD in to the DVD-ROM drive in the server
  • Plugging in a bootable USB device
  • Mounting an ISO remotely

When instructed to begin, the installer reformats and partitions the target disk and installs the ESXi boot image. If you have not installed ESXi on the target disk previously, all data located on the drive is overwritten, including hardware vendor partitions, operating system partitions, and associated data.

Note: The formatting and partitioning done by the ESXi installer is permanent and overwrites existing data. To ensure that you do not lose any data, migrate any important data from the host to another machine before you install ESXi. If you are installing ESXi on a disk that contains an installation of ESXi/ESX or a VMFS datastore, you are presented with upgrade options.

For additional information, see VMware Knowledge Base article Methods for installing ESXi 6.0 (2109708).

How to install the vCenter Server 6.0 Platform Services Controller on a Windows machine

Our second video today will discuss and demonstrate How to install the vCenter Server 6.0 Platform Services Controller on a Windows machine and also How to install an additional vCenter Server 6.0 Platform Services Controller on a Windows machine.

For additional information, see VMware Knowledge Base article Installing the VMware vCenter Server 6.0 Platform Services Controller on a Windows machine (2108801).

How to install vCenter Server 6.0 with an external Platform Services Controller on a Windows machine

Our second video today discusses and demonstrates how to install vCenter Server 6.0 with an external Platform Services Controller on a Windows machine.

For additional information, see VMware Knowledge Base article Installing VMware vCenter Server 6.0 with an external Platform Services Controller on a Windows machine (2108802).

How to install vCenter Server 6.0 with an embedded Platform Services Controller on a Windows machine

For our first video today we discuss and demonstrate how to install vCenter Server 6.0 with an embedded Platform Services Controller on a Windows machine.

For additional information, see VMware Knowledge Base article Installing VMware vCenter Server 6.0 with an embedded Platform Services Controller on a Windows machine (2108799) for more information.

Installing VMware Workstation 11 on your PC

VMware Workstation 11 was released recently and this video tutorial demonstrates how you can install VMware Workstation 11 on a Windows based PC.

Before installing, ensure that your system meets the system requirements as laid out in the Getting Started with Workstation 11 guide.

Download instructions are available in VMware Knowledge Base article Downloading and installing VMware Workstation (2057907).

How to Download and Install VMware Fusion 7

VMware Fusion 7 was just recently released, so here is a new video which demonstrates how you can download and install VMware Fusion 7. Follow these steps to get your copy up and running as quickly and smoothly as possible.

For additional information and instructions concerning the download and installation process, see VMware Knowledge Base article Downloading and installing VMware Fusion (2014097).

Installing, upgrading, and uninstalling VMware vCenter Support Assistant 5.5

Today the KBTV team have a new video for you which discusses and demonstrates installing, upgrading, and uninstalling vCenter Support Assistant 5.5 in a vCenter Server environment and is based on VMware Knowledge Base article Installing, upgrading, and uninstalling VMware vCenter Support Assistant 5.5 (2070787).

This tutorial covers the following topics:

  • Installing vCenter Support Assistant
  • Configuring the virtual appliance
  • Removing vCenter Support Assistant
  • Updating vCenter Support Assistant

Additional information and resources that may be of some interest to you:

Patching ESXi 5.5 for Heartbleed without installing Update 1

On April 19th, VMware released a series of patches for ESX 5.5 and ESX 5.5 Update 1 to re-mediate the CVE dubbed “Heartbleed” (CVE-2014-0076 and CVE-2014-0160).

VMware also recently announced that there was an issue in the newest version of ESXi 5.5 (Update 1 and later), which can cause difficulties communicating with NFS storage. This NFS issue is still being investigated, and customers are encouraged to subscribe to KB article: Intermittent NFS APDs on ESXi 5.5 U1 (2076392) for updates.

Due to the confluence of these two unrelated issues, you might find yourself trying to patch ESXi to protect yourself from the Heartbleed vulnerability, while at the same time trying to avoid installing ESXi 5.5 Update 1.

Here is the information from the VMware Knowledge Base on the topic:

2

The note at the bottom is the key. Stated simply, if you are…

  • Using NFS storage
  • Concerned about patching to Update 1 due to change control
  • Not already running ESXi 5.5 Update 1 (build-1623387)

… then you should patch your install for the Heartbleed issue and at the same time stay at ESX 5.5 by applying Patch Release ESXi550-201404020, and not ESXi550-201404001.

An Explanation of Patch Release Codes

To better understand the Patching process in a VMware environment, it is valuable to understand the codes which are used in VMware Patch Releases.

When VMware releases a patch, or a series of patches, they are bundled together in what is known as a Patch Release. A Patch Release will have a coded name which is formed using the following structure. I have added braces to demonstrate the different sections better in each example.

[PRODUCT]-[YEAR][MONTH][THREE DIGIT RELEASE NUMBER]

For example, the patch release for ESXi 5.5 that was released in January 2013 would be coded like this (without the explanatory braces):

[ESXi550]-[2013]-[01][001]

As part of a Patch Release, there will be at least one Patch. Each Patch is given a Patch (or Bulletin) ID. Patch IDs are similarly structured to Patch Release codes, but also have a two letter suffix. For Security Bulletins, the prefix will be SG. For Bug Fix Bulletins, the prefix will be BG.

For example, the two Patch IDs which were released to patch Heartbleed are:

[ESXi550]-[2014][04][401]-[SG]
[ESXi550]-[2014][04][420]-[SG]

Note that the only difference in the Patch IDs here is in the three digit release number (401 vs 420).

Patching with VMware Update Manager

There are a number of methods for patching ESXi hosts, and the most commonly used is VMware Update Manager (VUM). VUM will present a pair of Dynamic Baselines which will be automatically updated when patches are available. The danger in this case is that VUM may show you both the Pre-Update 1 patch, as well as the Post-Update 1 patch. If you are not careful as to which patches you apply, you might accidentally end up patching your host to Post-Update 1.

Here are the patches which were released on April 19th, as seen in VUM. The Update 1 patch is highlighted in red, while the Pre-Update 1 patch is marked in green.

1

Note: VMware also released two other ESXi 5.5 patches on April 19th, as part of Patch Release but these are not related to the Heartbleed vulnerability in any fashion. (ESXi550-201404402-BG, and ESXi550-201404403-BG).

Creating a Fixed Baseline

Patching a host using ESXi550-201404420-SG (Pre-Update 1), while avoiding ESXi550-201404401-SG (Post-Update 1) requires the use of a Fixed Baseline in Update Manager.

  1. Start in the Update Manager Admin view.
  2. Select the Baselines and Groups tab.
  3. Click Create… in the Baselines column.
    3
  4. Give the new Baseline a descriptive Name (and optionally a Description).
    4
  5. Click Next.
  6. For Baseline type, select Fixed.
    5
  7. Use the Search feature to find the only Patch we want to apply. You will need to select the Patch ID option from the dropdown menu to ensure the search scans for the appropriate column.
    6
  8. Enter the Patch ID into the search field: ESXi550-201404420-SG and click Enter to search.
  9. Select the Patch which shows up in the filtered list, and click the Down Arrow to move it into the selected Baselines.
    7
  10. Click Next and confirm that the Patch ESXi550-201404420-SG is the only one selected.
    8
  11. Click Finish.

The Baseline is now created and available for use.

Remediating a Host using the Fixed Baseline

Once the Fixed Baseline has been created, we can use it to Scan and Remediate an ESXi host.

  1. Select the host you wish to patch, and place it into Maintenance Mode.
  2. Click the Update Manager tab.
  3. Make sure that there are no Dynamic Baselines attached to the host you wish to patch. Detach any baselines which are currently attached:
    Critical Host Patches (Predefined)
    Non-Critical Host Patches (Predefined)
    Any other Custom Baselines which you have created
  4. Click the Attach link.
    9
  5. Select the newly created Baseline and click Attach.
    10
  6. Click the Scan link and make sure Patches and Extensions is selected. Click Scan again.
    11
  7. When you are ready to patch the host, select Remediate.
  8. Complete the Remediation wizard.

Once the host is patched, it will reboot automatically.

Patching an ESXi host manually via the command line

Another option to patch an ESXi host is to use the esxcli command line tool. The patch files required are the same. For more information on how to proceed with this route, refer to the vSphere 5.5 Documentation under the heading Update a Host with Individual VIBs.

References

Author: Andrew Lytle
As a member of the VMware Mission Critical Support Team, Andrew Lytle is a Senior Support Engineer who is specializes in vCenter and ESXi related support.