Powered by System Center
Today is the 7th day of a Christmas-themed competition that is running through the TechNet Blog. It’s based around the ‘Twelve Days of Christmas’ carol, and @TechNetUK is giving away a number of prizes on a daily basis between now and 20th Dec. Today our Microsoft Private Cloud Computing book features as one of the prizes,
Head over to the TechNet UK page for further details on how to win of of the prizes.
Thanks to Steven Mullaghan for organizing this competition and featuring the book that was co-authored by Aidan Finn, Damian Flynn, Patrick Lownds and myself.
Note: only entries from the UK will be eligible
WHAT CAN YOU WIN?
Of course if you are not one of the lucky winners, you can still order Microsoft Private Cloud computing here:
At Inovativ, the company I work for, we more or less use Windows Azure Pack in production now. We have begun to operate as a hoster and each consultant is a tenant in our Inovativ Cloud. They can go to the Windows Azure Pack tenant portal and consume the resources we have available in our cloud. If you don’t set any rules your tenants are likely to grab all the resources that are available. Currently we have not yet set any quotas, but I’m afraid we will have to very soon.
One problem that we encountered was that VMs which were created outside of the portal did not have the correct Owner and User Role. This would mean that those VMs were not visible as owned by a certain tenant in the Windows Azure Pack tenant portal. Also when you set quota on for instance the number of VMs that could be created or the amount of memory that could be consumed, only the VMs were counted that were actually owned by the tenant.
This would be a serious problem if you are a hoster an wanted to move existing VMs to a tenant’s subscription or service plan as it is called in Windows Azure Pack. Another problem that we think is linked to this is that Cloud Cruiser which collects usage information for billing or showback is not able to process the usage records.
This is what it looks like from the admin portal when you go to VM Clouds and find all VMs for a certain tenant and subscription to a tenant plan. As you can see there not all of my VMs are listed.
It was quite easy to give access to the manually added VMs via the VM properties in Virtual Machine Manager 2012 R2. The first requirement is assign the VM to the same VMM Cloud that is used in Windows Azure Pack. If the VM does not have an Self-Service owner, you can select one. The problem however is that the only accounts you can choose are Active Directory accounts. This is exactly what we don’t want.
Have you ever wondered why you DO see performance data in Windows 8/8.1 under the performance tab in Task Manager, but DON’T see this same information in Windows Server 2012/2012 R2?
Well I kind of missed seeing that information in Server but never really bothered to really investigate.
Windows Server 2012/2012 R2
I know the solution is too simple for words, but just in case you also forgot about this good old Diskperf command which you can run from an administrative command or Powershell prompt:
Diskperf –Y to switch on the Disk Performance counters. You don’t need an academic degree to figure out how to disable them again.
So much for an easy tip with great results.
A hotfix has been released today for Windows Server 2012 Hyper-V servers which are unable to access LUNs over a Synthetic Fibre Channel after a VM is live migrated to another host in the cluster.
This problem can occur if the following conditions are met:
- You have two Windows Server 2012-based computers that have the Hyper-V role installed
- You install a virtual machine on one of the Windows Server 2012 Hyper-V hosts
- You set up a guest failover cluster, and then you make the virtual machine a cluster node
- The virtual machine is configured to access LUNs over a Synthetic Fibre Channel
- You try to perform live migration to move the virtual machine to another host.
This issue is caused by the inability of the Hyper-V host to restore the Synthetic Fibre Channel LUN on behalf of the virtual machine during live migration.
The problem applies to Windows Server 2012 Standard and Datacenter.
For further details look up the Microsoft Support Article: http://support.microsoft.com/kb/2894032
Several months ago I had a very short encounter with a Dell Compellent storage array which had just been installed for a customer in their New Jersey office. In a short blog I showed that creation of a 250GB VHDX could be done in just a few seconds. This was the result of Compellent’s support for Microsoft Offloaded Data Transfer (ODX).
In the current project I have access to an HP 3PAR P10000 V400 with HP 3PAR OS v3.1.2 and just wanted to get some idea of 3PAR’s ODX capability in a customer environment with Windows Server 2012 servers. HP 3PAR StoreServ storage is ODX compatible beginning with the HP 3PAR OS v3.1.2 (December 2012). The servers we are testing with are HP ProLiant DL380 Gen8 (32 logical processors, 256GB RAM) and are configured as Windows Server 2012 Hyper-V servers and some as SMB3 Scale-Out File Servers directly connected with 3PAR for the backend storage. The servers I use for testing are using a 10Gb Ethernet ISCSI connection using redundant Juniper EX3300 switches. The SMB3 File Servers and Hyper-V Fabric Management cluster nodes are connected to redundant 10Gb Ethernet Arista switches, just like the Internet facing Hyper-V tenant cluster nodes. The tests are done on servers with direct 10Gb Ethernet ISCSI connections to the 3PAR storage array.
Not very often do I remember a Windows Update KB article off the top of my head, but this time I have talked and written about KB2855336 so often that it was probably written into my short term read-cache..
If you have been careful and missed the first version of this update because you rather wait and see what others run into after Patch Tuesday, I must compliment your smartness!
This time I have an update on the update for you. First of all the rewritten version of the KB article and secondly a link to a blog of Microsoft’s Escalation Engineer, Rob Scheepens
The part of the July update rollup KB2855536 that corrects the AD corruption risk was KB2853952. The updated KB article, which is now titled “Loss of consistency with IDE-attached virtual hard disks when a Windows Server 2012-based Hyper-V host server experiences an unplanned restart”, can be found here: http://support.microsoft.com/kb/2853952
The blog by Rob Scheepens details a debug for the 0xD1 bug check after installing the first release of KB2855336:
http://blogs.technet.com/b/dip/archive/2013/07/23/resolved-win2012-stop-0xd1-in-mslbfoprovider-lbfosetmacaddrvmsportmapping-b4.aspx. This blog refers to the source of the bug check while live migrating virtual machines: http://support.microsoft.com/kb/2866029/EN-US
In the past week we have not seen any problems after updating all clusters with the latest Windows Updates and hotfixes. So make sure you reserve some extra testing time when next Patch Tuesday arrives. Tell your boss you definitely need a test cluster to try these updates on first. I know of several customers who found about the 0xD1 STOP by first deploying the updates to their test clusters.
In my last blog I sent out a red alert on a killer Windows Update that had not been sufficiently tested. The net result was a full crash of a two-node System Center fabric management cluster. The fabric was still in the making and backups were only provisionally taken in the form of Virtual Machine exports of the most important virtual machines. As fellow Hyper-V MVP Aidan Finn wrote unambiguously: “Something Has Gone Very Wrong With Microsoft Patch Testing”
Where did it go wrong?
I was actually demonstrating the fantastic Cluster Aware Updating functionality in Windows Server 2012 clusters, which would automatically move all VMs off a host, update it, reboot it, live migrate the VMs back to the updated cluster node and move on to the next.
The problematic July Update Rollup KB2855336 – which was one of the updates to be processed – is actually a collection of originally 20 issues that solves problems in several areas. A still unidentified part of that rollup caused a 0x000000D1 Stop error while live migrating a VM on a Windows Server 2012-based server. So Cluster Aware Updating using the Live Migration mechanism to place a host in maintenance mode, combined with the mentioned update, sent shockwaves through the cluster. In this case both cluster nodes crashed within minutes.
Ironically enough this same July Update Rollup also contained an important fix for a problem that has been around for some time: Active Directory database becomes corrupted when a Windows Server 2012-based Hyper-V host server crashes (KB2853952).
Assume that you have a Windows Server 2012-based virtualized domain controller on a Windows Server 2012-based Hyper-V host server. When the Hyper-V host server crashes or encounters a power outage, the Active Directory database may become corrupted.
This issue occurs because the guest system requests the Hyper-V server to turn off disk caching on a disk. However, the Hyper-V server misinterprets the request and keeps disk caching enabled.
If you try to disable the write caching manually you will see this error: “Windows could not change the write-caching setting for the device. Your device might not support this feature or changing the setting.” On a physical domain controller this has never been a problem.
CORRUPTED DOMAIN CONTROLLER
It takes very little imagination to guess what happened to Active Directory if you combine the full STOP of the fabric management cluster and the AD domain controllers that were virtualized on that same Hyper-V cluster without the required updates and hotfixes.
[Update July 13, 2013 - I was able to deploy the newly issued KB2855336 to all of my physical and guest cluster nodes. There have been no issues so far. The same KB will also show up in most of your VMs as it is a collection of 21 updates touching all kinds of bugs including four stop errors]
[Update July 13, 2012 – For a thank you to Microsoft testers, may I kindly refer to Aidan Finn’s very direct blog called “Something Has Gone Very Wrong With Microsoft Patch Testing”]
[Update July 12, 2013 - Meanwhile Microsoft has expired KB2855336. In WSUS you can no longer approve installation of this update and you are recommended to decline this update
Problem has been acknowledged and KB2855336 has been reissued ]
Unfortunately we again see a problem with Hyper-V clusters just after installing the Windows Updates. The previous one only broke Cluster Failover Manager which could be solved by uninstalling the responsible update or install the fix which came out very quickly afterwards.
This time we face a much more serious problem and should be a strong warning for those responsible for testing updates at Microsoft.
After updating the cluster nodes with the Windows Server 2012 update rollup (July 2013) and when Windows Server 2012 NIC teaming is used with VLANs (not entirely uncommon), you may get a 0x000000d1 bug check on one or more of your cluster nodes. If you analyze the debug, it points to MsLbfoProvider.sys which is for NIC teaming. The upgraded version of MsLbfoProvider.sys is 6.2.9200.16628.
Uninstalling KB2855336 will return you to 6.2.9200.16451 of MsLbfoProvider.sys
Please avoid the July rollup until we find out which part of the rollup is responsible for this problem.
[See updated info top of blog!]
Today I received word from Microsoft that I am re-awarded as a Microsoft Most Valuable Professional for Virtual Machine. When I received my first award for Cluster back in 2009, I could not begin to understand its consequences and how much such an award would mean in terms of recognition, access to knowledge, direct contact with the product teams and all those forums crowded by fellow MVPs in Hyper-V, cluster, System Center, file & storage.
Today you can’t live on an island anymore and only specialize in one direction. Although my focus has always been Hyper-V, clusters, servers, storage, I now see so many other technologies need be be learnt to provide high level services in the private, service provider and public clouds. Networking is one subject which is difficult to ignore, although I must admit I have tried. Especially NVGRE and Hyper-V Network Virtualization, the in-box Gateway in Windows Server 2012 R2, the Hyper-V Extensible Switch, physical switch integration with the OMI standard …… there are so many technologies in networking alone, that this will easily be the subject I will be studying in the coming year.
My sincere thanks to all my fellow MVPs, the EMEA MVP team, my book and blog readers, the Windows Server and System Center product teams, my colleagues and my family who’ve all made this possible.
This morning my new colleague at INOVATIV, Marc van Eijk had to remind me that my MVP was due. I had simply been too busy after TechEd and had forgotton all about it. Then again I did not think of my re-award until Microsoft sent me this email message:
Looking forward to another great year being part of a superb community!
This blog is intended to help you get started with Windows Server 2012 R2 and Windows 8.1 real easy. It is just a quick reminder of an older blog of mine describing the Boot from VHDX process, which is sometimes also referred to as Native VHD boot. The idea is that you boot off a self-created VHDX and have all the functionalities of the operating system at your disposal. Running Hyper-V is just one of these options.
Wait for the upcoming new Preview builds of Windows which you will be able to download next week as ISO files. To make Boot from VHDX work as intended, you need to convert that ISO file to either a VHD or VHDX. If you are running Windows Server 2008 R2 or Windows 7, I suggest you use VHD because VHDX was not supported at the time. If you are running Windows 8 or Windows Server 2012, you can convert the OS ISO file to VHDX by running this handy script created by Mike Kolitz.
The Convert-WindowsImage.ps1 script does all the work.
All you need to do is have the ISO file available, use above script and make the VHDX bootable.
Start Windows PowerShell in Administrator mode and run the script like this:
If you run it with –ShowUI parameters a menu will appear asking you to fill out some details:
The script will run for a will so wait till the VHX has been created.
As soon as the VHDX is ready, place it in the preferred directory. In my case I have placed the VHDX in the c:\VHDX directory:
Finally you can make the VHDX bootable by just two steps:
- Right-click the VHDX to mount it (check the drive letter, e.g. F:\ )
- Run this command in an administrative prompt: bcdboot F:\Windows
And you are done. The bootable VHDX is now at the top of your boot order list. As soon as you reboot your machine, it starts he new operating system without hurting your current installation.
Have fun testing the great new Windows versions for both server and client!