Hi all! 

Let me first start off by stating i am very computer savvy, and have enough 
knowledge of sbs 2003 to have had it set up and running well in our office 
for about 3 years now, but i am struggling with this issue. 


We have many users in the office who connect remotely to their computers 
using logmein. 

We want to move away from this and take advantage of either vpn or remote 
desktop connections to access files/desktop outside of our office, as we are 
currently doing with logmein. 


I have read many articles over the net explaining vpn and how to set it up, 
etc, but i am not sure if it is what we are looking for or not. 

From what i understand, if i set up vpn through our single server running 
sbs 2003, only 1 vpn connection is allowed at a time? 

What is the best option so that users can access files outside the office 
without using a service such as logmein or gotomypc? We would like straight 
access to the server, would prefer remote desktop so that our employees have 
a virtual desktop, but if not, vpn is fine. But how can this be done so that 
more than one user can access the server at a time? Is the only option for 
multiple connections to set it up so that they are accessing the client 
computers rather than the server itself? The only problem with that is we 
have a few employees that do not work on site at the office that need access 
to files on the server that do not have a client computer at the office. I do 
not know enough about sbs 2003 and its capabilities with remote access. 

So again to clarify, remote desktop would be ideal but from what i 
understand, only 1 connection at a time can be made whether its remote 
desktop connection or vpn, so i really dont know what to do. 

Any feedback would be greatly appreciated! 

Thank you!

First off, it is a very very very bad idea to use the SBS 2003 desktop as a 
"client" or workstation desktop.  The reason that the remote desktop is 
restricted to one connection is because that is all that should be needed 
for administrative duties.  It was never meant for, and is not designed to 
be, used by end-users.

You have a couple of options:

1)  The most straightforward is the remote desktop component of RWW.  RWW is 
an SBS-specific feature and the remote desktop option there will allow your 
end users to connect to *client* machines in the office (not the server!) 
without the need for a VPN.

2) If not all users have machines in the office to act as remote desktops 
then you may want to look at deploying a dedicated terminal server. 
Properly set up and licensed, this would allow multiple users to connect and 
would give each one a unique desktop, similar to RWW but without the 
multiple machine requirement.

3) Finally, you could set up a VPN without any remote desktop features. 
Users would have to use their own machines to access file-shares, printers, 
etc.  This setup does *not* have a 1-user restriction, but it can be a 
security issue because end-point machines will be outside of your security 
(firewall and A/V) and will have direct access to your server fileshares, 
etc.  Less than ideal, difficult to maintain in some instances, but 
certainly an option if you are willing to take up the responsibility for 
maintaining such a beast.

That should give you a basic idea of the directions you can go and give you 
good leap-points for some google-fu.

Good luck!

-Cliff


"Alexjbriggs" <Alexjbriggs@discussions.microsoft.com> wrote in message 
news:CAAC133F-3D1F-4630-B286-449C52FB194D@microsoft.com...
> Hi all!
>
> Let me first start off by stating i am very computer savvy, and have 
> enough
> knowledge of sbs 2003 to have had it set up and running well in our office
> for about 3 years now, but i am struggling with this issue.
>
>
> We have many users in the office who connect remotely to their computers
> using logmein.
>
> We want to move away from this and take advantage of either vpn or remote
> desktop connections to access files/desktop outside of our office, as we 
> are
> currently doing with logmein.
>
>
> I have read many articles over the net explaining vpn and how to set it 
> up,
> etc, but i am not sure if it is what we are looking for or not.
>
> From what i understand, if i set up vpn through our single server running
> sbs 2003, only 1 vpn connection is allowed at a time?
>
> What is the best option so that users can access files outside the office
> without using a service such as logmein or gotomypc? We would like 
> straight
> access to the server, would prefer remote desktop so that our employees 
> have
> a virtual desktop, but if not, vpn is fine. But how can this be done so 
> that
> more than one user can access the server at a time? Is the only option for
> multiple connections to set it up so that they are accessing the client
> computers rather than the server itself? The only problem with that is we
> have a few employees that do not work on site at the office that need 
> access
> to files on the server that do not have a client computer at the office. I 
> do
> not know enough about sbs 2003 and its capabilities with remote access.
>
> So again to clarify, remote desktop would be ideal but from what i
> understand, only 1 connection at a time can be made whether its remote
> desktop connection or vpn, so i really dont know what to do.
>
> Any feedback would be greatly appreciated!
>
> Thank you! 

