Unless you have been living in a cave you will have heard that next month sees the virtual launch of Office 2010. Details of the virtual launch and other availability stuff at http://blogs.msdn.com/chrisfie/archive/2010/04/28/microsoft-project-server-2010-availability-on-msdn-and-technet-subscribers-download-it-s-coming.aspx but I thought I’d take a few minutes to prepare the scene. I know you will all read the wealth of documentation we have up on the TechNet Project Server 2010 TechCenter http://technet.microsoft.com/en-us/projectserver/default.aspx but sometimes our customers can get imaginative and read more into what we don’t say that what we do. “I know TechNet says that apples are apples, but it doesn’t say that apples are not bananas!”
So to cover off the things that have caught some of our internal folks and early adopters out;
Apples are not bananas. Full details of the requirements can be found at http://technet.microsoft.com/en-us/library/ee683978(office.14).aspx and there is also a great webcast detailing upgrade and migration at http://www.microsoft.com/events/series/epm.aspx?tab=Webcasts&seriesid=51&webcastid=12840
Please note the SQL Server requirements particularly:
So start getting your servers or HyperV images prepared and above all – enjoy! Project Server 2010 is an awesome product, and that is a word I do not use lightly!
just to clarify one specific point in this article, related to SQL2008 R2 - are you saying that if you are running your 2010 farm against a single SQL server/cluster, you have to have 2 instances of Analysis Services if you plan to use both Project Server 2010 OLAP Cubes AND PowerPivot ? (due to different modes etc.)
Great point David - and yes, but not quite. the PowerPivot AS instance I am referring to is the one that gets installed to the SharePoint Server (so not a good place to have your Project data - and I'd even say Project Server and PowerPivot for SharePoint should be muutally excusive...
I stole the following from http://blogs.msdn.com/powerpivot/archive/2010/03/22/powerpivot-component-architecture.aspx in the PowerPivot for SharePoint
· Analysis Services Service Loads the VertiPaq engine to manage the data within PowerPivot workbooks retrieved from SharePoint content databases. The PowerPivot system service extracts the database from the Excel workbook, selects an appropriate SharePoint application server, which runs the Analysis Services service as well as an instance of the PowerPivot system service, and then attaches the database to the Analysis Services instance without requiring Excel 2010 on the server.
Note: On a SharePoint server, an Analysis Services instance can only load VertiPaq databases for in-memory BI processing. Analysis Services in VertiPaq mode does not support traditional OLAP processing modes. Although it is possible to install additional Analysis Services instances on the same server to support traditional OLAP processing, Microsoft does not recommend this configuration because of the differences in workload patterns and resource consumption.
We are in the planning stages of migration and I was wondering about the linkage to Exchange because we will not be upgrading our Exchange environment until the end of 2010. I would like to put up a Project Server 2010 environment before that so I can have plenty of time to build out the information and templates needed for the new proposal functionality to create and select projects. Can the connection to Exchange be added after an initial deployment, or is that something that has to be part of the installation?
Great question. The link to Exchange can easily be activated later. The code will be deployed when you install Project Server 2010 but does not get turned on automatically. There is a setting in Server Settings to switch the link on (once you have made the permission settings in Exchange - see TechNet article) and then another setting for each resource whose tasks you wish to sync. The article at http://technet.microsoft.com/en-us/library/ff468700(office.14).aspx.