Re: Setting up three laptops, should I or shouldn't I join them to SBS
- From: Joe <joe@xxxxxxxxxxxxxx>
- Date: Sun, 22 Jul 2007 14:35:09 +0100
Rick wrote:
I have three laptops I'm setting up. Two of them are second devices for a user (laptop for home and travel) and one user that will be their primary device, though, mostly out of the office.
So I'm wondering if I really should or shouldn't join them to SBS. I'll have outlook setup for rpc over http, two users will use RWW to connect to their PCs at work, and the other user will eventually use RWW to connect to a terminal server client at the office.
The only resources they may need from the laptop will be having to print at the office, though that also can be setup through http if I wanted. Any company files will be on WSS 3 that they can grap from RWW anyhow.
The advantage of joining the laptops to the domain are to enforce group policy.
The disadvantage is the same thing, enforcing group policy since it will add more complexity to the project.
Any recommendations or preferences for these scenarios for laptops? Any best practices?
As a rule of thumb, I'd say the one which connects locally sometimes,
and on which all the work is done, should be a domain member and connect
remotely by VPN, the others shouldn't. Most policy isn't relevant for
RWW and remote email only, so I wouldn't think much would be gained by
joining the others.
The 'primary device' is likely to be used offline a great deal, so using
offline folders over VPN would be important, though slow. There's no
real equivalent over RWW, which may be an obstacle to the traveller
moving to a TS environment. A truly mobile Internet connection may well
be necessary then. You also don't really want to get into trying to keep
two environments for one person synchronised, which doesn't sound
difficult but is bedevilled with tiny details.
As always, I'll point out that some networked applications are very
fragile, and should only be used remotely over RWW, not VPN. Microsoft
Access, when used with a split database for 'client-server' tasks, does
not actually have a server application, only a single data file. The
clients arbitrate access between themselves, using file system locking
and other bodges, and a network disconnection can wreck the data
backend. Low-cost accounting applications often have similar
architectural issues. SQL-based applications are much safer.
.
- Prev by Date: Re: Companyweb Issues
- Next by Date: Re: SMTP instance fully-qualified domain name does not match DNS r
- Previous by thread: Re: Setting up three laptops, should I or shouldn't I join them to SBS
- Next by thread: Re: Tape backup strange error
- Index(es):
Relevant Pages
|
Loading
