Hyper-V Manager within Windows Server 2012 (Datacenter Edition) can sometimes produce an odd error when attempting to turn on a typical virtual machine or VM after it has been shut down:
This error might make sense if the user is not logged in as an Administrator, but really what organization gives Windows 2012 Datacenter Hyper-V access to a standard user? In other words, the error indicating “the user has not been granted the requested logon type” makes little sense because the Administrator account normally has full control of everything. On the other hand, there are a variety of logon types that MIGHT not be granted even to an Administrator account within the server world. A quick workaround for the above is: open Services MMC and restart Hyper-V VM Manager [NOTE: this does NOT restart all the other VMs, if any, but only the service itself!]:
The VM that is shut down will turn on automatically once done. Or it can be turned on manually. This depends on how the automatic start up settings of the VM are configured. There is a full ‘fix’ for the ‘logon type’ matter, but this resolution takes under 5 seconds so it works for me, seeming as most VMs are not normally placed in a non running state – why have them around if that is the case?
Wait … what does a Linux virtual machine have to do with Microsoft? Well, in the Microsoft Azure world, virtualization is all encompassing: the idea is to support the business’s or organization’s overall needs through cloud and virtual technologies. Microsoft recognizes that Windows is not the only game in town when it comes to operating systems. Many, many organizations utilize Unix or Linux as well. And in Azure, a Linux virtual machine can easily be set up within minutes.
For those who remember setting up or installing a ‘Nix operating system over a decade ago, this process is almost incomprehensible with its ease of installation. You certainly do not have to grapple with the once common graphics or network card driver issues ;>
Quick tutorial video from Azure on installing Ubuntu in the Azure Cloud:
I want to thank Microsoft from the bottom of my heart for automating and completely cleaning up the mounting of ISO images! ISO’s are the de facto standard for Operating System (or SQL Server, Office, and others) installs these days. From the perspective of bits and bytes, ISOs are efficient, sleek, compressed packages. But in years past, they were sometimes … cumbersome to deal with.
In the virtualized world, it is important to have an ISO ‘mounted’ automatically. What does this mean? It means you click the ISO and within a split second the ISO transforms itself into a standard combination of installation binaries, or files and folders that are needed to perform an installation. The mount appears as just another ‘on-the-fly’ drive created in Explorer. From there you click the .Exe or .Msi and begin.
Back in the ‘old days’, Systems Administrators had to rely on 3rd party freeware or paid software to properly handle ugly ISOs. These did not always work as promised and frequently offered separate challenges. But this is no longer needed. For example: let’s say there is a need to install Windows Server 2012 Standard with Datacenter edition. No, I do not mean do an install while visiting your Datacenter, I mean installing a virtual machine (server) within the virtualized Windows 2012 Datacenter edition, the host. [as an aside, the ISO for Standard Edition and Datacenter Edition for Server 2012 is same].
Once, the OS is paid for and downloaded, then within the Hyper-V Manager, the new virtual machine process can be pointed to the ISO. It is transparently handled behind the scenes. And, mainly for demo purposes, the ISO for the server OS ISO can be double-clicked and mounted as well. Automatically the mount produces the needed “Setup” file. The below can also be done for Windows Deployment Services (WDS). The files below would look different, but WDS needs to have Windows 7 or 8 ISOs, for example, mounted so that the WDS server can pass needed images.
Windows 10 Preview is available. You must sign up for it, but remember this is EARLY, pre-release. You are essentially a guinea pig. Expect bumps.
But it can be fun to do betas [putting it on an old spare PC or laptop is best, provided you have nothing to lose on it]!
Microsoft will skip version 9, and will instead go to straight into version 10 sometime in the next year or so. This is very interesting, and one wonders: what COULD have been with Windows 9?! Not really, it’s just a number after all. But this is interesting, given the dramatic shifts away from PCs over to tablets or “phablets” [assorted phone devices + tablets] or more importantly, hybrid style laptops that can be adjusted to become a hand held tablet. Microsoft will need to be extremely aggressive in order to maintain any sizable chunk of business sales in any future workstation, hybrid device, and smart phone markets, given the enormous success of Google and Apple lately.
This woman does a nice simplistic overview of Microsoft’s announcement in this YouTube video.