Article ID: 124938, created on Mar 19, 2015, last review on Apr 30, 2015

  • Applies to:
  • Operations Automation 5.5

Fixed Issues

  • APSA-10906 The 2-way sync process removes the admin@ users that have been previously synced into PA
  • APSA-10467 Switching license assigned to user fails when source and target licenses have the same Provisioning ID.
  • APSA-10382 Method SetSubscriptionQuantity fails with error SubscriptionDisabledFault.
  • APSA-10238 Usage location Serbia is shown in incorrect order in Customer Control Panel.
  • APSA-10059 Sync script error: 'Error: Ambiguous license assignment for Offer'.
  • APSA-6817 Sync script fails with 'Domain name conflicts with existing domain' error.

Release Notes

Full release notes can be downloaded as PDF or viewed online.

Dependencies and Pre-Requisites

The Microsoft Office 365 Application Package requires POA 5.4.4 or later.

New Features and Changes

License Priority is Added

Obtaining

The Microsoft Office 365 Application Package can be downloaded from attachements of the KB.

Installation

To install the Microsoft Office 365 Application, use the instructions provided in the PA Office 365 Integration Provider's Guide.

Upgrade Procedure


Important: If you upgrade your Microsoft Office 365 Application to 4.16, do not forget to replace the synchronization script with the latest version.

To upgrade an existing installation of the Microsoft Office 365 Application, perform the following steps:

Upgrading Office 365 Gateway Application

  1. Identify the required Office 365 Gateway Application:
    Important: A single PA installation may use several Office 365 Gateway Applications on an Office 365 Gateway Host. So, you must identify and upgrade each Office 365 Gateway Application separately.
    1. Log in to PA Provider Control Panel, go to Services > Applications.
    2. Click on the name of the required Office 365 Application, and then select the Resource Types tab.
    3. Click on the name of the required 'Office 365 Application' Resource Type.
    4. Select the Activation Parameters tab, and then select the Global settings subtab.
    5. See the value of the URL for MOSI Connector global setting. It is structured in the following way: https://<Office365GatewayHostName>/<Office365GatewayApplicationName>/HTTPEndpoint.aspx.
    6. Write down the values of the Office365GatewayHostName and Office365GatewayApplicationName parameters.
    7. Obtain the IP address to which the Office365GatewayHostName is resolved via DNS.
  2. Log on to the required Office 365 Gateway Host as Administrator via RDP.
  3. Open the Internet Information Services (IIS) Manager.
  4. Select the site, which has the IP address obtained at step 1. Write down the name and IP address of the site.
  5. Select the application, which has the name obtained at step 1.
  6. Validate that the selected application is the required Office 365 Gateway Application:
    1. Right-click the application item and click the Explore menu item in the context menu.
    2. Verify that the SubscriptionEvents.svc file is listed among others in the displayed application root directory.
      Important: If there is no the SubscriptionEvents.svc file, contact Parallels support.
  7. Upgrade the required Office 365 Gateway Application:
    1. Put the Microsoft Office 365 Application Package on the Office 365 Gateway Host.
    2. Extract the O365-Web.zip file from the Microsoft Office 365 Application Package.
    3. Unpack the O365-Web.zip file.
    4. Start the Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
    5. Execute the setup.ps1 -SiteName <Office 365 Gateway site name> –IPAddress <IP address of the Office 365 Gateway site> -GatewayAppName <Office 365 Gateway Application name> command.
      Note: You may use the -MOSIBaseURL, -MOSIBillingID, -MOSIClientCertSubject options to override the appropriate MOSI settings of the installed Office 365 Gateway and Office 365 Callbacks-Dispatcher Applications.
Upgrading Office 365 Callbacks-Dispatcher Application

Important: If your PA installation uses the Single Office 365 Gateway Application topology, skip the steps provided below. To learn more about the supported topologies, refer to PA Office 365 Integration Provider's Guide >> Deploying Office 365 Application > Preparing Provisioning Gateway Host and Office 365 Gateway Host > Office 365 Gateway Host.

Important: If the Office 365 Callback-Dispatcher Application (Microsoft Office 365 Application Package version 4.x) was replaced with the Office 365 Dispatcher Application (Microsoft Office 365 Application Package version 5.x), do not upgrade it using files from the Microsoft Office 365 Application Package version 4.x. It must be upgraded with corresponding files from the Microsoft Office 365 Application Package version 5.x.
  1. Identify the required Office 365 Callbacks-Dispatcher Application:
    1. Obtain the URL specified in your syndication agreement with Microsoft. The URL is structured in the following way: https://<Office365GatewayHostName>/<Office365Callbacks-DispatcherApplicationName>/.
    2. Write down the values of the Office365GatewayHostName and Office365Callbacks-DispatcherApplicationName parameters.
    3. Obtain the IP address to which the Office365GatewayHostName is resolved via DNS.
  2. Log in to the required Office 365 Gateway as Administrator via RDP.
  3. Open the Internet Information Services (IIS) Manager.
  4. Select the site, which has the IP address obtained at step 1. Write down the name and IP address of the site.
  5. Select the application, which has the name obtained at step 1.
  6. Validate that the selected application is the required Office 365 Callbacks-Dispatcher Application:
    1. Right-click the application item and click the Explore menu item in the context menu.
    2. Verify that the Callbacks.svc file is listed among others in the displayed application root directory.
      Important: If there is no the Callbacks.svc file, contact Parallels support.
  7. Upgrade the required Office 365 Callbacks-Dispatcher Application:
    1. Put the Microsoft Office 365 Application Package on the Office 365 Gateway Host.
    2. Extract the O365-Web.zip file from the Microsoft Office 365 Application Package.
    3. Unpack the O365-Web.zip file.
    4. Start the Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
    5. Execute the setup.ps1 -SiteName <Office 365 Gateway site name> –IPAddress <IP address of the Office 365 Gateway site> -DispatcherAppName <Office 365 Callbacks-Dispatcher Application name> command.
      Note: You may use the -MOSIBaseURL, -MOSIBillingID, -MOSIClientCertSubject options to override the appropriate MOSI settings of the installed Office 365 Gateway and Office 365 Callbacks-Dispatcher Applications.
  8. Check your syndication agreement with Microsoft. If you provided to Microsoft the URL where a file name was specified (https://office365.provider.com/Office365/SubscriptionEvents.svc), you must perform the following actions:
    1. In the Internet Information Services (IIS) Manager, select the Office 365 Callbacks-Dispatcher Application.
    2. Right-click the application item and click the Explore menu item in the context menu.
    3. Create a copy of the Callbacks.svc file. Rename the copy to SubscriptionEvents.svc.
Updating Provisioning Gateway Host
  1. Starting with PA Office 365 Integration 4.0, provisioning scripts of the Microsoft Office 365 Application use the HTTP_Request2 PEAR Package. Make sure this PEAR Package is installed on the Provisioning Gateway Host following these steps:
    1. Log on to the Provisioning Gateway Host.
    2. Validate that the HTTP_Request2 PEAR Package is in the list of installed PEAR Packages using the pear list command. Otherwise, execute the pear install HTTP_Request2 command.
    3. If you have Application instances with versions lower than 4.0, make sure the HTTP_Request PEAR Package is in the list of installed PEAR Packages.
  2. Note: To install the HTTP_Request2 PEAR Package, the latest PEAR is required. To obtain the latest PEAR, download and execute the http://pear.php.net/go-pear.phar script. For example, execute the wget http://pear.php.net/go-pear.phar and php go-pear.phar commands. This script installs the latest PEAR or it upgrades the installed PEAR to the latest version.
  3. Make sure the max_input_vars parameter is set to 3000 in the php.ini file.
  4. If you need support for non-latin characters and you have version 4.11 of higher of the Microsoft Office 365 Application, perform the instructions of the https://kb.odin.com/en/123198 KB article.
Upgrading Microsoft Office 365 Application
  1. Import the Microsoft Office 365 Application Package to PA. See POA Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
  2. Make sure in the 'Office 365 Application' Resource Types the Autoprovisioning parameter is set to Yes for the Application service "Administration".
  3. Upgrade existing Microsoft Office 365 Application instances. See POA Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.
  4. If the script synchronizing changes applied in the Microsoft Online Services Portal to PA is used on your installation, the Empty Service Set Application Service Resource Type must be created. The Included Offers Activation Parameter must be set to 00000000-0000-0000-0000-000000000000. The Trial Offer ID Activation Parameter must be set to 00000000-0000-0000-0000-000000000000. See the PA Office 365 Integration Provider's Guide >> Configuring Offers > Creating Application Service Resource Type to obtain the instruction how to create Application Service Resource Types. The Empty Service Set Application Service Resource Type must be included into existing Office 365 Service Templates and existing Office 365 subscriptions must be updated accordingly.
  5. Perform the instructions of the https://kb.odin.com/117505 KB article.
Deploying New Features

The following table provides the list of features, that are not deployed automatically during the upgrade. These features must be deployed and configured manually after upgrading the Microsoft Office 365 Application. If you would like to get Professional Services assistance in deploying and configuring these features, please contact your Account Manager at Parallels.

Application Version Feature Instruction
2.0 Ability to Specify Custom Office 365 Subdomain Is Added See PA Office 365 Integration Provider's Guide >> Finalizing Office 365 Application Deployment > Configuring PBA for Custom Office 365 Subdomains.
3.0 Synchronization with Microsoft Online Services Portal Is Supported Install and configure the synchronization script. See PA Office 365 Integration Provider's Guide >> Finalizing Office 365 Application Deployment > Synchronizing Changes Applied in Microsoft Online Services Portal to PA for details.
4.0 Office 365 Wave 15 Offers Are Supported Create Application Service Resource Types for new Office 365 offers. See PA Office 365 Integration Provider's Guide >> Configuring Offers for details.
4.1 Improved Handling of Subscriptions It is recommended to specify the Administrator's login for connecting to Microsoft Online and Administrator's password for connecting to Microsoft Online activation parameters in Application Resource Types. See PA Office 365 Integration Provider's Guide >> Configuring Offers > Creating Office 365 Application Resource Type for details.
4.6 Office 365 Subscription Downgrade is Automated Turn off the downgrade report script if it is used on your PA installations. See https://kb.odin.com/en/112959 for details.
4.6 New Offers are Supported Create Application Service Resource Types for new Office 365 offers. See PA Office 365 Integration Provider's Guide >> Configuring Offers for details.

Help Resources

PA Office 365 Integration Guides are available here: http://download.pa.parallels.com/poa/.

All Office 365 Integration Release Notes

Supported APS Application Packages Versions in POA

Search Words

Office 365 4.16

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF