Article ID: 128211, created on Feb 1, 2016, last review on Mar 9, 2016

  • Applies to:
  • Operations Automation 6.0
  • Business Automation 6.0

Table of Contents

Release Notes

You can read the complete Office 365 6.4 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/84699.htm. Also, you can download the PDF version.

Dependencies and Pre-Requisites

The Office 365 Application Package requires:

  • Operations Automation 6.0.6 or later
  • Business Automation 6.0.6 or later

Important: If Windows-based Branding Servers are used on your Service Automation installation, make sure the instructions of the https://kb.odin.com/en/122036 KB Article are performed.

Fixed Issues

  • APSA-14033 upgradeAPS1ToAPS2.py script fails with error "Subscription #50053800 is skipped because of error: 'NoneType' object has no attribute 'lower'".
  • APSA-14032 prepareUpgradeAPS1ToAPS2.py and upgradeAPS1ToAPS2.py scripts do not handle situation when unit of measure of storage resource in Business Automation is not KB.
  • APSA-13911 'Provisioning "AsyncOperation"' tasks fail with error "The transition is in progress: One or more errors occurred...".
  • APSA-14349 Task 'Provisioning "Tenant" for APS application Microsoft Office 365' fails with error 'Culture de-DE is not supported in country BE'.
  • APSA-14348 Task 'Provisioning "Tenant" for APS application Microsoft Office 365' fails with error 'Language sr is not supported in country RS'.
  • APSA-14183 Double domain name in CNAME DNS records for domains linked to Office 365 service.
  • APSA-14149 Task 'Provisioning "Migration" for APS application Office 365' fails with error "Error converting value {null} to type 'System.Boolean'. Path 'value[2].dirSyncEnabled', line 1, position 3538".
  • APSA-14111 Task 'Provisioning "Migration" for APS application Office 365' fails with error 'An item with the same key has already been added'.
  • APSA-14104 Script readCSPAccounts.py fails with error "Unexpected character encountered while parsing value: j. Path '', line 0, position 0".

Important: This section provides the list of fixed issues. To obtain the detailed description of a fixed issue, you must read the corresponding section of the complete release notes. You can read the complete Office 365 6.4 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/84699.htm. Also, you can download the PDF version.

New Features and Changes

New Optional Parameter storage-limit-recalc-coef of Scripts for Upgrading Subscriptions from APS 1.2 to APS 2

The scripts prepareUpgradeAPS1ToAPS2.py and upgradeAPS1ToAPS2.py base the conversion of the limits of storage APS 1.2 resources to gigabytes on the assumption that the KB unit of measure is used for these resources in Business Automation. If a custom unit of measure is used for these resources, this assumption is not valid and a coefficient must be specified to make conversion from the custom units to gigabytes. The coefficient is calculated in the following way: 1 / the number of gigabytes one custom unit includes.

Examples:

  • The 'Additional SharePoint Storage for Office 365 Business Essentials' resource is part of a composite resource. One unit of the composite resource includes 10 gigabytes of the 'Additional SharePoint Storage for Office 365 Business Essentials' resource. In this case the coefficient is 0.1.
  • The 'Additional SharePoint Storage for Office 365 Business Essentials' resource is a separate resource and the GB unit of measure is used for this resource. In this case the coefficient is 1.0.
  • The 'Additional SharePoint Storage for Office 365 Business Essentials' resource is a separate resource and the MB unit of measure is used for this resource. In this case the coefficient is 1024.0.

Important: This section provides the list of new features and changes. To obtain the detailed description of a new feature or change, you must read the corresponding section of the complete release notes. You can read the complete Office 365 6.4 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/84699.htm. Also, you can download the PDF version.

Obtaining

Contact your Odin Support account manager to obtain the new versions of the Office 365 Application Package.

Installation

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

Upgrade Procedure

Upgrade Procedure (Syndication Partner Scenario)

