Installing and configuring required Monitoring Server software
Updated: 2009-04-09
Monitoring Server Setup happens in two stages: software installation, and then software configuration.
First, you install Monitoring Server software on the computer by running PSCSrv.msi. After the software is installed, you must configure the server components by running Monitoring Server Configuration Manager. You can think of this configuration step as turning on or turning off the components on the local computer.
The following two configuration options are available in Monitoring Server Configuration Manager:
Stand-alone configuration Selects all the Monitoring Server components that meet the prerequisites to be configured on one computer — including the Monitoring System Database.
Distributed configuration Enables you to selectively configure Monitoring Server components on the local computer. Choose this option if you want to have a customized topology.
Note
Monitoring Server Configuration Manager configures components only on the local computer. Distributed configuration means that you have selected to have a customized topology and want to selectively configure components on this computer. To completely set up your distributed or customized topology, you must run Monitoring Server Setup on each separate computer in your distributed topology.
Monitoring Server Configuration Manager automatically runs after the initial server installation. By using Monitoring Server Configuration Manager, you choose the components that you want to configure on the local computer — for example, the Monitoring Server Internet Information Services (IIS) component, or the Monitoring System Database.
You can run Monitoring Server Configuration Manager multiple times to add or remove Monitoring Server components on the local computer.
Note
When you uninstall Dashboard Designer, all published content in the %ProgramFiles%\Microsoft Office PerformancePoint Server\3.0\Monitoring\PPSMonitoring_1\Preview directory is deleted. Before you uninstall Monitoring Server, ensure that the information in this directory is no longer needed. During the removal process, a backup of all information is copied to the following temporary directory: %TEMP%\MonitoringPreview_<Timestamp>.
Note
Dashboard Designer does not support Microsoft SQL Server 2000 Analysis Services as a data source in 64-bit installations of PerformancePoint Monitoring. Monitoring Server will not install on a Windows 2000 Server domain controller or a Windows Server 2003 domain controller.
Permissions and accounts
When deploying Monitoring Server, you need to specify an account to run IIS application pools for Monitoring Server and SharePoint Products and Technologies. Use a domain account with no permissions. Monitoring Server and SharePoint Products and Technologies add the required permissions as part of the server configuration.
When installing Monitoring Server, log on with an account that has the following permissions:
A member of the Local Administrators group on the computer where you are installing Monitoring Server.
A member of the dbcreator and securityadmin server roles on the computer running SQL Server.
When configuring data sources, use the following guidelines:
Assign "read" permissions to the application pool identities for each data source.
Assign the minimum permissions needed by SQL Server and Analysis Services for the data source user. This will vary depending on the data sources you use.
As a best practice, we recommend that you use the Monitoring Server Admin role rather than the Local Administrators group on the computer to give users administrative access to Monitoring Server.
For information about planning SharePoint Products and Technologies security, see Plan for and design security (Office SharePoint Server).
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.