The replacement deployment scenario describes how to substitute Microsoft Provisioning System (MPS) for your existing provisioning system. Your decision to do so might coincide with the release of a new services offering. You might also simply need to reduce operational costs by making use of the flexibility of MPS instead of employing manual or scripted provisioning methods, which are generally costly and inefficient.
In your existing system, you might have a Web-based control console or a Microsoft Windows-based application that you want to continue to use to call into the provisioning system. Moreover, you might be planning to create a new control console for your new provisioning system. Whether you want to leverage your existing Web-based control panel or create a new one, you will need to integrate the functionality into these applications for programmatically calling the MPF Client. This will facilitate the submission of XML requests into MPS. If you want to create a new ASP.NET-enabled, Web-based control panel, you must use the MPF Client .NET Wrapper to generate a base XML request that can be submitted to the Provisioning Engine through the MPF COM Client object. Otherwise, if you do not want to implement a .NET application, your Web service can utilize Active Server Pages (ASP) and VBScript technologies to call the MPF Client.
For the replacement scenario, refer to New Installation Deployment Scenario for a sample MPS configuration.