Clustered
CMSU_SPV_Develop_API_MPF--Deployment.xml (4 Computers)
In a clustered deployment, Microsoft® Provisioning
Framework (MPF) components can be distributed among servers in
a variety of ways. A common 4-server configuration for an
active/passive cluster is as follows:
- Servers 1 and 2 (Virtual Server): Servers 1 and 2 share
the drive array for the virtual server, which houses the MPF
database components.
- Server 3: Server 3 houses the MPF components that
process incoming requests from a client server.
- Server 4: Server 4 is the client server that processes
incoming requests and passes them to server 3.
The following table illustrates the platform and MPF component
requirements for each server. For additional information on MPF
component dependencies, see System
Requirements.
Server |
Platform |
MPF Components |
1 |
- Member server
- Clustered SQL Server 2000 with Service Pack 1
|
The following components are installed on the shared drive
array for servers 1 and 2:
|
2 |
- Member server
- Clustered SQL Server 2000 with Service Pack 1
|
3 |
- Member server with Microsoft® Data Access Components (MDAC)
version 2.6 with Service Pack 1
|
|
4 |
- Member server with MDAC 2.6 SP1
- Microsoft® Internet Information Server (IIS) version 5.0 3
|
|
1 Prerequisite for all other non-database MPF components
2 For running Microsoft
Provisioning Manager.
3 Required if ISAPI Extension (SOAP ISAPI) is
installed as part of client components.
4 ISAPI Extension is required if the server will process SOAP
requests.
Deploying a clustered configuration
The requirements for clustered deployments are the same as those
for domain
deployments except that:
- Virtual servers and SQL clustering must also be configured.
When installing on a cluster, you specify the virtual server name
rather than the server/computer name. On SQL computers, the
installation detects the existence of a cluster and prompts for the
necessary information.
- Clustered servers must have Provisioning
Auditing and Recovery Service installed for proper failover. In
this scenario, this is accomplished by installing the transaction
log on server 2 as well as on server 1. (The transaction log
automatically installs Provisioning Auditing and Recovery
Service.)
The following installation instructions will install the above
configuration on four servers.
Important To successfully execute these instructions:
Before installing MPF on any computer, verify that the following
items are configured and operational:
- Microsoft® Active Directory® domain setup
- DNS in Microsoft® Windows®
- Virtual servers and SQL clustering
There are two ways to deploy the configuration: by running Setup.exe on
each server, or by executing an
unattended installation. The following instructions illustrate
both approaches.
Once setup is complete on all computers, you can verify the
deployment using the instructions in Testing an MPF
Install.
Installing MPF by running Setup.exe
Server 1:
- In the welcome screen, click Next.
- In the License Agreement screen, click I accept the
terms in the license agreement, then Next.
- In the Customer Information screen, enter the user name
and organization, then click Next.
- In the Installation Mode screen, click Domain,
then Next.
Domain indicates that the installation involves multiple
computers that will communicate with each other. (Local is
only used for stand-alone computers used for development or
evaluation installs.)
The Installation Mode screen displays only for member
servers (which can be either local or domain), and only when
one of the following conditions is true:
- In the Setup Type screen, click Custom, then
Next.
- In the Custom Setup screen, disable all components
except Configuration Database, Transaction Log
Database, Audit Database, and Resource Manager
Database, then click Next.
- In the Cluster Information screen, enter the virtual
server name for the clustered database install, then click
Next.
- In the MPF Account Passwords screen, enter and confirm
the passwords for the MPF service account and client account, then
click Next.
Depending on the components to be installed, Setup.exe creates a
service account and/or a client account in Active Directory. The
service account (MPFServiceAcct) is the default user account for
the Provisioning
Engine, Provisioning Queue
Manager Service, and Provisioning Auditing
and Recovery Service. The client account (MPFClientAcct) is the
user account for the client that receives provisioning requests
submitted to MPF. For more information on how these accounts are
used in MPF security, see MPF
Accounts.
Note If you cancel an MPF setup, you must delete accounts
manually before re-attempting setup. For more information, see
Readme.htm.
- In the Ready to Install screen, click Next.
The Installing MPF screen displays.
- When installation is finished, a completion screen displays.
Make a note of the MPF product ID, then click Finish.
- When setup completes, use Cluster Administrator to initiate
failover and transfer ownership of the cluster to server 2.
Server 2:
- In the welcome screen, click Next.
- In the License Agreement screen, click I accept the
terms in the license agreement, then Next.
- In the Customer Information screen, enter the user name
and organization, then click Next.
- In the Installation Mode screen, click Domain,
then Next.
- In the Setup Type screen, click Custom, then
Next.
- In the Custom Setup screen, disable all components
except Transaction Log Database, then click
Next.
- In the Cluster Information screen, enter the virtual
server name for the transaction log, then click Next.
- In the MPF Account Passwords screen, enter and confirm
the password for the MPF service account, then click
Next.
- In the MPF Database Servers screen, enter the virtual
server name for the configuration database, then click
Next.
- In the Ready to Install screen, click Next.
The Installing MPF screen displays.
- When installation is finished, a completion screen displays.
Make a note of the MPF product ID, then click Finish.
Server 3:
- In the welcome screen, click Next.
- In the License Agreement screen, click I accept the
terms in the license agreement, then Next.
- In the Customer Information screen, enter the user name
and organization, then click Next.
- In the Installation Mode screen, click Domain,
then Next.
- In the Setup Type screen, click Custom, then
Next.
- In the Custom Setup screen, disable all components
except Core Components, Service Providers,
ISAPI Extension (if required), Queue Manager Service,
and Resource Manager Engine, then click Next.
- In the MPF Account Passwords screen, enter and confirm
the passwords for the MPF service account (and client account, if
using the ISAPI Extension), then click Next.
- In the MPF Database Servers screen, enter the virtual
server name for the configuration database and resource manager
database, then click Next.
- In the Ready to Install screen, click Next.
The Installing MPF screen displays.
- When installation is finished, a completion screen displays.
Make a note of the MPF product ID, then click Finish.
Server 4:
- In the welcome screen, click Next.
- In the License Agreement screen, click I accept the
terms in the license agreement, then Next.
- In the Customer Information screen, enter the user name
and organization, then click Next.
- In the Installation Mode screen, click Domain,
then Next.
- In the Setup Type screen, click Custom, then
Next.
- In the Custom Setup screen, disable all components
except Microsoft Provisioning Manager, then click
Next.
- In the MPF Account Passwords screen, enter and confirm
the password for the MPF service account, then click
Next.
- In the MPF Database Servers screen, enter the virtual
server name for the configuration database, then click
Next.
- In the Ready to Install screen, click Next.
The Installing MPF screen displays.
- When installation is finished, a completion screen displays.
Make a note of the MPF product ID, then click Finish.
Installing MPF by executing an unattended installation
Data centers typically deploy MPF using a script that allows
installation to be executed with little or no user input. For a
complete list of commands, see Unattended
Installations.
Before executing an unattended install, copy the MPF.MSI file to
all four servers. This file is located in the Setup directory of
the MPF CD. On each machine, run the installation script from the
command prompt, in the directory where MPF.MSI resides.
Server |
Command Syntax |
1 |
msiexec /i mpf.msi /qn unattended=1 MPF_DOMAIN_INSTALL=1
MPFSVCPASSWORD=password MPFCLIENTPASSWORD=password
MPF_CONFIG_SERVER=virtual server name
MPF_TRANLOG_SERVER=virtual server name
MPF_AUDIT_SERVER=virtual server name RM_SERVER=virtual
server name MPFCONFIG=1 MPFTRANLOG=1 MPFAUDIT=1 MPFRMLOG=1 /l*v
setup.log |
2 |
msiexec /i mpf.msi /qn unattended=1 MPF_DOMAIN_INSTALL=1
MPFSVCPASSWORD=password
MPFCLIENTPASSWORD=password MPF_CONFIG_SERVER=virtual
server name
MPF_TRANLOG_SERVER=virtual server name MPFTRANLOG=1 /l*v
setup.log
Note Since server 2 is part of a cluster, it is necessary
to install the transaction log in order to automatically install
Provisioning Auditing an Recovery Service. |
3 |
msiexec /i mpf.msi /qn unattended=1 MPF_DOMAIN_INSTALL=1
MPFSVCPASSWORD=password
MPFCLIENTPASSWORD=password MPF_CONFIG_SERVER=virtual
server name RM_SERVER=virtual server name
MPFCORE=1 MPFCLIENT=1 MPFISAPI=1 MPFQUEUE=1 MPFRMBASE=1 MPFADMIN=1
REGISTRYPROV=1 ADPROV=1 SQLPROV=1
SCRIPTPROV=1 ERRORPROV=1 FILEPROV=1 SOAPPROV=1 COMMANDPROV=1
INSTALLERPROV=1 /l*v setup.log |
4 |
msiexec /i mpf.msi /qn UNATTENDED=1 MPF_DOMAIN_INSTALL=1
MPFSVCPASSWORD=password
MPFCLIENTPASSWORD=password MPF_CONFIG_SERVER=virtual
server name MPFADMIN=1 /l*v setup.log |
Removing MPF
You can remove or modify an MPF installation from Control Panel
Add/Remove Programs, Setup.exe, or the command line. For more
information, see Removing or
Modifying Components.
When removing MPF from a domain, there is a recommended order to
removing components.
- Remove all non-database components from the servers.
- Remove all database components. If they are all installed on
one computer, you can remove them simultaneously. Otherwise, remove
them one at a time, leaving the configuration database for
last.
- After removing the transaction log from server 1, fail over the
cluster to server 2 and run MPF uninstall from that server. This is
necessary to remove the Provisioning Auditing and Recovery Service
from both servers.
- If you intend to permanently remove MPF accounts, groups, and
databases, remove the TranLog group created in Cluster
Administrator.
See Also
Getting
Started, Single-Computer
CMSU_SPV_Develop_API_MPF--Deployment.xml