testing exchange 2003

I'm going to bring email in house and I was considering
using Exchange 2003.

There's only about 20 or so pc's on this network and
there is no domain. Do I have to use a domain in order to
use Exchange 2003?

I hesitate on going ahead and installing Active Directory
because it wants a fully qualified domain name. I'm not
sure what to use because I want to test out exchange with
my own personal registered domain and setup everything
first so i can test it than use my companies registered
domain.

Thanks
Helm

Al
Thu Sep 30 11:55:35 CDT 2004

You do need Active Directory but you do not need to, nor want to use the
same domain name as your personal registered domain name. Exchange can live
in one FQDN domain name and accept mail for many many others without issue
(see the help file on recipient policy to see what I'm talking about).

Al
"Matt Helm" <anonymous@discussions.microsoft.com> wrote in message
news:248e01c4a70d$7e412af0$a601280a@phx.gbl...
> I'm going to bring email in house and I was considering
> using Exchange 2003.
>
> There's only about 20 or so pc's on this network and
> there is no domain. Do I have to use a domain in order to
> use Exchange 2003?
>
> I hesitate on going ahead and installing Active Directory
> because it wants a fully qualified domain name. I'm not
> sure what to use because I want to test out exchange with
> my own personal registered domain and setup everything
> first so i can test it than use my companies registered
> domain.
>
> Thanks
> Helm

Lanwench
Thu Sep 30 11:57:00 CDT 2004

Matt Helm wrote:
> I'm going to bring email in house and I was considering
> using Exchange 2003.
>
> There's only about 20 or so pc's on this network and
> there is no domain. Do I have to use a domain in order to
> use Exchange 2003?

Yes.
>
> I hesitate on going ahead and installing Active Directory
> because it wants a fully qualified domain name.

That's OK, it's not related to your public/web/mail domain name at all. Name
it mycompany.local for AD, or something like that. Note that it *must* not
be a single-label domain (i.e., mycompany) in DNS....the NetBIOS name of the
company can be mycompany, but the AD domain name must be
mycompany.something.....

> I'm not
> sure what to use because I want to test out exchange with
> my own personal registered domain and setup everything
> first so i can test it than use my companies registered
> domain.

You can test it with internal mail only to make sure it works. You don't
need to use it for internet mail - can add that later, as per
http://www.msexchange.org/tutorials/MF002.html.....

Another suggestion is to look at SBS2003 for this office - it's inexpensive
and will support up to 75 users. If you haven't got a lot of experience
setting up stuff like this, it might behoove you to get a good consultant in
to do the setup for you.
>
> Thanks
> Helm

For a network g

anonymous
Thu Sep 30 12:54:33 CDT 2004

>If you haven't got a lot of experience
>setting up stuff like this, it might behoove you to get
a good consultant in
>to do the setup for you.


AHAHHA... Than I couldn't bug you guys with all my newbie
questions! =)

Lanwench
Thu Sep 30 12:59:41 CDT 2004

anonymous@discussions.microsoft.com wrote:
>> If you haven't got a lot of experience
>> setting up stuff like this, it might behoove you to get a good
>> consultant in to do the setup for you.
>
>
> AHAHHA... Than I couldn't bug you guys with all my newbie
> questions! =)

Sure you could. Happens all the time. <g>
Just remember, it takes very little work to maintain a properly setup
network environment. It takes a LOT of work to fix problems in one that
wasn't set up right to begin with.

Matt
Thu Sep 30 13:15:09 CDT 2004

Okie... Well maybe you can point me in the right direction than if you would
please.

I have about 20 pc's on this network. Two are windows 2003 servers. One is
acting as a application server and the other is a file server.
I have a spare box that I'm going to go ahead and setup as a domain
controller with Active Directory.

Is there some tutorial or best practices or whatever that would kind of step
by step show me how to move my network to a domain configuration?

Thanks
helm


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:uXwoJfxpEHA.3396@tk2msftngp13.phx.gbl...
> anonymous@discussions.microsoft.com wrote:
>>> If you haven't got a lot of experience
>>> setting up stuff like this, it might behoove you to get a good
>>> consultant in to do the setup for you.
>>
>>
>> AHAHHA... Than I couldn't bug you guys with all my newbie
>> questions! =)
>
> Sure you could. Happens all the time. <g>
> Just remember, it takes very little work to maintain a properly setup
> network environment. It takes a LOT of work to fix problems in one that
> wasn't set up right to begin with.
>
>

Lanwench
Thu Sep 30 13:28:21 CDT 2004

