One of our customers had a problem with Windows 2003 Terminal Servers that would hang on a grey screen before the logon prompt after a reboot, one of my colleagues got tsdiag.exe from Microsoft in order to diagnose the problem. After some research we discovered that the problem was resolved when the following reg keys are set:
DWordValue HKLM, “SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management”,”LargeSystemCache”, 0
DWordValue HKLM, “SYSTEM\CurrentControlSet\Control\Session Manager\Configuration Manager”,”RegistryLazyFlushInterval”, 30
DWordValue HKLM, “SYSTEM\CurrentControlSet\Services\lanmanserver\parameters”,”Size “,3
LargeSystemCache explained..
RegistryLazyFlushInterval explained..
LanManServer explained..
Microsoft couldn’t explain why this could solve the problem on Windows 2003 Terminal Server but it did do the job. When you suffer the same symptoms please test these settings first before using this in a production environment.
I know lot’s of these configurations are already tested in all kind of scenario’s (as explained here and of course there’s the white paper by Dr Tritsch) but I like to start with a default installation and tweak and adjust per scenario rather than applying these adjustments to every environment because you could break something else in the process.
Kees Baggerman
Latest posts by Kees Baggerman (see all)
- Nutanix AHV and Citrix MCS: Adding a persistent disk via Powershell – v2 - November 19, 2019
- Recovering a Protection Domain snapshot to a VM - September 13, 2019
- Checking power settings on VMs using powershell - September 11, 2019
- Updated: VM Reporting Script for Nutanix with Powershell - July 3, 2019
- Updated (again!): VM Reporting Script for Nutanix AHV/vSphere with Powershell - June 17, 2019
