Home All Groups Group Topic Archive Search About

Testing Windows 2003 with Exchange 2003 - Advice needed

Author
16 Mar 2005 3:05 PM
Neil
Hello All,

I am testing a server with Windows 2003 Server (Standard Edition) and for
the moment, I do not have a registered domain. To test everything, the
domain for the DC is just prefixed with MyDomain.local and the domain is not
registered. Email on client computers is Outlook 2003. All email accounts
are POP3. The incomming mail and outgoing mail server is the same for all
email accounts (only the username and password changes). Is it possible to
set up exchange without having a registered domain? I havn't looked into the
setup for exchange but I if someone can tell me right now that it cant be
set up without a registered domain, then i wont even try testing it at the
moment.

Any help is appreciated.

Thanks,

Neil.

Author
18 Mar 2005 11:50 AM
Neil
Hi Rick,

Can see your latest reply in google, but it hasn't filtered through to my
news in outlook yet.

Anyway, I think a registered domain is the aim, but to fill the gap i have
tested exchangepop3 and its a great simple to use program and got it to work
no problem with exchange. The options in exchangepop3 were what i was trying
to find in exchange which explains why i was a bit confused.

Funny you should mention SBS 2003. I have been looking into this already. It
would be great if SBS 2003 is as easy to configure exchange as it was with
exchangepop3. I will have to look into it in greater details when i
(eventually) get a trial version.

This is the last question :-). We have 2 company names. For aguments sake
Company1 and Company2. From what you are saying, does this mean you would
have 3 servers? One for Company1, one for Company2 and the other is the
exchange server? If using SBS 2003, I would probably just use 2 servers as
SBS includes exchange anyway.

Thanks again,

Neil.
Author
18 Mar 2005 2:15 PM
Rick Gouin
SBS is very easy to configure.  It has all sorts of wizards that aren't
present in the normal version of Exchange and Windows.

Is it just one company with two names?  Or is it two companies?

If it is just one company, then you can get away with just one SBS.

If it is two companies, then each one should have their own SBS.

Some people will argue that you shouldn't put all your eggs in one
basket, but that is kind of the architecture of SBS, and by using it,
you have to acknowledge the creation of a single point of failure for
basically your entire systems infrastructure.
Author
18 Mar 2005 5:18 PM
Neil
Hi Rick,

It is the same company with 2 names EXCEPT to the outside world it is 2
seperate companies. Because of this, I feel each should have their own SBS
and be independant.

I agree with the eggs in one basket theory, and when creating a large
business network, seperating emails from files is a must do. As for a
network with 20 people I would say the worst case senario would be 4 hours
restoring a back-up tape. Like you say, because of the architechture of SBS,
it probably wont be worth the hassle of having exchange seperated.

I think I will suggest 2 servers with 2 domains after I figure out how SBS
works :-).

Thanks for your input on this. It has been a GREAT help on the few question
marks that I just couldn't figure out.

Neil.

Show quoteHide quote
"Rick Gouin" <r***@pragmaticutopia.com> wrote in message
news:1111155348.316818.81870@g14g2000cwa.googlegroups.com...
> SBS is very easy to configure.  It has all sorts of wizards that aren't
> present in the normal version of Exchange and Windows.
>
> Is it just one company with two names?  Or is it two companies?
>
> If it is just one company, then you can get away with just one SBS.
>
> If it is two companies, then each one should have their own SBS.
>
> Some people will argue that you shouldn't put all your eggs in one
> basket, but that is kind of the architecture of SBS, and by using it,
> you have to acknowledge the creation of a single point of failure for
> basically your entire systems infrastructure.
>