Our client has a 2k sbs environment with a dozen users. Currently 280 agents,
that work on behalf of the company, use mail services provided by a offsite
hosted mail server.

They want to have control over the mail for the entire organization but as
we all know sbs's exchange would up and die.

We would like to:
add an Ent. Exchange server with OWA to the sbs network
Liscense the internal users properly for the new server
create mail enabled contacts for the agents
add the external conector to the new server to cover the agents access

The part I see problems with is Exchange needing to authenticate the agents
and the SBS restrictions.

Is there any way to do this in a SBS network.

My fall back plan is to put a 'dummy' domain mycompany.mail on the Exchange
server. I would only need to liscence the 12 users and thats not a big deal.
The exchange server would host AD and be the only computer in its domain?

Any help fitting this server into the SBS network would be great. I plan to
upgrade them to SBS2003 so they can use RWW and it would be nice if the OWA
links worked?

__Side bar__ If I need to uninstall the SBS version of Exchange,will
Add/remove break anything that is not related to Exchange?


Thanks
These forums are worth their weight in gold!

--
Keith the confused MCSE

Re: Add 2003 exchange ent. to a sbs 2000 domain by John

John
Mon Sep 26 15:54:40 CDT 2005

The problem I see here is that technically the Agents would need Windows
CAL's in addition to the Exchange CAL's to access the Exchange Enterprise
Server. At that point, it would make more sense to just move away from SBS
and to a Standard Windows Domain since the additional 12 users is really a
drop in the bucket if you need 280 Windows CAL's and Exchange CAL's for all
the Agents.

Your Fallback plan is really your only course to proceed with. One thing
you should be aware of if you plan on making Exchange 2003 DC,
http://support.microsoft.com/kb/822179

FYI: Exchange 2003 SP2 coming later this year increases the Store Limits to
74GB from 16GB on Exchange Standard. Just thought you might want to know
this since Exchange Enterprise will cost much more than Exchange Standard.
You could always start out with Exchange Standard and upgrade later to
Exchange Enterprise if you find you are tight on space.

--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner

"Keith the confused" <Keiththeconfused@discussions.microsoft.com> wrote in
message news:A7B2648C-9B8B-4596-BB0D-87DC7049D853@microsoft.com...
> Our client has a 2k sbs environment with a dozen users. Currently 280
> agents,
> that work on behalf of the company, use mail services provided by a
> offsite
> hosted mail server.
>
> They want to have control over the mail for the entire organization but as
> we all know sbs's exchange would up and die.
>
> We would like to:
> add an Ent. Exchange server with OWA to the sbs network
> Liscense the internal users properly for the new server
> create mail enabled contacts for the agents
> add the external conector to the new server to cover the agents access
>
> The part I see problems with is Exchange needing to authenticate the
> agents
> and the SBS restrictions.
>
> Is there any way to do this in a SBS network.
>
> My fall back plan is to put a 'dummy' domain mycompany.mail on the
> Exchange
> server. I would only need to liscence the 12 users and thats not a big
> deal.
> The exchange server would host AD and be the only computer in its domain?
>
> Any help fitting this server into the SBS network would be great. I plan
> to
> upgrade them to SBS2003 so they can use RWW and it would be nice if the
> OWA
> links worked?
>
> __Side bar__ If I need to uninstall the SBS version of Exchange,will
> Add/remove break anything that is not related to Exchange?
>
>
> Thanks
> These forums are worth their weight in gold!
>
> --
> Keith the confused MCSE
>



Re: Add 2003 exchange ent. to a sbs 2000 domain by Keiththeconfused

Keiththeconfused
Mon Sep 26 18:13:01 CDT 2005

I was under the impression that the external connector liscence would suffice
for the agents since the only access to the network would be Via the web in
OWA?
Is this not what the External Connector license was disigned for?

Please advice
--
Keith the confused




"John Oliver, Jr. [MVP]" wrote:

> The problem I see here is that technically the Agents would need Windows
> CAL's in addition to the Exchange CAL's to access the Exchange Enterprise
> Server. At that point, it would make more sense to just move away from SBS
> and to a Standard Windows Domain since the additional 12 users is really a
> drop in the bucket if you need 280 Windows CAL's and Exchange CAL's for all
> the Agents.
>
> Your Fallback plan is really your only course to proceed with. One thing
> you should be aware of if you plan on making Exchange 2003 DC,
> http://support.microsoft.com/kb/822179
>
> FYI: Exchange 2003 SP2 coming later this year increases the Store Limits to
> 74GB from 16GB on Exchange Standard. Just thought you might want to know
> this since Exchange Enterprise will cost much more than Exchange Standard.
> You could always start out with Exchange Standard and upgrade later to
> Exchange Enterprise if you find you are tight on space.
>
> --
> John Oliver, Jr.
> MCSE, MCT, CCNA, Exchange MVP
> Microsoft Certified Partner
>
> "Keith the confused" <Keiththeconfused@discussions.microsoft.com> wrote in
> message news:A7B2648C-9B8B-4596-BB0D-87DC7049D853@microsoft.com...
> > Our client has a 2k sbs environment with a dozen users. Currently 280
> > agents,
> > that work on behalf of the company, use mail services provided by a
> > offsite
> > hosted mail server.
> >
> > They want to have control over the mail for the entire organization but as
> > we all know sbs's exchange would up and die.
> >
> > We would like to:
> > add an Ent. Exchange server with OWA to the sbs network
> > Liscense the internal users properly for the new server
> > create mail enabled contacts for the agents
> > add the external conector to the new server to cover the agents access
> >
> > The part I see problems with is Exchange needing to authenticate the
> > agents
> > and the SBS restrictions.
> >
> > Is there any way to do this in a SBS network.
> >
> > My fall back plan is to put a 'dummy' domain mycompany.mail on the
> > Exchange
> > server. I would only need to liscence the 12 users and thats not a big
> > deal.
> > The exchange server would host AD and be the only computer in its domain?
> >
> > Any help fitting this server into the SBS network would be great. I plan
> > to
> > upgrade them to SBS2003 so they can use RWW and it would be nice if the
> > OWA
> > links worked?
> >
> > __Side bar__ If I need to uninstall the SBS version of Exchange,will
> > Add/remove break anything that is not related to Exchange?
> >
> >
> > Thanks
> > These forums are worth their weight in gold!
> >
> > --
> > Keith the confused MCSE
> >
>
>
>

Re: Add 2003 exchange ent. to a sbs 2000 domain by John

John
Mon Sep 26 18:23:47 CDT 2005

If they Qualify for the Connector License, then Yes. I would verify from a
Microsoft Licensed Reseller (CDW, etc.) or Software Advisor this is the
case. If so, then I would also verify from them would the Connector License
be valid in a SBS Domain even with an additional Exchange Server for the
Connector License?

--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner

