Domain CMSU_SPV_Develop_API_MPF--Deployment.xml
(3 Servers)
In a domain deployment, Microsoft® Provisioning
Framework (MPF) components can be distributed among servers in
a variety of ways. A common 3-server configuration is as
follows:
- Server 1: MPF database components
- Server 2: MPF components that process incoming requests
from a client server
- Server 3: Client server that processes incoming requests
and passes them to server 2
The following table illustrates the platform and MPF component
requirements for each server. For additional information on MPF
component dependencies, see System
Requirements.
Computer |
Platform |
MPF Components |
Server 1 |
- Member server
- SQL Server 2000 with Service Pack 1 (or greater)
|
|
Server 2 |
- Member server with Microsoft® Data Access Components (MDAC)
version 2.6 with Service Pack 1 (or greater)
|
|
Server 3 |
- Member server with MDAC 2.6 SP1 (or greater)
- Microsoft® Internet Information Server (IIS) version 5.0 (or
greater) 3
|
|
1 Prerequisite for all other non-database MPF components.
2 For running Microsoft
Provisioning Manager.
3 Required if ISAPI Extension is
installed as part of Client Components.
4 ISAPI Extension is required if the server will process SOAP
requests.
Deploying a 3-Server Configuration
The following instructions install MPF on three servers.
Important To successfully execute the following
instructions:
Before installing MPF on any computer, verify that Microsoft®
Active Directory® domain setup and DNS in Microsoft® Windows® are
configured and operational.
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 servers, you can verify the
deployment using the instructions in Testing an MPF
Install.
Installing MPF by running Setup.exe
Server 1:
- Launch Setup.exe.
- 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 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, , and Provisioning
Auditing and Recovery Service components. 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 these
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.
Server 2:
- Launch Setup.exe.
- 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 name of
the server for the configuration database and resource manager
database. (That is, enter the name of server 1.)
- 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:
- Launch Setup.exe.
- 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 name of
the server for the configuration database. (That is, enter the name
of server 1.)
- 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 .
Before executing an unattended install, copy the MPF.MSI file to
all three 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
MPF_IMPERSONATE=1 MPFSVCPASSWORD=password
MPFCLIENTPASSWORD=password MPFCONFIG=1 MPFTRANLOG=1
MPFAUDIT=1 MPFRMLOG=1 /l*v setup.log |
2 |
msiexec /i mpf.msi /qn unattended=1 MPF_DOMAIN_INSTALL=1
MPF_IMPERSONATE=1
MPFSVCPASSWORD=password MPFCLIENTPASSWORD=password
MPF_CONFIG_SERVER=name of Server 1
RM_SERVER=name of Server 1 MPFCORE=1 MPFCLIENT=1 MPFISAPI=1
MPFQUEUE=1 MPFRMBASE=1 REGISTRYPROV=1
ADPROV=1 SQLPROV=1 SCRIPTPROV=1 ERRORPROV=1 FILEPROV=1 SOAPPROV=1
COMMANDPROV=1 INSTALLERPROV=1
/l*v setup.log
Note If using ISAPI Extension, include the additional
parameters MPFISAPI=1 and
MPFCLIENTPASSWORD=password. |
3 |
msiexec /i mpf.msi /qn unattended=1 MPF_DOMAIN_INSTALL=1
MPF_IMPERSONATE=1
MPFSVCPASSWORD=password MPFCLIENTPASSWORD=password
MPF_CONFIG_SERVER=name of Server 1
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.
See Also
Clustered
CMSU_SPV_Develop_API_MPF--Deployment.xml (4 Servers), Getting Started,
Single-Computer
CMSU_SPV_Develop_API_MPF--Deployment.xml