IMPORTANT ANNOUNCEMENT FOR OUR READERS!
AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at https://aka.ms/CISTechComm (hosted at https://techcommunity.microsoft.com). Please bear with us while we are still under construction!
We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either https://aka.ms/askpfeplat as you do today, or at our new site https://aka.ms/CISTechComm. Please feel free to update your bookmarks accordingly!
Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.
If you have never visited the TechCommunity site, it can be found at https://techcommunity.microsoft.com. On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.
NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at https://aka.ms/PFETechComm!
As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!
Hello, everyone! Roger Osborne here with an update on my Hyper-V Best Practices blog for Server 2012. It has been around 7-months since the initial posting, and might I say the response has been (and continues to be) A-MAZ-ING!
In my humble opinion, the interest surrounding my blog points directly to the volume of small, medium and large (Enterprise) businesses making Hyper-V their virtualization solution of choice! Not only has Hyper-V proven to be an enterprise-ready solution in very demanding datacenters around the world, it has also proven to be a cost-effective approach to reducing server footprints in today’s fiscally conscious businesses.
Having a great product doesn’t mean resting on your (proverbial) laurels, however! As some of you may know, Microsoft released Windows Server 2012 R2, and included in that release are some TERRIFIC new/improved features specific to Hyper-V!
Here are just a few of my personal favorites:
- A greatly improved Live Migration, which can greatly reduce the time to migrate VMs from one node to another using compression.
- The ability to resize a VHDX that is connected to a running VM
- Cross-Version Live Migration, which enables you to easily move VMs from Server 2012 Hyper-V hosts to 2012 R2 Hyper-V hosts
- Automatic VM activation. What’s not to love about automating activation when you’re running the datacenter version of Hyper-V!?
- And last, but certainly not least, a new Integration Service feature that allows you to copy file(s) from an R2 VM to the R2 host WITHOUT using a network connection! That’s very cool in Roger’s world, my friends!
For a complete list of updates and new features, check out this TechNet article: http://technet.microsoft.com/en-us/library/dn282278.aspx
With all the improvements in R2 you’d think there would be quite a few additions and/or changes to my Hyper-V Best Practices blog for Windows Server 2012, but that’s just not the case; which is good news for you!! If you’ve already followed the guidance provided in my blog, you can simply carry those same practices over to Hyper-V in Windows Server 2012 R2!
The only addition I am making to the Best Practices blog – related to new/improved R2 features – is the following:
⎕ (New R2 Feature) Shared Virtual Hard Disk: Do not use a shared VHDx file for the operating system disk. Servers should have a unique VHDx (for the OS) that only they can access. Shared Virtual Hard Disks are better used as data disks and for the disk witness.
For more information:
Other changes and updates (not specific to R2) have also been made to the blog over the last few months, so take a few minutes and head over to the newly updated Best Practice blog. Feel free to leave a comment if you have a question or suggestion.
While I have your attention, have you heard of the Windows 8.x app called Posterpedia? If not, you’re in for a treat! The latest release includes a great poster for Hyper-V on Server 2012 R2. Check it out!
Also, Microsoft is currently offering training and Hyper-V certification — for free!! Check out these posts to learn more:
So, tell me: What’s your favorite new feature in R2? I’d love to hear from you, so add your comment below!
I sincerely hope you find this blog posting useful! If you do, please forward the link on to others who may benefit!
Until next time,
Roger “best practicing” Osborne, Microsoft PFE
(Twitter: RogOsb; LinkedIn: http://www.linkedin.com/in/rogerosborne)