Firstly I would like to say thanks for all the help. I probably wasnt as clear
in my original description about a few things as I could have been so I will go
over the assumptions some of you made that were incorrect.
Ok so from my notes..
--
Existing Environment
The existing
If I were you, rather than put Exchange on a DC, I would put the second DC
on an older but still robust workstation (and beefed up to boot). A long
way from Best Practices, but still preferable to the Taboo Mix.
- Original Message -
From: Steven Johnston [EMAIL PROTECTED]
To:
Hello list,
(Skip the first Paragraph if your in a rush :p It is a
self introduction.)
This is my first post so I would like to introduce myself
and say hello to everyone and thanks for the bucket loads of good info floating
around. I am relatively new to the industry and this is my
Hello Steven,
why not choosing another god's name ? :)
After all, this is just a name !
Since you can dcpromo down the server, it should be ok.
Just be sure to remove replicate link and it's computer object from ADUC...Cleaning DNS
my 2 cents,
Mathieu CHATEAU
Friday, August 18, 2006,
Welcome to the list Steven! Buckle up and
enjoy the ride!
Im sure the gurus on this list can provide
more detailed replies, but there are 2 things I would stay away from (in the
real world):
1- Installing/Running Exchange on a DC (unless its a SBS)
2- Renaming a DC with a name
So let me get this straight:
Ceres AD only
Hades AD Exchange
Server3 Nothing
Your next state is:
Ceres AD Only
Hades AD Exchange
Server3 Exchange
Your next state is:
Ceres AD Only
Hades AD Only
Server3 Exchange
You then want to rebuild Hades and make it a
The only real requirement is to ensure the
dcpromo action to remove the DC functions is fully replicated to each DC in the
forest before you think about adding it back. In large environments (hundreds or
thousands of DCs) I recommend dont re-promote a name within the
tombstone lifetime J
Welcome.
To answer your general question, I don't have a problem
with reusing names. Just make sure things got cleaned up properly previously.
Previous environment I was inevery name of the 350+ DCs over the years was
reused at least once since 2000. Mostly a threeyear rollover on
Oh yeah, Exchange on DCs sucks... Even on SBS, but they
have to put up with it. ;o)
--
O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven
JohnstonSent: Friday, August 18, 2006 3:30 PMTo:
In your case I
would:
* execute from the E2K3 media: SETUP
/FORESTPREP (this preps your forest for E2K3 servers) (this will resolve the
incorrect attributes in a W2K AD with E2K)
* execute from the E2K3 media: SETUP
/DOMAINPREP (this preps yourdomain for E2K3 servers)
* execute from
I wouldnt make that generalization. The bigger issue I have in
large enterprises is that folks hardcode names into their crappy applications.
When you change a name you break their app (which is fine by me), but, in
general I try to avoid this by recycling names. It gets confusing when you
11 matches
Mail list logo
