RE: Windows 2003 Active Directory
- From: "adrian bolzan" <abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Wed, 9 Mar 2005 17:02:50 +1100
Hi Peter,
I agree that two DC's would be better than one, however, that is not
really an option- i.e. another AUD$1100 for a Windows server license
just to have another DC.
We are not a big shop so I am hoping that one DC will be enough, at
least until my next budget period.
Again, hardware faults aside, I assume that Windows 2003 is stable
enough not to fail.
Cheers,
Adrian
> -----Original Message-----
> From: Exchange [mailto:Exchange@xxxxxxxxxxxxxxxxxxxxx]
> Sent: Tuesday, 8 March 2005 9:48 PM
> To: [ExchangeList]
> Subject: [exchangelist] RE: Windows 2003 Active Directory
>
> http://www.MSExchange.org/
>
> Obviously Exchange should not be on a DC but would it not be
> useful to have a second DC in case the first DC get corrupted
> or fails?
>
> Peter
>
> > -----Original Message-----
> > From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx]
> > Sent: Tuesday 8 March 2005 06:09
> > To: [ExchangeList]
> > Subject: [exchangelist] RE: Windows 2003 Active Directory
> >
> > http://www.MSExchange.org/
> >
> > > Do not fear, you are not the bearer of bad news.
> > > I have read docs (and will re-read, anyway) and queried
> > this list, as
> > > well.
> > > We have two DC's, one hosting exchange. The plan is to:
> > > - Build another Exchange server (Exchange2) as a member server
> > > - move mailboxes to the new server (Exchange2)
> > > - uninstall Exchange from the DC
> > >
> > > - demote the DC to a member server
> > > - install exchange again on this server
> > > - move mailboxes back to the newly installed exchange
> > > - decommission the temporary Exchange server (Exchange2)
> > >
> > > This leaves us with only one DC but we only have about 100 staff
> > > accessing this DC.
> > >
> > >
> > > Hopefully this will be a relatively smooth transition.
> >
> > Ah, it is so nice and refreshing to see that some one has
> done their
> > homework.
> >
> > :))
> >
> > I might go 3 steps further: After demoting, remove from domain,
> > rebuild with new name, join to domain, then install Exchange. Yes,
> > that adds about 4-5 hours to the job, but that way you can
> avoid weird
> > errors that MAY (not
> > will) arise down the road. I would have to say these would
> be optional
> > steps that if you have the time would be nice to add.
> >
> > John Tolmachoff
> > Engineer/Consultant/Owner
> > eServices For You
>
> ------------------------------------------------------
> 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:
> World of Windows Networking: http://www.windowsnetworking.com
> 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
> ------------------------------------------------------
> You are currently subscribed to this MSEXchange.org
> Discussion List as: abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx To
> unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
============================================================
IMPORTANT - This email and any attachments is confidential.
If received in error, please contact the sender and delete
all copies of this email. Please note that any use,
dissemination, further distribution or reproduction of this
message in any form is strictly prohibited. Before opening or
using attachments, check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused
by the negligence of the sender or not, resulting directly or
indirectly from the use of any attached files, our liability
is limited to resupplying any affected attachments.
Any representations or opinions expressed in this email are
those of the individual sender, and not necessarily those
of the Capital Transport Group.
============================================================
Other related posts:
