Search Engine: Elastic

Article ID: 130644, created on Apr 14, 2017, last review on Oct 25, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Business Automation 7.0
  • Business Automation 7.1

Table of Contents

Release Notes

You can read the complete Office 365 16.8 Release Notes here: http://download.automation.odin.com/poa/Office365_APS2/doc/87686.htm. Also, you can download the PDF version.

Dependencies and Pre-Requisites

The Office 365 Application Package requires:

  • Odin Automation 7.1.0 or a later 7.1.x version
  • Odin Automation 7.0.1_hf130748 or a later 7.0.x version

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

New Features and Changes

Advanced Subscription Split Mode is Added to Syndication-to-CSP Conversion Scripts

Now, service providers can convert Office 365 syndication subscriptions which contain not only Office 365 resources but also non-Office 365 resources with non-zero limits.

When this new mode is used, an Office 365 syndication subscription is converted in the following way: If the subscription has non-Office 365 resources with non-zero limits, the subscription is switched to a service plan including only non-Office 365 resources and then new Office 365 CSP subscriptions are created. If the subscription has only Office 365 resources or all non-Office 365 resources of the subscription have zero limits, the subscription is cancelled and then new Office 365 CSP subscriptions are created.

Odin Automation Office 365 Integration Provider's Guide >> Conversion from Syndication Partner Program to CSP Program > Advanced Subscription Split Mode

Processing Cloud Subscriptions of Terminated/Removed Office 365 Subscriptions is Improved

Now, a customer can have licenses which are concurrently included in discontinued Office 365 subscriptions (Status/Service Status is Terminated/Removed) and functioning Office 365 subscriptions (for instance, Status/Service Status is Active/Running).

This works in the following way:

  1. A customer buys an Office 365 subscription including one or more licenses. As a result, the Office 365 subscription is created in Odin Automation and a cloud subscription is created for each license in the Microsoft cloud.

  2. When the Office 365 subscription gets discontinued (Status/Service Status is Terminated/Removed), all the cloud subscriptions are unbound from the Office 365 subscription, suspended, and kept within 90 days.

  3. The customer buys a new Office 365 subscription including one or more licenses; some of the licenses are also included in the discontinued Office 365 subscription. As a result, the new Office 365 subscription is created in Odin Automation and a cloud subscription is either created or activated for each license in the Microsoft cloud. The licenses included in both the subscriptions are processed as follows:

    • If the corresponding cloud subscriptions still exist, they are activated and bound to the new Office 365 subscription.
    • If the corresponding cloud subscriptions are already removed, new cloud subscriptions are created and bound to the new Office 365 subscription.

Fixed Issues

  • APSA-18178 Missing <br/> in BM_ProvisioningParams.xml.
  • APSA-18155 During synchronization, APS resources 'Office 365 User' can be linked to APS resources 'Office 365 Domain' which have status 'aps:unprovisioning'.
  • APSA-18152 Syndication-to-CSP conversion of account with 2 syndication subscriptions fails with error 'Import data for the OSA subscription(s) [...] missed'.
  • APSA-18040 Service users are duplicated during Syndication-to-CSP conversion.
  • APSA-17903 CCPv2: 6-8 second delays for account with 5000 service users
  • APSA-17869 'Switch Office 365 Business to ProPlus License' task fails because change order is stuck in status 'WI'.
  • APSA-17713 Culture en-IQ is not supported in country IQ.
  • APSA-17594 Missing <br/> in BM_ProvisioningParams.xml.
  • APSA-17547 readCSPAccounts.py fails with error "Poco::Net::NoMessageException" in case of huge quantity of tenants (7000+).
  • APSA-17421 Synchronization fails with error "Subscription #xxx is locked" when master customer tenant is bound to terminated but not yet removed Odin Automation subscription.
  • APSA-18198 Names of error files generated by scripts completeMOSI2CSP.py and importSubsCSP.py are almost the same.

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.8 Release Notes here: http://download.automation.odin.com/poa/Office365_APS2/doc/87686.htm. Also, you can download the PDF version.

Known Issues and Limitations

Office 365 and Azure CSP resources cannot be sold in the same service template/service plan. You must use separate service templates/service plans for selling Office 365 and Azure CSP resources.

Obtaining