On Sun, 24 Jan 2010 11:43:01 -0800, Alexjbriggs
<Alexjbriggs@discussions.microsoft.com> wrote:

>Hi all! 
>
>Let me first start off by stating i am very computer savvy, and have enough 
>knowledge of sbs 2003 to have had it set up and running well in our office 
>for about 3 years now, but i am struggling with this issue. 
>
>
>We have many users in the office who connect remotely to their computers 
>using logmein. 
>
>We want to move away from this and take advantage of either vpn or remote 
>desktop connections to access files/desktop outside of our office, as we are 
>currently doing with logmein. 
>
>
>I have read many articles over the net explaining vpn and how to set it up, 
>etc, but i am not sure if it is what we are looking for or not. 
>
>From what i understand, if i set up vpn through our single server running 
>sbs 2003, only 1 vpn connection is allowed at a time? 
>
>What is the best option so that users can access files outside the office 
>without using a service such as logmein or gotomypc? We would like straight 
>access to the server, would prefer remote desktop so that our employees have 
>a virtual desktop, but if not, vpn is fine. But how can this be done so that 
>more than one user can access the server at a time? Is the only option for 
>multiple connections to set it up so that they are accessing the client 
>computers rather than the server itself? The only problem with that is we 
>have a few employees that do not work on site at the office that need access 
>to files on the server that do not have a client computer at the office. I do 
>not know enough about sbs 2003 and its capabilities with remote access. 
>
>So again to clarify, remote desktop would be ideal but from what i 
>understand, only 1 connection at a time can be made whether its remote 
>desktop connection or vpn, so i really dont know what to do. 
>
>Any feedback would be greatly appreciated! 
>
>Thank you!
You can make as many vpn connections as you want. Remote desktop is
only one user at a time on a workstation, either in the office or
outside the office. After the users make their vpn connection they go
to Start\Run and \\servername to see server shares. Kind of slow
experience. Remote Web Workplace is much faster usually.

To set up vpn you rip through the connect to the internet wizard and
click the box for vpn. In your router you allow port 1723 and hope the
router does not block GRE 47. Some other clicks if you are running ISA
on the server.

If you made the mistake of setting up your internal network with the
ip of 192.168.0.x or 192.168.1.x then you have some drama as most home
networks where I live use those two ip schemes. Impossible to get
routing to work if you have the same ip scheme at home as you have in
the office.
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx

I'm going to say what everybody else said, but with different words, I 
think.
It might be helpful to know why you want to move away from logmein?
It might also be helpful to know what kinds of applications the users need 
to make use of?

You can either use RWW to do remote desktop to the individual workstations, 
or you can allow users to connect via VPN and use remote desktop to their 
individual workstations.  Each of these options should work for all of your 
users, and simultaneously--there is a one person limit to the individual 
workstation, but no such limit overall.  If your users share workstations, 
this may be a problem, or need some scheduling.  VPN connections have 
significant security implications as the other responses noted--the remote 
machine is on your network and you need to worry about its security state.



"Alexjbriggs" <Alexjbriggs@discussions.microsoft.com> wrote in message 
news:CAAC133F-3D1F-4630-B286-449C52FB194D@microsoft.com...
> Hi all!
>
> Let me first start off by stating i am very computer savvy, and have 
> enough
> knowledge of sbs 2003 to have had it set up and running well in our office
> for about 3 years now, but i am struggling with this issue.
>
>
> We have many users in the office who connect remotely to their computers
> using logmein.
>
> We want to move away from this and take advantage of either vpn or remote
> desktop connections to access files/desktop outside of our office, as we 
> are
> currently doing with logmein.
>
>
> I have read many articles over the net explaining vpn and how to set it 
> up,
> etc, but i am not sure if it is what we are looking for or not.
>
> From what i understand, if i set up vpn through our single server running
> sbs 2003, only 1 vpn connection is allowed at a time?
>
> What is the best option so that users can access files outside the office
> without using a service such as logmein or gotomypc? We would like 
> straight
> access to the server, would prefer remote desktop so that our employees 
> have
> a virtual desktop, but if not, vpn is fine. But how can this be done so 
> that
> more than one user can access the server at a time? Is the only option for
> multiple connections to set it up so that they are accessing the client
> computers rather than the server itself? The only problem with that is we
> have a few employees that do not work on site at the office that need 
> access
> to files on the server that do not have a client computer at the office. I 
> do
> not know enough about sbs 2003 and its capabilities with remote access.
>
> So again to clarify, remote desktop would be ideal but from what i
> understand, only 1 connection at a time can be made whether its remote
> desktop connection or vpn, so i really dont know what to do.
>
> Any feedback would be greatly appreciated!
>
> Thank you! 

