The hardware and software requirements for installing Microsoft® Provisioning Framework are as follows.
Machines must have sufficient processing speed and RAM to support the version of Microsoft® Windows® used in the MPF implementation. The following table summarizes the minimum hardware requirements.
|Machine||Intel or compatible Pentium 166 MHz or higher.|
|Memory (RAM)||256 MB or more recommended (128 MB or more supported; 4 GB maximum).|
|Hard disk||20 MB or more recommended; the disk space required depends on the amount of data you want to store in the MPF databases.|
|Monitor||VGA or higher resolution.|
|Pointing device||Microsoft (or compatible) mouse.|
Software requirements vary considerably, depending on which MPF components are included in the install.
Requirements for a typical install
For evaluation and development, Setup has a Typical option that installs all MPF components except ISAPI Extension (SOAP ISAPI) and Sample Provisioning Website and Database. For more information, see Running Setup. The following software is required for a typical install. For a deployment scenario, see Single-Computer Deployment.
|Microsoft® Windows 2000 Server with Service Pack 2||Or later versions of Windows.|
|SQL Server 2000 with Service Pack 1
Microsoft® Data Engine (MSDE) 2000 with Service Pack 1
|Or later versions of SQL Server and MSDE.
If using MSDE, install as follows.
|Microsoft® Data Access Components (MDAC) version 2.61||Or later versions of MDAC.|
|Microsoft® Internet Information Server (IIS) version 5.0||Or later versions of IIS.|
Requirements for individual MPF components
MPF components are usually installed separately and distributed to multiple machines in a domain. (In this context, "domain" refers to a Microsoft® Active Directory® or Microsoft® Windows NT® domain, not an Internet domain.) For examples of domain and clustered deployments, see Deploying MPF.
Note In addition to the items listed below, most components require Windows 2000 Server with Service Pack 2 or later server operating systems. The Administration Tools and Client Components can be installed on machines running Windows 2000 Professional with Service Pack 2 or later operating systems.
|Administration Tools||Tools used to administer the MPF, such as Provisioning Manager (a graphical user interface), , and ProvTest.exe.||
|Audit (Log) Database||Optional SQL database that stores completed provisioning requests. You can also
use the audit log as a data-mining repository.
Important Set up at most one audit log per MPF deployment.
|Client Components||Server-based client that receives incoming provisioning
requests from users and routes them to provisioning engines and
managers. All installs automatically include the client.
In addition to handling load balancing, the client's SOAP ISAPI provides an HTTP/SOAP interface to MPF. The ISAPI should always run in an IIS virtual directory that has been configured for Secure Sockets Layer (SSL).
|Configuration Database||Stores configurations for , procedures, and
other definitions used in the framework.
Important Set up oneand only oneconfiguration database per MPF deployment. If you plan to install components on multiple machines in a domain, install the configuration database on one of the machines prior to installing other components.
|Core Components||Collection of MPF components that includes the provisioning
engine, test namespace, and supporting components for extended
error reporting and auditing.
Important If your installation will have multiple servers running Core Components, install the same MPF components on all of them. For example, if you install SQL Provider on one machine, install it on all machines. This is because any machine can end up processing a request. If a necessary component is missing, the request will fail.
|(Provisioning) Queue Manager Service||Manages provisioning requests that are queued for batch processing.||
|Resource Manager||Allocates machine resources. Resource Manager is a critical component for scalability and optimization. Resource Manager consists of two providers (the engine) and a database. The providers use special algorithms to optimize requests for system resources. The database stores information about system resources.||
|Sample Provisioning Web Site||Demonstrates how to use MPF. This sample site is operational only for stand-alone evaluation purposes.||The following must be installed on the same machine:
|Service Providers||Standard providers and namespaces that execute specific types of requests. For example, Active Directory Provider executes requests such as creating user directories in Active Directory.||
|Transaction Log Database||SQL database that stores active request transactions. If multiple databases are installed, MPF will load-balance between them.||