Article ID: 117222, created on Sep 12, 2013, last review on Aug 12, 2014

  • Applies to:
  • Automation

Fixed Issues

APSA-5160 Office 365 Gateway error message should be more informative in case when subscriptions have not been provisioned yet.
APSA-5112 Incorrect MX records are created for Exchange Online.
APSA-5080 MOSI sends 60k VerifyDomain requests to MS.
APSA-5079 Integrate customizations into 4.x branch.
APSA-5246 Sometimes method get_mop_account does not report errors properly and synchronization script unprovides all Office 365 services from users.
APSA-5168 Log file is not created when synchronization script is executed.
APSA-5065 pem.activateSubscription works for several minutes because of database lock while providing several Office 365 services.

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.

Changes

  • Office 365 Subscription Downgrade is Automated
  • New Offers are Supported

Obtaining

The Microsoft Office 365 Application Package can be downloaded here.

Installation

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

Upgrade Procedure

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.
a Log in to PA Provider Control Panel, go to Services > Applications.
b Click on the name of the required Office 365 Application, and then select the Resource Types tab.
c Click on the name of the required 'Office 365 Application' Resource Type.
d Select the Activation Parameters tab, and then select the Global settings subtab.
e See the value of the URL for MOSI Connector global setting. It is structured in the following way: https://<Office365GatewayHostName>/<Office365GatewayApplicationName>/HTTPEndpoint.aspx.
f Write down the values of the Office365GatewayHostName and Office365GatewayApplicationName parameters.
g 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:
a Right-click the application item and click the Explore menu item in the context menu.
b 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:
a Put the Microsoft Office 365 Application Package on the Office 365 Gateway Host.
b Extract the O365-Web.zip file from the Microsoft Office 365 Application Package.
c Unpack the O365-Web.zip file.
d Start the Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
e 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.

1 Identify the required Office 365 Callbacks-Dispatcher Application:
a Obtain the URL specified in your syndication agreement with Microsoft. The URL is structured in the following way: https://<Office365GatewayHostName>/<Office365Callbacks-DispatcherApplicationName>/.
b Write down the values of the Office365GatewayHostName and Office365Callbacks-DispatcherApplicationName parameters.
c 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:
a Right-click the application item and click the Explore menu item in the context menu.
b 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:
a Put the Microsoft Office 365 Application Package on the Office 365 Gateway Host.
b Extract the O365-Web.zip file from the Microsoft Office 365 Application Package.
c Unpack the O365-Web.zip file.
d Start the Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
e 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:
a In the Internet Information Services (IIS) Manager, select the Office 365 Callbacks-Dispatcher Application.
b Right-click the application item and click the Explore menu item in the context menu.
c Create a copy of the Callbacks.svc file. Rename the copy to SubscriptionEvents.svc.

Updating Provisioning Gateway Host

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.

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.

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.

Help Resources

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

All Office 365 Integration Release Notes

caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF