locked
Terminal service session directory cannot be started on domain controller with windows 2003 sp2 RRS feed

  • Question

  • Hello,

    we have some terminal servers in our enviroment and service "Terminal service session directory" was originally running on one domain controller. Few days ago was this DC rebooted and after it, service cannot be started. There are no errors in eventlogs, service always started and stopped immeadiatelly. We had to change GPO and managing service is now running on one fileserver, anyway does somebody know what can be wrong and why this service cannot be started anymore? I tried to find some solution but seems nobody had simillar issue before. Session director itself is running without any changes now, so only problem is with this DC where service cannot be started, even after reboots. Thanks for all hints :)

    Thursday, February 28, 2013 2:00 PM

Answers

  • Hello check if you have Windows 2003 and Windows 2008 domain controllers in your domain, they uses the same group "Session Directory Computers", but different Pre-Windows 2000 group name: W2k3 "Session Directory Computers" vs. W2k8 "Session Broker Computers" this is causing problem. When W2k8 renames group name(pre-windows 2000), W2k3 cannot start "Terminal service session directory" service and when W2k3 rename service name, service "Remote Desktop Connection Broker" cannot start on W2k8 DC. So follow recommendation do not use it on DC.
    Friday, March 1, 2013 11:04 AM