I hope you always steel my thunder on having to recover when things go wrong!

When my issues happened, I was in the middle of deploying Windows Server 2003 Service Pack 2 to 30 prod boxes which I had a deadline of 6am Eastern time this morning. A handful of those had failed and needed troubleshooting. I was sweating bullets. Since I had lost my broadband internet connection, I had to fire up the Blackberry tether modem to continue the deployment and troubleshooting which was dog slow. While doing that, I was trying to fix the infrastructure issues so I could get my broadband back. And I had a flight to catch this morning for Hitachi SAN training.

Got it done despite the challenges.

Lesson learned, don’t fool around with infrastructure during work rollout weekends and I have a flight to catch in the morning.

Your morning sounded more frustrating than mine. At least I did not have the pressure of fixing other infrastructure issues like back up exec and AD!

I woke up this morning at 4am to my router, domain controller, and VCMS being down due to Backup Exec placing an exclusive lock on the .vmdk files. I had installed VMware Server 2.0 yesterday and in the process moved the folders where the VMs live. Well I forgot to exclude the new folder from Backup Exec’s backup list. Due to the router being down, my site was down for a few hours. When I cancelled the Backup Exec job and resumed the VMs, of course then their local clocks were all out of whack so Active Directory issues followed. I tell ya, sometimes…

Jas