According to WMI, it is now 132 days since we brought up the first production VM on Windows Server 2012 Hyper-V so I thought I’d recap a bit. If you don’t care to read all, here’s the main bullet points: -Performance-wise Hyper-V works as expected -The lack of management tools is hurting us every day
Stuff is so fast-paced at the moment I pretty much just sleep, work, repeat. In all the chaos and change I wanted to make a note of today just to be able to save the date for reference. We are live on Windows Server 2012. In production. Deployed. And although I’m eagerly awaiting at least a
It’s finally time to put things into production. If you’re like me you have a bunch of VMs working happily on Windows Server 2012 RC and you want to get your cluster updated. Here’s what I’ve found: I brought up a node with the RTM install and added it to my Hyper-V Cluster. All good.
UPDATE 15.08.2012: It turns out that the procedure I originally outlined will you end up with a CIM server (which SCVMM uses for comms) that cannot start its ssl port because of un-trusted certificates. I found that the best way to remediate the situation is to uninstall the cimserver (openpegasus) and then reinstall the whole
Now if that’s not a blog post title, I don’t know what is! Here’s the deal: We are currently testing Windows Server 2012 on production-scale hardware. We’ll probably put Hyper-V 3.0 into production the minute Microsoft releases the final version, in 2-3 weeks time if we’re lucky. Right now, we’re running a 2-node Hyper-V cluster