Re: How hard is it to config Win2003 to serve a single app and offer users little else?
- From: kiln <kiln@xxxxxxxxxxxxxx>
- Date: Tue, 20 Dec 2005 18:10:34 -0800
Thanks for that info.
The big thing I'm trying to figure out is: is it practical and safe to
serve an app to a set of say 100 users over the internet? I thought that
was the idea but I've run into threads here stating that it's not safe
to expose a ts to the internet. It ends up sounding like it's only safe
on a LAN or controlled WAN. It's very confusing. I'd get a server at
a web hosting company with firewalls and all, and serve an app to users
via RD who have appropriate logins etc?
In article <Xns9732F0CBAECADveranoesthemutforsse@xxxxxxxxxxxxx>,
vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> You can configure your Terminal Server to start a specific
> application upon connection. This means that users will not even
> see the TS desktop, but will be logged of their session
> automatically when they exit the application.
> Besides that, you can (and should!) use a Group Policy to restrict
> what users can do on your TS and NTFS permissions on the file
> system to lock it down further.
>
> 278295 - How to lock down a Windows Server 2003 or Windows 2000
> Terminal Server session
> http://support.microsoft.com/?kbid=278295
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> kiln <kiln@xxxxxxxxxxxxxx> wrote on 20 dec 2005 in
> microsoft.public.windows.terminal_services:
>
> > New to ts, more or less. I have an application that I'd like to
> > offer via terminal services to users over the internet. I've
> > dialed in to ts boxes using remote desktop, but I've always be a
> > person with admin priviledges, so I could do almost anything on
> > that machine. For the use I'm thinking about now, I'd have a
> > bunch of users dialing in in order to use one application that
> > I've designed. I'd not want those users to be able to start IE,
> > reboot the pc, use windows explorer, those sorts of tasks that
> > regular users can do. I'm pretty sure it's possible to restrict
> > those 'user' remote desktop sessions to the minimum needed for
> > my app, but how hard is it to do? Does one config for this
> > manually or are there like scripts that can config for me? I'm
> > likley to have a dedicated box for this, so I'd be able to
> > config as needed. I tried searching for this in the newgroup but
> > I couldn't come up with the right terms to query for, so I
> > apologise if this topic has been asked too many times.
>
.
- References:
- Prev by Date: Re: How hard is it to config Win2003 to serve a single app and offer users little else?
- Next by Date: Re: Remote terminal service - Comments
- Previous by thread: Re: How hard is it to config Win2003 to serve a single app and offer users little else?
- Next by thread: Re: How hard is it to config Win2003 to serve a single app and offer users little else?
- Index(es):
Relevant Pages
|
Loading