When I joined ISC Software
I received a new laptop which was pretty much a blank slate except for Windows itself. This meant that I had to install and configure everything I needed (I prefer this as it means I can configure everything exactly as I want it).
Due to having an SSD, instead of an HDD, in the laptop, I also got an external SSD which I am using for hosting my virtual machines using Hyper-V.
I thought nothing of this, but when I tried to start a VM from the external SSD, I received the following error:
...Failed to power on with the Error 'The requested operation could not be completed due to a file system limitation'.
I double checked the external SSD and discovered it had a File System of exFAT; I reformatted the SSD into NTFS copied the virtual hard disks back onto it and was able to successfully start the virtual machine.
When I joined Perfect Image they had, unfortunately, standardised on VMware Workstation for virtualisation and I have been stuck using it ever since (we have recently been transitioning to Hyper-V which I intend to start using exclusively once I can get all the VMs either converted or recreated).
I was away for a demo the other week and the night before I tried to launch the demo VM to do some final preparation when I got the following error:
GP Demo - VMware Workstation>/p>
Not enough physical memory is available to power on this virtual machine with its configured settings.
This error message was a baffling one as I had run the VM a couple of days previously with no problems and had made no changes to the laptop in the intervening period.
The fix was a rather odd, yet simple one: launching VMware Workstation using Run as Administrator allowed the application to launch and the VM work without further problem.
Since doing this I have been able to launch the VM at any time under my usual security context.
I make a lot of use of virtual machines for both testing and demonstrating Microsoft Dynamics GP. As a company, when I joined, Perfect Image tended to use VMware (I’ll reserve comment, which I realise tells it’s own story), but more recently have started making more use of Microsoft Hyper-V, which is what I also use at home for testing and writing my blog and books.
After installing Hyper-V on my work laptop I created a virtual machine and clicked start. Unfortunately, I received the below error messages:
I did some digging around and found that although Hyper-V was installed, the hypervisor wasn’t running. Fortunately, the laptop I have does support Hyper-V and I only had to do one thing which was to enable the hypervisor by opening an elevated command prompt and type the following command:
bcdedit /set hypervisorlaunchtype auto
Once I had run the command I was able to start the virtual machine without further problem; at least with Hyper-V.
What I found was that with the hypervisor running, I wasn’t able to start a VMware virtual machine. So a second command can be used to disable the hypervisor for those times when I need to use a VMware virtual machine:
bcdedit /set hypervisorlaunchtype off
Hopefully, I’ll be able to complete the transition away from VMWare very soon and stop toggling from one to the other.
I think I mentioned the other week that I had built a new Hyper-V server to use a as a test bed. I did run into an issue when I created the second virtual machine and tried to install SQL Server into it when it was complaining about S IDs.
I did a quick look around and realised that the problem was because I had created a virtual machine with Windows installed and made a backup of this VM which I had been copying to create subsequent machines.
The first VM I configured properly became my Domain Controller and had worked fine.
The second machine, and every subsequent ones needed to be tweaked using the System Preparation Tool before it is used.
To run the System Preparation Tool (sysprep), open the Run window and type sysprep;
Continue reading “SysPrep Virtual Machine After Replication”