OK, this was made way too hard on many levels.
1. This is a time for paper
2. We do have prescription pads
3. As soon as your server gives that many warnings, you stop using it and troubleshoot.
He has a hardware RAID.
@Jon, What we are trying to say is a client/server domain is not some magical and difficult concoction of computers. I have on two occasions in five years, simply turned off the server, restored AC on a pre-designated computer that has SQL, redirected the other computers and NEVER had a port problem. But, (and I make these rules up), but never look for the port -- turn off the firewalls). I have never had to open port 61067 which is also on the AC website. Most programs open ports by themselves. If not, use the exception on AC first if you don't know the port.
It is easy to back up your II onto the designated backup computer.
Here is one huge lesson, although not sure if I can convince everyone of this.
Do what Susan Bradley teaches (Google her) she is the SBS goddess. Seriously, she has Bill Gates' phone number and, more importantly, he has hers. DON'T put antivirus on your server. What? Yes, don't. There is little that goes to your server. Block the SPAM and viruses in the cloud. You have your firewall. All of your clients have antiviruses. Run MBAM and Super-Antispyware manually once per week.
This is especially true if you are using Hyper-V. Then antivirus on the physical server and none on the virtual. Have you ever looked at the list of exclusions for AV software on a server? There are more exclusions than the other way around.