The upgrade procedure consists of the following steps:

  1. Preparing necessary information for upgrading the Office 365 Application End-point (collecting Office 365 Dispatcher Site parameters).
  2. Preparing necessary information for upgrading the Office 365 Application End-point (collecting Office 365 Gateway Site parameters).
  3. Stopping provisioning Office 365 services.
  4. Upgrading the Office 365 Application End-point.
  5. Upgrading the Office 365 Application.
  6. Starting provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-6 are mandatory.
  • Make sure the current version of the Office 365 Application is 6.4. Upgrading from versions that are lower than 6.4 is not supported.
  • Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deployment Architecture > Preparing SQL Server Databases for details.

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

  1. Prepare necessary information for upgrading the Office 365 Application End-point. You must prepare the name of the Office 365 Dispatcher Site, the name of the Office 365 Dispatcher Application, and 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 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.
  2. Prepare necessary information for upgrading the Office 365 Application End-point. You must prepare the name of the Office 365 Gateway Site, the name of the Office 365 Gateway Application, the hostname of the Office 365 Gateway Site, and 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 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 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.
  3. Stop provisioning Office 365 services:

    1. In Operations Automation, go to Operations > Tasks and make sure all Office 365 tasks are processed.
    2. Stop provisioning Office 365 services. For example, deactivate the Office 365 Service Template in Operations Automation.
  4. Upgrade the Office 365 Application End-point:

    1. Upload the Office 365 Application Package to the Office 365 Application End-point Host.
    2. Unpack the Application Package.
    3. Unblock the content of the O365-Web.zip file. To do this, right-click the file in Windows Explorer, click Properties, click Unblock, click OK.
    4. Unpack the O365-Web.zip file.
    5. Start Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
    6. Run the .\setup.cmd -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.

    Notes:

    • 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.
    • 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 provided above; run the command.
  5. Upgrade the Office 365 Application:

    1. Import the Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 Application instances. See Operations Automation Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.
  6. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Operations Automation.

Upgrade Procedure (Cloud Solution Provider Scenario)

The upgrade procedure consists of the following steps:

  1. Preparing necessary information for upgrading the Office 365 Application End-point (collecting Office 365 Gateway Site parameters).
  2. Stopping provisioning Office 365 services.
  3. Upgrading the Office 365 Application End-point.
  4. Upgrading the Office 365 Application.
  5. Starting provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-5 are mandatory.
  • Make sure the current version of the Office 365 Application is 6.4. Upgrading from versions that are lower than 6.4 is not supported.
  • Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing SQL Server Databases for details.

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

  1. Prepare necessary information for upgrading the Office 365 Application End-point. You must prepare the name of the Office 365 Gateway Site, the name of the Office 365 Gateway Application, the hostname of the Office 365 Gateway Site, and 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 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 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.
  2. Stop provisioning Office 365 services:

    1. In Operations Automation, go to Operations > Tasks and make sure all Office 365 tasks are processed.
    2. Stop provisioning Office 365 services. For example, deactivate the Office 365 Service Template in Operations Automation.
  3. Upgrade the Office 365 Application End-point:

    1. Upload the Office 365 Application Package to the Office 365 Application End-point Host.
    2. Unpack the Application Package.
    3. Unblock the content of the O365-Web.zip file. To do this, right-click the file in Windows Explorer, click Properties, click Unblock, click OK.
    4. Unpack the O365-Web.zip file.
    5. Upgrade the Office 365 CSP Component (csp-agent-war) to the latest version using the instruction of the https://kb.odin.com/en/126003 KB Article.
    6. Start Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
    7. Run the .\setup.cmd -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.

    Note: 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.

  4. Upgrade the Office 365 Application:

    1. Import the Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 Application instances. See Operations Automation Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.
  5. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Operations Automation.

Help Resources

Office 365 Integration Guides are available here: http://download.automation.odin.com/pa/.

All Office 365 Integration Release Notes

Supported APS Application Packages Versions in Operations Automation

Search Words

office 365

Office 365

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF