Working on a project for a customer. Doing an exchange 2003 to 2007 migration and when you open up the exchange 2007 management console you get a bunch of errors that look pretty ominous. They are validation errors that state the path cannot be the root directory!

After looking into it a little deeper it turns out the customers exchange 2003 storage groups, transaction logs, and databases were stored on different drives but were in the root path of those drives.  Apparently Exchange 2007 is not to keen on that.

The following is what it looked like from the Exchange 2003 console.

I guess the moral of the story is I could move the transaction logs, databases, system paths on the 2003 ide to please the 2007 Mgt console….Or I could just ignore ignore it until the 2003 server is retired.  Since all messaging is flowing properly, I choose the latter…

Scott

Paul Robichaux has an awesome article up on windowsitpro http://bit.ly/RmWfS detailing why Microsoft never integrated the two products as has been oft rumored.

Just because something CAN be done, does not mean it necessarily Should!

Scott

Heads up to a great article from Sembee.
http://bit.ly/yFYFK

He is an awesome wealth of knowledge on Exchange. This article discusses common Exchange database myths and facts. I particularly liked the discussion around the stm versus the edb files, and how they get calculated towards database cumulative size. I was completely unaware that as of 2003 sp2 the limit is a soft limit that takes into account white space in the database.

I liked the fact that they state offline defragmentation is really not necessary any longer as proactive maintenance. This has long been a point of discussion with customers and I am glad to see it documented.

Great job Simon.
Scott