• TaskSynchronization requires user profile synchronization & work management service application.
• Task Synchronization requires Exchange Server 2013 & SharePoint web application on Secure Sockets Layer (SSL).
• “Synchronize Out of office calendars” option should be enabled at the server level (PWA).
• “Synchronize Out of Office Events” option should be enabled at the user level (MySite).
• Timesheet periods must be set up (Even if the actuals are not tracking using timesheets)

 High Level Steps:

1. Install Microsoft Exchange 2013

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

       2. Configure site bindings to include SSL (https and port 443)

       3. Configure Alternate Access Mappings for the SharePoint web application (Site can be accessed via the FQDN address).

       4. Add a Self-Signed Certificate as a trusted certificate on the Exchange Server by accessing the PWA .

       5. Download EWSManagedAPI.msi from the Microsoft Download Center (https://www.microsoft.com/en-us/download/details.aspx?id=35371)
            and save it to a folder on the application server.

             Run the following command and restart IIS:

              msiexec /i EwsManagedApi.msi addlocal="ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac"

       6. Configure Exchange Server 2013 for Task Synchronization

            Establish OAuth trust and service permission on Exchange Server.

            On the Exchange server, open Windows PowerShell and change to the "C:\Program Files\Microsoft\Exchange Server\V15\Scripts" directory.

            Run the following script:

             .\Configure-EnterprisePartnerApplication.ps1 -ApplicationType Sharepoint -AuthMetadataUrl https://<SP_FQDN>/_layouts/15/metadata/json/1

              Where <SP_FQDN> is the URL to the root site collection.

Troubleshooting Tips:

Issue: Users are unable to see the tasks in the my site

1. The user may not have permission on the Project / SharePoint site
2. Work management service is not running properly
3. User profile service / service application may have some issues
4. Search service doesn’t perform the crawl completely
5. If the timer job “Work Management Synchronize with Exchange” doesn’t run, Sync between Exchange and the users My Tasks won’t sync tasks. Sometimes restarting SharePoint timer
   service can help to process the sync.

Enterprise Project Management (EPM), in broad terms, is the field of Business Development that supports organizations in managing integrally and adapting themselves to the changes of
a transformation.

Microsoft Project Application, EPM solution has been specifically designed to meet the needs of industries managing complex projects. Companies across various industries today
are challenged to deliver their projects on time and within budget. EPM Deployment provides enormous supports to manage the complete Project Lifecycle.

The objectives of the EPM solution deployment are:

       
To standardize the way of proposing, planning, and tracking project. Project Management

    
Intuitively capture all requests in a central repository, and manage them using governance workflow: Demand Management

    
Proactively and reactively manage resources throughout the project life cycle: Resource Management

    
Easily create and communicate both simple and complex project schedules: Schedule Management

    
Simplify the collection of time and task status updates from team members: Time and Task Management

    
Better connect different teams to share information and drive collaboration: Team Collaboration

    
Identify, reduce, and communicate issues and risks that could adversely affect project success: Issues and Risk Management

    
Effectively measure project performance and gain visibility and control across all portfolios: Business Intelligence and Reporting

    
Initiate, plan, and deliver strategic programs: Program Management

Project Server 2013 for IT pros

https://technet.microsoft.com/en-us/projectserver/fp123546.aspx

What's new in Project Server 2013 upgrade?

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

Plan for upgrade to Project Server 2013

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

Upgrade to Project Server 2013

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

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

https://technet.microsoft.com/en-us/sharepoint/fp142375.aspx

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

Purpose

This document describes how to configure the Forms Based authentication using ASP NET SQL Membership provider to authenticate users for a Project Server 2010 instance.

This configuration is done for SharePoint 2010, and Project Server 2010 can then use this configuration to authenticate users.

Summary of  Steps

The following steps need to be done:

1.       Create the AspNet DB user/role repository: SQL database

2.       Create a web application that uses claim based authentication

3.       Update web.config file of Central Admin

4.       Add some users in the database using IIS Manager

5.       Update web.config file of the web application

6.       Update web.config file of the STS (Secure Token Service) Application

7.       Create a site collection specifying a Windows users as a primary admin and a user from SQL membership as the secondary admin

8.       Test the connection to the root of the site collection as the secondary admin using FBA

9.       Create the PWA instance

10.   Test the connection to this PWA instance as the admin user

11.   Create FBA users in PWA

The following examples values are used in these steps.

 Login as contoso\administrator.

a.       Open c:\Windows\Microsoft.NET\Framework64\v2.0.50727, and find the aspnet_regsql.exe and double-click to launch.

b.       Choose ‘Configure SQL Server for Application Services’ and click Next.

c.       Click Next and enter the name of the SQL Server, in this case the server name will be SQL.

d.       Confirm that we have our aspnetdb created in SQL Management Studio on the SQL server.

Create the AspNet DB user/role SQL repository in command prompt:

To create the SQL server database that will store the users and the roles, we can use the following tool from the .Net Framework: “aspnet_regsql”.

%WINDIR%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regsql /? Lists the parameters

To create the SQL authentication store

1.     Log on to any Windows Server on the farm running ASP.NET as a user with the DBCreate and SecurityAdmin permissions for the computer running SQL Server that will be used.

2.     At a command prompt, run %WINDIR%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regsql.exe -S <InsertSQLServerName> -d <InsertDBName> -E –A mr to create the authentication store database on the computer running SQL Server.

3.     Add all farm accounts to the DBO role for this newly created database.

For the following steps we assume that the database name is called aspnetdb and the SQL instance is SQLServer\sqlInstance1

aspnet_regsql.exe -S  SQLServer\Instance1  -d  aspnetDB -E –A mr

OPTION 1: Create Users with Visual Studio 2010. Switch to your Client machine that has Visual Studio installed.

2.        

a.       Launch the application. When you do you may see a prompt asking what environmental variables to use. Choose Visual C# Development Settings.

b.       Click New Project on the Quick Launch bar.

c.       Create an ASP.NET Web Application.

d.       In Solution Explorer open up the web.config. We will need to change the connection string (see the Code entry below).

<connectionStrings>

    <add name="ApplicationServices"

      connectionString="Data Source=SQL;Integrated Security=SSPI;Initial Catalog=aspnetdb;" providerName="System.Data.SqlClient" />

</connectionStrings>

e.       Click Build and then Build Solution in the Visual Studio menu. After the solution builds, click Project and ASP.NET Configuration.

f.        Click the Security tab on the Web Site Administration tool that launches. You will see headings for Users, Roles, and Access Rules.

g.       Click the Enable Roles link in the middle pane and Create or Manage Roles.

h.       Create new Roles:

i.         Click Create User and create users.

We now have Roles and Users in the aspnetdb database for use in the rest of this lab.

OPTION 2: Create Users in IIS 7.x. Using IIS to Populate Data for ASPNETDB We Created in Step Before.

a.       Open IIS Manger on MSF1 Server

b.       Select Default Web Site and Make Sure you are in Features View

c.       Open Connection Strings Option under ASP.NET Section.

d.       Click on LocalSqlServer Connection Sting & Provide SQL Server Name where you Created aspnetdb in Earlier Step also Provide name of Database Created.

e.       Click ok

f.        Once again Select Default Web Site & from Features View Click on .net Roles

g.       Click on enable from Actions

h.       Now Click on Add and Add .net Role to Database

i.         Create few more Roles.

j.         Now Go back to Features View for Default Web Site and Click on .NET Users

k.       Click on Add and Create New user in aspnetdb

Create a web application that uses claim based authentication

1.    Create a new Web application in Claims mode.

2.    Go to the SharePoint Central Administration Web site.

3.    Click Application Management.

4.    On the ribbon, click New. A pop-up window appears.

5.    In the pop-up window, select the Claims Based Authentication option.

6.    In the pop-up window, in the IIS Web Site section, select a unique name and port number.

7.    In the pop-up window, in the Security Configuration section, set Allow Anonymous = No and set User SSL to Yes or No, depending on whether the site you are extending will be SSL-enabled.

8.    In the pop-up window, in the Identity Providers section, select Enable ASP.NET Membership and Role Provider and specify a provider name and role manager. For this example AspNetSqlRoles and AspNetSqlMembers and used respectively.

9.    In the pop-up window, keep the default setting for Public URL.

10.  In the pop-up window, in the Application Pool section, choose to create a new pool with a pool name and the account that will be used.

11.  In the pop-up window, after Database Name set the value for the SQL server and database names for the content database.

12.  Click OK to close the window. A new Web App will be created.

13.  A Site Collection will be created later

Update web.config file of Central Admin

The web.config file of the Central administration needs to be updated in three places.

·         PeoplePicker

·         Add the membershitp/Role tags

·         Add the SQL connection String

Before modifying the file do a backup of the original file.

To locate the web.config file, use IIS Manager and choose Explore after selecting the web site.

The parts in bold need to be added in the XML file.

And the grayed parts are the part where the values of the chosen variables need to be updated.

    </SafeControls>

    <PeoplePickerWildcards>

      <clear />

      <add key="AspNetSqlMembers" value="%" />

    </PeoplePickerWildcards>

(…)

    <sessionState mode="InProc" timeout="20" cookieless="UseCookies" />

<roleManager enabled="true" cacheRolesInCookie="false" cookieName=".ASPXROLES" cookieTimeout="30" cookiePath="/" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieProtection="All"

defaultProvider="AspNetWindowsTokenRoleProvider" createPersistentCookie="false" maxCachedResults="25">

<providers>

<clear />

<add connectionStringName="SqlConn"

       applicationName="/"

       name="AspNetSqlRoles"

       type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

<add applicationName="/"

       name="AspNetWindowsTokenRoleProvider"

       type="System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

</providers>

</roleManager>

<membership defaultProvider="AspNetSqlMembers" userIsOnlineTimeWindow="15" hashAlgorithmType="">

<providers>

<clear />

<add connectionStringName="SqlConn"

       enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" passwordAttemptWindow="10"

       applicationName="/"

       requiresUniqueEmail="false" passwordFormat="Hashed"

       name="AspNetSqlMembers"

       type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

</providers>

</membership>

  </system.web>

(…)

  </appSettings>

<connectionStrings>

<clear />

<!-- FBA Claims Auth-->

<add name="SqlConn" connectionString="data source= SQLServer\instance1;Integrated Security=SSPI;Initial Catalog=aspnetdb" providerName="System.Data.SqlClient" />

<!-- FBA Claims Auth-->

</connectionStrings>

</configuration>

Add some users in the database using IIS Manager:

Using IIS Manager Select the Central Admin web site and .Net Users command and add Users

Update web.config file of the web application

The web.config file of the new web application (the one you’ve setup with the claims authentication type) needs to be updated in three places.

·         PeoplePicker

·         Add/update the membership/Role tags (AspNetSqlRoles, AspNetSqlMembers)

·         Add the SQL connection String

Caution: Some values are different then in the Central Admin configuration file

Before modifying the file do a backup of the original file.

To locate the web.config file, use IIS Manager and choose Explore after selecting the web site.

    </SafeControls>

    <PeoplePickerWildcards>

      <clear />

      <add key="AspNetSqlMembers" value="%" />

    </PeoplePickerWildcards>

(…)

    <machineKey validationKey (…)/>

<roleManager cacheRolesInCookie="false" cookieName=".ASPXROLES" cookiePath="/" cookieProtection="All" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieTimeout="30" createPersistentCookie="false" defaultProvider="c" enabled="true" maxCachedResults="25">

<providers>

<clear />

<add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

<add connectionStringName="SqlConn" applicationName="/" name="AspNetSqlRoles" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

</providers>

</roleManager>

<membership defaultProvider="i" hashAlgorithmType="" userIsOnlineTimeWindow="15">

<providers>

<clear />

<add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

<add connectionStringName="SqlConn" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" passwordAttemptWindow="10" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" name="AspNetSqlMembers" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

</providers>

</membership>

(…)

  </microsoft.identityModel>

<connectionStrings>

<clear />

<!-- FBA Claims Auth-->

<add name="SqlConn" connectionString="data source=SQLServer\instance1;Integrated Security=SSPI;Initial Catalog=aspnetdb" providerName="System.Data.SqlClient" />

<!-- FBA Claims Auth-->

</connectionStrings>

</configuration>

Update web.config file of the STS (Secure Token Service) Application

The web.config file of the new STS web application (the one you’ve setup with the claims authentication type) needs to be updated in two places.

·         Add the membershitp/Role tags (AspNetSqlRoles, AspNetSqlMembers)

·         Add the SQL connection String

This web.config file should be located at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken.

Before modifying the file do a backup of the original file.

The original file:

  </system.serviceModel>

<system.webServer>

    <security>

To update the file add this section:

  </system.serviceModel>

<connectionStrings>

<clear />

<!-- FBA Claims Auth-->

<add name="SqlConn" connectionString="data source=SQLServer\instance1;Integrated Security=SSPI;Initial Catalog=aspnetdb"

providerName="System.Data.SqlClient" />

<!-- FBA Claims Auth-->

</connectionStrings>

<system.web>

  <membership defaultProvider="AspNetSqlMembers">

    <providers>

      <add connectionStringName="SqlConn"

       enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" passwordAttemptWindow="10"

       requiresUniqueEmail="false" passwordFormat="Hashed"

       applicationName="/"

       name="AspNetSqlMembers"

       type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

    </providers>

  </membership>

  <roleManager enabled="true">

    <providers>

    <add connectionStringName="SqlConn"

       applicationName="/"

       name="AspNetSqlRoles"

       type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

    </providers>

  </roleManager>

  </system.web>

<system.webServer>

    <security>

Create a site collection specifying a Windows users as a primary admin and a user from SQL membership as the secondary admin

We will now create a site collection on this web application. 

1.    Go to Central Administration site

2.    Create site collections (under Application Management)

3.    Ensure the web application with claims authentication enabled is selected in the web application drop-down. 

4.    Provide a title and description for the site collection

5.    Select a template.

6.    Specify a normal Windows user as primary site collection administrator

7.    For the secondary site collection administration, specify the administrator user from the AspNetSqlMembers provider. 

Test the connection to the root of the site collection as the secondary admin using FBA

Enter your FBA admin account username and password

Create the PWA instance

Create a new Project Web App instance using the Web application created in step 2.

Specify as the admin account either a Windows account or a membership user.

Test the connection to this PWA instance as the admin user

Create FBA users in PWA

To create FBA users in PWA go to Manager Users.

Use the following syntax “membershipname|username” ,for example AspNetSqlMembers|Jason

Installed two machines with Microsoft Windows Server 2003 R2, Enterprise Edition, Service Pack 2.

Added my domain (Domain\Sriram) account on both the machines as Administrator.

Logged in using that account & Installed everything using the same account.

All the application pools are in Network Service.

SRIR1877706: (SQL Server with Reporting Services)

·         Configured IIS and Installed Framework 3.0

·         Installed SQL Server 2005 Enterprise Edition 2005 with Database Engine, Analysis service and Reporting service.

·         Installed Service Pack 3 for SQL server 2005

SRIR1877707: (Portfolio server)

·         Configured IIS and Installed Framework 3.0

·         Installed PPS with default Installation and selected SQL server as SRIR1877706.

·         Selected only ‘web site’ and provided https://SRIR1877706/reportserver as report server URL.

·         When I browse the PPS (https://SRIR1877707/portfolioserver, got the error : Login failed for user 'Domain\SRIR1877707$'.

·         Open SQL Management Studio at SRIR1877706 and Provided Sys Admin permission to the account 'Domain\SRIR1877707$ .  

·         Able to browse the PPS without any issues.

Report Server Configuration Part:

·         When I generate the report using https://SRIR1877707/portfolioserver, got the following error

The item '/Reports' cannot be found. More Info: https://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsItemNotFound&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.4035.00

·         Installed PPS at SRIR1877706 and selected only Reporting Services Configuration

• Provided the path for “Report server” , but portfolio component with default path

·         Later When I tried to build the report, first error vanished, got the following error

The permissions granted to user 'DOMAIN\SRIR1877707$' are insufficient for performing this operation. More Info: https://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsAccessDenied&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.4035.00

·         Added DOMAIN\SRIR1877707$ in Server SRIR1877706 with administrator groups, the issue has been resolved. Able to generate the report without any issues.

The following article describes the Microsoft Office Project Server 2007 Queuing System, which is a new, key feature in this version of Project Server. The article provides an overview of the Queuing System, the queuing process and architecture, the methods in which queuing jobs are grouped, states that queuing jobs can be in, and how to manage queuing through the Microsoft Office Project Web Access user interface.

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

 --Analyse the job's Type & State which are pending in the Queue, next action should be according to the same.

--Need to check all the jobs are stuck or particular type of jobs.

--Good to check whether the pending is project specific or server specific.

Steps:: (Waiting to be processed)

1. Stop and start the Project services & Timer service

2. Go back in History and find out any job which is in "Getting Queued", cancel it and check the behaviour.

3. Ensure project server Time and SQL server time are same.

Steps:: (Failed But Not Blocking Correlation)

4. Skip the first step 

5. Analyse the error details, work accordingly.

Under Construction::

      The Cube building creates a default Role ProjectServerViewOlapDataRole that automatically adds all the Project Server users to this Role. But during the standard Cube Building process in Project Server 2007, any manually added OLAP Roles in an OLAP database will be deleted.

Please follow the steps below to access the cube from non-domain environment and persisting the manaully added roles with the cube.

To access the Project server 2007 OLAP cube from Non-Domain workgroup environment:

·         Create a local user account in the Analysis server

·         Create a role in the OLAP cube along with “ProjectServerViewOlapDataRole”

·         Add the local users with that Role

·         Create the account on the workgroup computer with the same name and same password.

·         Login though that account on the computer to access the OLAP cube

To add the roles through a schedule job, please follow the steps below.

Workaround:

1.       Open Analysis server, expand database, expand Roles

2.       Add a new role and add the users manually

3.       Click on "Script" drop down in the Edit Role window

Select “Script Action to New Query Window”

Copy that XMLA script

4.       Create a job under SQL Server Agent

5.       In that job select “SQL Server Analysis services command” as step type.

6.       Paste the XMLA script in to the command portion

7.       Schedule the job to run after the OLAP cube completion, So that the role will be added after the OLAP cube created.

Please find the link below to schedule the job in SQL server 2005.

Backup Strategies with SQL Server 2005 Analysis Services:

https://www.microsoft.com/technet/prodtechnol/sql/2005/bkupssas.mspx

Disclaimer: All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights. Use of any script or code samples is subject to the terms specified in the Terms of Use.

On the front-end application server:(Where the project server URL is pointed)

1. Navigate to the following registry key and create a new String value as "Forward" with value "1".

******************************************************************************

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS Project\Services\Configuration\Views Notification

"Forward"="1"

******************************************************************************

2. Navigate to the following registry setting:

******************************************************************************

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS Project\WebClient Server\ xxxx \Datasets\ViewsFileDrop

******************************************************************************

XXXX - Name of the Virtual directory of your Project server instance.

(By default ProjectServer)

Drop Location - The folder where the Forwarder is going to pick the xml files to distribute across the servers

(By default C:\Program Files\Microsoft Office Project Server 2003\BIN\VIEWDROP\)

For each project server running the View Processing service, add a sequential registry entry, for example ForwardUNC001, ForwardUNC002, ForwardUNC003, and so on, with the value being the directory path for the ViewDrop location on the server running the View Processing service. If you skip a number in the sequential order, it will be ignored and the Project Server front-end application server will return to the ForwaredUNC000 entry. Additionally, each registry entry can only represent a unique server running the View Processing service.

Additional Help on Load balance:

==========================

By default this forwarder configuration performs "simple Round Robin" logic to distribute the XML files across the View Notification servers.

To use external load balancer (NLB) to distribute the XML files, keep the view notification servers in load balancing environment and configure the load balanced URL as UNC path.

MS-Articles on Deploying Multiple View Processing Servers and Distributed Deployment

======================================================================

https://office.microsoft.com/en-us/projservadmin/HA011654241033.aspx

https://www.microsoft.com/technet/prodtechnol/project/project2002/reskit/prk_sdistribdeploy_3535.mspx

Important things to keep in mind:

==========================

=To complete the process of offloading the View Processing service, you must edit the registry on the front-end application server or servers in your Project Server deployment. 

a. To restrict the resources to modify the Actual work 

b. To restrict the Project Managers to modify the Project Plan 

c. To move the completed projects away from PM and Team members, but the Project plan should be listed in OLAP cube.

d. This is specific to Project Server 2003, but you can use it for Project Server 2007 also. 

Archive completed projects in the production Project Server database.

Reference: https://support.microsoft.com/kb/920327

Methodology Overview:

This methodology allows an organization to archive completed projects in the production Project Server database, while only allowing members of the Executives, Portfolio Managers, and Administrators groups to view the completed projects using either Microsoft Project Professional or Project Web Access. To use this methodology properly, there are number of required steps that the Project Server administrators and project managers must perform initially.

1. Create an Enterprise Custom Field:

       The Project Server administrator should create a Project Level Enterprise custom field called "Project Status" and make it as Required Field. The Project Status code should contain a single level code mask with the following values in the Lookup Table: The field name and the values can be depends upon the business requirement.

·        Planned       ·        Production     ·        On Hold   ·        Cancelled  ·        Completed

2. Create a Custom Category:

In Project Web Access, the Project Server administrator should create a custom Category called My Completed Projects. Initially, this Category will not contain any projects. The Project Server administrator should include the Project Managers group in this new Category.

In the Permissions section of the Add Category page, the Project Server administrator should select each Group individually and set the following permissions in the Permissions grid for each Group:

·        Open Project - Deny

·        Save Project - Deny

The above Permissions settings in the My Completed Projects category will prevent all members of the Project Managers from seeing the completed project in Microsoft Project Professional.

3. Set the value for Project Status custom field to Each Project:

After the Project Server administrator creates the Project Status field and the My Completed Projects category, each project manager in the organization must complete the following steps:

1.          Open a project in Microsoft Project Professional.

2.          Click Project - Project Information.

3.          Select a value in the Project Status custom field to indicate the current status of the project.

4.          Save & Publish the Project Plan.

6.          Repeat the same process for every project that he/she manages.

The above set of steps will “push” the latest information for each project to Project Web Access.

4.Modify Project Center and Portfolio Analyzer Views:

The Project Server administrator should create a new custom Project Center view that includes the Project Status field and should add this new view to only the My Organization category. This gives access to the new View to only those in the Executives, Portfolio Managers, and Administrators groups. The Project Server administrator should also modify all of the default Project Center views in Project Web Access to exclude completed projects by adding the following Filter to each view:

        Project Status        Not equal to       Completed

Warning: Do not exclude the completed projects from every Project Center view; otherwise, no one will be able to see these projects, including members of the Administrators group.

The Project Server administrator should also modify Portfolio Analyzer views by adding the Project Status dimension to the Filter fields drop area, which allows users of the Portfolio Analyzer to exclude data for completed projects, if they wish to do so. In addition, the Project Server administrator may want to create one or more custom Portfolio Analyzers views to show Cost and Work for completed projects only.

5. Archive Completed Projects:

When a project team completes a project, the project manager should immediately do the following:

1.    Open the completed project in Microsoft Project Professional

2.    Click Project - Project Information, set the Project Status field value to Completed, and then click OK

3.    Click Tools - Build Team from Enterprise

4.    Set the Booking value for each project team member to Proposed and then click OK

5.    Click  Save & Publish the completed project

Note: Step #4 above is vital to the archiving process, as it will remove the task assignments from each team member’s timesheet in Project Web Access for the completed project.

After the project manager has completed the above steps for the completed project, the Project Server administrator should complete the following steps:

1.    Log into Project Web Access with administrator permissions

2.    Click Admin - Manage security

3.    Select the My Completed Projects category and click the Modify Category button

4.    In the Projects section, move the newly-completed project to the Projects in this category list on the right

5.    Click the Save Changes button

After performing the steps in each of the preceding sections, only those in the Executives, Portfolio Managers, and Administrators groups in Project Server will be able to access the completed project in Project Server.

Method 1:

1. Ensure you have an actual enterprise/corporate disc & product-key.
2. Notably, o2k7 uses setup patches (*.MSP) rather than transforms which previous versions used (*.MST). The below instructions will give you an MSP file, which is not accepted by non-corporate versions of o2k7.
3. Now at the command prompt, type: setup.exe /admin
4. Choose the product for which you want to make a customization-patch.
5. Then go through all steps in the customization wizard (to install the reqd apps & remove junk & change default settings).
6. Be sure to have "completion notice" turned on & "suppress modals" turned off (this is to get to see errors, if any exist). Once you're done with testing, go thru the customization again to modify the MSP to disable completion notice & enable suppress modals.
7. Save the resulting patch file in the same folder as o2k7 setup files.
8. Now just execute this command (thru any method) for silent install: setup.exe /adminfile CUSTOM.MSP

Method 2:

Prepare through XML file, please find below for sample XML file.

Since "Adminfile" method is especially for first time installation, always suggest XML file method.