To get the new look and feel of Project Server 2010, we need to follow the steps given below;

At the time of attaching a content database to Project Server 2010 we need to add a switch in “stsadm –o addcontentdb” command;

“–preserveolduserexperience false”

The whole command looks like;

stsdm -o addcontentdb -url https://PWA:80 -databasename contentdatabasename -databaseserver SQLservername -preserveolduserexperience false

PWA: Name of Project Web App

80: Port number of PWA.

If the environment has already been migrated and if we would like to get the 2010 look and feel, we need to follow below given step for each and every project workspace site.

Open the affected workspace with system account.

Click on Site Actions –> Visual upgrade.

The site(s) will have new 2010 look and feel.

Server Rollup Packages:

• Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): June 29, 2010 https://support.microsoft.com/kb/983311
• Description of the Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package): June 29, 2010 https://support.microsoft.com/kb/983310/

Individual Product Packages:

• Description of the SharePoint Server 2007 hotfix package (sts-x-none.msp): June 29, 2010 https://support.microsoft.com/kb/983307
• Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp; Pjsrvwfe-x-none.msp): June 29, 2010 https://support.microsoft.com/kb/983312
• Description of the Office Project 2007 hotfix package (project-x-none.msp): June 29, 2010 https://support.microsoft.com/kb/2028571

The Server CU is released in two different versions.  The first version is in Individual Packages specific to a particular product like WSS and Project Server.  These are smaller downloads but they do not include language packs or patches for other products so patches for those products would have to be downloaded and installed separately. 

The second version is the Server Rollup Packages.  This is a set of two rollup packages which contains all the fixes for WSS, Project Server and MOSS.  These packages should be used when MOSS is part of the deployment and/or you have language packs installed.  The Server Rollup Packages are much larger (~200MB each) but they will greatly simplify MOSS patch deployment.

The article below provides information on how to deploy the Project Server Cumulative Update.

• Deploy cumulative updates (Project Server 2007)  https://technet.microsoft.com/en-us/library/dd239177.aspx

Where customer has three exchange CAS servers (two Exchange 2010 servers and one exchange 2007 server)

We followed   Configure Project Server 2010 to work with Exchange Server 2010 and Configure Project Server 2010 to work with Exchange Server 2007 R2

But still we were getting following Impersonation errors in event log.

PSError: GeneralExchangeSyncError (40500) System.Web.Services.Protocols.SoapException: The account does not have permission to impersonate the requested user.

After deep drill we understand due to new RBAC concept in exchange server 2010, first we need to use the New-ManagementRoleAssignment Exchange Management Shell cmdlet to assign the ApplicationImpersonation role to users in the organization. (Only in the case of Exchange 2010)

To configure Exchange Impersonation for all users in an organization

New-ManagementRoleAssignment -Name:impersonationAssignmentName -Role:ApplicationImpersonation -User:serviceAccount

To configure Exchange Impersonation for specific users or groups of users

New-ManagementScope -Name:scopeName -RecipientRestrictionFilter:recipientFilter

1. Run the New-ManagementRoleAssignment cmdlet to add the permission to impersonate the members of the specified scope. The following example shows how to configure Exchange Impersonation to enable a service account to impersonate all users in a scope.

New-ManagementRoleAssignment -Name:impersonationAssignmentName -Role:ApplicationImpersonation -User:serviceAccount -CustomRecipientWriteScope:scopeName

The RecipientRestrictionFilter parameter of the New-ManagementScope cmdlet defines the members of the scope. You can use properties of the Identity object to create the filter. The following example is a filter that restricts the result to a single user with the user name "John."

Name -eq 'John'

Taken from Configuring Exchange Impersonation

Once it is done then we followed our Configure Project Server 2010 to work with Exchange Server 2010 article BUT  according to above document

At the prompt, type the following command:

Add-ADPermission -Identity (get-exchangeserver).DistinguishedName -User (Get-User -Identity <AppPoolAccount> | select-object).identity -extendedRights ms-Exch-EPI-Impersonation

<AppPoolAccount> is the application pool account for the Project Server service application noted in the previous procedure.

This would probably work fine in an environment with one Exchange server, but in the event you have more than one Exchange server the “Get-ExchangeServer” cmdlet would return an array of servers, causing the command to fail with “Cannot bind argument to parameter ‘Identity’ because it is null.”