Contact your Odin Account Manager to obtain the new version 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 endpoint (collecting Office 365 dispatcher site parameters).
  2. Preparing necessary information for upgrading the Office 365 application endpoint (collecting Office 365 gateway site parameters).
  3. Stopping provisioning Office 365 services.
  4. Upgrading the Office 365 application endpoint.
  5. Upgrading the Office 365 application.
  6. Updating the OA Billing online store and control panel customizations.
  7. Starting provisioning Office 365 services.

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.8.5. Upgrading from versions that are lower than 16.8.5 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.odin.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 (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=89581.htm) 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 endpoint. 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 Endpoint 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 endpoint. 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 Endpoint 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 OA Operations, 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 OA Operations.
  4. Upgrade the Office 365 application endpoint:

    1. Upload the Office 365 application package to the Office 365 Application Endpoint 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.
    7. Run the iisreset command.

    Notes:

    • If you have several Office 365 gateway sites on the Office 365 Application Endpoint 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 Endpoint 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 Odin Automation. See OA Operations Provider's Guide >> Application Hosting > Managing Applications > Importing Application (https://download.automation.odin.com/pa/6.0/doc/portal/6.0/oa-provider/index.htm?fileName=1-25-01-02.htm) for details.

    2. Upgrade existing Office 365 application instances. See OA Operations Provider's Guide >> Application Hosting > Bulk Application Upgrades (https://download.automation.odin.com/pa/6.0/doc/portal/6.0/oa-provider/index.htm?fileName=67909.htm) for details.
  6. Update the OA Billing online store and control panel customizations:

    • If Odin Automation 7.0.x is used on your installation, make sure that the OA Billing online store and control panel customizations provided at https://kb.odin.com/en/129556 are installed.
    • If Odin Automation 7.1.x is used on your installation, make sure that the OA Billing online store and control panel customizations provided at https://kb.odin.com/en/130229 are installed.

    Important: After upgrading Odin Automation from 7.0.x to 7.1.x, you must update the OA Billing online store and control panel customizations using the instructions of the KB article https://kb.odin.com/en/130229.

  7. Start provisioning Office 365 services. For example, activate the Office 365 service template in OA Operations.

Upgrade Procedure (Cloud Solution Provider Scenario)

The upgrade procedure consists of the following steps:

  1. Preparing necessary information for upgrading the Office 365 application endpoint (collecting Office 365 gateway site parameters).
  2. Stopping provisioning Office 365 services.
  3. Upgrading the Office 365 application endpoint.
  4. Upgrading the Office 365 application.
  5. Updating the OA Billing online store and control panel customizations.
  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 16.8.5. Upgrading from versions that are lower than 16.8.5 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.odin.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 (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=89409.htm) 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 endpoint. 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 Endpoint 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 OA Operations, 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 OA Operations.
  3. Upgrade the Office 365 application endpoint:

    1. Upload the Office 365 application package to the Office 365 Application Endpoint 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.
    8. Run the iisreset command.

    Note: If you have several Office 365 gateway sites on the Office 365 Application Endpoint 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 Odin Automation. See OA Operations Provider's Guide >> Application Hosting > Managing Applications > Importing Application (https://download.automation.odin.com/pa/6.0/doc/portal/6.0/oa-provider/index.htm?fileName=1-25-01-02.htm) for details.

    2. Upgrade existing Office 365 application instances. See OA Operations Provider's Guide >> Application Hosting > Bulk Application Upgrades (https://download.automation.odin.com/pa/6.0/doc/portal/6.0/oa-provider/index.htm?fileName=67909.htm) for details.
  5. Update the OA Billing online store and control panel customizations:

    • If Odin Automation 7.0.x is used on your installation, make sure that the OA Billing online store and control panel customizations provided at https://kb.odin.com/en/129556 are installed.
    • If Odin Automation 7.1.x is used on your installation, make sure that the OA Billing online store and control panel customizations provided at https://kb.odin.com/en/130229 are installed.

    Important: After upgrading Odin Automation from 7.0.x to 7.1.x, you must update the OA Billing online store and control panel customizations using the instructions of the KB article https://kb.odin.com/en/130229.

  6. Start provisioning Office 365 services. For example, activate the Office 365 service template in OA Operations.

Help Resources

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 c0f836394088a28cc30dd0e5fe8b600e b2c3b33425dfc50c7d41a2efaa7f84f3 7c0b495571a6c1bec50e4f324a20ec14 0871c0b47b3b86ae3b1af4c2942cd0ce 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF