OK, it wasn't an external article, so I can't share the entire thing. I wrote
it for a very specific customer.
That being said, here is the general overview for AD/server/DNS
Restore an Active Directory server
This could take a white paper into and of itself. That being said:
1] Have a customer take a system state backup of an AD server
2] Find out the PRECISE VERSION AND SKU of the Windows Edition (Standard,
Enterprise, DataCenter; what SP; Retail, FPP, MSDN, Select, EA, VLK, Open,
etc.; and the disk layout of same); make sure that you have a valid Domain
Admin account in that system state backup
3] Build a VM to those same specs, same server name, and leave it in
workgroup mode
4] Restore the system-state backup
5] Perform a repair reinstall of Windows
6] Install DNS if necessary and update IP addresses, network config,
etc.
7] Use BURFLAGS (KB 290762) so that the recovery DC is the FRS master
8] Do a metadata cleanup (KB 216498) so that the recovery DC is the only DC
left in the AD
9] Seize all FSMO roles
10] Clean up DNS so that the recovery DC is the only DC left in the DNS
There is (duh!) more involved if you are interested in other applications, such
as Exchange, SharePoint, SQL, etc. etc.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Michael B. Smith [mailto:[email protected]]
Sent: Tuesday, May 03, 2011 6:02 PM
To: NT System Admin Issues
Subject: RE: Full metal restore 2003 R2
What you need is a matching product code (not product id).
http://www.tacktech.com/display.cfm?ttid=387
This gets complicated because you can "upgrade" Windows Server 2003 RTM and SP1
to R2.
In that case, if you are doing a bare metal restore, you have to go through the
same process.
I greatly prefer disk images.
I wrote an article about this once, I think; I'll hunt for it.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: David Lum [mailto:[email protected]]
Sent: Tuesday, May 03, 2011 5:50 PM
To: NT System Admin Issues
Subject: FW: Full metal restore 2003 R2
>From a fellow SE...
From: Kris Laib
Sent: Tuesday, May 03, 2011 2:49 PM
To: David Lum; Jen Sells; Ed Quinn
Subject: RE: Full metal restore 2003 R2
Are they file-by-file identical? If not, I think we still need to know which
boxes are R2.. For instance, it shows XP x64 as 5.2 also, but I bet it has
a different splash screen ;) (and who knows what else).
From: Crawford, Scott [mailto:****]
Sent: Tuesday, May 03, 2011 2:40 PM
To: NT System Admin Issues
Subject: RE: Full metal restore 2003 R2
Yeah, Disc 1 of 2003R2 is 2003 SP1. All of the R2 stuff is on disc 2
From: David Lum [mailto:[email protected]]
Sent: Tuesday, May 03, 2011 4:38 PM
To: NT System Admin Issues
Subject: Full metal restore 2003 R2
Doing some OS auditing for full metal restore prep, I am not getting anything
(Joeware.net wools, SMS) that is returning 2003 R2 - I get 2003 Std and
Enterprise, 32 and 64-bit, and 2K8 and 2K8 R2.
For a full metal restore where you need the OS disk of the same version of what
you're restoring, does it matter if it's 2K3 or 2K3 R2? Is R2 more of a
feature-set than a code base change?
David Lum
Systems Engineer // NWEATM
Office 503.548.5229 // Mobile 503.267.9764
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin
