Server

Taking a tip from here, and due to the fact, in the current Intel/AMD chip architecture, only one hardware-based hypervisor can run at a time, you will want to create a special boot entry for a Hyper-V-less boot time configuration of Windows 2008.

Assuming you are currently booted into Windows 2008, at an administrative command prompt, type the following:
bcdedit /copy {current} /d "Windows 2008 (No Hyper-V)"

The above command should say:
The entry was successfully copied to {guid}.

Copy that {guid} to the clipboard including the curly braces.

Now, type the following command:
bcdedit /set {guid} hypervisorlaunchtype off

In the above command, replace {guid} with what you into the clipboard.

Boot into the 'Windows 2008 (No Hyper-V)' instance and you will no longer bluescreen while running VMWare guests.

This update adds support for the following Advanced Encryption Standard (AES) cipher suites in the Schannel.dll module for Windows Server 2003:
TLS_RSA_WITH_AES_128_CBC_SHA AES128-SHA and TLS_RSA_WITH_AES_256_CBC_SHA AES256-SHA

With this update, you can support 128-bit and 256-bit cipher suites without Cryptography Next Generation (CNG). This update enables you to use a higher cipher strength. This update also fixes the interoperability issue between the Exchange server and the Sendmail server. This update also fixes the interoperability issue between the Exchange server and the Postfix server.

If you need your Server 2003 server to be able to read SHA2 certificates created with Server 2008's Certificate Services (of the CNG variety), which are more secure than RC4 based certificates, you will need KB 938397.

And last but not least, if you want to upgrade your Server 2003's IIS certsrv site to support Vista and 2008 clients properly, you'll want KB 922706.

Hopefully, someone at MS is watching and they will release all 3 of these updates as a Certificate Services update rollup for Server 2003 to make life easier for Exchange 2007/Office Communications Server admins that want to take advantage of stronger crypto.

This download link might be from IBM, but these are “generic” reference drivers, which mean they will work with any Broadcom NetXtreme II based chipset.

The added benefit is that these seem to support Hyper-V better.

Problems with the Server 2008 inbox drivers are well documented here.
You can download the complete updated driver collection for Broadcom here.
Thanks go out to the comments in that referenced blog post for providing the IBM Broadcom link.

Install this update to enable remote management of a Windows Server 2008 computer that is running the Hyper-V role.

Grab it the x86 version here and the x64 version here.