To fix this the command will have to be run against every server running the Client Access Role. One way of doing this is to use the following PowerShell commands in the EMS:

$CAS = get-exchangeserver | where { $_.ServerRole -match "ClientAccess" }

$CAS | foreach-object {Add-ADPermission -Identity $_.DistinguishedName -User (Get-User -Identity DOMAIN\AppPoolAccount | select-object).identity -extendedRights ms-Exch-EPI-Impersonation}

Then we executed second command to configure exchange user

At the prompt, type the following command:

Add-ADPermission -Identity "<ProjUser>" -User <FarmAdministrator> -extendedRights ms-Exch-EPI-May-Impersonate

<ProjUser> is the name of the Project Server user whom you are configuring, and <FarmAdministrator> is the SharePoint Server farm administrator account.

Then we are successfully able to integrate Project Server 2010 with Exchange Server 2010/2007 without any errors and we are able to pull tasks in Outlook and update the assignments from Outlook to Project Server 2010

So in a nutshell just remember to use the New-ManagementRoleAssignment Exchange Management Shell cmdlet to assign the ApplicationImpersonation role to users in the organization. (Only in the case of Exchange 2010)

And in the case of multiple exchange CAS servers use above script to bypass the “Cannot bind argument to parameter ‘Identity’ because it is null.” Error.

Add to Calendar

Project 2010 new reporting functionality: Project server 2010 offers integration with excels services to create reports using MS Excel. In this session we will look at new reporting and business intelligence features.                                                                                   

                                                          Add to Calendar

Project server 2010 Task Delegation, editing plan from project web app, new time tracking and time sheet functionality.

                                                         Add to Calendar

Project Server 2010 Demand Management with Demo.

                                                          Add to Calendar

Project Portfolio Analysis:  Project Portfolio features are now a part of core Project Server product. In this session we will cover. In this session we will cover how to perform Portfolio analysis within project server 2010

Speaker:  Kiran Khanvilkar

Kiran is working as Senior Support Engineer for Project Server at Microsoft GTSC for more than four years. In current role he works with Microsoft worldwide premier customers on Project Server Implementation, troubleshooting and EPM best practices. Overall he has 8+ years of experience in field of Microsoft EPM and Microsoft Office products. Prior to joining Microsoft he worked as Corporate Trainer and has trained 800+participants on products like MS Project, MS Project Server, MS Excel, MS Access and VBA Programming.

How do You Report?

Project wants to know how you report. As we plan for future product improvements, we want to learn more about how you report on your project’s status today.

· What tools do you use?

· How often do you report on your project’s status?

· What data do you care about?

· How do you share your reports?

· What do you find difficult with your current process?

Server Rollup Packages:

(https://support.microsoft.com/kb/981043/ ) Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): April 27, 2010

https://support.microsoft.com/kb/981043/

Description of the Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package): April 27, 2010

https://support.microsoft.com/kb/981042/

Individual Product Packages:

Description of the Windows SharePoint Services 3.0 Cumulative Update server hotfix package (Sts-x-none.msp): April 27, 2010

https://support.microsoft.com/kb/981040/

Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp; Pjsrvwfe-x-none.msp): April 27, 2010

https://support.microsoft.com/kb/981044

Description of the Office Project 2007 hotfix package (Project-x-one.msp): April 27, 2010

https://support.microsoft.com/kb/981732/

Client Installation:

In order to install this hotfix, you will need to have Microsoft Project 2007 SP1 installed on the client. The article at the URL below contains information on how install download and install SP1 should you not have it installed already.

Note:  We strongly recommend that you install Project 2007 SP2 from the information earlier in the article.

Description of Project 2007 Service Pack 1 and of Project Language Pack 2007 Service Pack 1

https://support.microsoft.com/kb/937154/en-us

We are very happy to announce the availability of the Microsoft Project 2010 Ignite beta training slides on Microsoft’s download site:

https://technet.microsoft.com/en-us/library/ff358349(office.14).aspx

The downloadable file contains the following eleven presentations that are used in the three-day training course delivered worldwide:

· Project 2010 Ignite Introduction

· Project 2010 Overview

· Project 2010 Planning, Design, and Deployment

· Project 2010 Upgrade and Migration

· Project 2010 Demand Management

· Project 2010 Portfolio Strategy

· Project 2010 Timesheets and Statusing

· Project 2010 Reporting

· Project 2010 Administration

· Project 2010 Operations