Thank you everyone for the responses!

I spent the day reworking the setup on our server. We did have it deployed 
using a single NIC setup, but today i installed a second, and plan to set it 
up with a direct broadband connection via two NICs. I also through together a 
few extra client computers and set them up without monitors so that offsite 
employees can access remotely. This seemed like the easiest path with my 
limited knowledge of sbs 2003. I want to just review my layout to confirm 
that i have this set up correctly.

My intentions are to allow users to just connect via remote desktop 
connection built into windows, or via remote desktop through RWW. Would users 
be able to access their client computer from their computer at home via the 
remote desktop connection? (not through RWW, just through rdc built into 
windows). And if so, will they be able to do this even if using vista or 7? i 
believe i saw a hotfix or some type of update needed for vista (i will 
research this myself if you confirm this is the case). If not, i suppose the 
best option is remote desktop via RWW. Our employees are not so computer 
savvy, so id like to keep steps to use it at a minimum (which is why i 
suggest remote desktop connection)


But to confirm I am on the right path, this is what i did today while 
reworking the server:

-Installed second NIC
-Have ethernet cable running from DSL modem to first (onboard) NIC
-Have ethernet cable 2 running from NIC 2 (pci NIC) to switch/hub
-Have ethernet cables from hub to client computers (other hubs are being 
used for additional clients, routed from one hub to another)
-I am calling my ISP tomorrow for a static IP. I also should set up a DNS 
with my ISP, correct?
-Once this is done, i will re-run the internet/email connection wizard and 
run through this set up.
-Enable vpn/RWW/remote desktop connection via server management

Am i missing an additional steps, and/or am i correct with this setup?

Also, once this is done, i will use either the static ip, or the DNS name to 
enter into remote desktop connection outside the office, correct?

Thank you all again so much for the help!! 






"Cliff Galiher - MVP" wrote:

> First off, it is a very very very bad idea to use the SBS 2003 desktop as a 
> "client" or workstation desktop.  The reason that the remote desktop is 
> restricted to one connection is because that is all that should be needed 
> for administrative duties.  It was never meant for, and is not designed to 
> be, used by end-users.
> 
> You have a couple of options:
> 
> 1)  The most straightforward is the remote desktop component of RWW.  RWW is 
> an SBS-specific feature and the remote desktop option there will allow your 
> end users to connect to *client* machines in the office (not the server!) 
> without the need for a VPN.
> 
> 2) If not all users have machines in the office to act as remote desktops 
> then you may want to look at deploying a dedicated terminal server. 
> Properly set up and licensed, this would allow multiple users to connect and 
> would give each one a unique desktop, similar to RWW but without the 
> multiple machine requirement.
> 
> 3) Finally, you could set up a VPN without any remote desktop features. 
> Users would have to use their own machines to access file-shares, printers, 
> etc.  This setup does *not* have a 1-user restriction, but it can be a 
> security issue because end-point machines will be outside of your security 
> (firewall and A/V) and will have direct access to your server fileshares, 
> etc.  Less than ideal, difficult to maintain in some instances, but 
> certainly an option if you are willing to take up the responsibility for 
> maintaining such a beast.
> 
> That should give you a basic idea of the directions you can go and give you 
> good leap-points for some google-fu.
> 
> Good luck!
> 
> -Cliff

Thank you everyone for the responses! 

I spent the day reworking the setup on our server. We did have it deployed 
using a single NIC setup, but today i installed a second, and plan to set it 
up with a direct broadband connection via two NICs. I also through together a 
few extra client computers and set them up without monitors so that offsite 
employees can access remotely. This seemed like the easiest path with my 
limited knowledge of sbs 2003. I want to just review my layout to confirm 
that i have this set up correctly. 

My intentions are to allow users to just connect via remote desktop 
connection built into windows, or via remote desktop through RWW. Would users 
be able to access their client computer from their computer at home via the 
remote desktop connection? (not through RWW, just through rdc built into 
windows). And if so, will they be able to do this even if using vista or 7? i 
believe i saw a hotfix or some type of update needed for vista (i will 
research this myself if you confirm this is the case). If not, i suppose the 
best option is remote desktop via RWW. Our employees are not so computer 
savvy, so id like to keep steps to use it at a minimum (which is why i 
suggest remote desktop connection) 


But to confirm I am on the right path, this is what i did today while 
reworking the server: 

-Installed second NIC 
-Have ethernet cable running from DSL modem to first (onboard) NIC 
-Have ethernet cable 2 running from NIC 2 (pci NIC) to switch/hub 
-Have ethernet cables from hub to client computers (other hubs are being 
used for additional clients, routed from one hub to another) 
-I am calling my ISP tomorrow for a static IP. I also should set up a DNS 
with my ISP, correct? 
-Once this is done, i will re-run the internet/email connection wizard and 
run through this set up. 
-Enable vpn/RWW/remote desktop connection via server management 

Am i missing an additional steps, and/or am i correct with this setup? 

Also, once this is done, i will use either the static ip, or the DNS name to 
enter into remote desktop connection outside the office, correct? 

Thank you all again so much for the help!! 

Are you running SBS premium (with ISA intalled?)  IF not then you've just 
hung your SBS box onto the internet with no meaningful protection.  This is 
*very* bad.  So out of curiosity, is there a *reason* you installed the 
second NIC?  It isn't needed for RWW.  SBS 2008 doesn't even support the 
2-NIC configuration because of the problems and security implications it 
introduces, so I'm not sure why anybody would actively choose to go that 
direction now.  There are legacy installs, sure, but not new configurations.

To answer your other questions, no, in *most* configurations, you cannot 
directly access multiple client machines via RDP without using RWW.  I won't 
go into details, but the short version is that most networks use NAT and NAT 
has some inherent limitations with port forwarding.  You *can* get this to 
work if you are familiar with networking and digging into the setup, but 
usually a person with that level of expertise wouldn't have to ask if it 
will work.  No offense intended.

As far as your current setup, honestly, I am now at a point where, based on 
your questions, I strongly recommend calling in an experienced consultant 
that can help you set up the network.  This is for security as well as 
ease-of-use.  There are just enough gaps and there are enough *basic* tasks 
being asked that trying to cover all of the bases in a newsgroup or forum 
will lead to problems down the road.  Something *will* get overlooked and 
missed.

Trust me, it is worth it to call in an expert.

-Cliff


"Alexjbriggs" <Alexjbriggs@discussions.microsoft.com> wrote in message 
news:FBC4D75D-3DC3-4AC7-A985-F86577BFEA09@microsoft.com...
> Thank you everyone for the responses!
>
> I spent the day reworking the setup on our server. We did have it deployed
> using a single NIC setup, but today i installed a second, and plan to set 
> it
> up with a direct broadband connection via two NICs. I also through 
> together a
> few extra client computers and set them up without monitors so that 
> offsite
> employees can access remotely. This seemed like the easiest path with my
> limited knowledge of sbs 2003. I want to just review my layout to confirm
> that i have this set up correctly.
>
> My intentions are to allow users to just connect via remote desktop
> connection built into windows, or via remote desktop through RWW. Would 
> users
> be able to access their client computer from their computer at home via 
> the
> remote desktop connection? (not through RWW, just through rdc built into
> windows). And if so, will they be able to do this even if using vista or 
> 7? i
> believe i saw a hotfix or some type of update needed for vista (i will
> research this myself if you confirm this is the case). If not, i suppose 
> the
> best option is remote desktop via RWW. Our employees are not so computer
> savvy, so id like to keep steps to use it at a minimum (which is why i
> suggest remote desktop connection)
>
>
> But to confirm I am on the right path, this is what i did today while
> reworking the server:
>
> -Installed second NIC
> -Have ethernet cable running from DSL modem to first (onboard) NIC
> -Have ethernet cable 2 running from NIC 2 (pci NIC) to switch/hub
> -Have ethernet cables from hub to client computers (other hubs are being
> used for additional clients, routed from one hub to another)
> -I am calling my ISP tomorrow for a static IP. I also should set up a DNS
> with my ISP, correct?
> -Once this is done, i will re-run the internet/email connection wizard and
> run through this set up.
> -Enable vpn/RWW/remote desktop connection via server management
>
> Am i missing an additional steps, and/or am i correct with this setup?
>
> Also, once this is done, i will use either the static ip, or the DNS name 
> to
> enter into remote desktop connection outside the office, correct?
>
> Thank you all again so much for the help!!
>
>
>
>
>
>
> "Cliff Galiher - MVP" wrote:
>
>> First off, it is a very very very bad idea to use the SBS 2003 desktop as 
>> a
>> "client" or workstation desktop.  The reason that the remote desktop is
>> restricted to one connection is because that is all that should be needed
>> for administrative duties.  It was never meant for, and is not designed 
>> to
>> be, used by end-users.
>>
>> You have a couple of options:
>>
>> 1)  The most straightforward is the remote desktop component of RWW.  RWW 
>> is
>> an SBS-specific feature and the remote desktop option there will allow 
>> your
>> end users to connect to *client* machines in the office (not the server!)
>> without the need for a VPN.
>>
>> 2) If not all users have machines in the office to act as remote desktops
>> then you may want to look at deploying a dedicated terminal server.
>> Properly set up and licensed, this would allow multiple users to connect 
>> and
>> would give each one a unique desktop, similar to RWW but without the
>> multiple machine requirement.
>>
>> 3) Finally, you could set up a VPN without any remote desktop features.
>> Users would have to use their own machines to access file-shares, 
>> printers,
>> etc.  This setup does *not* have a 1-user restriction, but it can be a
>> security issue because end-point machines will be outside of your 
>> security
>> (firewall and A/V) and will have direct access to your server fileshares,
>> etc.  Less than ideal, difficult to maintain in some instances, but
>> certainly an option if you are willing to take up the responsibility for
>> maintaining such a beast.
>>
>> That should give you a basic idea of the directions you can go and give 
>> you
>> good leap-points for some google-fu.
>>
>> Good luck!
>>
>> -Cliff
> 

