The Session Directory service does not work on a Windows Server 2003-based session directory server (908479)
The information in this article applies to:
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows registry SYMPTOMSAfter you add a Microsoft Windows Server 2003 session directory server to a Microsoft Windows NT 4.0-based domain, the Terminal Services Session Directory service on the session directory server does not work. For example, the following symptoms occur: - The Terminal Services Session Directory service does not keep track of sessions on terminal servers.
- The Terminal Services Session Directory service does not reconnect users to existing sessions.
Additionally, when you try to add a terminal server to the Session Directory Computers local group, you receive the following error message: Information returned from the object picker for object computer_name was incomplete. The object will not be processed.
CAUSEThis issue occurs because of a Windows Server 2003 Terminal Services Session Directory service requirement. All the terminal servers that use the Session Directory service must be added to the Session Directory Computers local group. However, in Windows NT 4.0, you cannot add computer accounts to groups. Therefore, the Session Directory service does not work as you expect.RESOLUTIONWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. To resolve this issue, install the latest Windows Server 2003 service pack, and then enable the SDOnNT4Domain registry entry. After you enable the SDOnNT4Domain registry entry, terminal servers that use the Session Directory service do not have to be added to the Session Directory Computers local group.
For more information about how to obtain the latest Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100
How to obtain the latest service pack for Windows Server 2003
To enable the SDOnNT4Domain registry entry, follow these steps: - Click Start, click Run, type regedit in the Open box, and then click OK.
- In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TSSDIS\Parameters - In the right-pane, double-click SDOnNT4Domain.
Note You may have to create the SDOnNT4Domain DWORD registry entry if it does not exist. To create the SDOnNT4Domain DWORD registry entry, follow these steps:- Click Start, click Run, type regedit in the Open box, and then click OK.
- In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TSSDIS\Parameters - On the Edit menu, point to New, and then click DWORD Value.
- Type SDOnnNT4Domain, and then press ENTER.
- In the Value data box, type 1, and then click OK.
Note To disable the SDOnNT4Domain registry entry, type 0 in the Value data box. - Quit Registry Editor, and then restart the computer.
Modification Type: | Minor | Last Reviewed: | 10/20/2005 |
---|
Keywords: | kbwinservperf kbTermServ kbtshoot KB908479 kbAudITPRO |
---|
|