• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 121715, created on May 23, 2014, last review on Nov 7, 2014

  • Applies to:
  • Operations Automation 5.5

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.5.5 - POA 5.5.6
  • PBA for Linux 5.5.3 or later
  • PBA Application Package 5.5-5 or later
Important: The POA Management Node on Windows is not supported.

Fixed Issues

APSA-7278 Synchronization script fails with 'User with login XXXXXXXXX already exists' message.
APSA-4912 Simultaneous provisioning of Microsoft Office 365 Partner IUR and Office 365 Enterprise E3 (Trial) offers should be prohibited.
APSA-7156 Office 365 Dispatcher Application must authenticate incoming and outgoing connections of Microsoft cloud.

New Features and Changes

  • Auto-adding Domains to Office 365 Organization
  • German Language Is Supported
  • Support of MyCP
  • Support of Microsoft Office 365 Application in Service User Wizards
  • Improved Integration Between Microsoft Office 365 Application and PBA
  • New Parameter of Office 365 Application End-point Installation/Upgrade Script

Obtaining

Contact your Parallels Support account manager to obtain the new versions of the Microsoft Office 365 Application Package. The PBA 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 Application End-point

Before upgrading, prepare the following information:

The name of the Office 365 Dispatcher Site, the name of the Office 365 Dispatcher Application, the IP Address of the Office 365 Dispatcher Site. This can be done in the following way:

  1. Prepare the URL provided to Microsoft. This URL is structured in the following way: https://<Hostname_of_Office_365_Dispatcher_Site>/<Name_of_Office_365_Dispatcher_Application>/.
  2. Write down the name of the directory from the URL. This is the name of the Office 365 Dispatcher Application.
  3. Resolve the hostname from the URL into the IP address. This is the IP address of the Office 365 Dispatcher Site. Write down this IP address.
  4. Log on to the Office 365 Application End-point Host as Administrator via RDP.
  5. Open the Internet Information Services (IIS) Manager.
  6. Go to the list of sites.
  7. From the list, select the site with the IP address obtained above.
  8. Write down the name of the site. This is the name of the Office 365 Dispatcher Site.

The name of the Office 365 Gateway Site, the name of the Office 365 Gateway Application, the hostname of the Office 365 Gateway Site, the IP Address of the Office 365 Gateway Site. This can be done in the following way:

  1. Log in to Provider Control Panel.
  2. Go to Service > Applications and click the Microsoft Office 365 Application.
  3. Select the Instances tab and click the target Application Instance.
  4. Select the General tab.
  5. Obtain the value of the Application API end-point URI setting. This is a URL that is structured in the following way: https://<Hostname_of_Office_365_Gateway_Site>/<Name_of_Office_365_Gateway_Application>/aps/.
  6. Write down the name of the directory from the URL. This is the name of the Office 365 Gateway Application.
  7. Write down the hostname from the URL. This is the hostname of the Office 365 Gateway Site.
  8. Resolve the hostname from the URL into the IP address. This is the IP address of the Office 365 Gateway Site. Write down this IP address.
  9. Log on to the Office 365 Application End-point Host as Administrator via RDP.
  10. Open the Internet Information Services (IIS) Manager.
  11. Go to the list of sites.
  12. From the list, select the site with the IP address obtained above.
  13. Write down the name of the site. This is the name of the Office 365 Gateway Site.

Perform the upgrade procedure:

  1. Upload the Microsoft Office 365 Application Package to the Office 365 Application End-point 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. Run the .\setup.ps1 -DispatcherSiteName <The name of the Office 365 Dispatcher Site> -DispatcherAppName <The name of the Office 365 Dispatcher Application> -DispatcherIPAddress <The IP address of the Office 365 Dispatcher Site> -GatewaySiteName <The name of the Office 365 Gateway Site> -GatewayAppName <The name of the Office 365 Gateway Application> -GatewayIPAddress <The IP address of the Office 365 Gateway Site> -GatewaySiteCertSubject <The hostname of the Office 365 Gateway Site> -Force command.

Important: If you have several Office 365 Gateway Sites on the Office 365 Application End-point Host, use the provided above procedure to upgrade each Office 365 Gateway Site.

Note: If you need to update your client Microsoft certificate, you can do this in the following way: upload the new client Microsoft certificate to the Office 365 Application End-point Host; add -MSCertPath <path to certificate> to the command from step 5; run the command.

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. Upgrade existing Microsoft Office 365 Application instances. See POA Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.

Help Resources

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

All Office 365 Integration Release Notes

 

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF