Exchange doesn’t like drive error, or bad blocks. Never has, never will, and while there are things that can temporarily correct the problem, new hardware is the ultimate solution.

I’ve been slowly prepping to do a migration from Exchange 2007 to Exchange 2010 at the company I work for. I’ve done my reading, come up with all sorts of bad scenarios, and basically anything else I could think of to prepare for it. Mind you, I’m not the only high end internal IT guy (Engineer, support, sales, etc…), but I’m also the only outbound tech. I had things planned out to finish the actual prep the day before a long weekend a few weeks ago, just in case I ran into any problems.

Smart thing I did that, because I ran into a major problem. I had to go to a client site, due to a printer issues. the client is a major one for the company and the directive came at 10pm in the evening from by boss to be out there the next day. This of course caused me to cancel the planned migration.

The day of the cancellation was going to be installing Exchange 2010 on the newly purchased server, and installing the latest version of Blackberry Enterprise server so that we could keep using our Blackberries. Needless to say, a few days after the cancelled migration date, our current Exchange 2007 server starts running really slow. Disk errors, bad blocks, a chkdsk cleared the errors, and I was put on the hot seat.

I explained why the migration had not happened, how I was ordered to be down at a client for a printer problem. How the amount of e-mail data will take 2-3 days to migrate, and that I wanted to do it over a long weekend. I was asked for a hard date for the migration, something soon, since slow or non-working e-mail near the end of the month was not acceptable. So I gave a date of this upcoming weekend, and went to work on getting the domain all prepped.

So here I am trying to run the Schema and AD prep on a domain where the Exchange server is in a separate site (Not domain, just physical site) from the Schema Master. Not only that but the Schema Master is a 2003 server. Yes, following Microsoft’s information of just running the Schema Prep through a 2008 server that is in the site where the schema master is located, has not worked so far.

I know I’ll get it, I dealt with this went tossing SP2 on the Exchange 2007 server, I’m just frustrated that Microsoft doesn’t even know how its own stuff works.