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.
This video demonstrates how to troubleshoot Virtual SAN Providers which display the status as disconnected in the vSphere Web Client. This issue occurs if the SMS certificate for vCenter server is expired.
To resolve this issue, expired certificate will be removed and a new certificate will be generated.
This video demonstrates how to troubleshoot Virtual SAN on-disk format upgrade to 3.0, which may fail in small Virtual SAN clusters or ROBO/stretched clusters.
Attempting an on-disk upgrade in certain VSAN configurations may result in failure. Configurations that can cause these errors include:
The stretched VSAN Cluster consists of two ESXi Hosts and the Witness Node (ROBO configuration)
Each Host in the Stretched Cluster contains a single VSAN Disk Group
A Virtual SAN cluster consists of three normal nodes, with one disk group per node
A Virtual SAN cluster is very full, preventing the “full data migration” disk-group decommission mode
To allow an upgrade to proceed in these configurations, a compromise as to availability must be made. Data accessibility will be maintained, but the redundant copy of the data will be lost and rebuilt during the upgrade process. As a result, data will be exposed to faults and failures such as the loss of a disk on another node may result in data loss. This exposure to additional failure risk is referred to as “reduced redundancy,” and must be manually specified in the Ruby vSphere Console (RVC) to allow the upgrade to proceed. It is not possible to specify reduced redundancy when using the vSphere Web Client to start the upgrade.
Caution: During upgrade, a single point of failure is exposed. Follow all VMware best practices, and your business practices, regarding the backup of important data and virtual machines.
This video demonstrates how to troubleshoot Virtual San 6.2 upgrades which fail after 10% of the upgrade procedure. The resolution provided in this video tutorial will be useful to you if you experience the following symptoms within your VMware Virtual SAN environment:
When upgrading VMware Virtual SAN (VSAN) to version 6.2, the Virtual SAN Disk Format Conversion task fails at 10%.
In the vSphere Web Client, you see an error similar to:
A general system error occurred: Failed to realign following Virtual SAN objects, due to being locked or lack of vmdk descriptor file which requires manual fix
The Convert disk format for Virtual SAN task fails with a General Virtual SAN error status.
When upgrading the on-disk format, during the 10% – 15% phase, Virtual SAN realigns objects to prepare them for new features. The process is performed in two steps:
In the first step, Virtual SAN realigns objects and their components to have a 1 MB address space. The process fails in this step if the cluster is unstable or if there is not enough disk space.
In the second step, Virtual SAN realigns vsanSparse objects to be 4k aligned. The process fails if there are objects which cannot be upgraded to version 2.5.
An object will fail to upgrade under these conditions:
The object is left behind and no longer referenced by anything.
While watching this video you will see the necessary steps to launch, collect and display Virtual SAN Observer (VSAN Observer) performance charts and information for VMware Virtual SAN (VSAN).
VSAN Observer is designed to capture performance statistics for a Virtual SAN Cluster and provide access through a web browser and capture the statistics for customer use or for VMware Technical Support.
In this latest KBTV Webinar you will learn how to configure VMware vRealize Orchestrator (vRO) integration with VMware vRealize Automation (vRA).
This year we will be continuing our KBTV Webinars video series wherein staff members from our Technical Support teams cover and deep dive into a wide range of topics. To start us off, here is a new video which discusses and demonstrates how to configure VMware vRO integration with vRA.
Covered in this video demonstration:
Examples of a Simple Installation versus Distributed / HA Installation
Advanced Service Designer versus IaaS Extensibility
Understand the ways that vRealize Orchestrator is leveraged by vRealize Automation
A demonstration of a basic integration configuration between VMware vRealize Orchestrator integration with VMware vRealize Automation
Today we bring you a video which demonstrates downgrading from VMware Workstation Pro 12.x to VMware Workstation 11.x including changing the virtual hardware of your virtual machines.
VMware Workstation Pro 12.x and VMware Workstation 11.x use different virtual machine hardware compatibility. When downgrading Workstation, you must change the virtual machine hardware compatibility version of your virtual machine to Workstation 11.0.