Yesterday I was testing Bare-Metal deployment on a VMM 2012 R2 with a new Hyper-v image and got the error 21161 during the process of making a physical machine into a Hyper-V Server.
I did of course check the library server (which was the same as the VMM server) and also that the vhdx that contains the Hyper-V image was in the library. I also checked the profile where the reference to the VHDx is and everything looked good.
The error was resolved when checking out the library server properties and changing to a host group instead of the default.
I have been deploying servers from this VMM before and why it started to complain right now is a mystery and I will dig and see if I can find the reason and if I do you will get an update on the blog, but now you know how to get it running
Update: Daniel Clarke mentioned my fix, In the VMM I have as this error occured I had not updated to UR3 during the time between the deployments which would otherwise had maybe explained the error. I have now updated the server to UR3 and can still do bare-metal deploy.
I have been helping a customer a while with their Hyper-V environment and now I saw on twitter that HP had new Emulex drivers that could be downloaded so I thought that I should give it a try, there has been quite a storm about the problems with VMQ and Emulex and if you want to read more about that you can check out this link to my friends at Hyper-V.nu . My experience of this problem is that it have been on Gen8 HP blades with a newer Emulex networking on them. Right now I only had G7 to test on.
As a best practice I run the Hyper-V hosts in Core but that did not give me any issues when installing (yes I use VMM bare-metal deployment and will after verified success update that to have this latest drivers )
As it is networking drivers I lost my RDP session for a few seconds before it was fully installed and then I could see the result
And checking with powershell Get-NetAdapter I can verify that the GUI is not lying
And also you can see that the VMQ is enabled for my two NIC´s
Here you can find the HP drivers for in this case a HP BL460 G7 .
I have now in a couple of weeks been testing a Nokia Lumia 930 phone and it is soon time to return it. Importantly that need to be said here is that I have been using iPhones since 2008 and also for a short while I used an Android phone and quite quickly went back to the iPhone.
The iPhone and Apple has been very successful with their devices since the first came out. The amount of apps available for IOS is huge and companies and governments also have adapted and created usable apps for making the life of the user smooth.
The Windows Phone in it´s earlier versions have had its ups and downs and I have not seen it as a possible replacement before the version 8 of the OS and later..
Now as I have lived with the phone and tried to adapt I can really say that I like it.. the build quality is magnificent and the screen looks great, it is fast and I can manage my daily tasks, it is obvious that the development of the OS have got some attention and Microsoft have thought through how the phone should work and with the new features like for instance Cortana it is in the edge of Phone OS development..
Still I miss my banks app but they say that it is coming this year so when that one have arrived I can buy me self a beutiful Lumia
Some of the apps I have installed:
- SAS Scandinavian Airlines
- SVT Play
- Amazon Kindle
- Easy Park
- Facebook Beta
- Instagram Beta
- Lync 2013
- Office Lens
- PC Remote
There are of course more apps that would make it into the cut and the development of new apps go blazing fast so just because your favorite app right now only exist for Android or IOS that will change in a near future. I think we will see a fast changing map now that Microsoft owns the phone division of NOKIA and can make the momentum for devices and solutions that would attract new users that most likely could have been stuck with an iPhone before..
So when you are going to change device next time, think twice and look at the Lumia phones!
Today I was just checking my tweets and saw that the PowerShell team had released a new build of the Windows Management Framework v5, this time its the September build and it works only on Windows Server 2012 R2 or Windows 8.1 and if you have a previous version that was released in july of the v5 you have to uninstall that first and then you can install this version
here is a quote from the PowerShell team at http://blogs.msdn.com/b/powershell/archive/2014/09/04/windows-management-framework-5-0-preview-september-2014-is-now-available.aspx
The following is a list of all the new scenarios enabled since May 2014:
- Generate Windows PowerShell cmdlets based on an OData endpoint
- Manage .ZIP files with new cmdlets
- DSC Authoring Improvements in Windows PowerShell ISE
- New Attribute for defining DSC meta-configuration
- Use partial configurations DSC
- Cross-computer synchronization through DSC
- Get the current DSC configuration status
- Compare, Update, and Publish DSC configurations
- Audit Windows PowerShell usage by transcription and logging
- Extract and parse structured objects out of string content
- Extend the item noun to enable Symbolic Links
- Develop with classes in Windows PowerShell
- Register a PSRepository with PowerShell Get
- Network Switch management through Windows PowerShell (improvements)
I used a Azure VM to test and install this version
And once rebooted I can check via Get-Host what version I am actually running
I have had the privilege to read the book System Center 2012 R2 Virtual Machine Manager Cookbook – Second Edition by Edvaldo Alessandro Cardoso
This is a Cookbook with tons of recipes that will help you setup and configure VMM 2012 R2. With the Cookbook format you easily can get information and knowledge in the area that you need and use it as a reference.
The content includes
- VMM Architecture
- Upgrading from previous versions
- Installing VMM 2012 R2
- Installing a HA VMM
- Configuring Fabric resources
- Deploying VMs and services
- Managing VMware ESXi and Citrix Xen
- Managing hybrid clouds
- Integration with SCOM
- Scripting with Powershell in VMM
I can really recommend this book even if you know some about VMM, Edvaldo gives some more insights and information that can help you in your work!
If you want to buy this book you can do this at the following link http://bit.ly/1s7qAqO
Hope that you all have a nice summer!
I have been busy with vacation and taking care of the family the latest couple of weeks! But there is some news I want to share with you, Tomorrow I will work my last day at Lumagate and then a new adventure will start at my old employer Real Time Services.
My role will be Chief Technical Architect – Microsoft Solutions, within this I will be responsible for offerings and design with hybrid clouds based on Azure and all its features, Hyper-V and office 365. With the new functionality that Azure continuously delivers it will be exiting times ahead getting customers to utilise and see the benefits with an hybrid cloud environment.
Real Time Services is also in a new exciting phase with a recent merger with two other companies making a larger and broader company that will be able to be a better solution provider and also make a serious commitment on Microsoft Cloud OS. The other companies that is part of the merger are PMCG and Skypoint.
If you want to contact me from now on use the following details
In my latest blog I was exploring the possibility to get a Redhat Linux to work in a generation 2 VM and I was also explaining that I had some issues with the CentOS version 7 that is currently being developed and that issue was with the EFI boot and it was malfunctioning!
Now as of yesterday 25 of June when there was a new release I could actually get a working CentOS 7 in a generation 2 VM on my lab environment!
So to get the fresh build installed on a Gen2 HyperV 2012 R2 VM you can do the following,
here I found the Boot ISO -> http://buildlogs.centos.org/centos/7/os/x86_64-latest/images/ and downloaded the boot.iso and configured it to be used for boot in my test-VM and as I described in the other post I unchecked the Secure boot also
Once booted I connected the network and then added the path to the repository
The path to be added was http://buildlogs.centos.org/centos/7/os/x86_64-latest/ , by using -latest in the path you will get the latest build instead of some old maybe not so well working version, as described on their page the distribution is still being developed
And then choosing what roles to install and partitioning of the disk and then start the installation
Once installed you can see that it now nicely boots into CentOS and I can log in
And you can see that it utilizes the Dynamic Memory function of Hyper-V also
I was reading the post from Ben Armstrong how he installed and configured a Ubuntu Linux VM to work under a generation 2 VM.
And after that I wanted to try this with either Red Hat Enterprise Linux 7 or CentOS 7 as they would incorporate the Linux integration components that would be needed for being able to let go of that VM BIOS legacy generation 1 Hyper-V VM :-). Red Hat has released their 7 but CentOS is still in buildmode and thus this would be done on their “nightly build” as described on the site http://seven.centos.org and I did take a test with the current release but got an error during install with the EFI Boot so I went for the Red Hat and tried with that.
So Downloading the Redhat ISO and creating a VM was the first steps, If you do not have an account at redhat you can sign up and download a trial.
And then I created a VM and as Ben showed I disabled secure boot and added the ISO to boot:
After that I booted the VM and connected the network and configured the settings and choosed a Server with A GUI
The installation was successful and I could reboot with no warnings or errors
Then once the installation was complete I could start a browser and test and as you can see it is a Generation 2
I will during the next couple of days check out the new builds of CentOS and see if my error will be fixed and I can create a Gen2 VM of that one also
I have for a Server Lifecycle project been investigating the possibility to add a vCenter 5.5 to a System Center VMM 2012 R2 environment as we are going to use WAP, SMA, SPF and VMM.
Based on the documentation on Microsoft Technet site the support ends with vSphere 5.1. Now this customer already runs vSphere 5.5 and I wanted to quickly check if it was possible at all to connect a vCenter 5.5 to VMM 2012 R2 and manage some basic tasks on VM´s.
And as you can see I managed to add the vCenter Server and after adding a ESXi host the view in VMM looks like this
Checking it in PowerShell, I can see that it looks and reports in the same manner as the 5.1 vCenter that I have registered
And after some VM massage I can see that basic tasks as starting, stopping and also taking snapshots works as intented through the vCenter 5.5.
Of course new features introduced in vCenter 5.5 and ESXi 5.5 for the VM´s will not work and there might be other things that also can have issues, I will continue to explore and if I find anything that seems to be a showstopper I will do a followup blog post.
Read on Twitter that someone wanted an image in the gallery for a Windows Server Core to get a smaller footprint instead of the full gui VM
As you know there is a way to go to core mode from a full installation so after you have deployed a IaaS VM you can run the following commands to remove the GUI. The roles Server-Gui-Shell and Server-Gui-Mgmt-Infra can be removed.
And then as instructed, you reboot and when you are up and running again there is some configuration that needs to be done so just be patient and wait…
After that is done you can proceed to the wonderful world of the command prompt and sconfig
And the next step is to sysprep and shut down this and capture an Image to be able to provision this one.
Once the VM is in a Stopped State you can capture it
Once that job has completed you can find your image in the gallery, observe that as this is saved in your storage account that is bound to the location you cannot deploy Core VM´s to all azure datacenters if you do not copy this storage blob to the other azure datacenters storage accounts that you have set up.
And when I have deployed a new VM it is in the wonderful world of Server Core!