Deploying PerformancePoint Planning Server in a test lab

Updated: 2009-04-09

This document provides detailed information for setting up a distributed deployment of PerformancePoint Planning Server in a test lab environment.

By following these guidelines you will be able to successfully deploy Planning Server by completing the following tasks:

  • Installing software prerequisites

  • Adding user accounts and assigning permissions in the Active Directory directory service and SQL Server

  • Installing Planning Server

  • Verifying the installation of Planning Server


As shown in the following figure, this scenario involves three servers — an Active Directory domain controller, a computer running PerformancePoint Planning Server, and a computer running SQL Server 2005.


Before installing the software prerequisites, you should read the following regarding the preconfigured baseline information for each of the three servers used in this test lab scenario.

In the remainder of this document, each of the servers is referred to as follows:

  • DC = Active Directory domain controller

  • PSRV = PerformancePoint Planning Server

  • SQL = SQL Server 2005 database


Operating system

Windows Server 2003 R2 Enterprise x64 Edition


Domain functional level

Windows Server 2003

IP address

Subnet mask


Operating system

Windows Server 2003 R2 Enterprise x64 Edition

IP address

Subnet mask


Operating system

Windows Server 2003 R2 Enterprise x64 Edition

SQL Server version

SQL Server 2005 with Service Pack 2 (SP2). Download Microsoft SQL Server 2005 Service Pack 2


Download Cumulative update package 7 for SQL Server 2005 Service Pack 2


IP address

Subnet mask

Installing software prerequisites

You need to install all of the following prerequisites (both Stage 1 and Stage 2) in order to have the ability to choose all of the options for installing PerformancePoint Planning Server.

PSRV prerequisites: Stage 1

Prerequisite component Description and location

Microsoft SQL Server Native Client 9.0 (SP2)

File name: Sqlncli_x64.msi — part of Feature Pack for Microsoft SQL Server 2005 – February 2007


Microsoft .NET Framework 2.0

Microsoft .NET Framework Version 2.0 Redistributable Package (x64)


Microsoft ASP.NET 2.0

ASP.NET 2.0 is included in the .NET Framework Version 2.0 Redistributable Package and installed as part of the package.

Stage 1 prerequisites allow you to complete the first stage of the installation, which will then let you begin the second stage by using Planning Server Configuration Manager.

PSRV prerequisites: Stage 2

Prerequisite component Description and location

Microsoft Core XML Services (MSXML) 6.0

File name: msxml6_x64.msi — This is a prerequisite for installing Analysis Management Object 9.0 (SP2).


Analysis Management Objects 9.0 (SP2)

File name: SQLServer2005_XMO_x64.msi — part of “Microsoft SQL Server 2005 Management Objects Collection”, which is one of the downloads included in the Feature Pack for Microsoft SQL Server 2005 – February 2007



File name: SQLServer2005_ADOMD_x64.msi — part of Feature Pack for Microsoft SQL Server 2005 – February 2007


Internet Information Services (IIS) 6.0

IIS 6.0 is included in Windows Server 2003. To install IIS 6.0, open Control Panel and double-click Add or Remove Programs. Then click Add/Remove Windows Components and choose Application Server.

IIS 6.0 Isolation Mode

The application isolation mode needs to be set to Worker Process, which is the default setting when IIS 6.0 is installed and there is not a previous version of IIS already installed on the computer.

ASP.NET 2.0 Registration with IIS

To register ASP.NET with IIS, you need to use the aspnet_regiis.exe command-line tool. For example, in this scenario where we are using Windows Server 2003 R2 Enterprise x64 Edition, open a command prompt to the follow directory: <drive letter>:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727. Type aspnet_regiis –ir to register ASP.NET.

ASP.NET 2.0 Web Service Extension in IIS

To enable Web Service Extensions in IIS you need to use Internet Information Services (IIS) Manager to configure the Web Service Extensions to “Allowed”. For example, you need to change both “All Unknown CGI Extensions” and “All Unknown ISAPI Extensions” from the default setting of “Prohibited” to “Allowed”.

Adding user accounts and assigning permissions

In this test lab scenario, the following user accounts were created in Active Directory on the DC computer in the FABRIKAM domain:


User Account Name Description


This is a required domain-joined user account used by Planning Server and is referred to as the service identity account. Specify the “Password never expires” account option.


You must have a domain-joined user account configured, which will be used when first opening and connecting to Planning Server. This account is referred to as the "global administrator account" during the installation process.


This domain-joined user account is used during the second stage of the installation process of Planning Server. This user account is also added to SQL Server and assigned the necessary account permission in SQL Server.

In this test lab scenario, the following user account was created in SQL Server 2005 on the computer named SQL:


User Account Name Description


In this lab scenario, the login name FABRIKAM\dbAdmin was added to SQL Server. The following server roles were assigned to this login account: dbcreator, public, and sysadmin. This account is used for the second stage of the installation process of Planning Server, where access and permissions are required for the creation of database files.

In this lab scenario, the dbAdmin account was added as a member of the Administrators group on the computer named PSRV.

Installing Planning Server

In this lab scenario, we use the user account FABRIKAM\dbAdmin to log on to PerformancePoint Planning Server and begin the installation process.

Install Planning Server

  1. Insert the Microsoft Office PerformancePoint Server 2007 CD. When the program starts, a startup screen appears. If it does not, browse the CD and click Setup.hta.

  2. From the installation startup screen, select Planning Server to begin the Planning Server installation.

    Prerequisite checks are run and the Microsoft Licensing Terms are presented.


    Any missing prerequisites are indicated in the Prerequisites dialog box. All prerequisite checks must succeed. If there are failures, cancel Setup, install the missing prerequisites, and then rerun Setup.

  3. Accept the License Terms, and then click Next.

  4. On the Directory Selection page, select the installation directory you want, verify that enough disk space exists, and then click Next.

  5. Click Install to run Planning Server Setup.

    Planning Server Setup runs, extracting all installation files to the directory path that you specified in step 4.

  6. On the Planning Server Setup Has Completed page, ensure that the Run the Planning Server Configuration Manager box is selected, and then click Finish.


    If you choose to exit Setup without starting Planning Server Configuration Manager, the components will not be configured for use, and your Planning setup will remain incomplete. You must run Planning Server Configuration Manager to complete Setup and successfully configure your Planning Server.

     To run Planning Server Configuration Manager, do the following:

    1. Navigate to the Windows Start menu.

    2. Click Start, point to Programs, then point to Microsoft Office PerformancePoint Server 2007, and then click Planning Server Configuration Manager.

  7. On the Planning Server Configuration Manager Welcome page, click Next.

  8. On the Prerequisites page, verify that all prerequisites have passed. If there are any that fail, note them, cancel Planning Server installation, install all prerequisites, and then rerun Planning Server Configuration Manager.

  9. On the Installation Options page, select Distributed configuration, and ensure that all of the following components are selected: Planning Server databases, Planning Process Service, Planning Web Service, and Planning Administration Console. Then click Next.

  10. On the Databases page, in the SQL Server location field, type the IP address of the computer running SQL Server, which in this test lab scenario is, and then click Next.


    This procedure assumes a clean SQL Server computer with no previous PerformancePoint Server databases. If previous PerformancePoint Server databases are detected on the selected SQL Server computer, then an error message appears. To correct this error, select a new SQL Server computer or SQL Server instance, or manually delete the existing PerformancePoint Server databases. Do not rename existing databases, because this will leave the *.mdf and *.ldf files in an orphaned state and make new PerformancePoint Server database creation impossible.

  11. On the Global Administrator Account page, confirm that the account in the Domain and User Name field is the account that will be used for the first member of the Global Administrator (GA) role. In this test lab scenario you would enter the account, PSRV_GAA. This account will be used to log on to the Planning Administration Console for final system configuration and future administration. Click Next.

  12. On the Service and Application Pool Identities page, specify a domain, user name, and password for the service identity account. In this test lab scenario you would enter the account, PSRV_SIA. Click Next.

  13. On the System Logs page, leave the defaults for all options, and then click Next.

  14. For this test lab scenario on the Port Configuration page, clear the Require SSL connections to all Planning Server Web sites box. This allows you to view the network traffic for analysis without having the traffic for the connections to the Planning Web sites encrypted. (Of course, this is not necessarily what you would want to do in a production environment.) Then click Next.

  15. On the Validation page, pre-installation validation occurs and confirms that the installation will proceed successfully. When this is finished, click Next.

  16. On the Confirmation page, review this information, and then click Configure.

  17. On the Summary page, you can view the results of the installation. To indicate a successful installation, it should read “Configuration completed successfully.” Click Close.

The installation of Planning Server is complete.

In this test lab scenario you should now log off from PSRV as FABRIKAM\dbAdmin.

Verifying installation of Planning Server

To verify the successful installation of Planning Server in this test lab scenario, perform the following tasks:

Verify the installation of Planning Server

  1. Log on to the computer named PSRV as FABRIKAM\PSRV_GAA.

  2. In this test lab scenario, open Internet Explorer and browse to: https://localhost:46788, where 46788 is the default port number specified for the Planning Administration Console.

  3. In this lab scenario, the following should be entered in the Location dialog box: http://PSRV:46787, where PSRV represents the name of the server where the Planning Web service was installed and where 46787 is the default port number for the Planning Web service. Click Connect.

You should now have a working installation of Planning Server; however, before you can begin working with models or applications, you must first create a PerformancePoint Planning application on the system that can be accessed by service clients, such as PerformancePoint Planning Business Modeler and PerformancePoint Add-in for Excel.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for PerformancePoint Monitoring Server.