Re: Out grown sbs2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

BrianMultiLanguage wrote:
I wish all these threads added up to easier reading but here's my
recap.
1. you can have multiple DCs in multiple AD sites in multiple
locations but SBS must be the PDC.
2. there's nothing stopping you from having an additional DC in the
SBS domain.
(BDC) including off site.
3. But you *can* have DC redundancy w/an SBS domain. You can have
multiple DNS servers, multiple WINS servers, use DFS, whatnot.
4. The only thing you can't do is 'break out' stuff like
Exchange/SQL/etc to other boxes. But remember, with Exchange, you
can't have full mailbox replication between servers anyway. That is
a key.
5. I think you could add a standard 2003 server to locations 2 and 3
and make them domain controllers so that logon time would be short at
those locations. SBS will replicate the logon database to locations 2
and 3 from your SBS server.


You're pretty much on course above.

So I need to figure out how I can have a redundant for
Email (different server of course)

You can purchase additional Exchange Server licenses and upgrade to SBS2003
R2 where your SBS USER CAL's will cover user access to the additional
Exchange servers. This *may* help your remote users, but it will certainly
multiply your admin complexity. Exchange 2003 doesn't really have any
provision for full redundancy. You can build Clustered servers and get
redundant servers, but not redundant Information stores (where the actual
emails are kept). Your best investment is making the Exchange server as
reliable as possible, doing good backups, and practicing restoration methods
so your prepared for unexpected disruptions.

Internet (how to regateway w/s to an alternate)
vpn/rdp. (how to get in teh network if SBS is down.)

Not using ISA, I'd recommend putting a good hardware firewall /VPN/
appliance in places for Internet access and configuring SBS as a single NIC.
This will help you going forward to the next versions of SBS or Windows
Server 2008 as well. Users access to the Internet is then no dependant upon
the SBS server alone (Still need second DNS & DC servers though).

??





"Kevin Weilbacher" wrote:

RWW was designed for SBS, you don't get it as designed in a std W2K3
server environment.

What was the specifics of your downtime? Until you address the cause
and result, simply throwing more hardware will not solve the
problem, but rather triple your potential problems.

Then, as with any other down time scenario, once has to weight the
various cost of redundancy, backups, and equipment with the ROI.

And have you considered that simply throwing more servers into the
mix with "DC redundancy" doesn't mean squat in keeping the
Internet/email up if the problem is with your ISP service? My
Internet at work went down last thursday morning. My ISP was not
aware of a problem til I called them, and they're supposed to be
monitoring this all the time.

--
Kevin Weilbacher [SBS MVP]
"The days pass by so quickly now, the nights are seldom long"
"BrianMultiLanguage" <BrianMultiLanguage@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:2986F91A-E6D4-4866-9A34-2C5B081DB549@xxxxxxxxxxxxxxxx
We have out grown SBS I am afraid.
We are going to need three different locations, and multiple sbs
servers won't do. When our went out, we were dead in the water.
Does RWW work on std Server?
I know'll I have to buy:
Server Std 2003 or ?
ExchangeStd 2003 or ?
What else I am not sure off.
Any one else migrated up?

--
/kj


.

Quantcast