I’ve been working with VMware vSphere 6.5 recently on a few projects and had to make some minor tweaks to the vCenter Server Appliance (VCSA) to configure NTP and time synchronization. Here is a quick guide on how to change the NTP settings.
The change can’t be made from logging into the normal vCenter Server Appliance web client you would use for managing the cluster, you have to log directly into the vCenter appliance.
I’ve been doing a fair bit of VMware patching recently so thought it would be useful to highlight the current and past versions of ESXi and how to check which version you are running. The latest version is 6.7 released 17 April, 2018. Since then there have been a few patches.
Below is a snapshot of the current versions as of 18 December 2018.
As with any new software test in a development environment first before upgrading to a new major version, let others lead the way on the bleeding edge and wait for Patch 1 to be released.
So I turned on my test SBS 2011 server today to test out the latest Exchange Update Rollup and was greeted by an VM that was hanging on startup. Looking into the issue more closely the virtual network adapter was disconnected and when I tried to select ‘connect’ I received the following error message:
The network bridge on device ‘VMnet0’ is not running. The virtual machine will not be able to communicate with the host or with other machines on your network. Failed to connect virtual device ‘Ethernet0’.
I’m updating my certifiactions at the moment and to help with my VCP I’m in the process of building a vSphere 6 home lab. I’m using VMware workstation and within it I’m setting up two ESXi 6.0 hosts, a vCSA and a single DC. Each ESXi host has ten NICs with will be distributed and teamed onto five different networks, Management, Storage, vMotion, and two sudo VLANs for VMs. The problem is only the first Network Adpater which was bridged has been detected correctly.
At first i didn’t notice it, as in VM Workstation everything looks ok. The Network Adapters were added in VMware Workstation with out an issue, and assigned to the correct custom virtial networks. Continue reading →
In this post we’ll look at how to convert a Hyper-V virtual machine using the VHDX format virtual disk to a VMware Workstation virtual machine using the vmdk format virtual disk.
Until Windows 8 I’ve used VMware Workstation for testing, but with the advent of Windows 8 and the built in Hyper-V I decided to give it a try and have been using it quite happily ever since. In the near future though I’m going to be looking at some vSphere testing, and from memory recall that you can nest it within VMware Workstation, so I thought I would give the latest version a go.
The only problem is I don’t want to rebuild my current test environments so I need some way of converting the VHDX that Hyper-V uses to vmdk that VMware Workstation uses.
You have to register to download the product, but once you have and installed it below are the steps I took to convert a UEFI Boot, Gen 2, 2012 R2, Hyper-V VM using VHDX to vmdk for VMware Workstation.
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.