Administering the configuration database

The configuration database requires very little administration. Most changes to the configuration database are made automatically when you make changes to the individual components of Microsoft Provisioning Framework (MPF), including provisioning servers, namespaces, and credentials.

You can, however, change the way that the database is implemented. By default, Microsoft Provisioning Framework (MPF) uses the configuration database on the local computer. If you have an MPF installation that crosses multiple domains or forests, and you also have appropriate trusts configured across those domains or forests, the configuration database can be located in another domain. To use a configuration database in a different domain, you can use Provisioning Manager to specify the location of the configuration database to which MPF should connect.

Caution

• All Microsoft Provisioning Framework (MPF) databases, including MPFConfig, MPFAudit, MPFTranLogData, MPFSample, and Resource Manager, are SQL databases. The only database you should access directly in SQL, however, is the MPFAudit database. Directly accessing the MPFConfig, MPFTranLogData, MPFSample, and Resource Manager databases can cause database corruption, transaction processing errors, and the loss of data. Access these databases using Provisioning Manager or Configuration Database Windows Management Instrumentation (WMI) Provider only.
• SQL authentication mode must be configured to use the integrated mode, which uses both Windows authentication and SQL Server authentication, not just SQL authentication.

For more information, see Configuration database and To change the configuration database to which Microsoft Provisioning Framework connects.