Sign in with
Sign up | Sign in
Your question

How do you setup local workstations for TS Clients???

Tags:
  • Workstations
  • Microsoft
  • Servers
  • Windows
Last response: in Windows 2000/NT
Share
Anonymous
June 1, 2005 12:42:35 AM

Archived from groups: microsoft.public.windowsnt.terminalserver.client,microsoft.public.windowsnt.terminalserver.connectivity,microsoft.public.windowsnt.terminalserver.setup,microsoft.public.windowsnt.terminalserver.user (More info?)

I have a bunch of remote offices where we have dedicated VPN's between
them and the home office. Due to bandwidth issues of one accounting
application, we've moved to a single Dual Xeon / 3GB Terminal Services
server in the home office and will now have all remote user offices
without their own server use TS/RD to run applications ONLY on the
Terminal Services server.

This means I want to remove the computers (remote workstations) from the
domain, set them up to auto-logon as a User account and start RD
connecting to our home office (prompts for user/password). I don't want
users running anything on the workstations, I want to force them to use
the remote TS Server connection.

I've already got the web/intern issue resolved by setting no DNS entry
and using a host file to resolve the TS Server's name, but I would be
interested in knowing how other Admins are handling this type of setup.

TIA.


--
--
spam999free@rrohio.com
remove 999 in order to email me

More about : setup local workstations clients

Anonymous
June 1, 2005 1:30:03 AM

Archived from groups: microsoft.public.windowsnt.terminalserver.client,microsoft.public.windowsnt.terminalserver.connectivity,microsoft.public.windowsnt.terminalserver.setup,microsoft.public.windowsnt.terminalserver.user (More info?)

The simplest thing to do would be to turn the remote computer into
thin-clients, using software like thinstation or PXES, or a hardware device
like F.Boot. Another option would be to deliver pre-configured thin-client
terminals to the remote offices to replace their workstations. The second
option is better if you have no remote IT staff.

http://www.workthin.com/thinclient.htm

--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com


"Leythos" wrote:

>
> I have a bunch of remote offices where we have dedicated VPN's between
> them and the home office. Due to bandwidth issues of one accounting
> application, we've moved to a single Dual Xeon / 3GB Terminal Services
> server in the home office and will now have all remote user offices
> without their own server use TS/RD to run applications ONLY on the
> Terminal Services server.
>
> This means I want to remove the computers (remote workstations) from the
> domain, set them up to auto-logon as a User account and start RD
> connecting to our home office (prompts for user/password). I don't want
> users running anything on the workstations, I want to force them to use
> the remote TS Server connection.
>
> I've already got the web/intern issue resolved by setting no DNS entry
> and using a host file to resolve the TS Server's name, but I would be
> interested in knowing how other Admins are handling this type of setup.
>
> TIA.
>
>
> --
> --
> spam999free@rrohio.com
> remove 999 in order to email me
>
!