Re: imaging a Domain Controller in a multi-Domain Controller environment

Hello Cary,

I would ask them "Why did you ask me" wenn Du dann trotzdem andere Wege suchst. :-)

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Meinolf...

Problem is that everyone in my company calls me for AD
issues....(sometimes I am not so sure that this is a good idea!).

Anyway, noch Mal vielen Dank!

Hey, we sure did a good job of Eingedeutsching this post!!!!!

I lived in Germany for three+ years after I graduated from University
(20 years ago) and have simply not forgotten it! I guess that I
really learned it. So, hope that you do not mind that I "practised" a
little bit.

Thanks again for your post. You are correct...has everything that we
need.

Cary

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66a404a8cab6f5f8f3084c@xxxxxxxxxxxxxxxxxxxxxxx

Hello Cary,

Enthält alles was Du brauchst. Wenn er es nicht verstehen will.....
He can also find a lot of help himself on the web for his self
created problems. :-)

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Meinolf,

Genau das, was ich brauchte. Obwohl ich meinem Kollegen das schon
gezeigt habe.....;-)

Anyway, thanks for the links. I will show him them (again!).

Cary

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66a40378cab6f17c2cba8c@xxxxxxxxxxxxxxxxxxxxxxx

Hello Cary,

See inline.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Good morning!!!!

Hey, we have a client that has two Domain Controllers (both
running Windows Server 2003 SP2, not that this really matters
here).

On one of the Domain Controllers there is a small possibility that
we will have to do some "hardware" work that might result in a
wipe and load situation. Now, this particular DC is currently
just sitting there for redundancy. In a month it will be doing
several things (yes, Exchange 2007 will be one of those 'several
things'......yes, I know! I know!....do not put Exchange on a
Domain Controller....believe me, I know!!!!)

Anyway, my colleague is stating that before we do the hardware
work (RAID Controller...if you need to know) we should image the
machine (we use Acronis True ImageServer). I have suggested that
- if we are going to do that - then we should run dcpromo on the
machine, reboot and then image the machine. He suggests that the
machine will only be off-line for an hour - tops! So, no need to
do this. No need to worry about all of the things that I have told
him will go wrong.

I have suggested to him that if he does this that I am not going
to help him to resolve everything (which will be a whole lot more
fun once Exchange 2007 is put on this machine).

Can someone please explain to "me" why imaging a Domain Controller
in a multi-Domain Controller environment is - regardless of how
short or how long the DC is off-line - a horrible horrible
horrible idea?

Think this gives an overview:
http://support.microsoft.com/kb/875495
Furthermore, can someone please explain to "me" that MS will not
support a Domain Controller that has been imaged?

Go to "Software and methodologies that cause USN rollbacks"
http://support.microsoft.com/kb/875495

Additionally, can someone please explain to "me" why - if we are
going to do this for the sake of saving time - that it would be a
really good idea to run dcpromo on that machine FIRST and to then
image it and THEN to do the work on the RAID Controller?

http://support.microsoft.com/kb/875495

Finally, can someone please explaing to "me" all that fun that "I"
will have resolving all the issues that will pop up if we do what
my colleague is suggesting. Also, could you please explain to
"me" what those issues are?

Like before the USN rollback, that will mostly ending with a
demotion/promotion. Especially if this DC is only a redundancy DC,
i would also strongly recommend to demote it before. Will take some
minutes in a small environment and is really quick again a DC.

Thanks,

Cary



.

Relevant Pages

  • Re: Install Windows Patch via GPO
    ... Best regards ... Meinolf Weber ... Disclaimer: This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.group_policy)
  • Re: Install Windows Patch via GPO
    ... Best regards ... Disclaimer: This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.group_policy)
  • Re: Failing DC
    ... Best regards ... Meinolf Weber ... Disclaimer: This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Failing DC
    ... Best regards ... Meinolf Weber ... Disclaimer: This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Thanks
    ... Best regards ... Disclaimer: This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.server.general)