Here’s What’s New in VMware vSphere and vCenter 6.7 You can expect some incremental changes to VMware hypervisor (ESXi) and management (vCenter Server)

Widenet is VCP Certified for VMware Products.
In many Article, we talked about Tips & tricks, or to solve problems, like here, or here. Now we will talking about a big news from VMware.

vSphere 6.7, released today, includes an update to both its hypervisor (ESXi 6.7) and management console (vCenter Server 6.7). This release shows that VMware Inc. is not content to let its hypervisor become a commodity, and that it’s possible to make incremental, evolutionary changes to a proven product and, moreover, that VMware is still making substantial investments in its hypervisor. The vSphere 6.7 beta, though NDA-constrained, has been available to the public since October 2017. Despite the fact that a lot of new features were baked into the 6.5 release, this release does make some nice incremental changes. Following are some of the most important changes included with vSphere 6.7.

Hardware Caveat
An important hardware caveat to be aware of is VMware has released an HCL for vSphere 6.7 that excludes some older, yet popular CPUs. If you’re thinking about running this release on an older system for development or testing first before placing it into production on your newer servers, make sure to check the HCL to ensure compatibility.

Single Reboot Upgrade
vSphere upgrades can now be completed with one single reboot. Prior to vSphere 6.7, major version upgrades took quite a while (although they could be done without disruption by transferring workloads by using the Distributed Resource Scheduler [DRS]). vSphere 6.7, on the other hand, allows you to do a “quick boot” where it loads vSphere ESXi without restarting the hardware because it only restarts the kernel. This feature is only available with platforms and drivers that are on the Quick Boot whitelist, which is currently quite limited.

VMware Configuration Maximum Tool
The most visible configuration maximum change in vSphere 6.7 is the number of devices that can be attached to a host. VMware has increased some of the other maximums.

