CloudBlue Technical Support

This version of the application reached its end of life. We recommend that you upgrade to the latest supported version of the application. To obtain the latest supported version, see this article.

Table of Contents

• Release Notes
• Dependencies and Pre-Requisites
• Fixed Issues
• Obtaining
• Installation
• Upgrade Procedure
  • Upgrade Procedure (Syndication Partner Scenario)
  • Upgrade Procedure (Cloud Solution Provider Scenario)
• Help Resources

Release Notes

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

Dependencies and Pre-Requisites

The Office 365 Application Package requires:

• Odin Automation 6.0.7 or a later 6.0.x version

Important:

• If Odin Automation billing 6.0.7 is used on your installation, perform the instruction of the https://kb.cloudblue.com/en/128704 KB article.
• After upgrading Odin Automation from 6.0.x to 7.0.x, the Office 365 app must be immediately upgraded from 16.6.x to 16.8.x (see the allowed upgrade paths for the app in the KB article at https://kb.cloudblue.com/en/130752).
• Starting with Odin Automation 7.0.0 the new branding implementation is used (see http://download.automation.odin.com/oa/7.0/oapremium/portal/en/release_notes/index.htm?fileName=about.htm#o86067 for details). This change affects the Office 365 Application (see http://download.automation.odin.com/oa/7.0/oapremium/portal/en/upgrade_workflow/87663.htm and http://download.automation.odin.com/oa/7.0/oapremium/portal/en/upgrade_workflow/87658.htm for details). You must back up and restore the respective Office 365 data when migrating brands.

Fixed Issues

• APSA-15547 FORCE_CHANGE_PASSWORD_NEXT_LOGIN setting is added.
• APSA-15509 Please recheck BM_ProvisioningParams.xml from https://kb.cloudblue.com/en/128653.
• APSA-15405 "Violation of PRIMARY KEY constraint 'PK_Customer'. Cannot insert duplicate key in object 'dbo.Customer'" appears when tenant is created.
• APSA-13980 Provisioning Office 365 subscription fails with error "Domain already exists".
• APSA-15849 Permanent fix for issue "Office 365 unprovisioning tenant task gets stuck due to error 'Object reference not set to an instance of an object'".
• APSA-15811 Online store & control panel customizations were updated in Office 365 16.6.
• APSA-15808 [Online Store] String "Please type longer subdomain" cannot be localized.
• APSA-15788 en_US locale errors.
• APSA-15406 Processing order fails with "Invalid value passed for setting 'subdomain': Value must be no longer than 25 characters..." error.
• APSA-14945 Tenant creation fails with error "Unable to register MS Account ID ...: the ID ... has been already registered for APS Account ...".
• APSA-13408 Parent license unprovisioning causes add-on license unprovisioning.
• APSA-15514 Office 365 synchronization cannot add new user if country of user in Office 365 Portal is different from country in Utils.cs.
• APSA-15432 Newly created Office 365 subscriptions are not subscribed to events related to onSubscriptionChanged.
• APSA-15380 importSubsCSP.py script incorrectly uses Odin Automation billing API.
• APSA-15362 [Syndication Partner Scenario] Customers purchasing Office 365 are prompted to use existing MS account.
• APSA-15875 readCSPAccounts.py fails with error "Unable to prepare the import data because of error: The appropriate service plan can not be found."

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 16.6 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/86178.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 Odin 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. Updating the Odin Automation billing online store and control panel customizations.
7. Starting provisioning Office 365 services.
8. Performing additional upgrade actions.

Important:

• The upgrade procedure is not reversible.
• Upgrade steps 1-8 are mandatory.
• Make sure the current version of the Office 365 Application is 16.5.x. Upgrading from versions that are lower than 16.5.x is not supported.
• Before upgrading the Office 365 application from one version to another one, make sure that you are going to follow the allowed upgrade paths. See the KB article https://kb.cloudblue.com/en/130752 for details.
• Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Odin 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 Odin 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 Odin 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.

5. 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.

6. Upgrade the Office 365 Application:

   1. Import the Office 365 Application Package to Odin Automation. See OA Operations Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
   2. Upgrade existing Office 365 Application instances. See OA Operations Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.

7. Update the Odin Automation billing online store and control panel customizations on your installation. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for Odin Automation billing Online Store and Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for Odin Automation billing Control Panel for details.

   Important: If Odin Automation billing 6.0.7 is used on your installation, make sure the instruction of the https://kb.cloudblue.com/en/128704 KB article is performed.

8. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Odin Automation.

9. Perform the following additional upgrade actions:

   1. Update all existing Office 365 Service Templates:

      1. In Provider Control Panel, go to Products > Service Plans.
      2. Select the Service Templates tab.
      3. Click on the required Service Template.
      4. Click Edit.
      5. Set Destroy Service on Cancel to No (the checkbox is clear).
      6. Click Save.

   2. Note: If the Office 365 Service Template you selected is intended for a Test in Production (TIP) account, you can speed up resource cleanup of the TIP account by setting up Destroy Service on Cancel to Yes.

   3. Run the fixLimitChangeSubscription.py script using the instruction of the https://kb.cloudblue.com/en/126337 KB article.

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. Updating the Odin Automation billing online store and control panel customizations.
6. Starting provisioning Office 365 services.
7. Performing additional upgrade actions.

Important:

• The upgrade procedure is not reversible.
• Upgrade steps 1-7 are mandatory.
• Make sure the current version of the Office 365 Application is 16.5.x. Upgrading from versions that are lower than 16.5.x is not supported.
• Before upgrading the Office 365 application from one version to another one, make sure that you are going to follow the allowed upgrade paths. See the KB article https://kb.cloudblue.com/en/130752 for details.
• Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Odin 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 Odin 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 Odin 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.cloudblue.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.

4. 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.

5. Upgrade the Office 365 Application:

   1. Import the Office 365 Application Package to Odin Automation. See OA Operations Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
   2. Upgrade existing Office 365 Application instances. See OA Operations Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.

6. Update the Odin Automation billing online store and control panel customizations on your installation. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Odin Automation billing Online Store and Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Odin Automation billing Control Panel for details.

   Important: If Odin Automation billing 6.0.7 is used on your installation, make sure the instruction of the https://kb.cloudblue.com/en/128704 KB article is performed.

7. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Odin Automation.

8. Perform the following additional upgrade actions:

   1. Update all existing Office 365 Service Templates:

      1. In Provider Control Panel, go to Products > Service Plans.
      2. Select the Service Templates tab.
      3. Click on the required Service Template.
      4. Click Edit.
      5. Set Destroy Service on Cancel to No (the checkbox is clear).
      6. Click Save.

   2. Note: If the Office 365 Service Template you selected is intended for a Test in Production (TIP) account, you can speed up resource cleanup of the TIP account by setting up Destroy Service on Cancel to Yes.

   3. Run the fixLimitChangeSubscription.py script using the instruction of the https://kb.cloudblue.com/en/126337 KB article.

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 Odin Automation

Office 365 and Azure CSP Subdomain Form for Odin Automation billing Control Panel (Customization Files)

Office 365 and Azure CSP Subdomain Form for Odin Automation billing Online Store (Layout Template Customizations)

[Odin Automation Premium] [Office 365] Allowed Upgrade Paths

Internal content

Link on internal Article