While working with my home vSphere 5.1 lab the other day, I was trying to create a VMFS5 datastores on my local SATA disk. Each time I tried to do that I was just welcomed with the following error:

Call “HostDatastoreSystem.CreateVmfsDatastore” for object “ha-datastoresystem” on ESXi “xxx.xxx.xxx.xxx” failed.

Please note xxx.xxx.xxx.xxx stand for my host IP. To visualize the error below is a screen shot of the error as it has appeared in my home lab

After fuzzing around trying to figure out what happened, I have remembered this particular disk was used by one of my old lab ESXi hosts. As I do all kind of crazy things in my labs, I thought I should try to wipe the disk clean then try to format it with VMFS5 afterward. That has actually solved the problem. This error seems to happen if you have a file system on that LUN/disk that ESXi does not understand, cannot overwrite or if You don’t have a full write access to the disk/LUN(ex: SRM replication target)

Below is how I went about doing it if you are not familiar with the procedure:

Note: In previous versions of ESXi fdisk was your friend in such a situation, though if you try it in vSphere 5.x… Read More

In earlier versions of VMware vSphere, many of us used to configure VMware tools settings by double clicking VMware tools inside the guest OS. This was most often used to configure NTP in the Virtual Machine VMware tools. Just to remind you of what that looked like:

Alright if you try to do the same in vSphere 5.1, you will be surprised that you will not have any options to choose when double clicking on VMware tools inside the guest OS. What you will get will look like the below screen shot:

Maybe what I have mentioned so far is already what you know and its why you got here. Now let’s cover how you can configure your VMware Tools to sync the VM time with your host. The way this is done in vSphere 5.1 is a bit different. You actually don’t need to login to the VM to change VMware tools setting & in most use cases the VMware Tools NTP Sync setting, but now you can do it from the VMware setting page. The VMware tools settings now can be accessed  in Virtual Machine –> Edit Settings –> Options –> VMware Tools. The below screenshot show just how to set it up.… Read More

I know most of my readers are already aware that Microsoft Exchange & Microsoft SQL have been supported on VMware vSphere for quite long time. In fact, there is so many companies are using it at unbelievably large production scale. Though today while going back from my customer site by train, I was talking to two of their engineers. One of them worked within their Virtual Infrastructure team & the other one within their Microsoft Infrastructure team. What sparked the idea of this post is when the Virtual Infrastructure engineer asked his colleagues what he think of virtualizing their Exchange 2010 setup. The shocking answer was “Our Exchange 2010 environment is too large to be virtualized as we have about 10,000 users. Further, if we virtualize we have have to use Hyper-V to be supported by Microsoft although I know it will run better on VMware vSphere.”

Let me address the status of Microsoft support for running MS Exchange 2010 on VMware vSphere, as it seems there is a lot of misleading believe that Microsoft Exchange 2010 is only supported on Hyper-v. Unfortunately, this seems to be fueled even further by few Microsoft Sales Reps that does not play fair and welling to do anything to win a deal even by misrepresenting facts.… Read More

While data security has always been one of the top CEOs concerns for the past decade or so, more compliance regulation has been hitting organizations doors every year. After organizations have mastered how to secure their physical environment by using physical segregation, Virtualization came around and changed the security game. Now organizations has to ensure that their Virtual Infrastructures are meeting compliance regulations such as PCI, HIPAA, SOX, and FISMA. Trying to manually keep up with such regulations that get updated regularly can be an endless hassle, & that why VMware has released vCenter Configuration Manager few years back.

vCenter Configuration Manager can help organizations not only audit their virtual infrastructure against compliance regulations such as Sarbanes-Oxley (SOX), Payment Card Industry (PCI), Health Insurance Portability and Accountability Act (HIPAA), and Federal information Security Act (FISMA), but as well it help you audit your environment against vSphere best practices including vSphere Security best practices. vCenter Configuration Manager can even help you re-mediate your environment to ensure it is meeting such regulation where many of those remediation can be carried out automatically others will include the recommendations on how to fix it. vCenter Configuration Manager is not limited to the vSphere Infrastructure, but it can check physical machines, Windows/Linux/Unix OS, & even applications for such compliance.… Read More

As part of my job as a consultant at VMware, I get to deliver Health Check & Architecture Reviews engagement on regular basis. I have found quite few best practices that is generally missed by most & thought to document the top 5 in here for everyone to benefit. Maybe on the next round more enterprises will pass these best practices check. The list below is not ordered in any manner, its just how they happen to kick into my mind and all of them quite important best practice to follow unless you have a strong reason not to.

1- Change port group security default settings ForgedTransmits and MACAddressChanges to Reject unless the application requires the defaults. As well ensure promiscuous mode kept its default setting of reject unless your application require it. The reason why you want to ensure all these are set to reject is to increase your environment security as the last thing you want to allow in your environment is some one forge transmitting packages on your network or a compromised VM claiming to be some one else & crashing another VM and receiving packets meant to be sent to it.  Even worse if you have promiscuous mode set to accept then a VM can sniff all the data flowing on that particular port group.… Read More

With all the enhancements and new features were announced with vSphere 5, many of you waiting patiently for vSphere 5 to be available for download. The good news that the long waited vSphere 5 has been announced available for download yesterday. You can download the vSphere 5 installers at: http://downloads.vmware.com/d/info/datacenter_cloud_infrastructure/vmware_vsphere/5_0

vSphere 5 has a tons of enhancements & new features, below just a summary of the major new features:

• Convergence. vSphere 5.0 is the first vSphere release built exclusively on the vSphere ESXi 5.0 hypervisor architecture as the host platform.
• VMware vSphere Auto Deploy. VMware vSphere Auto Deploy simplifies the task of managing ESXi installation and upgrade for hundreds of machines. It makes stateless ESXi possible.
• New Virtual machine capabilities. 32-way virtual SMP, 1TB virtual machine RAM, Software support for 3D graphics, and more. Did anyone say I need a larger VM? Dare you to say that now!!!
• Expanded support for VMware Tools versions. VMware Tools from vSphere 4.x is supported in virtual machines running on vSphere 5.0 hosts.
• Storage DRS. This feature delivers the DRS benefits of resource aggregation, automated initial placement, and bottleneck avoidance to storage. For those of you used to DRS and how it load balance VMs across hosts, Storage DRS do the same but for storage.