![how to configure fancycache how to configure fancycache](https://sadtohappyproject.com/wp-content/uploads/2015/10/Creative-DIY-Bookmarks-Ideas32.jpg)
I created the drive, moved one of the VDI node’s disks into it and, boom. PS C:\> New-IscsiVirtualDisk –Path ramdisk:test.vhdx –Size 80GB Windows Server 2012 R2 has a nice feature in the iscsi server that allows you to create a ramdrive from a vhdx file:
![how to configure fancycache how to configure fancycache](https://rsload.net/images3/PrimoCache.0.9.2.Beta.png)
This sounded great in theory – after moving things around, one of our nodes had enough free RAM to give this a try. The system images were only ~80gb each and no information is actually stored on the system – all user data and settings are in roaming profiles/redirected folders from other servers.
#How to configure fancycache install#
The new plan was to purchase enough RAM to install in a server and run the entire VDI setup from a ramdrive. The storage for the VDI was entirely consumer-grade SSDs, due to a very limited budget – it seemed like a good idea at the time and kept everyone happy. Our remote desktop infrastructure is setup as a 6-node Hyper-V cluster, with shared storage being presented as an SMB share from a scale-out fs cluster. Logon times were slow – sometimes taking upwards of 5 minutes, other times failing to load roaming profiles and just giving up. Our remote desktop infrastructure was crawling to a halt – it has become so popular, that at times over 25% of the total user base was connected. Well earlier this week I had one of those moments! There are times when you have a bright idea and think “I wonder if someone has done that before”.