Andrew and I are attending the Ignite Technical Airlift today and tomorrow, whilst Tony is off amusing himself in other ways (Tony, it’s up to you to post on what you’ve been doing – or you can choose to let our massive audience make up their own minds).
The Airlift is a general overview of the 2010 EPM suite. The first thing we were told was we couldn’t talk about what we heard here until the official launch on Wed of this week.
So, since the Airlift has turned into Fight Club, perhaps we can creatively allude to some of the cool stuff.
First, let’s say that there is some cool stuff. There have been a few oohs and ahhs from the group of seasoned EPM consultants in the room, and we are group not easily impressed.
I think we can get away with saying that Project Server 2010 is not a complete rewrite. As you will recall, MOPS 2007 was a complete rewrite – new architecture, new databases, new communication between client and server. A lot of new. A lot that needed to be done. But a lot of opportunity for, well, trouble.
The new version of Project Server is based on the fundamental architecture of MOPS 2007. To me, that’s good news. Big changes scare me, especially big base-level changes. There aren’t many big base-level changes here.
Beyond that, Microsoft has already announced publicly that Project Server 2010 will be dependent on Microsoft SharePoint Server 2010 Enterprise version. No more installations on WSS.
You’ll need 64-bit Windows Server 2008 on your app servers and WFEs. You’ll need 64-bit SQL. And you’ll need gobs of memory to take advantage of the 64-bit servers.
There are some significant changes to Project on the desktop, both in Pro and Standard. There are significant changes in PWA. Many of you will like them. Some of you will not, at least not at first.
To say any more at this point will risk letting the cat out of the proverbial bag, which we certainly want to avoid. Instead, we’ll start cooking up blog posts over the next few days, and stage them to post on Wed.