Great news in was announced today in It’s here! The Microsoft Ignite Session Catalog. Basically the Ignite session catalog is available as of this moment! That means we can start planning to make sure we make the most of our time there. If you need some tips on what’s the value of a conference and how to make the most of it than please read a previous blog of mine on the subject Why I Find Value In A Conference
But MSFT is also organizing an #IgniteJam on Twitter on February 3rd, 9:00 am Pacific Time (That’s 18:00 in GMT+1). Join them and get your questions answered.
I know a good many of people in my global network that will be there so that’s great news. Networking and exchanging information is a big part of what makes a conference a success. The right people being there makes a huge difference. Whilst on that subject, here’s a tip to the vendors in the expo hall: make sure you have technical people there as well, only sales and marketing isn’t good enough. Go for the right mix.
Follow @MS_Ignite on twitter for the latest news and developments about the conference. Go to the registration page to secure your ticket and consider add one of the Pre-Day session to the agenda to optimize your investment in time. See you there!
As you all probably know I’m also playing around with and testing Windows Server vNext Tech Preview and one of the nice new features in there I have my eye on is Soft Restart.
There is little information on this feature out there right now but from the description “Soft Restart” looks like a way to get faster Windows boot times by cutting down on device firmware initialization. When it’s not needed that would be a great thing to have as with > 10gbps live migration speeds the boot time of our hardware loaded (DRAC, NICs, HBA, BMC, …) servers is what makes it the longest single step per node during cluster aware updating. Interesting if this is indeed what it’s there for.
But let’s find out if this is indeed what we think it is . First of all the installation of this feature requires a restart. Keep this in mind.
There are 2 ways to kick it off that I know of but to me there must be more … it would be a shame not to have this integrated as an option into Cluster Aware Updating for example.
Option 1: via shutdown
So let’s try shutdown /r /soft /t 000. No joy, doesn’t make one bit of difference and nothing logged or so to indicate an issue.
Option 2: PowerShell via Restart-Computer –Soft
No joy here either …
What could be the problem?
So I figured I needed enterprise grade server hardware with some FC cards & lots of NIC and memory to notice the difference. On a VM it might do nothing, but I assure you I doesn’t do anything on the PC based home lab either. So I dragged a DELL PowerEdge R730 with exactly that into the game. But still no joy. Then I thought some more and decided it might integrate with the hardware capabilities to do so of I went to install the latest and greatest DELL Server Manager software to see if that make a difference. But again, no joy.
It’s probably not lit up yet in this release of the Technical Preview 9841. For now I’ll be content with the 28-30% improved reboot speeds the DELL R730 UEFI brought us. I’d love to speed things up a bit as time is money and valuable but we’ll have to wait for the next code drop to see if and how it works …
Benefits of delivering updates to the integration services via Windows Updates
In Windows Server vNext aka the Technical Preview the integration services are being delivered through Windows Update (and as such the well know tools such a s WSUS, …). This is significant in reducing the operational burden to make sure they are up to date. Many of us turned to PowerShell scripting to handle this task. So did I and I still find myself tweaking the scripts once in a while for a condition I had not dealt with before or just to get better feedback or reporting. Did I ever tell you that story about the cluster where a 100VMs did not have a virtual DVD drive (they removed them to improve performance) … that was yet another improvement to my script => detect the absence of a virtual DVD drive. In this day and age, virtualization has both scaled up and out with ever more virtual machines per host and in total. The process of having to load an ISO in a virtual DVD drive inside a virtual machine to install upgrades to integration services seems arcane and it’s very timely that it has been replaced by an operation process more befitting a Cloud OS .
I have optimized this process with some PowerShell scripting and it wasn’t to painful anymore. The script upgrades all the VMs on the hosts and even puts them back in the state if found them in (Stopped, Saved, Running). A screenshot of the script in action below.
I’m glad that it’s now integrated through Windows Update and part of other routine maintenance that’s done on the guests anyway.
But is not only good news for us “on premises” system administrators and integrators. It’s also important for service/cloud providers and (hosted) private cloud hosters. This change means that the tenants have control of updates to the integration services of their virtual machines. They update their Windows virtual machines with all updates during their normal patch cycles and now this includes the integration services. This provides operation ease (single method) and avoids some of the discussions about when to upgrade the integration services.
Legacy Operating Systems
Shortly after the release of the Windows Server Technical Preview, updates to integration services for Windows guests began being distributed through Windows Update. This means that on that version the vmguest.iso is no longer needed and as such it’s no longer included with Hyper-V. This means that if you run an unsupported (most often legacy) version of Windows you’ll need to grab the latest possible vmguest.iso from an W2K12R2 Hyper-V host and try to install that and see if it works.
What about Linux and FreeBSD?
Well nothing has changed and how that’s taken care of you can read here: Linux and FreeBSD Virtual Machines on Hyper-V
I’ve discussed the efforts Microsoft is putting into enhancing the storage offerings (Storage Spaces, SOFS, SMB) in its OS since Windows Server 2012 (R2) before in previous articles. In my last blog post on this subject Microsoft Keeps Investing In Storage Big Time I talked about their latest announcements around storage replica in the Windows Server Technical Preview.
In this post I’d like to show case how to set up server to server storage replication and demonstrate how to recover from certain events. We are doing this asynchronously as the scenario is one were we replicate a backup target off site to another city. Not an uncommon scenario and one that gives copies off site without introducing the cost & operational overhead of portable media.
The easiest way to show this without writing elaborate white papers is a video. I’ll wait with more elaborate writings or demo videos as things are bound to change a lot prior to RTM. After all we still only have the more then 3 month old Technical Preview bits. It’s important to realize what we are now getting in box with Windows Server aka the Cloud OS that used to require 3rd party solutions.
I hope to be doing some talks & presentations on this subject and in good tradition make those presentations demo heavy as I like to really show how technology in action.