Thank you everyone, going to put my comments and answers all in the same email.
I have our restart procedure down pat. This is being done because of HVAC/Elec issues. I have had a ton of practice. No one will be active at the remote sites. So I will take them down. Public DNS is offsite, but good point. I didn't think of that. My drives should be ok considering all the weak ones have been replaced over the last six months...see above on HVAC/Elec issues. :) But my backups are solid, tested and duplicated to a remote location. From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Thursday, July 18, 2013 11:38 AM To: [email protected] Subject: [NTSysADM] Week long shutdown. We are shutting our data center down for 7 days to repair the HAVAC/Electrical systems. Long story but it needs to be done this way. Since we are a school district and it is summer we are just going to pull the plug on the network and let that summer staff fend for themselves. I have a secondary MX up with a hold and forward. There are 4 offsite DC's that could be left running, but they will not be able to talk to each other, their connectivity is via the data center. I am thinking shut them down too. Any issues or concerns that come to mind for a week long downtime for AD?
