Re: Easiest way to share existing files saved on SBS server with remote users?

In article <1185330331.691217.171090@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
mike.google@xxxxxxxxxxxxxxxxx says...
On Jul 24, 9:53 pm, Leythos <v...@xxxxxxxxxxx> wrote:
In article <1185327514.494033.85...@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
mike.goo...@xxxxxxxxxxxxxxxxx says...



My client's remote users work with very small files, and do not open/
save very often. I know how well TS works, for the very reasons you
described. So TS is an option. But, I'd still like to give SBS/RWW/
SharePoint (or Exchange) a try, since usage will be so light. So do
you have any suggestions on how to implement sharing of files stored
on a SBS machine to a server-less remote office? I did not like the
"Document" part of Documents and Links, as it requires too much admin
work. But "Links" are very close to what I want, as I can point a
link to a file share on the SBS. So the user is presented with a
Windows Explorer-like GUI of the folders and files - excellent. But
how about forcing it to use the file's NTFS permissions - as opposed
to the Admin/Web Admin/Contributor/Viewer security groups?

We implement a LOT of remote users all over the country with a LOT of
clients - it's one reason people come to us when the other shops can't
get it right.

The best method is Terminal Server, no matter what else, it's the only
way to ensure that they don't corrupt files/folders and to ensure that
the files get backed-up properly.

A high-end workstation with Win 2003 Std will serve 10 users for a long
time if needed. One thing we do is implement site-site VPN's and let
them print from the T/S to their local printer (putting it on a IP at
their side) - so that we don't have to mess with Terminal Server printer
issues.

We have a number of customers that use Verizon BB wireless cards with
generic laptops - we set a limited user account, remove all software (as
much as possible), install self-managed AV, FireFox, remove IE access,
remove Outlook Express, etc... There are three icons, Verizon, VPN to
company, Terminal Server. This means that no PT data or company data is
stored on the laptops and the loss does not expose the company or
patients data....

Drop the idea of the web interface and just bite the bullet and use a
small terminal server - your customer will love you and you'll get more
sleep at night and weekends.



Thanks for the feedback Leythos! I thought SBS/RWW/SharePoint seemed
like such a simple, all-in-one solution for connecting a few remote
users to SBS at a main office :) Sounds like you do not have much
confidence in the underlying technology? Not having attempted it, I
admit I am a newbie:) Just curious, have you ever tried the approach
I am contemplating? If so, how many users at remote site? What part
of the technology did you attribute the failure to?

I don't like anything where a remote user has the files on their remote
computer where we don't strictly control their security. I don't like
people to upload files that were not part of the company network to
start with.

I have no issues with the technology used in SBS, I have security issues
and reliability issues based on how people really work with their
computers/data.

I would go so far as to install Neoware Thin-Clinet systems (about $250
each) at the remote office and not even give them computers, the take
the savings (I figure that a loaded XP Prof box costs about $1100) which
would be about $700-800 and use it to purchase a Terminal Server box
with licenses... This scales and works well.

We have one client with a exposed Remote Desktop (IP/Port) connection
that has users all over the country, they work from anywhere they can
get a connection.

I have one client with a beefy terminal server with about 140 remote
connections (users, not part of SBS network) running 24/7, but I also
have a cheap $2000 terminal server that supports 14 users without any
real problems.

The key reason for terminal server is the savings in support, security,
risk, management, control.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@xxxxxxxxxx (remove 999 for proper email address)
.

Relevant Pages

  • Re: Easiest way to share existing files saved on SBS server with remote users?
    ... on a SBS machine to a server-less remote office? ... their side) - so that we don't have to mess with Terminal Server printer ... We have one client with a exposed Remote Desktop connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Easiest way to share existing files saved on SBS server with remote users?
    ... I know how well TS works, for the very reasons you ... on a SBS machine to a server-less remote office? ... The best method is Terminal Server, no matter what else, it's the only ...
    (microsoft.public.windows.server.sbs)
  • Re: Managing SBS 2000 Remotely
    ... Merv Porter [SBS MVP] ... so by a Remote Desktop Client ... SBS 2000 is configured as a Terminal Server ... >>Desktop client to access the server remotely.. ...
    (microsoft.public.backoffice.smallbiz2000)
  • RE: Remote Desktop (connecting more than 2 clients) to SBS
    ... The reason that SBS does not contain the Terminal Services in Application mode is due to security considerations. ... If your database is on a shared drive on the server, a VPN connection will also give them access to the database though they will have to manually map a drive. ... The whole reason for purchasing SBS was I was told you could have multiple clients using remote desktop. ...
    (microsoft.public.windows.server.sbs)
  • Re: Will SBS be the correct app for this?
    ... there are 4 local employees and 20 more users who are remote. ... but you'd need to purchase the Terminal Server OS, ... Les Connor [SBS Community Member - SBS MVP] ... SBS with a Terminal Server running in VS to service your 30 users. ...
    (microsoft.public.windows.server.sbs)
Loading