While moving some VM’s from Hyper-V to VMware using VMware Converter a VM failed to convert with the error: FAILED: The VSS snapshots cannot be stored.
FAILED: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).
Come to find out the System Reserved partition was full. Our soon to be retired Appassure backup application was nice enough to fill up the volume.
Luckily Appassure is being replaced by Veeam and fixing the above VMware Converter error is an easy fix.
How-to fix VMware Converter error FAILED: Unable to find the system volume, reconfiguration is not possible.
I was recently tasked with migrating a Hyper-V machine to our VMware environment. However, each time VMware Converter was ran, the task would fail at 97% with an error “FAILED: Unable to find the system volume, reconfiguration is not possible.“.
Looking further into the virtual machine there were a number of concerns I had on the VM. One such issue which I believe might be causing the above error, is that the system volume drive was on drive 0 while the “C:” drive was on drive 1. Whereas these are typically on the same drive in most Windows installs.
Below are the steps I took to fix this VM and made the migration from Hyper-V to VMware a success.
I recently redid my VMware home lab environment and after enabling HA the warning message “This host currently has no management network redundancy” started displaying on each of my ESXi hosts.
This warning happens because in a HA cluster there is a requirement for the management network to have redundant NICs, but in my case I’m using Intel NUCs which only have a single NIC and since this is only a lab I don’t care to see the warning so lets disable it.
If you have the pleasure or meeting certain audits or security compliance then having a login banner message on your systems is a pretty common requirement. Sometime ago I detailed how to add a login banner message to ESXi hosts, below I’ll show how easy it is to do the same with your VMware vSphere web client or HTML5 client using vSphere 6.0 Update 2 or better.
With the release of VMware vCenter 6.5 Update 1 also comes VMware ESXi 6.5 Update 1 and just like vCenter there are a number of changes, updates, and fixes for ESXi as well in 6.5 Update 1 – you can see the release notes here.
Yesterday I made a post on how to upgrade VMware VCSA 6.5 to 6.5 Update 1. Below I’ll show you three ways to upgrade your ESXi hosts to 6.5 Update 1.
VMware just released VMware vCenter 6.5 Update 1 just last month, in case you’ve missed it check out the release notes as there are a lot of fixes, improvements and additions.
In this post we’ll see just how easy it is to update the VMware VCSA. Before you do any VMware update I’d highly recommend checking out the VMware Interoperability Matrices to check compatibility of other VMware products. Once you’ve done that, lets begin!