"Keith the confused" <Keiththeconfused@discussions.microsoft.com> wrote in
message news:0D964121-888D-417F-98D0-E1255ACB471B@microsoft.com...
>I was under the impression that the external connector liscence would
>suffice
> for the agents since the only access to the network would be Via the web
> in
> OWA?
> Is this not what the External Connector license was disigned for?
>
> Please advice
> --
> Keith the confused
>
>
>
>
> "John Oliver, Jr. [MVP]" wrote:
>
>> The problem I see here is that technically the Agents would need Windows
>> CAL's in addition to the Exchange CAL's to access the Exchange Enterprise
>> Server. At that point, it would make more sense to just move away from
>> SBS
>> and to a Standard Windows Domain since the additional 12 users is really
>> a
>> drop in the bucket if you need 280 Windows CAL's and Exchange CAL's for
>> all
>> the Agents.
>>
>> Your Fallback plan is really your only course to proceed with. One thing
>> you should be aware of if you plan on making Exchange 2003 DC,
>> http://support.microsoft.com/kb/822179
>>
>> FYI: Exchange 2003 SP2 coming later this year increases the Store Limits
>> to
>> 74GB from 16GB on Exchange Standard. Just thought you might want to know
>> this since Exchange Enterprise will cost much more than Exchange
>> Standard.
>> You could always start out with Exchange Standard and upgrade later to
>> Exchange Enterprise if you find you are tight on space.
>>
>> --
>> John Oliver, Jr.
>> MCSE, MCT, CCNA, Exchange MVP
>> Microsoft Certified Partner
>>
>> "Keith the confused" <Keiththeconfused@discussions.microsoft.com> wrote
>> in
>> message news:A7B2648C-9B8B-4596-BB0D-87DC7049D853@microsoft.com...
>> > Our client has a 2k sbs environment with a dozen users. Currently 280
>> > agents,
>> > that work on behalf of the company, use mail services provided by a
>> > offsite
>> > hosted mail server.
>> >
>> > They want to have control over the mail for the entire organization but
>> > as
>> > we all know sbs's exchange would up and die.
>> >
>> > We would like to:
>> > add an Ent. Exchange server with OWA to the sbs network
>> > Liscense the internal users properly for the new server
>> > create mail enabled contacts for the agents
>> > add the external conector to the new server to cover the agents access
>> >
>> > The part I see problems with is Exchange needing to authenticate the
>> > agents
>> > and the SBS restrictions.
>> >
>> > Is there any way to do this in a SBS network.
>> >
>> > My fall back plan is to put a 'dummy' domain mycompany.mail on the
>> > Exchange
>> > server. I would only need to liscence the 12 users and thats not a big
>> > deal.
>> > The exchange server would host AD and be the only computer in its
>> > domain?
>> >
>> > Any help fitting this server into the SBS network would be great. I
>> > plan
>> > to
>> > upgrade them to SBS2003 so they can use RWW and it would be nice if the
>> > OWA
>> > links worked?
>> >
>> > __Side bar__ If I need to uninstall the SBS version of Exchange,will
>> > Add/remove break anything that is not related to Exchange?
>> >
>> >
>> > Thanks
>> > These forums are worth their weight in gold!
>> >
>> > --
>> > Keith the confused MCSE
>> >
>>
>>
>>



RE: Add 2003 exchange ent. to a sbs 2000 domain by Keiththeconfused

Keiththeconfused
Mon Sep 26 20:55:03 CDT 2005

After a short talk with MS pre sales, it would seem that the definition of
'business partener' is a bit grey.

I was advised to make sure the 'agents' could not be construed as employees
in order for them to qualify for the external liscense. I will ask the client
a few pointed questions about their 'agents'. I believe these agents are self
employed and are able to sell policies for any company not just my client.

As for the SB server I don't think I'll attempt to involve it. I will stick
with a seperate domain and just get cals for the local users.

Thanks for the insight.
--
Keith the confused
MCSE



"Keith the confused" wrote:

> Our client has a 2k sbs environment with a dozen users. Currently 280 agents,
> that work on behalf of the company, use mail services provided by a offsite
> hosted mail server.
>
> They want to have control over the mail for the entire organization but as
> we all know sbs's exchange would up and die.
>
> We would like to:
> add an Ent. Exchange server with OWA to the sbs network
> Liscense the internal users properly for the new server
> create mail enabled contacts for the agents
> add the external conector to the new server to cover the agents access
>
> The part I see problems with is Exchange needing to authenticate the agents
> and the SBS restrictions.
>
> Is there any way to do this in a SBS network.
>
> My fall back plan is to put a 'dummy' domain mycompany.mail on the Exchange
> server. I would only need to liscence the 12 users and thats not a big deal.
> The exchange server would host AD and be the only computer in its domain?
>
> Any help fitting this server into the SBS network would be great. I plan to
> upgrade them to SBS2003 so they can use RWW and it would be nice if the OWA
> links worked?
>
> __Side bar__ If I need to uninstall the SBS version of Exchange,will
> Add/remove break anything that is not related to Exchange?
>
>
> Thanks
> These forums are worth their weight in gold!
>
> --
> Keith the confused MCSE
>