[THIN] Re: OTish: Stretching the use case for RDP admin session
- From: Nick Smith <nick@xxxxxxxxxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Fri, 26 Mar 2010 13:58:10 +0000
FWIW if this a processor/RAM intensive app – which I assume it is hence why
they want to keep it off their machines – then I’d go for a single small
quad-core PC with RDP access. 8GB RAM and Windows 7 for £500, job done. If
it’s a licensing cost issue, VDI doesn’t help you – you would still need to
pay the license for each PC in the pool.
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Magnus Hjorleifsson
Sent: Friday, March 26, 2010 12:34 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OTish: Stretching the use case for RDP admin session
Doesn't Citrix have a 3 user free edition ( developer edition)?
Sent from my iPhone
On Mar 26, 2010, at 0:18, Christopher Wilson
<christofire@xxxxxxxxx<mailto:christofire@xxxxxxxxx>> wrote:
Thanks Lan and Joe for the feedback.
I'm learning that there are a lot of odd app sharing arrangements on the
trading floor at my company. Besides the issue of resource intensiveness there
is the issue of some of these apps just being flat expensive on licensing.
This leads folks to things like the use of generic accounts and trying to do TS
on the cheap.
I agree that Windows 2003 server is probably unnecessary. I view this is a
good use case for VDI and a group of pooled PC's they can share.
Was essentially looking for confirmation that the scenario I described is
*technically* feasible. It sounds like if they went from generic accounts to
named accounts, they could essentially accomplish what they want. Hopefully,
this "solution" will not make the cut.
Thanks again for the feedback,
CW
On Thu, Mar 25, 2010 at 6:35 PM, Joe Shonk
<joe.shonk@xxxxxxxxx<mailto:joe.shonk@xxxxxxxxx>> wrote:
So let me get this straight, they want the benefits of Terminal Services but
don’t want to pay for it?
With Remote Admin, you’re looking at two concurrent sessions total. Aside from
that, Remote admins is designed for remote administrators, not users. They
still gotta pay.
Joe
From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>
[mailto:thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf
Of Christopher Wilson
Sent: Thursday, March 25, 2010 11:44 AM
To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] OTish: Stretching the use case for RDP admin session
Hey, List.
Looking for some RDP expertise. Pardon the inherent kludginess of this inquiry.
I have a group of users who are trying to coble together a shared desktop
solution straight outta LowCash. The idea is this: A windows 2003 server is
accessed as needed by users over RDP from a single shared AD account. From the
RDP desktop they run a proc intensive app they don't want to run on their own
PC's. Questions:
1) Is it possible with the out of the box RDP admin sessions to limit a given
user account to only one connection? First session would get in, subsequent
attempts would get an error and logoff because their AD account already has an
active session. Would be nice if this could be configured in the OS. Perhaps
there is something you could do programatically at logon.
2) In the above scenario, if I get disconnected, is there a way to guarantee I
will reconnect to the original session.
Thanks in advance for your insights.
Best regards,
Christopher
________________________________
SUBJECT TO CONTRACT
Other related posts:
