Re: Small office Recomondations

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Merv Porter [SBS-MVP] (mwport_at_hotmail.com_no_spam)
Date: 02/12/04


Date: Wed, 11 Feb 2004 19:42:47 -0500

While SBS 2003 may be a solution, it may be more complexity (and $$$ for
maintenance) than your users want to deal with. And while some of features
of SBS 2003 will work with Win9x machines, it's best to have either Win2K
Pro or WinXP Pro (but not WinXP Home Edition) workstations in the new
domain. This may mean added $$$ for software/hardware for a total network
upgrade to SBS 2003. And if these are true techno-phobes, they aren't going
to handle major changes gracefully. :-)

If all they need is File and Print sharing, buy an external USB hard drive
for the File sharing and attach it to a workstation that will be left on all
the time (essentially, a workstation/server). Preferably, this would be a
WinXP Pro machine. Put the shared files on the USB hard drive. Schedule
NTBackup to do a nightly backup of the USB drive to the workstation hard
drive. This offers the possibility of data recovery but nothing if they
have a fire, theft, or other disaster since you're not moving the data
offsite for safekeeping (a penalty that many P2P networks pay).
Alternately, if they can live with a weekly back up, you could add a second
"file sharing" HD to the workstation/server and back up the shared files to
the external USB drive. This could then be (gently) transported offsite for
safekeeping until the next scheduled backup.

While you're at it, create a "user" folder for each user and configure all
their Word, Excel and other apps to point to the "file-sharing" HD (no more
saving data to the local hard drives). These then will also be backed up
nightly.

The print sharing can be handled by sharing local workstation printers,
buying a cheap print server (<$150) to directly connect supported printers
to the network, or purchasing a network-ready printer to drop onto the
present P2P network.

The firewall part can usually be handled by an inexpensive and properly
configured "firewall" router (assuming a broadband connection). If they
have a dial-up account, there are other devices that can implement a shared
dial-up connection for the network users.

Now, if they truly need all the benefits (and associated costs) of a
client-server network, disregard everything I've previously said and buy SBS
2003 and upgrade the workstations to WinXP Pro.

-- 
Merv  Porter  [SBS MVP]
===================================
"Phil Fluhr" <pfluhr@softskills.com> wrote in message
news:OB#L4mL8DHA.1716@TK2MSFTNGP10.phx.gbl...
> I am looking for a Server Recomdation for a Server and Firewall for a
Small
> office 5 users currently with little chance of adding users next 18
months.
> Currently they are a peer to peer and use a 3rd party contact manger.
These
> are old school technaphobes who have not used the network much but, need
the
> benifits of a Server for Print and File sharring.
>
> I'm looking for a simple solution that will be easy to install and
maintain
> Server and Firewall.
>
> Can I get the solution for under 2K
>
> Thanks in Advance
>
> Phil
>
>


Relevant Pages

  • RE: Slow login, network browsing on SBS 2003
    ... I understand that several workstations in your SBS ... domain are having trouble logging in the domain and access the network ... shares on the SBS Server. ... Let's perform a Clean Boot on the problematic workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting up client computers after SBS 2003 install
    ... you are not going to get the good stuff that SBS should be providing. ... examples of how to set up your network. ... > administrator of both the workstation and the network user name so that I ... > "Roger" wrote in message ...
    (microsoft.public.windows.server.sbs)
  • Re: Web Traffic by Hour
    ... "Jim Behning SBS MVP" wrote: ... Wireshark and watch what is happening. ... Best bet it to format the workstation. ... Wireshark is a network monitoring utility. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cliients Cannot ping or connect to new SBS 2003 Server
    ... Win2k3 SP2 but that seems very messy and may force a complete server rebuild. ... pinging one workstation from another? ... you may need to install Network Monitor on the ... See what SBS support is working on ...
    (microsoft.public.windows.server.sbs)
  • Re: For the AdaOS folks
    ... Mach's concept of thread migration seems inappropriate. ... Since priorities must be enforced by the AdaOS kernel at all times (to ... could be on any workstation in the network. ...
    (comp.lang.ada)