For anyone who has been following my posts on upgrading my Win2000 AD to Win2003, looks like we should be good to go. We did a test upgrade on our virtual AD domains (on our ESX cluster) twice, and both times the upgrade succeeded successfully. We even tested running GPOs on the newly upgraded domain, and that went fine - login scripts mapped drives, etc, fine.
So I think we're close to ready. Last step - a plan to rollback the upgrade, if it all goes to hades in a handbasket ... My configuration: parent/child domain. 4 parent DCs (3 physical, 1 VM). 3 child DCs (2 physical, 1 VM) on site, and another 3 in other sites (both physical sites, and AD defined sites). So what should our recovery plan be, if the upgrade doesn't work, for some unforseen reason? Will I have to do an AD restore, from a full backup created prior to the upgrade? How exactly would that work - would we decide that everything is hosed, and then .. what? Run an AD restore on one of the DCs? Which one? etc I've never had to do an AD restore like that, just a D/R restore by restoring the virtual DC and seizing roles. Any advice, or links to a description from someone who has had to unfortunately do it, would be most appreciated. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