Matt Helm wrote:
> Okie... Well maybe you can point me in the right direction than if
> you would please.
>
> I have about 20 pc's on this network. Two are windows 2003 servers.
> One is acting as a application server and the other is a file server.
> I have a spare box that I'm going to go ahead and setup as a domain
> controller with Active Directory.
>
> Is there some tutorial or best practices or whatever that would kind
> of step by step show me how to move my network to a domain
> configuration?

Not sure where to point you at on the internet, although the newsgroups are
a great place to ask specific questions - but I'd pick up some books first &
get reading.

Q - have you already bought another license for Windows server & Exchange?
If not, I must repeat my SBS recommendation (unless you think your network
will soon outgrow the 75-user limit or you require Exchange Enterprise
edition).
>
> Thanks
> helm
>
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
> message news:uXwoJfxpEHA.3396@tk2msftngp13.phx.gbl...
>> anonymous@discussions.microsoft.com wrote:
>>>> If you haven't got a lot of experience
>>>> setting up stuff like this, it might behoove you to get a good
>>>> consultant in to do the setup for you.
>>>
>>>
>>> AHAHHA... Than I couldn't bug you guys with all my newbie
>>> questions! =)
>>
>> Sure you could. Happens all the time. <g>
>> Just remember, it takes very little work to maintain a properly setup
>> network environment. It takes a LOT of work to fix problems in one
>> that wasn't set up right to begin with.

Matt
Thu Sep 30 13:44:47 CDT 2004

I have the Win2k 2003 license.. dont have the exchange one yet. I'm going to
look into using SBS. Will there be any limitation with features? or just
with the number of users? I'll be able to use OWA?

thanks
helm



"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:eey5EwxpEHA.1688@TK2MSFTNGP10.phx.gbl...
> Matt Helm wrote:
>> Okie... Well maybe you can point me in the right direction than if
>> you would please.
>>
>> I have about 20 pc's on this network. Two are windows 2003 servers.
>> One is acting as a application server and the other is a file server.
>> I have a spare box that I'm going to go ahead and setup as a domain
>> controller with Active Directory.
>>
>> Is there some tutorial or best practices or whatever that would kind
>> of step by step show me how to move my network to a domain
>> configuration?
>
> Not sure where to point you at on the internet, although the newsgroups
> are
> a great place to ask specific questions - but I'd pick up some books first
> &
> get reading.
>
> Q - have you already bought another license for Windows server & Exchange?
> If not, I must repeat my SBS recommendation (unless you think your network
> will soon outgrow the 75-user limit or you require Exchange Enterprise
> edition).
>>
>> Thanks
>> helm
>>
>>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
>> message news:uXwoJfxpEHA.3396@tk2msftngp13.phx.gbl...
>>> anonymous@discussions.microsoft.com wrote:
>>>>> If you haven't got a lot of experience
>>>>> setting up stuff like this, it might behoove you to get a good
>>>>> consultant in to do the setup for you.
>>>>
>>>>
>>>> AHAHHA... Than I couldn't bug you guys with all my newbie
>>>> questions! =)
>>>
>>> Sure you could. Happens all the time. <g>
>>> Just remember, it takes very little work to maintain a properly setup
>>> network environment. It takes a LOT of work to fix problems in one
>>> that wasn't set up right to begin with.
>
>

Lanwench
Thu Sep 30 15:07:47 CDT 2004

Matt Helm wrote:
> I have the Win2k 2003 license.. dont have the exchange one yet. I'm
> going to look into using SBS. Will there be any limitation with
> features?

You can't use Exchange Enterprise, or Win2003 Advanced Server, or set up
trusts to other domains. You can't have more than 75 users. You can't
install its bundled components to other servers. You can't run terminal
services on it for users (although you can use remote desktop/admin mode for
remote admin). It has to hold all the FSMO roles in AD, but you can add
additional DCs. You can't run SBS as a member server (but of course, what
would be the point of buying it if that's what you wanted?)

> I'll be able to use OWA?

Yep. Also, there's a feature called Remote Web Workplace for remote desktop
access to any Windows XP Pro workstations on your network.... see
http://www.winnetmag.com/SQLServer/Article/ArticleID/40757/SQLServer_40757.html