vSphere Client
vSphere 6.5 eliminated the vSphere Client that ran natively on Windows (also known as the C# Client or Thin Client) in favor of the vSphere Web Client, which was Flash-based. Also introduced in version 6.5 was the vSphere Client, which replaced Flash with HTML5. vSphere 6.7 further extends the capabilities of the vSphere Client and will eventually replace the vSphere Web Client. It looks like the vSphere Client can do about 90 percent that the vSphere Web Client can do. In vSphere 6.5, VMware had a list of the functionalities not yet supported in the vSphere Client; hopefully the company will do the same for vSphere 6.7.
Figure 1 shows the main menu of the vSphere Web Client, and Figure 2 shows the main vSphere Client menu. Although the new client looks cleaner, and does seem more responsive than the vSphere Web Client, the location of some items has changed and some workflows will have to be adjusted accordingly with these changes. I wrote an article on the vSphere Client when it first came out that explains why VMware is switching to an HTML5-based client.

[Click on image for larger view.]Figure 1. 
The vSphere Web Client main menu.
[Click on image for larger view.]Figure 2.

vCenter Server Appliance

Now that the vCenter Server Appliance (VCSA) is functionally equivalent to the Windows-based vCenter Server, it would take a lot to convince me to use the Windows-based one instead of VCSA. Overall, I have found that the VCSA embedded database (PostgreSQL) performs great. Furthermore, the VCSA is very easy to update, and the Linux OS (Photon OS) is rock solid. As a side note, the VCSA can easily be monitored using vimtop (be sure to read my recent articles on using vimtop). You can also read my article about migrating from a Windows-based vCenter Server to a VCSA, as well as another article on using the built-in VCSA backup tool. The built-in backup tool in vSphere 6.7 offers more scheduling options for its VCSA backup tool than in vSphere 6.5. The Backup Scheduler tool (Figure 3) can be accessed from the vCenter Server Appliance Management Interface (VAMI). VMware is also stating that there are “phenomenal” performance improvements in vCenter operations per second, in reduction of memory usage and DRS-related operations.

[Click on image for larger view.]Figure 3. 
The Backup Scheduler tool.

Suspend and Resume of vGPU Workloads
vGPU allows you to carve up a physical GPU into multiple virtual GPUs that can be used by VMs. Although vGPUs were introduced with vSphere 6.0, the VMs that used vGPUs there were limited in what you could do with a VM that was using a vGPU. vSphere 6.7, on the other hand, removes some of these barriers, and now you can suspend and resume a vGPU-enabled VM.

For quite some time vSphere has had the ability to mask off CPU features so that VMs that were running on systems with newer CPUs could be vMotion to servers with older CPUs. This is called Enhanced vMotion Compatibility, or EVC. In vSphere 6.7 VMware has extended this capability to allow you to do this on a per-VM, rather than on an ESXi-host basis. This means that if you have VMs that you want to take advantage of CPU-specific features, and are willing to limit those VMs to CPUs that only have those features in your cluster, you can configure them to do so.

A per-VM EVC is set from the vSphere client by selecting a VM, going to the Configure tab and selecting Edit (Figure 4).

[Click on image for larger view.]Figure 4. Setting up a per-VM EVC.


Instant Clone
I’ve been a fan of using instant clones with virtual desktops—they’ve proven to be a big space saver, to use only a fraction of the disk resources compared to a full clone, and to allow VMs to be provisioned in seconds from a parent image. With vSphere 6.7, VMware has exposed the APIs that can be used to create instant clones. It looks like a straightforward process and I suspect that many people will figure out some very interesting ways to use the instant clone API.

ESXi Quick Boot
vSphere 6.7 introduces the Quick Boot feature, which allows a system to reboot in less than two minutes as it does not re-initialize the physical server BIOS. This can speed up operations that require an ESXi system to be rebooted; however, Quick Boot is only supported on certain systems and does not work with systems that have ESXi Secure Boot enabled.

Figure 5 shows two hosts, one with Quick Boot enabled and another without it enabled. By default, Quick Boot is enabled if the system supports it.

[Click on image for larger view.]Figure 5. 
The New ESXi Quick Boot feature is enabled by default if the system supports it.

Persistent Memory (PMem) Devices
vSphere 6.7 now supports the next generation of storage devices that use persistent DRAM memory, known as non-volatile dual in-line memory module (NVDIMM) devices. This technology is still in its infancy, but applications that require the lowest possible latency regardless of the cost will find this feature invaluable. PMem is presented to vSphere as either as vPMemDisk, which is treated somewhat like a datastore, or as a virtual NVDIMM (vNVDIMM), which is presented directly to guest OSes that can use NVDIMM devices.

Virtual Hardware Version 14
Virtual hardware is the abstract version of physical hardware to a virtual machine or, in essence, a virtual motherboard. As physical hardware supports more features, VMware builds new virtual hardware accordingly to emulate the physical version. vSphere 6.7 comes with a new virtual hardware, version 14. Version 14 adds support for NVDIMM, as well as Trusted Platform Module (TPM), Microsoft Virtual-based Security (VBS) and I/O Memory Management.

VMFS Datastores
VMFS3 datastores have been around for a long time, but VMware is now phasing them out. To assist with this transition, vSphere 6.7 automatically upgrades VMFS3 datastores to VMFS5 when they’re mounted. If you want to upgrade VMFS5 datastores to VMFS6 datastores, you’ll need to upgrade the datastore with vSphere Storage vMotion because an in-place upgrade of a VMFS5 to VMFS6 datastore isn’t possible.

As a side note, vSphere 6.7 supports VMFS5 and VMFS6; however, vSphere 6.0 and earlier systems only support VMFS5 datastores. As such, if you have an environment that contains vSphere 6.0 or earlier systems, you’ll want to only use VMFS6 datastores on systems that won’t be accessed by them.

Upgrading to vCenter Server 6.7
A specific order must be used when upgrading to vSphere 6.7. Check the documentation for the latest order and caveats, but the basic procedure can be carried out by first upgrading the Platform Service Controller (PSC), then upgrading vCenter Server and, last, updating the ESXi hosts.

Because upgrading directly from vSphere 5.5 to 6.7 isn’t supported, you’ll need to first upgrade from vSphere 5.5 to vSphere 6.5, and then finally to vSphere 6.7. It needs to be noted that an ESXi 5.5 host cannot be managed by VCSA 6.7. On the contrary, upgrading from vSphere 6.0 to 6.7 is supported. If you’re still running a window-based vCenter Server rather than a VCSA, VMware does offer a tool to assist you in the migration; be sure to read my article on using this tool.

Upgrading to ESXi 6.7
As mentioned earlier, ESXi 6.5 doesn’t support all the CPUs that ESXi 6.0 does, so be sure to check the HCL to unsure that your system is supported. Roughly speaking, what you’ll typically find supported, at the minimum, is a 2 core CPUs that were released after September 2006 and have NX/XD enabled. You can use the VMware Update Manager (VUM) to do an orchestrated automated upgrade. Alternatively, you can manually update the ESXi systems using an ISO image or esxcli commands or, if you use stateless host, you can use vSphere Auto-Deploy to update your servers. To see how to update an ESXi system using esxcli commands, be sure to read my article.

Wrapping Up
If I’m forced to pick one single standout feature in vSphere 6.7, it would have to be the instant clone API. I see this feature as a great enabler for the VMware ecosystem and VMware developers because the ability to spawn hundreds of identical VMs that only use a small amount of space in minutes has some mind-boggling use cases. However, with great power comes greater responsibility, and it will be interesting to watch the development of tools to manage and orchestrate these VMs over time.

Yes, instant clones is the gee-wiz feature in this release, but the rest of the improvements in this release prove that the hypervisor has room for evolutionary growth—and that VMware is serious in maintaining its leadership position in this regard.

Related Article: Here’s What’s New in vSphere 6.7

How to recover GRUB and Root password on VCSA This article will provide the step by step screenshot to recover the VMware vCenter Appliance

This article will provide the step by step screenshot to recover the VCSA (5.5 and 6.0 tested) root password and breaking the GRUB password.

VMware vCenter Appliance(VCSA) is a pre-configured Linux VM based on SUSE Linux.
If you forget the root password of the appliance, you need to recover the root password like other Linux Operating systems.
Recovering root password is very simple if there is no grub password has been setup or if you know the GRUB boot loader password. If you don’t know the grub password, then you need to reset the grub password first by using Redhat or SUSE Linux DVD or live cd such Hiren’s Boot CD.


If you deployed a VCSA changing grub password, and you lost it, you can remove it following this steps. Default grub passsword for VCSA is ‘vmware‘:

  1. Power OFF VCSA Server (it culd be a Physical server or VM);
  2. Insert a Live Boot CD linux for recover (Live Linux, Hiren’s Boot etc..);
  3. Power ON the Server, then Boot from CD;
  4. Start Recovery procedure from CD;
  5. Mount VCSA file system on a mount point like ‘/mnt/vcsa‘, in RW mode: ‘mount -o remount,rw /partition/identifier /mount/point‘;
  6. Navigate into /mount/point/boot/grub;
  7. List file into grub and find ‘menu.lst‘;
  8. Ensure to backup menu.lst: ‘cp menu.lst menu.lst.bck‘;
  9. Edit menu.lst with Vim editor or similar, then remove or place # to comment the ‘Password’ row:Recover Grub Password, commented ‘password’
  10. Exit VIM saving;
  11. Reboot Server.


  1. Start the VCSA Server (or VM) and interrupt the GRUB menu by pressing “ESC” key .  Press “e” edit the commands;If you know the GRUB password , you can pass it by press “p” and enter the GRUB password. If you don’t know the GRUB password , you need to follow the above procedure to break the grub password first.

    Recover Root Password Linux
    Recover Root Password Linux
  2. Press “e” to edit the commands again for the kernel;
  3. Append “init=/bin/bash” in this step and press enter;
  4. Press “b” to boot the system;
  5. You will get the bash;
  6. Set the new root password for VCSA ‘passwd root’;
  7. Exit the shell using “exit” command.

Once the system is booted , you should be able to login with new root password.

Related article:

How To Design An Effective Naming Convention A short guideline to name server in data center

While recording my VMware vSphere 5 Training course this past summer, I made mention that I developed a process for building an effective naming convention for enterprises. Server and desktop virtualization significantly increases the number of named objects within our enterprises, so an effective naming convention that describes what an object is, its location, function and purpose is critical. Doing so allows us to identify objects in a speedy way, but it also provides a structured way of searching for objects using keywords in a logical manner.
Even as I developed these guidelines, I did not think it would interest folks very much. But I started receiving near daily tweets and e-mails requesting a copy of the document. So, I’ve decided to publish it and share it with everyone in today’s blog.
Here are my basic guidelines for the object naming convention:

  • A name should identify the device’s location and its purpose/function/service.
  • A name should be simple yet still be meaningful to system administrators, system support, and operations.
  • The standard needs to be consistent. Once set, the name should not change.
  • Avoid special characters; only use alphanumeric characters.
  • Avoid using numeric digits, except for the ending sequence number.
  • Avoid the use of specific product or vendor names, as those can be subject to change. (There are some generally accepted exceptions: Oracle, SMS, SQL, CTX, VMW)

Here are some basic recommendations:

  • The name should begin with a rigid header portion that identifies the location and optionally a type identifier. These should be followed by a delimiter to signify the end of the header portion. This delimiter shall be a ” – ” (dash) unless the system does not recognize a “-“. In this case, substitute the dash for another suitable agreed-upon character (i.e. $ or #).
  • Allow for a variable section that completes the identification (function, service, purpose, application).
  • End the name with a unique ID, a sequence number, which can be multi-purpose.
  • Allow for flexibility. Since technology is constantly evolving, this standard must also be able to evolve. When necessary, this standard can be modified to account for technological, infrastructure, and or business changes.
  • There must be enforcement, along with accurate and current documentation for all devices.Here is an example of the proposed naming convention standard


Naming Convention
Naming Convention

Header portion

  • GG — Geographical location
  • L — Location should be generic and not vendor- or building-specific to facilitate moves, building name changes due to mergers, acquisitions or dissolution of business, etc.
  • T — Type – — Dash is a required delimiter to signify the end of the header portion

Variable portion:

  • AAA — Function /Service/Purpose
  • BBB — Application(Unique ID)
  • ## — 2 digit sequence #

Values Defined:


  • CH — Chicago
  • NY — New York
  • LN — London
  • SY — Sydney
  • MA — Madrid
  • SI — Singapore
  • MU — Mumbai


  • D — Main Data Center
  • C — COLO Data Center
  • T — Test Area (should be used for test machines that are to permanently stay in the test area)

Type (optional):

  • V — Virtual
  • C — Cluster server
  • P — Physical
  • O — Outsourced or vendor supported system

Delimiter (required):

  • – A “-” (dash) will be used unless the system does not recognize a “-” at which point an agreed upon character can be substituted. This could be a $ or # or other character.

Variable portion – AAA Identify the primary purpose of the device:

  • DC — Domain Controller
  • FS — File Server
  • PS — Print Server
  • ORA — Oracle database
  • SQL — SQL database
  • DB — other database(s)
  • EXH — Microsoft Exchange
  • CTX — Citrix Server
  • ESX — VMware ESX Server

Variable portion BBB Identify the Application on this server.

If the server is for a specific application, then an application identifier should be the second part of this portion of the name, preceded by the service:

  • JDE — JDEdwards
  • DYN — Dyna
  • EPC — Epic

This area of the name offers a lot of flexibility to handle identifiers for specific purposes, functions, and/or applications. There are many challenges to select identifiers that are meaningful and consistent and are not subject to frequent change. Here are some examples based on th guidelines I propose above:

  • CHD-DC01 — Chicago Office, Data Center, Domain Controller, sequence # 1
  • CHD-FS01 — Chicago Office, Data Center, File Server, sequence # 1
  • CHD-EXH01 — Chicago Office, Data Center, Microsoft Exchange, sequence # 1
  • CHD-ESX01 — Chicago Office, Data Center, VMware ESX Server, sequence # 1
  • CHC-CTXJDE01 — Chicago Office, Data Center, Citrix Server,JDEdwards Application, sequence # 1
  • CHC-WEB01 — Chicago Office, Data Center, Web Server, sequence # 1

Unique ID / sequence number

## This is a 2 digit sequence number

I would love to hear your comments on this naming convention and if you have ideas to improve it.

Related Article: Link

Troubleshooting importing OVF Template into VMware ESXi Error while importing OVA files, Unsupported hardware family, Unsupported devices

This post shows how to adapt a VMWARE OVA exported from Virtual BOX for a Virtual Machine, compatible with ESXi.

When you try to open an OVA with the VMware format on an ESXi you get the following error:

 “The OVF package requires unsupported hardware
Details: Line 25: Unsupported hardware family ‘virtualbox2.2’.”
Details: Line 25: Unsupported hardware family ‘_unsupported_version’.”


Uncompresse OVA Archive :

First off all uncompress the OVA archive (with a zip extractor like 7-ZIP)

You will get a directory with 3 files on it like this :

Modify the OVF file :

Open the *.ovf file (with Notepad+)

Change the following line :


By this one :


Modify the *.mf file and calculate the SHA1 hash of the modified OVF file:

Open the *.mf file which contains the SHA1 hash of *.ovf file. So you need to replace the value specified by the new SHA1 hash of .ovf file.

SHA1(VMFile.ovf)= 48432f9cb8b0bfa97098006abb390805449303be
SHA1(VMFile.vmdk)= ffa3500bc379a2e040badce315d6b3b06876d5a9

To calculate this hash you can use a tool like FCIV from microsoft. You can download it there :

>D:\FCIV\fciv.exe -sha1 "VMFile.ovf"
// File Checksum Integrity Verifier version 2.05.
da39a3ee5e6b4b0d3255bfef95601890afd80709 VMFile.ovf

So, put the new hash in the *.mf file and save it

SHA1(VMFile.ovf)= da39a3ee5e6b4b0d3255bfef95601890afd80709
SHA1(VMFile.vmdk)= ffa3500bc379a2e040badce315d6b3b06876d5a9

Maybe you may encounter other errors while importing the OVF template like:

Line XX: OVF hardware element ‘ResourceType’ with instance ID ‘5’: No support for the virtual hardware device type ’20’

This is a problem of SATA controller, change settings in ovf like this:

From this

<rasd:Description>SATA Controller</rasd:Description>

With this
<rasd:Description>SCSI Controller</rasd:Description>

Other problems could happen if in the <Item> is listed an audio card, you should delete whole line starting from


Then save again OVF file.

Remember that every time you save the ovf file, and you what to try to import into ESXi, you must generate the hash, replace the hash in the .mf file, follow the steps above.

Deploy the new OVF :

Now, you can deploy directly the new OVF file on ESXi.
On VSPHERE select :

File > Deploy OVF Template
Select your OVF file :

The following WARNINGS are raised but you can move forward.


So now you can deploy and start your VM.

Related Article: VIRTUALBOX OVA TO VSPHERE OVF | Uncompress a VMWARE OVA and modify its VM version | File Checksum Integrity Verifier

How To Fix Scsiport.sys Blue Screen Errors (BSOD) Converting P2V a Windows 2000 error KMODE_EXCEPTION_NOT_HANDLED – scsiport.sys

What Is Scsiport.sys?

Scsiport.sys is a type of SYS file associated with Microsoft Office System Beta 2 Kit 2003 developed by Microsoft for the Windows Operating System. The latest known version of Scsiport.sys is, which was produced for Windows. This SYS file carries a popularity rating of 1 stars and a security rating of “UNKNOWN”.

What Are SYS Files?

SYS files such as scsiport.sys are third-party (eg. Microsoft) device drivers or critical system files that come as part of the Windows operating system. Most SYS files allow internal PC hardware or attached hardware, such as a printer, to communicate with third-party software programs (eg. web browsers, word processors, Microsoft Office System Beta 2 Kit 2003) and the operating system (eg. Windows).

Other SYS files are critical system files called “kernel mode device drivers” which are used to power the Windows operating system. Files such as “CONFIG.SYS” contain configuration settings and specify what device drivers should be loaded by the operating system. Without driver files such as scsiport.sys, you wouldn’t be able to do simple tasks such as printing a document.

Why Do I Have SYS Errors?

SYS file errors are typically caused by faulty hardware or corrupt device driver files. Because of the importance of Scsiport.sys in the functionality of Microsoft Office System Beta 2 Kit 2003 and other Windows functions, any corruption or damage to this file can create critical system errors in the form of a “blue screen of death” (BSOD). Please see “Causes of Scsiport.sys Errors” below for more information.

When Do SYS Errors Occur?

SYS errors, such as those associated with scsiport.sys, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. printing).

Common Scsiport.sys Error Messages

The majority of scsiport.sys errors that you encounter will be “blue screen of death” errors (also know as a “BSOD” or “STOP error”) that occur in Windows XP, Vista, 7, 8, and 10:

  • “A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: Scsiport.sys.”
  • “:( Your PC ran into a problem and needs to restart. We’re just collecting some info, and then we’ll restart for you. If you would like to know more, you can search online later for this error: scsiport.sys.”
  • “STOP 0x0000000A: IRQL_NOT_LESS_EQUAL – scsiport.sys”
  • “STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED – scsiport.sys”
  • “STOP 0×00000050: PAGE_FAULT_IN_NONPAGED_AREA – scsiport.sys”

In most cases, you will experience scsiport.sys blue screen errors after you’ve installed new hardware or software. These scsiport.sys blue screens can appear during program installation, while a scsiport.sys-related software program (eg. Microsoft Office System Beta 2 Kit 2003) is running, while a Microsoft driver is being loaded, or during Windows startup or shutdown. Keeping track of when and where your STOP error occurs is a critical piece of information in troubleshooting the problem.

Causes of Scsiport.sys Errors

Scsiport.sys blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues. These could be related to either Microsoft Office System Beta 2 Kit 2003 software or Microsoft hardware, but it is not necessarily the case.

More specifically, these scsiport.sys errors can be caused by:


  • Incorrectly configured, old, or corrupted Microsoft Office System Beta 2 Kit 2003 device drivers. (very common)
  • Corruption in Windows registry from a recent scsiport.sys-related software change (install or uninstall).
  • Virus or malware infection that has corrupted the scsiport.sys file or related Microsoft Office System Beta 2 Kit 2003 program files.
  • Hardware conflict after installing new Microsoft hardware, or hardware related to scsiport.sys.
  • Damaged or removed system files after you’ve installed software or drivers related to Microsoft Office System Beta 2 Kit 2003.
  • scsiport.sys blue screen caused by a damaged hard disk.
  • scsiport.sys STOP error due to memory (RAM) corruption.


  • VMware Standalone Converter version 4.0.1 (See Additional Info at the end)
  • Update Rollup 1 for Windows 2000 SP4 from our repository (KB891861)
  • Windows 2000 Sysprep tools (Q257813)
  • A Windows or Linux LiveCD. I recommend Knoppix (6.4+ – Linux) or Hiren (Windows).
    If you need to modify registry keys, use Hiren.


  1. Install VMware Standalone Converter version 4.0.1 on target machine
  2. Converto machine to VMware host or infrastructure;
  3. Extract sysprep tools and place them in C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\sysprep\2k
    That should be on the same machine that has VMware Converter, not the Windows 2000 server.
    * On Windows 2008, the location is C:\Users\All Users\VMware\VMware vCenter Converter Standalone\sysprep\2k (Thanks Anonymous for the tip!)
    or C:\ProgramData\VMware\VMware vCenter Converter Standalone\sysprep\2k (thanks Ben!)
  4. Either apply the update rollup to the server or extract the update rollup and replace it with the file SCSIPORT.SYS in C:\WINNT\system32\drivers. Applying the update is recommended if the system is stable.
  5. Run the Converter and deploy the agent. If you’re asked to restart, restart then start the VMware Converter service manually before running the Converter again, otherwise it’ll ask you to deploy the agent again.
  6. In Step 3: View / Edit Options, Click on the Devices pane and change the disk controller to BusLogic SCSI.
  7. Keep the number of processors as is, because if you change it, Windows 2000 won’t auto-detect new CPUs and you’ll need to update the Hardware Abstraction Layer (HAL) on it manually. See KB234558 and KB249694 for more details.
  8. In the Networks pane, deselect the option to connect at power on.
  9. In the Advanced Options pane, do not select the options to power off the source and select the option to power on the target (VM). Do install VMware tools.
    Do NOT select “configure guest preferences for the virtual machine”