May 18, 2010

Interesting Google Apps / Exchange Online Post

Curses. Comments are disabled on the blog due to the platform migration. I'll ask my questions when they come back online but in the meantime, here's my thoughts and what I don't understand because it hasn't been explained.

The company made the decision last year to go with Google Apps. All well and good. Despite being an Exchange MVP I don't, today, have a horse in that race because I also work for a storage vendor who stands to make a very tidy sum from people outsourcing services to the cloud.

Now the company has made the decision to go with Exchange Online services.

Holy heck Batman. After a year? Lemme take a look and see what's going on. At first I thought that Google trumpeted a sale rather than an agreement to do a trial. Nope. The company pulled the trigger and said as much.

1. June 11 2009 the Senior Manager of Global IT and his sysadmin posted on Google.
2. May 18 2010 the Director of IT posted via the Technet, Online Services blog.
Ahh, interesting. A power play?

An on-premise Exchange environment for 800 people will not cost you a million dollars. There's the first indication of something fishy going on numerically.

25GB of mailbox space? No. You don't get 25GB each. You get storage. You get told that you have 25GB each. If you go and look you're not going to see a 1:1 capacity correlation between 25GB and users.

But hang on, all that went before was nit picking at tactical points. The real question is what changed in the 11 months between Google Apps coming in and Office 2010 coming in. What were the business requirements in June 2009 and what are those utterly new business requirements in May 2010? Can you, in the business that the company is in, have such a radical change in business requirements over the course of 11 months that caused them to throw Google Apps out and put Office, and Office 2010 at that, on the desktops all over again.

I am genuinely flummoxed at this. Personally I think it's the right solution because the feature-rich messaging client is backed up by a comprehensive back end. But I go back to the original point. What the heck changed in a year? Can you even operate it for long enough before you decide it's not for you and then make the plans to migrate to something new. Can you even plan and execute that migration in, say, 6 to 9 months?

There's way more to this than meets the eye and it's fascinating to me, geek that I am.

0 comments: