Re: Out grown sbs2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hey Brian:
I am far from being a licensing guru but I was under the impression that you
could break out SQL and Exchange. They would require a 2003 standard server.
It seems that I remember reading somewhere there might be a way to do this
to migrate your licenses for say SQL from the SBS box onto anotehr 2003
server and get credit for the SQL you already have. I'm less sure about
Exchange but if you can it with SQL that would also make sense.

Chuck

"kj [SBS MVP]" wrote:

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



.



Relevant Pages

  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Easy to use second 2000 Server for Exchange?
    ... Existing Exchange 2000 server - therefore have the CALs - so no new ones are ... Frank McCallister SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email for second domain
    ... The Microsoft Exchange MTA Stacks service is normally disabled on Exchange 2003 Servers on SBS 2003. ... You can safely ignore the MTA warning messages on the SBS 2003 server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Configuring exchange 2003 in SBS
    ... As I know, this is not related to per user mailbox, it refer to the mailbox ... store on the whole Exchange server. ... This newsgroup only focuses on SBS technical issues. ... What minimum requirement if I want this server for a fileserver? ...
    (microsoft.public.windows.server.sbs)