irnax.blogg.se

In other words, it's up to you to decide if you should apply these in your setting. If implementing one (or more) of these Best Practices seems sensible, great if it doesn't, simply ignore it. As such, you should carefully review each item to determine if it makes sense in your environment. Best Practices are general guidelines, not hard, fast rules that must be followed. So, without further ado, here’s the newly updated Hyper-V 2012 and Hyper-V 2012 R2 Best Practice Checklist!ĭisclaimer: As with all Best Practices, not every recommendation can – or should – be applied. It’s important to note this is not an exhaustive compilation, rather a grouping of features/options commonly used in businesses I’ve had the pleasure of assisting.Ī special thanks to Ted Teknos, Ryan Zoeller and Rob Hefner for their input/suggestions/corrections as I put this together! I find having a checklist can be a great tool to use not only when reviewing an existing Hyper-V implementation, but one which can be leveraged as part of pre-planning stages, to ensure best practices are implemented from the start. Those of you who have used my previous checklist will notice quite a few items remaining that’s because many of the best practices still apply to Hyper-V in Server 2012 and Server 2012 R2!! and overhauled with the latest release of Server 2012 and Server 2012 R2. The following is a checklist I initially developed for Windows Server 2008 R2 SP1 (which can be found here. Windows Server 2012 and Windows Server 2012 R2 provided major improvements to the Hyper-V role, including increased consolidation of server workloads, Hyper-V Replica, Cluster Aware Updating (CAU), network virtualization and the Hyper-V extensible switch, just to name a few! Hyper-V 3.0, as some call it, helps organizations improve server utilization while reducing costs. First published on TechNet on Mar 10, 2013