PC Review


Reply
Thread Tools Rate Thread

how clients access application from terminal server

 
 
=?Utf-8?B?YWxpIGFrYmFy?=
Guest
Posts: n/a
 
      8th Jan 2006
hello
i just have configured window server 2003 enterprise edition as terminal
server in application mode.now i wnat to know how clients computers (all win
XP professional)can access application from terminal server.what settings i
have to made on client side.
 
Reply With Quote
 
 
 
 
Vera Noest [MVP]
Guest
Posts: n/a
 
      8th Jan 2006
The short answer is: none.
Just start the Remote Desktop Connection client, type the name of
the server, login and you will get to the desktop on the server.

Long answer: it sounds like you have never worked with a Terminal
server before, so let me add some advice.
Your users will be running on the desktop of the server,
effectively using it as their workstation. They will surf the
Internet, try to download and install applications etc.
If you don't lock down the server, it will very soon be unstable.
So before you let any user in, make sure that you configure your
server:

* use NTFS permissions on the file system of the server to lock
users out of sensitive areas. Normally, the default 2003
permissions are OK, provided you run in native 2003 mode.
* implement a Group Policy to further lock down the server: hide
system drives, disable access to the servers floppy and CD-ROM,
disable access to Windows Installer, disable access to Windows
Update, etc. You can find recommended settings here:
278295 - How to lock down a Windows Server 2003 or Windows 2000
Terminal Server session
http://support.microsoft.com/?kbid=278295
* be aware that installing applications on a Terminal Server *must*
be done while the server is in "install" mode. The best way to
ensure this is by typing "change user /install" (without the
quotes) in a command window, then install the application. After
installation, type "change user /execute" to put the server back
into the normal execute mode again.
* users should *not* use the same profile on their XP workstation
and their Terminal Server session. So make sure that you define a
TS-specific profile, recommended is a roaming profile on a network
share.
* once you have locked down the server and tested your
configuration (create a test account!), you can give users access
to the TS by making them members of the local build-in group Remote
Desktop users on the Terminal Server
* you can run for 120 days without a TS Licensing server. After 120
days, you must install and activate a TS Licensing Server. You will
also have to purchase and install TS CALs on it, one for every User
or Device (depending on which type of licenses you buy).

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?YWxpIGFrYmFy?= <ali (E-Mail Removed)>
wrote on 08 jan 2006 in microsoft.public.win2000.termserv.apps:

> hello
> i just have configured window server 2003 enterprise edition as
> terminal server in application mode.now i wnat to know how
> clients computers (all win XP professional)can access
> application from terminal server.what settings i have to made on
> client side.

 
Reply With Quote
 
=?Utf-8?B?UGF0cmljayBSb3VzZQ==?=
Guest
Posts: n/a
 
      9th Jan 2006
I've also added a quick list of things I do to lock down new terminal servers:

http://www.sessioncomputing.com/security.htm

I hghly recommend that you take the time to get things exactly the way you
want, and make an image based backup before letting users connect in a
production environment.

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


"Vera Noest [MVP]" wrote:

> The short answer is: none.
> Just start the Remote Desktop Connection client, type the name of
> the server, login and you will get to the desktop on the server.
>
> Long answer: it sounds like you have never worked with a Terminal
> server before, so let me add some advice.
> Your users will be running on the desktop of the server,
> effectively using it as their workstation. They will surf the
> Internet, try to download and install applications etc.
> If you don't lock down the server, it will very soon be unstable.
> So before you let any user in, make sure that you configure your
> server:
>
> * use NTFS permissions on the file system of the server to lock
> users out of sensitive areas. Normally, the default 2003
> permissions are OK, provided you run in native 2003 mode.
> * implement a Group Policy to further lock down the server: hide
> system drives, disable access to the servers floppy and CD-ROM,
> disable access to Windows Installer, disable access to Windows
> Update, etc. You can find recommended settings here:
> 278295 - How to lock down a Windows Server 2003 or Windows 2000
> Terminal Server session
> http://support.microsoft.com/?kbid=278295
> * be aware that installing applications on a Terminal Server *must*
> be done while the server is in "install" mode. The best way to
> ensure this is by typing "change user /install" (without the
> quotes) in a command window, then install the application. After
> installation, type "change user /execute" to put the server back
> into the normal execute mode again.
> * users should *not* use the same profile on their XP workstation
> and their Terminal Server session. So make sure that you define a
> TS-specific profile, recommended is a roaming profile on a network
> share.
> * once you have locked down the server and tested your
> configuration (create a test account!), you can give users access
> to the TS by making them members of the local build-in group Remote
> Desktop users on the Terminal Server
> * you can run for 120 days without a TS Licensing server. After 120
> days, you must install and activate a TS Licensing Server. You will
> also have to purchase and install TS CALs on it, one for every User
> or Device (depending on which type of licenses you buy).
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> SQL troubleshooting: http://sql.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?YWxpIGFrYmFy?= <ali (E-Mail Removed)>
> wrote on 08 jan 2006 in microsoft.public.win2000.termserv.apps:
>
> > hello
> > i just have configured window server 2003 enterprise edition as
> > terminal server in application mode.now i wnat to know how
> > clients computers (all win XP professional)can access
> > application from terminal server.what settings i have to made on
> > client side.

>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot access application while accessing from terminal server. =?Utf-8?B?VG9ueQ==?= Microsoft Access 8 19th Apr 2007 05:25 AM
Running Access application on Terminal Server reidarT Microsoft Access Form Coding 1 7th May 2006 02:46 PM
limiting access to terminal clients for server programs Sue Microsoft Windows 2000 Terminal Server Clients 2 1st Oct 2004 08:21 PM
Terminal Server and connected Terminal Services clients pause while working Neeraj Microsoft Windows 2000 Terminal Server Applications 1 1st Sep 2004 03:57 PM
Restrict application access in Terminal Server sessions KL Wong Microsoft Windows 2000 Terminal Server Clients 1 26th Jul 2003 08:14 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 08:52 PM.