Another reason to use dynamic memory…

Have you started looking at dynamic memory in Windows Server 2008 R2 SP1?

If you have not – why??

I have been using dynamic memory on my home server infrastructure since January at the begining of this year, and have become completely addicted to it.  Recently I decided to setup a Remote Desktop Gateway server so that I could easily and securely connect to my various home server systems when I was at work.

I have notice that it has been sporadically dropping connections (and then immediately reconnecting).  There are a number of things that could be causing this (and top of the list would probably be that I am using pre-release software for pretty much everything) but I decided that the first thing I would try would be to give the server more memory.

So while I was at work – I connected to my Hyper-V server (through the Remote Desktop Gateway virtual machine), opened the virtual machine settings for the Remote Desktop Gateway virtual machine, and changed the memory buffer setting from 20% to 30%.

Instantly my Remote Desktop Gateway server received more memory – while I was connected to other servers through the gateway – all with no downtime.  Neat!

Now to wait and see if this fixes the dropped connection issue.