· Project 2010 Developer

The goal for the Project 2010 Ignite Program is to prepare EPM professionals for deployment, operations and customization of Project Server 2010, hence to build skilled EPM partners by General Availability scheduled for June 2010. The "Ignite" curriculum is targeted towards EPM consultants, IT Professionals, Admin Professionals and Developers that have experience deploying, operating and customizing Project Server 2007.  Content will be technical and will range from 300 to 400 levels (Experienced to Advanced/Expert). With this in mind, the "Ignite" content will not be designed to cover all Project Server functionality, only the new functionality of Project Server 2010 will be presented.  In other words the goal is to help better understand the differences, deltas and new features. The content will be a combination of instructor-led training, product demonstrations and hands-on labs. The Project 2010 "Ignite" training will be delivered in English by EPM experts from Microsoft.

Ignite agenda and registration: https://dynamicevents.emeetingsonline.com/emeetings/websitev2.asp?mmnno=327&pagename=SITE52841

Key Microsoft Project 2010 Resources

· Project 2010 Web site: https://www.microsoft.com/project/2010

· Project 2010 Demo Image: https://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8e709e2e-c9a1-4c7e-90d6-a52bcc8e5daf

· Project Server 2010 Beta TechCenter (TechNet): https://technet.microsoft.com/en-us/projectserver/ee263909.aspx

· Project 2010 Beta Resource Center (MSDN): https://msdn.microsoft.com/en-us/office/ee695847.aspx

· Project 2010 webcasts and podcasts: https://www.microsoft.com/events/series/epm.aspx?tab=webcasts

· Project 2010 Forums: https://social.technet.microsoft.com/Forums/en-US/category/projectserver2010,projectprofessional2010

I am Project 2010 ready, are you?

Explore More

• Project 2010 Site :  https://www.microsoft.com/project/2010
• Learn more about powerful new features
• Read Blogs
• See Videos
• Experience Project Conference 2009

  Provisioning PWA Using Kerberos Authentication

Step 1:

Create web application with Kerberos Auth.

Step 2:

Download Windows 2003 Support tools (https://support.microsoft.com/kb/892777)

Steps 3:

Create SPN’s for the web application/s

Syntax:

Setspn.exe -A HTTP/%SHAREPOINTSERVERFQDN% %SERVERFARMACCOUNT%

Example: Setspn.exe –A HTTP/Servername.domain.com:20266 domain\account

Step 4:

In addition to setting the SPNs for each of your service accounts, you also need to trust each of the computer accounts and some of the service accounts for delegation. Trusting for delegation means that the accounts are allowed to delegate on a user's behalf.

In order to trust for delegation you need to open Active Directory Users and Computers as a user with domain administration rights and follow these instructions

• Locate the account and click 'properties'
• Navigate to the 'Delegation' tab
• Choose 'Trust this user/computer for delegation to any service (Kerberos)'

Note: if you do not see Delegation tab, Make sure you have raised the domain functionality level to Windows Server 2003 (Open Active Directory -> Right Click on Domain name -> Select Raise Domain Functional Level -> Select Windows Server 2003 -> Click on Apply

Step 6:

Login into MOSS server, Configure Component services to allow Kerberos

Open Component Services on the MOSS server

                > Navigation to Component Services > Computers > My Computer

                                  • Right Click on My Computer -> Properties - > Default Properties -> Default Impersonation Level = Delegate (see https://support.microsoft.com/kb/917409)

> Navigate to Component Services > Computers > My Computer > DCOM Config > IIS WAMREG Admin Service

Click on Properties (for IIS WAMREG Admin Service) and navigate to the Security tab

>Edit Launch and Activate Permissions

>Grant all three of your application pool account 'Local Activation' permissions

Step 7:

Create a new SSP using the new web application

Change SSP to Kerberos ('STSADM.exe -o SetSharedWebServiceAuthn -negotiate')

Enable Kerberos on IIS

                cscript adsutil.vbs set w3svc/NTAuthenticationProviders "Negotiate,NTLM"

Provision PWA on new SSP

Additional Links

https://technet.microsoft.com/en-us/library/cc263449.aspx

https://blogs.msdn.com/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx

Our product group recently posted very interesting posting about Project 2010 look and feel

Must visit on https://blogs.msdn.com/project/archive/2009/09/24/project-2010-introducing-the-ribbon.aspx