imaging Domain Controllers in a multi-Domain Controller environment
- From: "Cary W. Shultz" <cshultz@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Jan 2008 13:54:34 -0500
Good afternoon!
Can you all please tell me:
1) why this is a bad idea (in terms of recovery)?
2) what is a better idea (in terms of recovery)?
Furthermore, let's assume that at least one of the domain controllers is
also the Exchange 2003/Exchange 2007 server.
Furthermore, let's assume that there are often multiple sites (in Active
Directory Sites and Services) in the environment..
Furthermore, let's assume that at least one of the DCs is a File Server.
Please, oh, please .... someone mention USN in the long list of reasons why
this is a bad idea. But, forget that you just read this. I would not want
to accused of bribery! ;-) And, forget that I mentioned "long list of
reasons why this is a bad idea". I would not want to be leading anyone...
Now, what to do if imaging is *THE* single solution proved by management?
Thanks,
Cary
.
- Follow-Ups:
- Re: imaging Domain Controllers in a multi-Domain Controller environment
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: imaging Domain Controllers in a multi-Domain Controller environment
- From: Jorge Silva
- Re: imaging Domain Controllers in a multi-Domain Controller environment
- Prev by Date: Re: OU Organization
- Next by Date: Re: DCDIAG error
- Previous by thread: Adprep with Windows 2000 Domain - Schema Master issue
- Next by thread: Re: imaging Domain Controllers in a multi-Domain Controller environment
- Index(es):