In article <FBC4D75D-3DC3-4AC7-A985-F86577BFEA09@microsoft.com>, 
Alexjbriggs@discussions.microsoft.com says...
> My intentions are to allow users to just connect via remote desktop 
> connection built into windows, or via remote desktop through RWW. Would users 
> be able to access their client computer from their computer at home via the 
> remote desktop connection? (not through RWW, just through rdc built into 
> windows). And if so, will they be able to do this even if using vista or 7? i 
> believe i saw a hotfix or some type of update needed for vista (i will 
> research this myself if you confirm this is the case). If not, i suppose the 
> best option is remote desktop via RWW. Our employees are not so computer 
> savvy, so id like to keep steps to use it at a minimum (which is why i 
> suggest remote desktop connection)
> 

First, if you want to RDP directly through to a desktop you need one of 
two things, either 1 public IP per workstation inside your LAN that you 
want to allow RDP into OR you need a firewall that maps from one port to 
another port (as in mapping from 50000 > 3389, then 50001 > 3389 and so 
on for each internal computer in question). You'll also need to do a 
DCHP reservation so that the computers (workstations inside the lan) 
that are to be connected to from outside always appear at the same LAN 
IP.

As for VPN and users, get a real firewall appliance that supports VPN's 
as a end-point at the firewall and go back to a SINGLE NIC - you won't 
be able to use DUAL NIC's in 2008 anyway.

RWW, as long as they can run IE on their home/remote computer, allows 
for RWW directly to any windows computer properly joined to the SBS 
network where the users were given remote desktop access permission.

-- 
You can't trust your best friends, your five senses, only the little 
voice inside you that most civilians don't even hear -- Listen to that.  
Trust yourself.
spam999free@rrohio.com (remove 999 for proper email address)

Thank you Larry.

We have definitely decided to take the RWW approach. Now it is a question of 
either setting up the TS, or just use the existing set up and add a client 
computer that would be accessed whenever we have a new remote location being 
added (which isnt TOO often, mind you)

I know the better option is to hire someone with the knowledge, but Id much 
rather further my own knowledge but learning and doing myself, which is how 
i've learned everything in the past. Again, my knowledge of computers is as 
great as the next guy, it is only with sbs/server that I am limited.

A few questions for you Larry (or anyone able to answer)

BY THE WAY, i have reverted back to the single NIC setup.
(DSL to router, router to server, router to other hubs/switch)
All is running perfect.

So, if i decide to go with the terminal server, here are a few questions:

