[THIN] Re: New RDP session knocks out previous user

  • From: Melvin.Columna@xxxxxxxxx
  • To: thin@xxxxxxxxxxxxx
  • Date: Thu, 8 Dec 2005 19:07:00 -0500

Would it be this...
 
To select a specific license server, locate the following key in the
registry: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters
Add the following value: 
Name: DefaultLicenseServer
Data type: REG_SZ
Data value: ServerName
 
 -----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Nagarajan Haridas
Sent: Thursday, December 08, 2005 6:22 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: New RDP session knocks out previous user



Melvin

 

Don't use the Admin Console option for mstsc.exe . That would cause issues
in TSLicensing pooling information in Licensing Server

 

Check in the registry whether License server is pointed properly.

 

 

nagarajan haridas

 


  _____  


From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Raffensberger, Stephen D
Sent: Friday, December 09, 2005 3:05 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: New RDP session knocks out previous user

 

1.      The reason it's failing at all is because Server A can't find your
license server. 

2.      The reason it's failing for only some people is because some have
already gotten a license, others have not. 

3.      The reason it works with /console is because that session is
probably administrative and doesn't require a license, even if the server is
in application mode. (Just guessing...anyone know for sure?) 

4.      Only one user should be able to use /console at a time. In your
example, are person A and person B both using /console? 

 

Steve Raffensberger

Sovereign Bank Office Automation Group


  _____  


From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Melvin.Columna@xxxxxxxxx
Sent: Thursday, December 08, 2005 3:59 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: New RDP session knocks out previous user

 

Ohh no... all that is handled/paid for.  We have about 1000 licenses.  

 

The issue is that this server (let's call it Server A) has this problem.
Another Win2003 server in the same OU, built from an image relatively at the
same time (days apart) is not exhibiting this problem.

 

The shared ID thing was a scenario we tested, but mostly, folks will be
going into the box with their own ID.  When I TS/RDP it only allows 1 user
on the box (thus notifying me that the previous user is going to get logged
off)


If I don't specify the /console parameter, it will display that message you
guys see below.

 

 -----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jim Kenzig http://Kenzig.com
Sent: Thursday, December 08, 2005 12:02 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: New RDP session knocks out previous user

And set up your licensing to be Per user so you don't run out. (assuming you
purchased TS licenses in the first place and are properly running them on a
licensing server) Otherwise you need to convert the system into admin mode
from application mode. 

JK

Jeff Pitsch <jepitsch@xxxxxxxxx> wrote:

First off it's a really bad idea to have users sharing ID's.  It really
screws things up with the profiles, printers, etc.  You'll be fighting
problems alot that will seem strange and bizarre and have no explanantion.
It will relate back to profiles and settings overwriting each other bcause
of the shared id's. 

 

Second, in Win2k3 in TS config you can turn off only allow one session per
user.

 

Jeff Pitsch

 

O n 12/8/05, Melvin.Columna@xxxxxxxxx <mailto:Melvin.Columna@xxxxxxxxx>
<Melvin.Columna@xxxxxxxxx <mailto:Melvin.Columna@xxxxxxxxx>  > wrote: 

Hi Guys,

 

A few of our Win2003 servers are experiencing the following issue.... and it
happens to some admins all the time, but not others at all.

 

When we try to RDP to a server, we get the following message...

"The remote session was disconnected because t here are no Terminal Server
License Server available to provide a license."

"Please contact the server administrator."

 

If I change the RDP client shortcut to "C:\Program Files\Remote
Desktop\mstsc.exe" /console  <-- adding the /console parameter 

I can get in, but then this happens....

 

When person A RDPs to a server (Windows 2003 Standard Edition NO SP1) via
RDP, he gets on.  Yippee!!!!

 

If person B RDPs to the same server, he is prompted that he is going to
logoff person A.

 

If person B logs in, using the same ID as person A he knocks off person A
w/o any warning.

 

Here's the installed Windows Updates...  Per Windows Update


Windows Server 2003 family Windows Malicious Software Removal Tool - July
2005 (KB890830)
Windows Malicious Software Removal Tool - August 2005 (KB890830)
Windows Server 2003 family Security Update for Windows Server 2003
(KB896423)
Windows Server 2003 family Security Update for Windows Server 2003
(KB899587)
Windows Server 2003 family Security Update for Windows Server 2003
(KB899591) 
Windows Server 2003 family Security Update for Windows Server 2003
(KB893756)
Windows Server 2003 family Security Update for Windows Server 2003
(KB899588)
Windows Server 2003 family Security Update for Windows Server 2003
(KB896358) 
Windows Server 2003 family Security Update for Windows Server 2003
(KB901214)
Windows Server 2003 family Security Update for Windows Server 2003
(KB890046)
Windows Server 2003 family Security Update for Windows Server 2003
(KB896422) 
Windows Server 2003 family Security Update for Windows Server 2003
(KB896428)
Windows Server 2003 family Security Update for Windows Server 2003
(KB893066) 
Windows Server 2003 family Security Update for JView Profiler (KB903235) 
Windows Server 2003 family Security Update for Microsoft Data Access
Components (KB832483)
Windows Server 2003 family Cumulative Se curity Update for Internet Explorer
for Windows Server 2003 (KB896727)
Windows Server 2003 family Cumulative Security Update for Internet Explorer
for Windows Server 2003 (KB883939) 
Windows Server 2003 family Cumulative Security Update for Outlook Express
for Windows Server 2003 (KB897715)
Windows Server 2003 family 816093: Security Update Microsoft Virtual Machine
(Microsoft VM)
Windows Server 2003 family Intel Corporation - Networking - Intel(R)
PRO/1000 MT Dual Port Network Connection 
Windows Server 2003 family Critical Update for ADODB.stream (KB870669)
Windows Server 2003 family Microsoft Windows Installer 3.1 
.
.
----------------------------------------------------------------------------
-------------- 
Melvin Columna
Kraft Foods/GDC - Application Management
eMail: Melvin<.>Columna<@>Kraft.com <http://kraft.com/>   {remove the < and
> characters}
----------------------------------------------------------------------------
-------------- 

 

 



This message contains information which may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee),
you may not use, copy or disclose to anyone the message or any information
contained in the message. If you have received the message in error, please
advise the sender by reply e-mail, and delete or destroy the message. 


Thank you.


Other related posts: