[THIN] Re: Multiple Users Sharing one Domain Account

  • From: "Luchette, Jon" <JLuchette@xxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Tue, 19 Sep 2006 10:01:12 -0400

Well, I think I now know WHY it worked before and doesn't work now:  

 

*       in 2003 Servers the "restrict each user to one session" setting
is enabled by default.  In 2000, no such setting existed.

 

Another question related to this.  If I was FORCED to disable this
setting and allow this monstrosity to continue, how would my users
reconnect to disconnected sessions?  It seems that this setting would
break the "reconnect to disconnected sessions" setting.

 

 

_______________________________________________
Jon Luchette



Emerson Hospital

Technology Specialist III

Work: 978-287-3369

Cell:  978-360-1379

jluchette@xxxxxxxxxxxxxxx
_______________________________________________

 

 

 

________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Luchette, Jon
Sent: Tuesday, September 19, 2006 9:25 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Multiple Users Sharing one Domain Account

Hello-

 

I have a tech that setup several offices connecting in to our Citrix
farm remotely.  We were running 6 Metaframe XP FR3 servers on Windows
2000 sp4 boxes.  This tech setup the office users to all use the same
domain account to logon to a published desktop to these servers.
Apparently this use to actually work before we upgraded.

 

We now run 6 Metaframe XP FR3 boxes on Server 2003 sp1 boxes.  Now when
they happen to logon to this published desktop and hit the same server,
the first session will get overwritten/disconnected.

 

Can someone help me list out the MULTIPLE reasons that this type of
setup is a bad idea.  And also help me understand why it might have
worked on the old servers and not the new servers?


Thanks!

 

 

_______________________________________________
Jon Luchette



Emerson Hospital

Technology Specialist III

Work: 978-287-3369

Cell:  978-360-1379

jluchette@xxxxxxxxxxxxxxx
_______________________________________________

 

 

Other related posts: