Cached credentials on shared folders
|
Prev: Console log File Trimming
Next: Firewall Appliances
From: Anteaus on 24 Jul 2010 04:18 My ten cents worth would be that no VPN is reliable enough to make an office totally dependent on it for logon. Unless you can afford a leased line you should avoid domino-effect scenarios. The question here is whether you need to manage the users from the central location, or whether the small amount of extra work in maintaining separate useraccounts would be preferable to creating an SPOF which can bring both sites down in one fell swoop. I would argue that resilience is more important. It's either that or you need to ditch the SBS. "yaro137" wrote: > > You can open the shares, you can have the users access the branch server > > with branch server local accounts, or you can put a second dc at the branch. > > > > Or improve the reliability of the SBS server connectivity, which would be > > the preferred choice.
From: yaro137 on 26 Jul 2010 07:12
On 24 July, 09:18, Anteaus <Ante...(a)discussions.microsoft.com> wrote: > My ten cents worth would be that no VPN is reliable enough to make an office > totally dependent on it for logon. Unless you can afford a leased line you > should avoid domino-effect scenarios. > > The question here is whether you need to manage the users from the central > location, or whether the small amount of extra work in maintaining separate > useraccounts would be preferable to creating an SPOF which can bring both > sites down in one fell swoop. I would argue that resilience is more important. > > It's either that or you need to ditch the SBS. > > "yaro137" wrote: > > > You can open the shares, you can have the users access the branch server > > > with branch server local accounts, or you can put a second dc at the branch. > > > > Or improve the reliability of the SBS server connectivity, which would be > > > the preferred choice. Interesting view. It's not that easy to just discard SBS especially after a recent upgrade. Thanks for your input. yaro |