RE: Researching TS for new setup
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 09 Apr 2007 15:08:59 -0700
The main advantages of hardware thin clients is not the initial
costs of buying them, but the minimal maintenance costs.
You can manage them centrally, from the management program which
usually comes with the hardware, and they are fool-proof (there's
nothing users can do wrong, because there are no other options then
connecting to the TS - just what you wanted).
I have personally tested too few brands that I would be willing to
recommend one over the other. But check the "Thin clients" page on
my website, there's a list of things that you should check when
choosing a thin client manufacturer.
The whole idea with thin clients is that they have minimal local
hardware, so not having a CD/DVD is pretty standard, yes.
What do you want your users to do with a CD/DVD drive anyway?
If you want to give them access to a CD/DVD, then you can't lock
down your clients completely, because they will need to have access
to various other local resources to be able to do something usefull
with whatever is on these CD/DVDs.
So that is not compatible with your wish to start a connection to
the TS automatically as the only option.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?QW1hbmRh?= <Amanda@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
09 apr 2007 in microsoft.public.windows.terminal_services:
Hi Vera,.
Thank you for the links, they helped a lot, but now of course, I
have a few more questions:
Not taking into account appearance and price, what are the
advantages and disadvantages of hardware thin clients verses
software thin clients? We're buying new and either way, thin
vs. fat, they appear about even price wise.
Is one easier to use/setup or more reliable than the other,
especially for those new to TS?
Which hardware and sofware maufacturer(s) do you recommend?
I looked at several thin client manufacturers on the websites
you gave and it appears none of the models have CD/DVD-Drives.
Is this standard?
Once again, thank you for your help.
"Vera Noest [MVP]" wrote:
If you want to stick to XP on your PCs and you want
pass-through authentication, then you need to use Citrix on top
of Windows TS.
But your very best option is what I already wrote: thin
clients, either hardware or software.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?QW1hbmRh?= <Amanda@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 02 apr 2007 in microsoft.public.windows.terminal_services:
Hi Vera,
Thanks for the reply. Is there a way to configure the logon
to do what we want, essentially bypassing the local computer
and do all work from TS w/out having 2 logons (once onto the
computer, once onto TS)? We're trying to make this as idiot
proof as possible.
"Vera Noest [MVP]" wrote:
I'm only going to reply to the logon portion of the thread
here.
I don't think that the link Matt provided covers your
situation.
If you configure the generic user account to *only* be able
to logon to the TS, users will not be able to logon to the
PC to start with. They won't be able to choose the TS in the
logon screen, you are confusing domains and allowed
workstations.
Moreover, it wouldn't do what you want, which is to make
sure that "when a computer is restarted, it goes straight to
TS."
To accomplish this, you would have to replace the local
shell of the PC with the rdp client. That's doable, but not
the best solution.
I would recommend buying thin clients, and / or turn your
existing PCs into "software" thin clients.
From a post from Patrick Rouse (another MVP):
http://groups.google.com/group/microsoft.public.windows.termi
nal _se rvices/msg/1e16df7b6440a4ae?&hl=en
<quote>
If you mean can you replace the local GINA with the RDP
Logon, the best way to do this is to replace the local OS
with a Linux Thin- Client OS like PXES or ThinStation, both
of which are free, or supported non-free OS:
http://www.sessioncomputing.com/thin-clients.htm
If you mean can the local credentials be passed-thru to the
RDP logon, this is a feature of Longorn Server TS and most
current 3rd party products like Provision Networks
Management Framework, Citrix Presentation Server, Ericom
Powerterm WebConnect....
http://www.sessioncomputing.com/add-on.htm#suites
</quote>
This solution would also mean minimal intervention with the
local client, since there is nothing there which has to be
updated.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?TWF0dFNoZWxs?=
<MattShell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 30 mar 2007
in microsoft.public.windows.terminal_services:
"Amanda" wrote:
Hi Matt,
I've read your reply and the thread with you, Alex
and Vera. Now, let me recap what I got out of this
to be sure I understand correctly:
Logon: In ADUC we set the account to only logon to
the TS, meaning that if our TS was named Moscow, we
set it to that and the only option in the pulldown
menu on the logon screen will be Moscow. Will admin
still have the option to logon to the local computer?
"MattShell" wrote:
As far as the log on is concerned check this post
http://www.microsoft.com/technet/community/newsgroup
s/d gbr
owser/en-us/default.mspx?&query=MattShell&lang=en&cr
=US &gu
id=&sloc=en-us&dg=microsoft.public.windows.terminal_
ser vic
es&p=1&tid=aa22a65e-f01b-4c2d-9ef4-4d419d6d0d02&mid=
aa2 2a6 5e-f01b-4c2d-9ef4-4d419d6d0d02
"Amanda" wrote:
I'm needing help researching TS.
Here's what we have: I work for a hospitality
company. In our current hotel, we have five
stand-alone computers for guests to use. Three
are in a business center setup as a workgroup
with MS Office applications, internet connection
and printing via a local printer. We have two
additional computers on another floor that have
internet access, no productivity software or
printing. All computers have Cybersitter to
restrict access to certain websites as
well as certain areas of the computer, like the
control panel. Also, we use Deep Freeze so that
if anything does get changed, we just restart the
computer and it goes back to the our settings.
However, if I have to do anything, like update
the anti-virus or Windows, I have to physically
touch the computers, which, depending on what
needs to be done, can take a good chunk of time.
Here's what we're trying to accomplish: The same
setup as above, with at least double the number
of computers, and using a solution that will make
it very easy to update and maintain the computers
without having to go and physically touch each
computer. When discussing TS with my boss, he
said one of the things that we need to be sure
happens is that when a computer is restarted, it
goes straight to TS.
I know very little about TS, I'm just getting
started in this field, so any help I can get will
be greatly appreciated.
Thanks for any replies.
- References:
- RE: Researching TS for new setup
- From: Amanda
- RE: Researching TS for new setup
- From: Vera Noest [MVP]
- RE: Researching TS for new setup
- From: Amanda
- RE: Researching TS for new setup
- Prev by Date: Re: Terminal Service and 120 days problem
- Next by Date: Re: Delprof.exe doesn't work
- Previous by thread: RE: Researching TS for new setup
- Next by thread: Re: UPHClean didn't work...
- Index(es):
Relevant Pages
|
