Re: Same Email Domain 2 Sites

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

The problem, Patrick, is that you want failover, so that means the same mailboxes on both machines, and that is a trust relationship. If you were doing simple round-robin or forwarding it'd be a different story. But the configuration you outlined is not achievable in SBS. Sorry...

-Cliff


"Patrick" <Patrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6E80F722-B038-4B70-A00A-DD3B05008799@xxxxxxxxxxxxxxxx
So there's no way to have two separate Exchange servers talk to eachother
without a domain trust of some sort?

We've also realized that since we don't have full control over this server
and we'll be relying on another company to maintain it, we don't actually
want it to be part of the domain. Is a forest or domain trust the best way
to accomplish this and then can we use the transition pack and break SBS on
our end without purchasing all 75 SBS licenses first since we won't be
licensing them under the same domain server?

Patrick

"Cliff Galiher" wrote:

With two MX records, to work as you've outlined, would still require 80
users per exchange instance for proper failover (if I understand what you
want to accomplish.) and yea...that still breaks the 75 user barrier. If I
came across as implying you were trying to circumvent licensing, I
apologize. I just wanted to be clear that this is one of those scenarios
where the right path is, sadly, the expensive path. Sometimes the toughest
job in IT is telling the boss (or client, or customer) that they need to
bite the bullet...

-Cliff


"Patrick" <Patrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E6CAAA75-D521-46A6-9872-9C430F579613@xxxxxxxxxxxxxxxx
> This would work but I want to setup 2 MX records, one pointing to one, > the
> other pointing to the other. That way if one server is down or slow, > the
> other will pick up all the email. If they handle the email internally
> like
> Exchange does over the VPN, then the receiving email server would hold > any
> email that can't be delivered until the other server comes up.
>
> Of course, we want to do everything legally - we aren't trying to > bypass
> any
> licensing. The transition pack has already been priced out and will
> probably
> cause someone an aneurism.
>
> The two offices share only email at this point so there's no real > reason
> to
> setup a single domain across both sites. Email is important to them so > we
> don't want a single point of failure.
>
> Thanks,
> Patrick
>
> "Joe" wrote:
>
>> Patrick wrote:
>> > Hello,
>> >
>> > I have a client with two separate (geographical) offices that share >> > the
>> > same
>> > email domain. The one I work with has SBS 2003 R2 and the other has
>> > Server
>> > 2003 Standard. We'd like to bring their email inhouse. We can >> > setup a
>> > VPN
>> > between the two offices. Between the two offices there are 80 users >> > so
>> > obviously we can't join them both to the same SBS domain without
>> > exceeding
>> > the 75 user SBS limit. Can we install Exchange 2003 on the other
>> > server and
>> > have the same First Administrative Group cross both domains so we >> > can
>> > share
>> > the mailboxes (split geographically) and have email received by the
>> > wrong
>> > server go to the correct one transfered over the VPN?
>> >
>>
>> It's not unusual for Exchange to have to use a domain which is also
>> externally hosted. http://support.microsoft.com/kb/321721 is an
>> authoritative source for details. It should be possible to do this >> with
>> two Exchange installations. You wouldn't necessarily need a VPN if >> both
>> Exchanges are open to the Internet.
>>

.

Relevant Pages

  • Re: Connection to a SAMBA Active Directory
    ... Keep in mind that you're trying to setup a NT4 style trust ... if you setup the Exchange as a resource forest model, ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ...
    (microsoft.public.exchange.connectivity)
  • Re: exchange 2003 install
    ... explicit trusts - by default domains in the same Forest trust each other. ... You could set up the other Exchange box in any Domain in the Forest. ... server can and do see the same GAL - that functionality is provided by AD. ...
    (microsoft.public.exchange.setup)
  • Re: moving exchange 5.5 server to a different domain
    ... > Exchange 5.5 They are all in domain a. ... > Since I have permissions via the trust to the exchange services site ... I'd reccomend a spare server to be involved. ...
    (microsoft.public.exchange.admin)
  • Re: search for a guid
    ... the exchange part that got screwed up, so i should be able to remove the ... > all have two way external trust in place. ... My forest has two trees and two ... >>> This has been an issue ever sincethe domain and exchagne server were ...
    (microsoft.public.win2000.active_directory)
  • Re: Sometimes it works and sometimes not???
    ... Thanks Patrick for the links. ... I've tried the nslookup stuff and I get back ... > The first error is not an Exchange error, look to your Spam filter or AV ... > tot he other Server cannot be made. ...
    (microsoft.public.exchange2000.general)