Having problems with a new physical build of a Terminal Server box? You certainly don’t expect Windows Server 2008 R2 SP1 to have lockup or BSOD issues so when it arises it’s one to deal with immediately. Our users were unable to remote in via RDP, although remote management was still working,
In this case the server load wasn’t heavy, and the problem occured on 2 diffent TS boxes in 2 different datacentres. Error from dump file below:
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: rdbss!RxFsdCommonDispatch+ad7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdbss
IMAGE_NAME: rdbss.sys
How to fix it now that you have some inkling of the culprit?
Disable resource/drive redirection in Terminal Services, 3 ways to do it.
1) Group Policy
The full path of this node in the Group Policy Management Console is:
Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Device and Resource Redirection
2) Locally by following this > http://technet.microsoft.com/en-us/library/cc770631.aspx
3) Using Device Manager – a sneaky way to do it, i’m sure you can work it out yourself!
Good luck!