RE: Windows 2003 Active Directory
- From: "William Lefkovics" <william@xxxxxxxxxxxxxxxxx>
- To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
- Date: Tue, 8 Mar 2005 22:11:14 -0800
That is a reasonable business assessed risk.
I always want to have at least 2 Domain Controllers even for the smallest
non-SBS shops, both of which should be global catalog servers (which
provides for Exchange/Outlook to use secondary).
Hardware faults can cause software corruption.
I don't want rebooting a DC (service pack, patches) to cause email users to
have to wait.
-----Original Message-----
From: adrian bolzan [mailto:abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, March 08, 2005 10:03 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Windows 2003 Active Directory
http://www.MSExchange.org/
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
Other related posts:
