Hyper-V Program Manager
With the release candidate build of service pack 1 for Windows Server 2008 R2 you can now enabled Dynamic Memory on the standard and web editions of Windows Server. However – there is a slightly different process to do this on the various versions of Windows server:
How come when I go to download the hot fix associated with 2230887 I get linked to a doanload for Vista Fix324410. When I'm then sent the link to download 324410 I get a file with KB2230887 in the name, but it won't install on my Windows Server 2008 Standard FE - is this because it is a SBS version of windows, or because the download is fundamentally wrong?
Ben -- With the release of Windows 2008 R2 SP1 on MSDN, we were attempting to use Hyper-V Dynamic Memory with a new SBS 2011 Standard virtual machine only to find that after we installed SP1 on both the host and the guest that Dynamic memory would not enable (memory always stays allocated at the minimum value) on the SBS 2011 Standard virtual machine. Dynamic memory is enabled and working on this same host with a Windows 2008 R2 Enterprise SP1 virtual machine so we know it's working, but not on our SBS 2011 Standard (based on Windows 2008 R2 Standard). Is this a known bug in the released SP1?
I am also trying to run SBS 2008 (Windows Server 2008 FE) with SP2 as a child partition on Hyper-V Server 2008 R2. However, when I attempt to download the above hotfix, the page asks me to agree to the EULA (which I dutifully do) and then it says "There are no publicly available download for this hotfix." What gives? SBS is supported in a virtual environment (not sure about on Hyper-V Server, though, according to my license, but since Hyper-V Server is free, I don't see why not, as long as I don't have more VM instances than my licensing allows), so I should be able to download this hotfix to take advantage of these memory improvements for the VM.
Dyanmic Memory doesn't work on the SBS VMs due to Exchange. Exchange best practices state to pre-allocate the memory due to the way the Mailbox Role handles memory allocation. I'm fairly certain (Ben could possibly confirm) that the Integration Services checks for Exchange (possibly even as specific as the Mailbox Role) on the VM and disables Dynamic Memory if it exists.