Windows Server Technical Preview Hyper-V – A Few Things

IT Engineer insert a Blade Server in Data Center Besides not knowing the final name of Windows Server Technical Preview (Windows Server 2016, or perhaps Windows Server TP) here are a few things coming with this release of Hyper-V that I am looking forward to with Microsoft’s latest OS.

First, finally being able to hot add/remove a vNIC or RAM. This isn’t shaking the world of virtualization, but it sure is terrible when you want to add a vNIC and you have to take a server offline. Thank you Microsoft.

Second, moving Integration Services into Windows Updates will be great to help automate the upgrades with centralized management tools and put more control with the server administrators.

Third, the ability to add the latest Hyper-V server to an existing Hyper-V 2012 R2 cluster. This will make it a lot less of an ordeal to roll a client up to the next OS.

Lastly, Production Checkpoints. They have made this the default checkpoint, but have left the option for the standard one. They are stating that it will be able to create a “point in time” image of a VM that can be restored in a way that is completely supported for all production workloads. Using VSS inside Windows and flushing the system buffers on Linux to create a file consistent checkpoint. I would still advise to backup your SQL databases before upgrades. 🙂


Presenting on “Hyper-V Innovations for the SMB” next weekend. Featuring Hyper-V Server 2012 R2.


I am getting my presentation finished up for my session at the IT Pro Camp event at Northwest Florida State College next weekend and I am pretty stoked.

I will be looking at a virtualization solution from a cost, HA/DR/BC, and management standpoint. I will be showcasing how innovations to Hyper-V with Hyper-V Server 2012 R2 are changing the game for the SMB. Looking at VMware ESXi 5.5 free hypervisor and Hyper-V Server 2012 R2 free offering to see what value you can get out of them as an SMB. I will have a live lab demonstration with a Hyper-V 2012 R2 host cluster and will go over so many exciting features.

I will be posting my slide deck, possibly videos from the presentation, and a PDF with the details after the presentation. So check back after the October 5th!

If you are in the Northwest Florida area I hope you can make it to this free event at IT Pro Camp on October 5th.

IT Pro Camp Information and Registration

Selecting the right collation when setting up your SQL Server instance for your System Center 2012 SP1 components

Microsoft System Center 2012 SP1 is a great product for managing your modern private cloud. The System Center suite has been moving closer and closer together in integration with one another, and I believe that this will continue to be the trend for obvious benefits of a tightly integrated solution. For now, in my opinion, they are rather involved to setup and integrate together, but for what they deliver I believe it is well worth the trouble. Which is why I am investing in my MCSE Private Cloud certification. 🙂

However, in working to integrate the components in my lab environment I found that selecting the right collation (ex. SQL_Latin1_General_CP1_CI_AS)  for your SQL Server instance is paramount unless you want to encounter issues when linking them together. This turn out to be a rather deep issue after searching online and comparing system requirements for the System Center components, and I came upon a very helpful and informative article, “Clarification on SQL Server Collation Requirements for System Center 2012” by Travis Wright at Microsoft. I recommend reading this article as I cannot explain it any better.

I will say, this little Collation tab has never stood out so much until now.