I wanted to share an interesting case in hopes that it would save an admin out there from an unnecessary headache.
The environment was a small XenApp 6.5 farm, maybe 1-2 servers on Server 2008 R2. It had maybe 30-35 users. One day, users started getting Temporary Profiles. Looking in the event log there was numerous “<> took too long to respond…” events. Every so often, connections would come back with a server is low on resources message. Though, all performance metrics were seemingly normal.
Before I logged a support case, I came across this website. http://carlwebster.com/the-curious-case-of-the-bloated-default-profile/
This described our problem and when I looked at the size of the registry, it was 1.5 GB in size! Navigating to below registry keys, the screen would hang, there were hundreds of entries, if not more!
Deleting the keys seemed to help, the screen would no longer hang, but the registry was still the same size. We ended up compressing the registry, and the problem went away. There are quite a few resources that should be able to help if looking to compress the registry.
The issue stemmed from some registry keys being created for each printer, each time the user logged in. This occurred over and over again. Over time, I suspect the issue would have reoccurred. Citrix provides a tool to stress test printer drivers, http://support.citrix.com/article/CTX109374 We switched out most drivers for the Citrix Universal Drivers. After that, the registry didn’t grow as it did before and after watching it for about a couple of weeks, stayed about the same size, ~100MB. After that I called the problem fixed.
Hope this Helps if your experiencing a similar issue!