>
> thanks
> helm
>
>
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
> message news:eey5EwxpEHA.1688@TK2MSFTNGP10.phx.gbl...
>> Matt Helm wrote:
>>> Okie... Well maybe you can point me in the right direction than if
>>> you would please.
>>>
>>> I have about 20 pc's on this network. Two are windows 2003 servers.
>>> One is acting as a application server and the other is a file
>>> server. I have a spare box that I'm going to go ahead and setup as
>>> a domain controller with Active Directory.
>>>
>>> Is there some tutorial or best practices or whatever that would kind
>>> of step by step show me how to move my network to a domain
>>> configuration?
>>
>> Not sure where to point you at on the internet, although the
>> newsgroups are
>> a great place to ask specific questions - but I'd pick up some books
>> first &
>> get reading.
>>
>> Q - have you already bought another license for Windows server &
>> Exchange? If not, I must repeat my SBS recommendation (unless you
>> think your network will soon outgrow the 75-user limit or you
>> require Exchange Enterprise edition).
>>>
>>> Thanks
>>> helm
>>>
>>>
>>> "Lanwench [MVP - Exchange]"
>>> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
>>> message news:uXwoJfxpEHA.3396@tk2msftngp13.phx.gbl...
>>>> anonymous@discussions.microsoft.com wrote:
>>>>>> If you haven't got a lot of experience
>>>>>> setting up stuff like this, it might behoove you to get a good
>>>>>> consultant in to do the setup for you.
>>>>>
>>>>>
>>>>> AHAHHA... Than I couldn't bug you guys with all my newbie
>>>>> questions! =)
>>>>
>>>> Sure you could. Happens all the time. <g>
>>>> Just remember, it takes very little work to maintain a properly
>>>> setup network environment. It takes a LOT of work to fix problems
>>>> in one that wasn't set up right to begin with.

Matt
Fri Oct 01 07:20:56 CDT 2004

Thanks for the INFO!

helm


>-----Original Message-----
>Matt Helm wrote:
>> I have the Win2k 2003 license.. dont have the exchange
one yet. I'm
>> going to look into using SBS. Will there be any
limitation with
>> features?
>
>You can't use Exchange Enterprise, or Win2003 Advanced
Server, or set up
>trusts to other domains. You can't have more than 75
users. You can't
>install its bundled components to other servers. You
can't run terminal
>services on it for users (although you can use remote
desktop/admin mode for
>remote admin). It has to hold all the FSMO roles in AD,
but you can add
>additional DCs. You can't run SBS as a member server
(but of course, what
>would be the point of buying it if that's what you
wanted?)
>
>> I'll be able to use OWA?
>
>Yep. Also, there's a feature called Remote Web Workplace
for remote desktop
>access to any Windows XP Pro workstations on your
network.... see
>http://www.winnetmag.com/SQLServer/Article/ArticleID/4075
7/SQLServer_40757.html
>
>>
>> thanks
>> helm
>>
>>
>>
>> "Lanwench [MVP - Exchange]"
>>
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com
> wrote in
>> message news:eey5EwxpEHA.1688@TK2MSFTNGP10.phx.gbl...
>>> Matt Helm wrote:
>>>> Okie... Well maybe you can point me in the right
direction than if
>>>> you would please.
>>>>
>>>> I have about 20 pc's on this network. Two are
windows 2003 servers.
>>>> One is acting as a application server and the other
is a file
>>>> server. I have a spare box that I'm going to go
ahead and setup as
>>>> a domain controller with Active Directory.
>>>>
>>>> Is there some tutorial or best practices or whatever
that would kind
>>>> of step by step show me how to move my network to a
domain
>>>> configuration?
>>>
>>> Not sure where to point you at on the internet,
although the
>>> newsgroups are
>>> a great place to ask specific questions - but I'd
pick up some books
>>> first &
>>> get reading.
>>>
>>> Q - have you already bought another license for
Windows server &
>>> Exchange? If not, I must repeat my SBS recommendation
(unless you
>>> think your network will soon outgrow the 75-user
limit or you
>>> require Exchange Enterprise edition).
>>>>
>>>> Thanks
>>>> helm
>>>>
>>>>
>>>> "Lanwench [MVP - Exchange]"
>>>>
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com
> wrote in
>>>> message news:uXwoJfxpEHA.3396@tk2msftngp13.phx.gbl...
>>>>> anonymous@discussions.microsoft.com wrote:
>>>>>>> If you haven't got a lot of experience
>>>>>>> setting up stuff like this, it might behoove you
to get a good
>>>>>>> consultant in to do the setup for you.
>>>>>>
>>>>>>
>>>>>> AHAHHA... Than I couldn't bug you guys with all my
newbie
>>>>>> questions! =)
>>>>>
>>>>> Sure you could. Happens all the time. <g>
>>>>> Just remember, it takes very little work to
maintain a properly
>>>>> setup network environment. It takes a LOT of work
to fix problems
>>>>> in one that wasn't set up right to begin with.
>
>
>
>.
>