The beta 2055 release of XP PRO SP2 let you run two sessions (one local console and one remote desktop) concurrently. This functionality was removed in the Final release. You can obtain copies of the termsrv.dll from version 2055 that lets you renable concurrent sessions. You must use a different user for each session. To enable concurrent sessions, perform the following steps:
1. Start a registry editor (e.g., regedit.exe).
2. Navigate to the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Licensing Core registry subkey.
3. From the Edit menu, select New, DWORD Value.
4. Enter the name "EnableConcurrentSessions," then press Enter.
5. Double-click the new value, then set it to 1.
Here are some more detailed instructions and a link to get the termsrv.dll file from 2055.
Install the recovery console onto the hard drive (to use in the process, plus its good to have anyway in case of emergency http://support.microsoft.com/default.aspx?scid=kb;EN-US;307654
Copy this DLL file
into your system32 directory as TERMSRV.2055 make the appropriate registry changes listed above
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core\
Make the policy changes:
Local Computer Policy - Computer Configuration - Administrative Templates - Windows Components - Terminal Services | Allow users to connect remotely using Terminal Services=enabled
Local Computer Policy - Computer Configuration - Administrative Templates - Windows Components - Terminal Services | Sets rules for remote control of Terminal Services user sessions=enabled+Full Control without user`s permission
Computer config./admin. templates/windows components/terminal services and enabling the setting:
Limit number of connections, then entering values in there.
Make sure you have multiple accounts with a PASSWORD (that are in the remote users group or are administrators), you have FAST USER SWITCHING enabled, and are NOT in a domain.
Reboot, and enter the recovery console
cd /d c:\windows\system32
ren termsrv.dll termsrv.sp2
ren termsrv.2055 termsrv.dll
cd /d c:\windows\system32\dllcache
ren termsrv.dll termsrv.sp2
Reboot into windows- you should be able now to terminal in from another computer
AND use the console, as long as you do it from DIFFERENT accounts.
Thanks to Rick Mack for his excellent answer to this recent question on the Thin List.
Getting useful information out of BSOD dump can be fairly easy
(or pretty challengin) depending on what the problem is. However if
we`re dealing with driver (printer or whatever) induced crashes, things couldn`t be easier.
If you want a good introduction, the place to start is Mark Russinovich`s
great whitepaper on crash dump analysis at:
If you want to get a bit more serious, check out:
Then go to:
Download windbg, and either get the symbol files for the OS version
(+SP depending on detail required) or set things up so that windbg
can use a symbol server at Microsoft.
When you run windbg and open a dump file, the first thing it tells you to
do is run "!analyze -v", which will generally tell you as much as you need to know.
While browsing the web I found the following page on how to disable the close x box on the RDP client from MS MVP Mathew Harris.
Using Mathew`s examples I created a locked down version of the RDP client with Microsoft Visual C+ that disables the X box. This is a lock down of the latest Windows 2003 Server RDP client available at:
Download and install the above client and then make a backup copy of mstsc.exe file in the Program files\Remote Desktop folder on your drive
Then download and unzip the following file into your Remote desktop folder:
When in a session if a user clicks on the X to try and close their session they will get an error box telling them to properly close their applications and log off to exit. Clicking the OK box returns them to their session. They will not be able to close the session via the X
Open regedt32.exe to remove the following 3 values to get your server connecting again to your license server.
To fix navigate to:
Hkey Local Machine/System/Current Control Set/Services/TermService/Parameters
Delete the following entries:
- X509 Certificate
- X509 Certificate ID>
Once you do this, reboot your server and it should take care of this particular issue.
1. Click on the start button
2. Click on Run
3. Type in winver in the dialog box
A window will pop up that shows what version of windows you are running.
One tip that has worked for us in the past when this happens is to delete two registry keys under the CDROM device key. Be sure and back up your registry before messing with and and don`t mess with it if you don`t know what you are doing! The problem I had was that device manager told me my drivers were corrupted. Even after downloading new drivers, uninstalling and reinstalling device manager still claimed that the CD drivers were corrupt.
In order to resolve this problem you can try the following.
Go to Start/Run and type in Regedit
In regedit navigate to:
Make an export backup of the key and then delete the value entries in the right hand pane that are for Upperfilters and Lowerfilters.
Exit regedit and reboot your machine.
Terminal Services logons are local logons, so you can audit for account logon events - results appear in Event Viewer Security logs. If you are running Terminal Services on Windows Server 2003, you can enable Directory Logging Service which outputs detailed information to a log file. See:
You need to grant the users you want to have access permissions on the server.
To set custom Terminal Services connection permissions:
1. Click Start, point to Programs, point to Administrative Tools, and then click Terminal Services Configuration.
2. Open the Connections folder.
3. Right-click the connection (RDP-TCP), and then click Properties.
4. On the Permissions tab, add the group(s) that needs access to this connection.
5. Click OK.
If the above does not work you can try the following from the Citrix Knowledge Base:
CTX127867 - Error: "Cannot Connect to the Citrix Server: The Citrix Server
you have selected is not accepting connections."
This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX127867
Document ID: CTX127867, Created on: Mar 29, 2002, Updated: Jun 7, 2003
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000
Check Registry for WDICA key
1. Unable to telnet to port 1494. Connecting to servername. Could not open a connection
to host on port 1494: Connect failed.
2. NetStat -a does not show the server listening on port 1494.
3. A Microsoft RDP connection works.
4. Idle sessions are available and the ICA listener is created and enabled.
1. Run regedt32.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDICA.
3. Save the key.
4. Delete the key.
5. Reboot the server.
6. Make a custom ICA connection to the server IP address.
1. Run regedt32.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
3. Create a key named WDICA.
4. Manually add the following values:
ErrorControl: REG_DWORD : 0
Start: REG_DWORD : 0x3
Type: REG_DWORD : 0x1
5. Reboot the server.
6. During the reboot of the server in step 5, a subkey
named Enum will be created with the following values.
0 : REG_SZ : Root\LEGACY_WDICA\0000
Count : REG_DWORD : 0x1
NextInstance : REG_DWORD : 0x1
7. Make a Custom ICA Connection to the servers IP address.
If the above steps do not resolve the issue, check for the existence of
and its subkeys. You may need to add permissions to this key in order to
save and restore the key from a working server. When this key is manually deleted
and the server is rebooted, the key should regenerate itself. If the key does not
automatically regenerate itself, you can restore a copy of this key from a known
good server or manually create the entries. When replacing this key with a copy
of the key from another server it is necessary to navigate to the following location:
Delete the data of the following value located within the above referenced
key and then reboot the server:
Upon reboot the data should repopulate.
NOTE: The cause for the disappearance or corruption of these registry
keys is currently unknown
Most likely your clients do not support the FIPS encryption level.
From: Start| Run: gpedit.msc| Computer Configuration| Administrative Template| Windows Components| Terminal Services| Encryption and Security| double click: Set client connection encryption level, and then set it to Disabled or to Not Configured (whichever suits you).
Here is a good comprehensive one right from Microsoft: