Search Engine: Elastic

Article ID: 115830, created on Mar 26, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation

Windows Hosting Provisioning Infrastructure and Deployment

Provisioning System

POA may use two Provisioning Systems to provision Windows services like IIS, Exchange, SharePoint, etc to customers:

  • Microsoft Provisioning System (MPS, or HMC (Hosted Messaging and Collaboration))
  • Parallels Windows Provisioning Engine
In the current version POA may use only MPS to provision IIS hosting services to customers. Refer to the Windows Infrastructure Deployment Guide for more details about supported Provisioning Systems for different Windows services - Deploying Windows Hosting Infrastructure.
The picture below demonstrates how requests are being sent between POA, MPS and the target IIS server:


POA management node generates XML request passing the next parameters to the POA Agent (pleskd.exe) on the managed IIS server:

  • XML string
  • References to Namespaces
  • References to Procedures
POA Agent forwards the request to the locally installed MPS Provisioning Client which performs the next actions:

  • Receives requests and forwards XML requests to the MPS Provisioning Engine
  • Returns the results back to the requester after the provisioning system executes the request
Provisioning Engine on the MPS server does the following actions:

  • Accepts XML requests and activates necessary Namespaces and Procedures stored in the MPS configuration database (MS SQL database)
  • Activates the MPS Provider which is responsible for the particular hosted service
The corresponding MPS Provider executes the hosting request by means of low-level API calls to the corresponding hosted application, IIS in particular.
Then, results of request are being sent back through all components in the chain to POA Management Node which marks corresponding provisioning task as Completed or Failed.
All provisioning requests from POA to Provisioning System may be traced for troubleshooting purposes, use the proper Knowledgebase article to do this:

POA provides own (custom) providers for the Microsoft Provisioning System, they take into account POA-specific aspects during services provisioning. Corresponding POA package 'MPFCustomProviders' should be installed on POA-managed MPS server.

MPS Provisioning Client has to be installed on all hosting servers managed by MPS, corresponding POA package is 'MPFProviderClients'.

Active Directory

POA is using Active Directory (AD) for all Windows-related services. During creating subscription with any Windows service POA creates corresponding Organizational Unit (OU) in AD. The name of an OU is being generated automatically in accordance with the template defined in POA Provider Control Panel at System Director > Configuration Manager > Auto-generated Names, it may be based on subscription ID, customer ID or customer company name.

POA creates as many OU in AD for a single customer as many subscriptions with Windows services a customer has. It is natural to configure POA to name OU in AD based on subscription ID (it is unique), in this case it will be easy to find the exact OU in AD in case customer has many subscriptions with Windows services.

The picture below demonstrates mapping between POA objects (Provider, resellers, customers, subscriptions) and corresponding AD objects (OUs):


Notes to the picture above:

  • All POA objects are located within single OU in AD, its name is usually 'Hosting'.
  • POA creates separate OU for Provider and for every single reseller
  • Structure of resellers' OUs in AD is plain, all resellers' OUs are created within the root 'Hosting' OU, POA does not create nested OUs for sub-resellers of a reseller
  • Customers' OUs are being created in the OU of their vendor
  • A single customer may have multiple OUs in AD if they have many subscription with Windows services

See the main Knowledgebase article #115790 Website Hosting: General information, Best Practices and Troubleshooting for more information.

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF