[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] Hotfixes for Hyper V - THE OFFICIAL BLOG OF THE SBS "DIVA"
Thu, Dec 4 2008 23:36 bradley

Hotfixes for Hyper V

Jose Barreto's Blog : Apply these Windows Server 2008 hotfixes to avoid known Hyper-V issues:
http://blogs.technet.com/josebda/archive/2008/12/04/apply-these-windows-server-2008-hotfixes-to-avoid-known-hyper-v-issues.aspx

The SBSized version of Jose's Grid is as follows with my comments as to whether they are needed for virtualization in SMB in italics

Article Number

Description

Date Released

When it’s needed

950050

Hyper-V RTM

26-Jun-2008

Always, also in Windows Updates - Must have in order to have SBS 2008 be deployed in the Child of the HyperV parent

950182

Resolve issue with Hyper-V virtual machine running x86 version of Windows using fewer processors than expected if the number of cores on a socket is not a power of 2

11-Apr-2008

If Windows x86-based VM used with a 6-core processor, apply to child  Not needed as SBS 2008 is 64bit

951308

Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role

11-Sep-2008

If Failover Clustering is used

Can't do clustering so not needed

951636

Hyper-V Language Pack Update for Windows Server 2008

11-Sep-2008

If using the additional languages offered

Only needed if you plan to localize in your language

952627

Remote management of Windows Server 2008 Hyper-V

11-Sep-2008

If managing Hyper-V remotely, apply to remote - Need to plan for remote management if you don't use the full GUI of Windows

953585

Resolve issue when you try to start a Hyper-V virtual machine on a Windows Server 2008 computer that uses the NUMA architecture

04-Sep-2008

If NUMA hosts are used

NUMA what? :-) Not needed.

953828

Resolve issue with NLB host not working as expected on virtual machines

25-Jun-2008

If NLB is used, apply to child

Network load balancing probably not used in a SBS setting

956589

Resolve potential issues when you manage Hyper-V with SCVMM

23-Sep-2008

If SCVMM is used

You might use this

956697

Resolve issue in which the Hyper-V Volume Shadow Copy Service (VSS) does not back up virtual machines properly

08-Sep-2008

If VSS is used for backups

You might need this?

956710

Increased number of logical processors to 24 and virtual machines to 192

23-Sep-2008

If more than 16 logical processors are used

If you install a system with more than 16 processors, I want to hear from you and get a picture of that box :-)

956774

Resolve the scenario where a BITS client cannot handle files that have paths that contain the volume GUID in Windows Server 2008

23-Sep-2008

If volume GUIDs are used - not needed

957967

Resolve issue with Hyper-V memory management

08-Oct-2008

If issue described surfaces - appears to only occur on clustering

958065

Resolve issue with Hyper-V and Failover Clustering combined with a storage device managed by a third-party clustered file system or a third-party replication solution

03-Nov-2008

If third-party clustered file system or third-party replication solution used - probably not needed

958184

Resolve issue with virtual machine backup operations failing in Windows Server 2008 when Hyper-V virtual machine files are saved on a volume that is mounted on a failover cluster by using a volume GUID

05-Nov-2008

If backing up a volume mounted using a volume GUID - probably not needed

Filed under:

# Re: Hotfixes for GUID

Friday, December 05, 2008 10:38 AM by Joe_Raby

While those GUID issues crop up if you install SBS on a GPT disk in a UEFI-equipped system?

Something to be aware of in the next couple of years anyway.  I haven't seen too many servers that have UEFI support yet.  Some have EFI 1.1 (not the same), for whatever reason, but it's not supported by Vista SP1/Server 2008 - only UEFI (EFI 2.0) is.  Most systems don't fully support it properly though, at least on the desktop motherboards I've tried.  They often have major performance issues, or are lacking hardware drivers in the EFI firmware for things like AHCI or RAID mode, making it completely unusable.  I'd like to use it, but it's not what I would call a stable standard right now.