Article ID: 120904, created on Apr 4, 2014, last review on May 10, 2014

  • Applies to:
  • Operations Automation 5.3

Symptoms

After deploying Windows Provisioning Engine (WPE) to a Parallels Operations Automation (POA) 5.3 environment, all tasks started provisioning via this engine instead of WPE. As a result, all tasks fail with different errors.

There are several examples of such errors:

Error position:

    At C:\Program Files\Parallels\Windows Provisioning Engine\Providers\Common\ProviderUtils\ProviderUtils.psm1:53 char:26
+                       [void]$Context.Execute <<<< ($Provider, $Method, $exec_data)

Provisioning request failed. No 'SW Managed Exchange.GetPublicFolderActualSize' procedure found
    Type: Parallels.Wpe.Utils.WpeException.

   Provisioning request failed. Error in 'BESProvider.getUser'.
    Unable to execute any BlackBerry User Admin Tools:
      BES5: Target server not responding\n  BES4: BESUserAdmin tools not found

   Provisioning request failed. Error in 'SW Managed Exchange.GetMailboxActualSize'.
    Exception calling "Execute" with "3" argument(s): "remoteAccess"

   Provisioning request failed. No 'SW Managed Exchange.CleanDeletedObjectsFromOWKO' procedure found
    Type: Parallels.Wpe.Utils.WpeException.

   Provisioning request failed. No 'SW Managed Exchange.GetPublicFolderActualSize' procedure found
    Type: Parallels.Wpe.Utils.WpeException. 

Cause

In POA 5.3, WPE should not be deployed in one domain with MPS.

Resolution

According to the POA 5.3 Windows Hosting Infrastructure Deployment Guide, WPE can only be used to provide services of Exchange Server 2010 (Multi-Tenant mode), and WPE should be deployed in a separate domain.

If you deployed WPE as a preparative measure before upgrading to POA 5.4 or 5.5, it should be temporarily disabled by uninstalling the WindowsProvisioningEngine package from this host.

To do this, go to Deployment Director > Server Manager > Hardware Node, click on the required WPE node, switch to the Packages tab and click the cross near the package WindowsProvisioningEngine.

a8cdca46e4357a6e38fded820770e272 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF