Avatar of bobox00
bobox00
Flag for United States of America asked on

Hyper-V Best Practices for Windows 2008 and 2012

We are trying to set standards for Hype-V in our organization. What are considered best practices for Hyper-V for server 2008 and 2012. What should be on a server that will be setup as a hyper v server for each. Please state whether you sentences pertain to 2008, 2012 or both.

Thanks in advance for your responses!
Microsoft Server OSWindows Server 2008Windows Server 2012Hyper-V

Avatar of undefined
Last Comment
Philip Elder

8/22/2022 - Mon
SOLUTION
Ram Balachandran

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
Svet Paperov

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
bobox00

ASKER
Thanks
Philip Elder

Some thoughts on this:

CPU: GHz over Cores
Memory: Largest, fastest for CPU, and one stick per channel
BIOS: Disable C3/C6 States
Disk subsystem: Hardware RAID, 1GB Cache, Non-Volatile or Battery backed
Disk subsystem: SAS only, 10K spindles to start, and 8 or more preferable
Networking: Intel only, 2x Dual-Port NICs or more ports.
Networking: Team Port 0 on both NICs for management Port 1 for vSwitch
Hyper-V: Server Core has a reduced attack surface plus lower update count
Hyper-V: Fixed VHDX files preferred unless dedicated LUN/Partition
Hyper-V: Max vCPUs to Assign = # Physical Cores on ONE CPU - 1
Hyper-V: Standalone preferred to keep Workgroup and use HVRemote

Those are some of the key things we keep in mind when configuring Hyper-V environments whether standalone or clustered.

Philip
Your help has saved me hundreds of hours of internet surfing.
fblack61