Re: Is SBS 2003 suited for this client?
From: Richard Fagen (no_spam_at_my_isp.com)
Date: 11/30/04
- Next message: webb: "Re: sbs.domain name #4.4.7"
- Previous message: Eugene Tan: "Re: Backup Problems!!!!!"
- In reply to: Dave Nickason [SBS MVP]: "Re: Is SBS 2003 suited for this client?"
- Next in thread: Kevin Weilbacher [SBS-MVP]: "Re: Is SBS 2003 suited for this client?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Nov 2004 23:21:04 -0500
Hi Dave,
Thanks for the great comments. I'll have to digest them all and talk
with the client.
My first thought too was to host the FTP site, but their reason is the
need of near instantaneous access to the large files. If their clients
use high speed to access the lab's internal FTP site and it is slow, the
lab doesn't mind, however, once the files are on the internal FTP site,
they need fast internal access among their workstations and printers.
Local internet connections range from 2-3Mb/sec which is fine for the
customers to send the lab the data, but the lab wants 100Mb/sec speed
internally. If they hosted it externally, they'd slow down to the ISP's
2-3Mb/sec. I finally saw their point.
They are also a small lab and I'm sure getting a hosting package with
10-20G of storage for an FTP site would break their budget.
About Exchange....
I'll admit I don't know enough about Exchange. I have read all of
Harry's books, plus the MS Press, but I still am not 100% comfortable
with Exchange. I have used Public folders and agree they are great, but
in practice, I can't get my clients to use them. No one seems to want
the responsibility of maintaining a centralized source for company
contacts and calendars. I have really tried many times, but my clients
(all smaller business with 5-15 users) claim they have no time.
Backup....
I only convinced a few people to buy proper tape systems. They go nuts
when I mention cost (I know, I know, what is the cost of their data).
They don't understand why I can build them a great server for under
$2000 Cdn but a DAT tape, SCSI card and server programs cost more than
the server itself! Most gamble and backup just the data to CD's. It is
dumb but at least lately, I've convinced them to install DVD burners and
use cheaper DVD+RW blanks. FYI, I have Ghost images of their SBS setups
in case their C: partition gets screwed. I really hoping the new 'blue
light laser DVD's' will be available. A 50G DVD is something I know I
can sell them :)
Antivirus....
I've been using Symantec Corporate Edition for viruses. Isn't that good
enough? Besides, spyware is much more of a threat to most people. I've
have only one minor virus outbreak in the past few years, but 90% of
PC's I come across are infected with Spyware. I keep preaching about
AdAware and Spybot, but they complain 'they have no time' .... now they
get my invoices :)
Richard
Dave Nickason [SBS MVP] wrote:
> There are a couple of issues you may want to explore further. FTP is not by
> default a secure protocol, and it's not a best practice to host an FTP site
> on SBS or any domain controller. Also, if the FTP clients are
> authenticating, you probably need SBS CALs for them. I'm not the licensing
> expert, but if I'm right about that it would probably be a big negative.
>
> My idea would be to install SBS 2003 in a conventionally-configured domain.
> I'd continue to host the FTP site on the NT box, which I would give its own
> Internet connection separate from that of the SBS network. Or, get a router
> with a DMZ port and connect the FTP box to that, allowing it to share the
> SBS network's Internet connection. Then let the SBS clients access the FTP
> server over the Internet rather than having it inside the firewall. You'd
> have the SBS domain at yourdomain.local, and the ftp site at
> ftp.yourdomain.com or whatever it is now.
>
> By the way, if FTP is a core part of your client's business, isn't that more
> of a reason to use a hosting company rather than less? I've seen data
> center specs for some of the big hosting outfits, and their infrastructure
> far outdoes anything a typical small business could afford (live backup,
> redundant systems, UPS, fire supression, etc.).
>
> One other comment - IMO Exchange server is what makes life at the office
> worth living. Even if you use POP accounts, please consider using Exchange
> and the POP connector. Centralized backup and virus scanning, public
> folders - there are a zillion benefits to Exchange, and if you're going to
> purchase SBS, why give them up. It'll be configured with the CEICW, which
> takes out 99% of the complexity.
- Next message: webb: "Re: sbs.domain name #4.4.7"
- Previous message: Eugene Tan: "Re: Backup Problems!!!!!"
- In reply to: Dave Nickason [SBS MVP]: "Re: Is SBS 2003 suited for this client?"
- Next in thread: Kevin Weilbacher [SBS-MVP]: "Re: Is SBS 2003 suited for this client?"
- Messages sorted by: [ date ] [ thread ]