Re: Which is the best for allowing users to work from home? Terminal Services / Remote Access?

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




<ryanshumaker@xxxxxxxxx> wrote in message
news:1171978040.466835.50170@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the advice James, Anthony and Frank.

I had pretty much ruled out Remote Control of individual PC's. That
sounds like a problem just waiting to happen. From what I am
gathering from all of you, I am most likely looking at either the
terminal services or VPN is the way to go.

With 2003 Terminal Services, I suppose I'd be looking at an additional
Server 2003 box with terminal service licenses which sounds like it
could be a costly investment although I haven't looked into the cose
of licensing for terminal service clients yet. Frank's suggestions
pretty much helped me to really focus on this avenue. So to put this
all together, I would need a Win 2003 member server, terminal services
installed, and available client licenses, loaded with all apps I want
users to run. I would then have it set to allow them to save to their
home directories with drive mappings when they login (I suppose their
roaming user profiles and login scripts would run to allow the
mappings?). Do you need to worry about the Administrative tools
package that is on a Win 2003 server? I wouldn't want users exposed
or to even see network administration tools or other server features/
tools that would pose a problem for me to administer or control access
to.

As for the other possibility of VPN's, I'm not as well versed in
understanding them at this point in time. I haven't worked with VPN's
beyond a general understanding in theory. We use a Cisco router and
firewall so could that be used to setup the VPN or would we need a
server running VPN software and as for the clients, is it fairly
difficult for my average users to install and setup a VPN connection
on their own?

Thanks again for everyone who responded.

Basically, your thoughts are right-on. With one possible exception (or
confusion). The whole VPN idea is sort of independent of the Terminal Server
thing. The VPN can serve as a secure conduit (tunnel) from the home user to
the network. This can be done with or without a TS. If you use a VPN
connection from home first, then after that connects you then use RD to
connect to the TS, you will be operating the TS through the VPN Tunnel. If
you do not use the VPN from the client, but simply use RD to connect to the
TS, then you will be connected directly. Either way works, technically. Just
depends on what you want to do.

Now... having said that... if you only VPN, you could then map drives on the
network (no TS needed). This would be one alternative.

Clear? :)

-Frank


.



Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS VPN connects but no shares..
    ... VPN clients can no longer access internal resources after you install ... Windows Server 2003 Service Pack 1 on a computer that is running ISA Server ... How to configure a VPN connection to your corporate network in Windows XP ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN issue
    ... I understand that you cannot initialize the VPN ... Could you please let me know if this is a Premium SBS server box with ISA ... To support the PPTP VPN clients behind the ISA server, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS VPN Strengthening
    ... to my other clients, so a software only configuation would be preferred. ... Have SBS 2003 along with Server 2003 at various sites, ... each location and they would establish the VPN between those offices. ... connect to remote offices you could use a hub and spoke method VPN or use ...
    (microsoft.public.windows.server.sbs)
  • RE: Cant remote desktop to clients connected via VPN
    ... that the VPN connection works well. ... that RDP does not work to clients connected via VPN (to all other clients it ... > the SBS 2003, but from your IP configuration, I found your DNS server is ...
    (microsoft.public.windows.server.sbs)