RE: Questions before diving in.
- From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
- To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
- Date: Fri, 5 Dec 2003 09:08:46 -0500
I think clarification is needed.
You must have an Active Directory forest/domain to install Exchange 200x
into. Once there, you won't be able to move it to another forest. Since a
lot of the information is at the forest level, you will have to extend the
schema to get it to work. That's an irreversible change to the Active
Directory and you should fully understand the implicataions prior to
deployment (it's not that big a deal, but it needs to be understood).
If you so choose, you could deploy on a single server running Active
Directory, DNS, and Exchange and be fine. You just won't be able to move it
later. Putting a machine in the Active Directory can be done without users
using it and without sending email to it so you could still achieve your
goal of a "burn-in" period prior to putting users on it. That's quite
common unless this is a 5.5 upgrade. Then it's a little more involved, but
could still be done this way.
Better docs? What did you have in mind?
-----Original Message-----
From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx]
Sent: Friday, December 05, 2003 1:46 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Questions before diving in.
http://www.MSExchange.org/
There is more involved than changing DNS. If you intention is to use
Exchange for mailboxes, not associated with users in a domain, yes you can
do that.
But if your intent is to use Exchange like it is meant to be used, it must
be installed in the domain from the get go to avoid problems.
John Tolmachoff
Engineer/Consultant/Owner
eServices For You
> -----Original Message-----
> From: Chris Rollison [mailto:crollison@xxxxxxxxxxxxxxxxxxx]
> Sent: Thursday, December 04, 2003 8:06 PM
> To: [ExchangeList]
> Subject: [exchangelist] Questions before diving in.
>
> http://www.MSExchange.org/
>
> I have a couple of questions before I fully dive into Exchange. I
> started to setup the trial software on a test server, I didn't get
> very far. I tried using the deployment guide, but I still ran into
> problems. One thing before I go too far, is it possible to setup
> exchange on a machine as a test server then move it into use when I feel
comfortable with it.
> This would pretty much mean changing the dns, wouldn't it? I know
> this is possible, but not very well documented.
>
> The other question is, is there any better step by step guides out
> there on setting up, other than the deployment guide? I run a small
> network for a k-12 school district and we only have about 450
> computers and will probably only have around 100 accounts on the
> exchange box. Most of the deployment guide seemed to focus more on large
corporate use.
>
> Thanks for any help.
>
> ------------------------------------------------------
> List Archives:
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> Leading Network Software Directory: http://www.serverfiles.com
> No.1 ISA Server Resource Site: http://www.isaserver.org Windows
> Security Resource Site: http://www.windowsecurity.com/ Network
> Security Library: http://www.secinf.net/ Windows 2000/NT Fax
> Solutions: http://www.ntfaxfaq.com
> ------------------------------------------------------
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
Other related posts:
