Please read our Community Guidelines before posting in this forum.
POLITE NOTE: Please be courteous to all members. We are here to help. Flaming, Spamming, Advertising, and unnecessary signatures will NOT be tolerated. Graphic Material/Content, Swearing/Cursing, Verbal Abuse, and Warez will NOT be tolerated.
Group: Members
Posts: 8
Joined: 24-December 03
Member No.: 12,900
These guidelines will show you how a Windows XP system with SP2 build 2055 can host two concurrent sessions. This Service pack can be found on the filesharing-networks. By creating a registry key you will be able to let Termsvr.dll on your system allow two concurrently active sessions, unlike all previous builds where only one active session was allowed. A previously leaked document from Microsoft hinted about a registrykey which would allow a smart-display to connect and create a new session on a Windows XP system without interrupting the console-user or affecting fast user switching on the console. Microsoft first confirmed this option, but later they explicitly denied it. Well, this new build of Windows XP SP2 contains everything the document suggested, only the registrykey was named differently.
Step 1: Activate the license for a second session
Click: Start - Run And type: regedit Go to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core Right-mouse-click on the right pane and create a new DWORD: EnableConcurrentSessions Double-click the value and type: 1 Confirm
Step 2: Create a policy for a second session using the Group Policy Editor
Click: Start - Run And type: gpedit.msc
Go to: Local Computer Policy - Computer Configuration - Administrative Templates - Windows Components - Terminal Services Double-click in the right pane on: Allow users to connect remotely using Terminal Services Select: Enabled Confirm
Step 3: Install Remote Desktop Client software on your client machine if you don't already have it
GREAT! You can now use the Remote Desktop Client to connect from a client to this Windows XP SP2 Host. Poke around some more in the Policies and Security Setting to tweak your system some more. The explanations about the settings are not difficult to understand. Here are some tips.
Tip 1: Install this administration pack on the Windows XP host-system
Description: Windows Server 2003 Administration Tools Pack File: Adminpak.msi Located on: Windows 2003 Server CD (find it on filesharing networks) Or download it here: Windows Server 2003 Administration Tools Pack
After installation these and other applications are available: tsmmc.msc -> View the remote desktops on a system tsadmin.exe -> Use in a remote session to get session-information of a system
Tip 2: Enable yourself to take over your home desktop from your office (or vice versa) using the Group Policy Editor
Click: Start - Run And type: gpedit.msc
Go to: Local Computer Policy - Computer Configuration - Administrative Templates - Windows Components - Terminal Services Doubleclick in the right pane on: Sets rules for remote control of Terminal Services user sessions Select: Enabled And select option: Full Control without user's permission Confirm
Tip 3: Allow users, other than 'Administrator' to remote login too, using Local Security Settings
Click: Start - Run And type: secpol.msc /s
Go To: Security Settings - Local Policies - User Rights Assignment Doubleclick in the right pane on: Allow logon through Terminal Services Click on: Add User or Group Click on: Advanced Click on: Find now Hold CTRL and select the users you want to allow to connect directly to your computer Confirm three times
Note: This is not necessary if you only want to remotely login as 'Administrator'. From that session you would be able to remote control another session. Users without a password can never login remotely. To remotely control active sessions of these users you should login to an account with a password. From within that session do this:
Click on: Start - Windows Security - Users Rightclick on: The session you want to control Select: Remote Control Select and escapekey Confirm
Tip 4: Edit users from within a remote session
Click: Start - Run And Type: lusrmgr.msc <enter>
Goodluck and Enjoy! Heathcliff.
This post has been edited by Heathcliff: Dec 24 2003, 11:27 AM
Group: Members
Posts: 8
Joined: 24-December 03
Member No.: 12,900
QUOTE(Cal2002 @ Dec 24 2003, 04:47 PM)
Didnt work for me. Do both machines have to be running sp2?
Not both machines have to be running SP2. Only the host. But is has to be build 2055 of SP2. In earlier releases the concurrent sessions were not implemented yet. If it still won't work, then tell me what exactly goes wrong. Maybe I can help.
Group: Members
Posts: 3
Joined: 29-December 03
Member No.: 13,183
Doesn't work here either - host machine is XP SP2 build 2055, has all the criticals from WU-v5 also. Added the regkey as said, and the group policy changes, rebooted, then tried to connect from a win2k3 server to it - got the message that the user logged in the XP box would be booted off if I continued, just like SP1 did...
Group: Members
Posts: 3
Joined: 29-December 03
Member No.: 13,183
One thing I should add - and this may be the problem.. this particular machine is on a win2k domain, so Fast User Switching is completely disabled (nothing I can do about that). It's a common thing to turn off in standalone installs too, so perhaps that's the root of both of our problems.
Group: Members
Posts: 1
Joined: 16-January 04
Member No.: 14,751
You can enable more than 2 simultaneous log-ins by running gpedit.msc and going to: Computer config./admin. templates/windows components/terminal services and enabling the setting: Limit number of connections, then entering values in there.
Group: Members
Posts: 1
Joined: 22-January 04
Member No.: 15,275
I had heaps of trouble get concurrent connections working with SP2. After completley rebuilding a machine, and it still not working it turned out the problem was as cazlaz suggested.
Concurrent connections only work if the 'Welcome Screen' and 'Fast User Switching' are both enabled. I always turn these off, which is why my rebuild didnt work either - I turned them off before testing it.
After turning them both back on, Concurrent connections work great!
Group: Senior Moderator
Posts: 3,491
Joined: 27-October 03
From: K-PAX, in the constellation Lyra.
Member No.: 7,150
Or perhaps the feature won't exist at all. I doubt MS are gonna let you operate two windows sessions from one box - especially considering they have now dropped the whole tablet PC around the house idea.
Group: Members
Posts: 23
Joined: 15-November 03
Member No.: 9,724
QUOTE(vaughaag @ Jan 23 2004, 07:12 AM)
When SP2 is released I dought you will have to do this, and will be able to use concurrent session with the normal login as seen in win2k3.
Yup. rumor has it from Redmond, that they will make this change once it comes out.They have aleady gottten lots of gripes about the full welcome screen use requirement. I am not positive that is a must. While I have not tried to change it, apparently is all depends on both OS.
Group: Members
Posts: 30
Joined: 17-September 03
Member No.: 3,463
i wonder if it is possible to get concurrent sessions just by patching Termsvr.dll with the one from sp2...? i can't afford 2 install a beta service pack on this system, (nor reinstall!), but i would really love concurrent rd sessions.
can anyone give this a try? i will try myself if i can find a way to get Termsvr.dll from sp2 without actually installing the whole thing.
Dec 24 2003, 11:23 AM
Close Topic Options