1. I am running server 2003 right now on the (main) domain server. Should 
this be upgraded to 08 if i implement an additional server with 08 to run as 
the TS?
2. Is a separate/additional static IP required for the TS?
3. By taking the TS approach, when a new remote location is needed, all that 
is required is to purchase an additional CAL for that location, correct? So 
the new location is connecting through the terminal server, which allows 
concurrent connections when properly licensed, and no additional hardware or 
client computer needs to be purchased, correct?
4. I will research on my own the proper set of to implement a TS in the 
current network set up, but out of curiosity, is implementing the TS 
hardware/unit itself as "simple" as NIC to hub/switch, or will the entire 
setup need "re-doing" or whatever you will. Just a "for the most part yes/no" 
is all im looking for here, as i said i will do the work in researching. Just 
looking for a starting point ;)

Thanks again everyone!

Thanks again everyone.

I believe we are going to stick with a very simple path.

We already have a few extra client computers that arent being used. We only 
have a total of 5 employees outside the office that need remote access, and i 
dont see us adding more than 5 more in the next couple years.

It seems the least expensive route, and easiest set up, is to just set up 
extra client computers in the office, and have remote users access the client 
computer set up for them in the office via RWW. 

Anyone see any issues with this? 

Yep, that's probably the easiest and cheapest approach as long as your 
Internet access is stable and you have sufficient bandwidth to handle the 
traffic.

-- 
Merv  Porter   [SBS-MVP]
============================

"Alexjbriggs" <Alexjbriggs@discussions.microsoft.com> wrote in message 
news:5FF904F6-B505-4331-9B4A-AD4FBD54F095@microsoft.com...
> Thanks again everyone.
>
> I believe we are going to stick with a very simple path.
>
> We already have a few extra client computers that arent being used. We 
> only
> have a total of 5 employees outside the office that need remote access, 
> and i
> dont see us adding more than 5 more in the next couple years.
>
> It seems the least expensive route, and easiest set up, is to just set up
> extra client computers in the office, and have remote users access the 
> client
> computer set up for them in the office via RWW.
>
> Anyone see any issues with this? 

BTW... I assume you're redirecting all My Documents folder to the server and 
making sure that the remote users (actually all users) save all files to 
their My Documents folder (no files allowed on the workstations).  This 
facilitates the nightly backup of the server and all important data files 
for disaster recovery.

-- 
Merv  Porter   [SBS-MVP]
============================

"Alexjbriggs" <Alexjbriggs@discussions.microsoft.com> wrote in message 
news:5FF904F6-B505-4331-9B4A-AD4FBD54F095@microsoft.com...
> Thanks again everyone.
>
> I believe we are going to stick with a very simple path.
>
> We already have a few extra client computers that arent being used. We 
> only
> have a total of 5 employees outside the office that need remote access, 
> and i
> dont see us adding more than 5 more in the next couple years.
>
> It seems the least expensive route, and easiest set up, is to just set up
> extra client computers in the office, and have remote users access the 
> client
> computer set up for them in the office via RWW.
>
> Anyone see any issues with this? 

Oh absolutely. We have had the server pretty much being run as a file server 
for at least 4 years now. No employee in the office is allowed to store files 
on the local hard drive. We have Carbonite backup service for over a year now 
on the server for an offsite backup. We use quickbooks in the office and have 
the quickbooks file server set up on our server. So EVERYTHING is run off the 
server. 

I appreciate all the advice and help. I will post back when the project is 
complete and update how everything went and is running in case anyone comes 
across this thread in the future with similar wants/needs. Maybe they will 
find use of this thread.

If anyone thinks of anything else related to this, please post!

"Merv Porter [SBS-MVP]" wrote:

> BTW... I assume you're redirecting all My Documents folder to the server and 
> making sure that the remote users (actually all users) save all files to 
> their My Documents folder (no files allowed on the workstations).  This 
> facilitates the nightly backup of the server and all important data files 
> for disaster recovery.
> 
> -- 
> Merv  Porter   [SBS-MVP]
> ============================
> 
> "Alexjbriggs" <Alexjbriggs@discussions.microsoft.com> wrote in message 
> news:5FF904F6-B505-4331-9B4A-AD4FBD54F095@microsoft.com...
> > Thanks again everyone.
> >
> > I believe we are going to stick with a very simple path.
> >
> > We already have a few extra client computers that arent being used. We 
> > only
> > have a total of 5 employees outside the office that need remote access, 
> > and i
> > dont see us adding more than 5 more in the next couple years.
> >
> > It seems the least expensive route, and easiest set up, is to just set up
> > extra client computers in the office, and have remote users access the 
> > client
> > computer set up for them in the office via RWW.
> >
> > Anyone see any issues with this? 
> 
> .
>