You can rename the computer account in AD even if the computer is no longer on the network IIRC. Now you need to be careful in how you bring the original server back online in your 'test disaster' but it's just about getting the steps right.
We spent a bunch of time coding various permutations of pear shaped scenarios requiring for DR, but in a scripted test scenario it's much more straightforward. -- Chris Scharff Messaging Services Architect MessageOne [o] 512.652.4500 x244 [m] 512.560.2984 [f] 512.652.4504 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of East, Bill > Posted At: Friday, January 14, 2005 2:54 PM > Posted To: swynk > Conversation: Testing Disaster Recovery > Subject: RE: Testing Disaster Recovery > > > We did not. In this scenario the original machine was in the > middle of a smoking, slightly radioactive crater. > > -- > be - MOS > > This is the kind of tool set professionals use. Not > only is it inexpensive, but it also has a great safety > feature not found in the so-called quality tools sets: The > handle will actually break right off if you accidentally hit > yourself or anything else, or expose it to direct sunlight. > -- Dave Barry, "The Taming of the Screw" > > > > -----Original Message----- > > From: Chris Scharff [mailto:[EMAIL PROTECTED] > > Sent: Friday, January 14, 2005 2:50 PM > > To: Exchange Discussions > > Subject: RE: Testing Disaster Recovery > > > > Did you rename the original machine (the one being replaced > in this DR > > scenario)? > > > > -- > > Chris Scharff > > Messaging Services Architect > > MessageOne > > [o] 512.652.4500 x244 > > [m] 512.560.2984 > > [f] 512.652.4504 > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > Behalf Of > > > East, Bill Posted At: Friday, January 14, 2005 1:12 PM Posted To: > > > swynk > > > Conversation: Testing Disaster Recovery > > > Subject: Testing Disaster Recovery > > > > > > > > > We just completed our annual DR testing. This was the > first year in > > > which we managed to get all of the servers up and running, yay us. > > > > > > One of the things that led to this outcome was the > installation of > > > Exchange 2000 SP3 (not Enterprise) with the /disasterrecovery > > > switch. In short, we: > > > * Built a new server with the old server's name, service > packed and > > > install the ArghServe client > > > * Ran exchange setup with the aforementioned switch > > > * Ran ArghServe to put the databases back. > > > > > > The only funny thing that happened was after we did the > restore. We > > > rebooted and the server refused to go through the Windows > startup. > > > We identified this as a SID problem, removed the server > from the DC, > > > took it off the network and put it into Workgroup mode, > then put it > > > back on the network and rejoined it to the domain. At > that point we > > > had to re-add it to about half a dozen domain groups. > > > > > > So my question would be, what steps could we have taken to avoid > > > this little dance, if any? It would save us an hour or so > in our DR > > > plan if we could. > > > > > > -- > > > be - MOS > > > > > > Fry: I must be a robot. Why else would human women refuse > > to date me? > > > Leela: Oh, lots of reasons. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
