RE: Researching TS for new setup

Tech-Archive recommends: Fix windows errors by optimizing your registry

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.terminal_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/newsgroups/dgbr
owser/en-us/default.mspx?&query=MattShell&lang=en&cr=US&gu
id=&sloc=en-us&dg=microsoft.public.windows.terminal_servic
es&p=1&tid=aa22a65e-f01b-4c2d-9ef4-4d419d6d0d02&mid=aa22a6
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.
.

Relevant Pages

  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.exchange2000.general)
  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Network Connection
    ... For the clients make sure that you use following policy to prevent logon with cached credentials: ... Additional post an unedited ipconfig /all from the DC/DNS server and a problem machine so we can exclude DNS configuration problems. ... From last December I have been experiencing network connection problem ... out client pc some with Vista and the rest with XP. ...
    (microsoft.public.windows.server.networking)
  • Re: Still strange not fully working DNS server
    ... At logon on the network with a client the error event ID 1054 appears. ... The new server is global catalog and has joined the domain as a member, ... If the clients are domain members they have to be registered in your DNS ...
    (microsoft.public.windows.server.dns)
  • Re: Slow domain logon (with detail try out)
    ... "The speed of the logon is directly related the size of the profile and the ... rather than copying the profile from the server. ... Uninstall "Client for Microsoft Network", restart, install it again ... Boot the client machine and logon (TCP/IP configured to get IP from ...
    (microsoft.public.windows.server.general)