Article ID: 129354, created on Aug 31, 2016, last review on Oct 19, 2016

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0

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.0.0 or later.

Important:

Fixed Issues

  • APSA-16473 [CCP v2] 'Office 365' tab is not shown in MyCP.
  • APSA-16561 New OA Billing control panel and online store customizations must be used for Office 365 16.8.1.
  • APSA-16285 [CCP v2] Wizard "Buy more licenses" gets stuck when composite resources are used.
  • APSA-16548 Manual deployment instruction does not contain step about resource type "Office 365 Tenant Contact Data".
  • APSA-16514 Office 365 application instance settings are not shown after upgrading application.

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 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 (From Version 16.6.x, 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. Configuring access to the OA Operations Public API.
  4. Stopping provisioning Office 365 services.
  5. Upgrading the Office 365 Application End-point.
  6. Running the upgradeResourceSettings16-6To16-8.py upgrade script.
  7. Upgrading the Office 365 Application.
  8. Updating the configuration of Office 365 Resources, Office 365 Service Templates and Office 365 Service Plans.
  9. Running the addTenantCountersToSubscriptions.py upgrade script.
  10. Adding the Office 365 Tenant Contact Data Resource Type.
  11. Updating the Odin Automation billing online store and control panel customizations.
  12. Updating the trial subscription checker.
  13. Starting provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-13 are mandatory.
  • Make sure the current version of the Office 365 Application is 16.6.x. Upgrading from versions that are lower than 16.6.x is not supported.
  • 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=86229.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 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. Configure access to the OA Operations Public API:

    1. Allow access from the Office 365 Application End-point Host to the OA Operations Public API. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deployment Architecture > Preparing Odin Automation Public API User (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86260.htm) for details.

    2. Specify the Operations Automation OpenAPI URL, User name for connecting to Operations Automation API, and User password for connecting to Operations Automation API settings of the target Application Instance. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deployment Architecture > Preparing Odin Automation Public API User (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86260.htm) and Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deploying 'Office 365' Application > Creating 'Office 365' Application Instance (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86275.htm) for details.
  4. 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.
  5. 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.
  6. Run the upgradeResourceSettings16-6To16-8.py upgrade script:

    1. Upload the Office 365 Application Package to the Management Node.
    2. Unpack the Application Package and go to the directory containing the Application Package content.
    3. Unpack the O365-Import.zip file.
    4. Go to the directory containing the content of the file.
    5. Run the script. For example: python upgradeResourceSettings16-6To16-8.py

    Important: If you forget to run the upgradeResourceSettings16-6To16-8.py upgrade script, the upgrade of the Office 365 Application will fail.

  7. Upgrade the Office 365 Application:

    1. Import the Office 365 Application Package to Odin Automation. See Odin Automation 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 Odin Automation 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.

    If the tasks 'APS application 'Office365', id XXX : updating upgrade relations for APS packages of application' fail with a message about the upgradeResourceSettings16-6To16-8.py script, try performing the following steps:

    1. Make sure none of the existing Office 365 Application Instances are upgraded.

    2. Remove version 16.8.1 of the Office 365 Application Package from Odin Automation.

    3. Run the upgradeResourceSettings16-6To16-8.py script as described above.

    4. Import version 16.8.1 of the Office 365 Application Package and upgrade the existing Office 365 Application Instances.
  8. Update the configuration of Office 365 Resources, Office 365 Service Templates and Office 365 Service Plans by running the autoconf.py script. The script does the following:

    • It sets up the units of measure of 'Office 365 License' and 'Office 365 Add-on' Resources. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Offers > Setting Up Units of Measure for 'Office 365 License' and 'Office 365 Add-on' Resources (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86753.htm) for details.

    • It adds the o365_based_on_email Service Parameter to Office 365 Service Templates. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Offers > Creating 'Office 365' Service Template (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86222.htm) for details.

    • It adds the Resource Type Office 365 Tenant Contact Data to Office 365 Service Templates (Application Service = TenantContactData, Automatically provision service = Off).

    See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Offers (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86212.htm) to obtain the instruction on how to run the script.

  9. The addTenantCountersToSubscriptions.py upgrade script adds the auxiliary Total points sold and Total seats sold Resource Types to Office 365 Service Templates and Subscriptions.

    Run the script for the Office 365 Application:

    1. Prepare the identifier of the Application (for example, go to Services > Applications).
    2. Make sure the addTenantCountersToSubscriptions.py script is uploaded to the Management Node. The addTenantCountersToSubscriptions.py script has the same location as the upgradeResourceSettings16-6To16-8.py script (see the corresponding step above).
    3. Run the script:

      python addTenantCountersToSubscriptions.py --o365-app-id O365_APP_ID
      

    The script processes all Service Templates and Subscriptions for each Application Instance of the Application. The suitable Total points sold and Total seats sold Resource Types are automatically found.

    Notes:

    1. It is possible to run the script for a specific Application Instance by using the --o365-app-instance-id option. In this case the script processes all Service Templates and Subscriptions of the specified Application Instance. The suitable Total points sold and Total seats sold Resource Types are automatically found. For example:

      python addTenantCountersToSubscriptions.py --o365-app-instance-id O365_APP_INST_ID
      
    2. When running the script for a specific Application Instance, it is also possible to specify the auxiliary Total points sold and Total seats sold Resource Types the script must use. The required Resource Types are specified by using the --o365-points-counter-rt-id and --o365-seats-counter-rt-id options. For example:

      python addTenantCountersToSubscriptions.py --o365-app-instance-id O365_APP_INST_ID --o365-points-counter-rt-id TOTAL_POINTS_SOLD_RT_ID --o365-seats-counter-rt-id TOTAL_SEATS_SOLD_RT_ID
      
  10. Create the Office 365 Tenant Contact Data Resource Type if it does not exist. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Offers > Creating Office 365 Resource Types > Creating Auxiliary Resource Types (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86300.htm) and Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Offers > Creating 'Office 365' Service Template (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86222.htm) for details.

    Then, add the Resource Type to all the Office 365 Service Templates and their Subscriptions. You can use instructions of the https://kb.odin.com/en/123749 KB article to do this.

  11. Update the OA 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 OA Billing Online Store (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86301.htm) and Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for OA Billing Control Panel (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86303.htm) for details.

  12. Update the script3.js file of the trial subscription checker. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Odin Automation billing Customer Control Panel for Trial Subscriptions (http://download.automation.odin.com/poa/Office365_APS2/doc/86307.htm) for details. Note, you must obtain the updated content of the script3.js file from the section provided above.

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

Upgrade Procedure (From Version 16.6.x, 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. Configuring access to the OA Operations Public API.
  4. Upgrading the Office 365 Application End-point.
  5. Running the upgradeResourceSettings16-6To16-8.py upgrade script.
  6. Upgrading the Office 365 Application.
  7. Updating the configuration of Office 365 Resources, Office 365 Service Templates and Office 365 Service Plans.
  8. Running the addTenantCountersToSubscriptions.py upgrade script.
  9. Adding the Office 365 Tenant Contact Data Resource Type.
  10. Updating the Odin Automation billing online store and control panel customizations.
  11. Starting provisioning Office 365 services.
  12. Configuring new offers.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-12 are mandatory.
  • Make sure the current version of the Office 365 Application is 16.6.x. Upgrading from versions that are lower than 16.6.x is not supported.
  • 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/86383.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 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. Configure access to the OA Operations Public API:

    1. Allow access from the Office 365 Application End-point Host to the OA Operations Public API. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing Odin Automation Public API User (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86425.htm) for details.

    2. Specify the Operations Automation OpenAPI URL, User name for connecting to Operations Automation API, and User password for connecting to Operations Automation API settings of the target Application Instance. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing Odin Automation Public API User (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86425.htm) and Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deploying 'Office 365' Application > Creating 'Office 365' Application Instance (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86446.htm) for details.
  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. 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.

  5. Run the upgradeResourceSettings16-6To16-8.py upgrade script:

    1. Upload the Office 365 Application Package to the Management Node.
    2. Unpack the Application Package and go to the directory containing the Application Package content.
    3. Unpack the O365-Import.zip file.
    4. Go to the directory containing the content of the file.
    5. Run the script. For example: python upgradeResourceSettings16-6To16-8.py

    Important: If you forget to run the upgradeResourceSettings16-6To16-8.py upgrade script, the upgrade of the Office 365 Application will fail.

  6. Upgrade the Office 365 Application:

    1. Import the Office 365 Application Package to Odin Automation. See Odin Automation 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 Odin Automation 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.

    If the tasks 'APS application 'Office365', id XXX : updating upgrade relations for APS packages of application' fail with a message about the upgradeResourceSettings16-6To16-8.py script, try performing the following steps:

    1. Make sure none of the existing Office 365 Application Instances are upgraded.

    2. Remove version 16.8.1 of the Office 365 Application Package from Odin Automation.

    3. Run the upgradeResourceSettings16-6To16-8.py script as described above.

    4. Import version 16.8.1 of the Office 365 Application Package and upgrade the existing Office 365 Application Instances.
  7. Update the configuration of Office 365 Resources, Office 365 Service Templates and Office 365 Service Plans by running the autoconf.py script. The script does the following:

    • It sets up the units of measure of 'Office 365 License' and 'Office 365 Add-on' Resources. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers > Setting Up Units of Measure for 'Office 365 License' and 'Office 365 Add-on' Resources (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86760.htm) for details.

    • It adds the o365_based_on_email Service Parameter to Office 365 Service Templates. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers > Creating 'Office 365' Service Template (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86406.htm) for details.

    • It adds the Resource Type Office 365 Tenant Contact Data to Office 365 Service Templates (Application Service = TenantContactData, Automatically provision service = Off).

    See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86395.htm) to obtain the instruction on how to run the script.

  8. The addTenantCountersToSubscriptions.py upgrade script adds the auxiliary Total points sold and Total seats sold Resource Types to Office 365 Service Templates and Subscriptions.

    Run the script for the Office 365 Application:

    1. Prepare the identifier of the Application (for example, go to Services > Applications).
    2. Make sure the addTenantCountersToSubscriptions.py script is uploaded to the Management Node. The addTenantCountersToSubscriptions.py script has the same location as the upgradeResourceSettings16-6To16-8.py script (see the corresponding step above).
    3. Run the script:

      python addTenantCountersToSubscriptions.py --o365-app-id O365_APP_ID
      

    The script processes all Service Templates and Subscriptions for each Application Instance of the Application. The suitable Total points sold and Total seats sold Resource Types are automatically found.

    Notes:

    1. It is possible to run the script for a specific Application Instance by using the --o365-app-instance-id option. In this case the script processes all Service Templates and Subscriptions of the specified Application Instance. The suitable Total points sold and Total seats sold Resource Types are automatically found. For example:

      python addTenantCountersToSubscriptions.py --o365-app-instance-id O365_APP_INST_ID
      
    2. When running the script for a specific Application Instance, it is also possible to specify the auxiliary Total points sold and Total seats sold Resource Types the script must use. The required Resource Types are specified by using the --o365-points-counter-rt-id and --o365-seats-counter-rt-id options. For example:

      python addTenantCountersToSubscriptions.py --o365-app-instance-id O365_APP_INST_ID --o365-points-counter-rt-id TOTAL_POINTS_SOLD_RT_ID --o365-seats-counter-rt-id TOTAL_SEATS_SOLD_RT_ID
      
  9. Create the Office 365 Tenant Contact Data Resource Type if it does not exist. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers > Creating Office 365 Resource Types > Creating Auxiliary Resource Types (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86473.htm) and Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers > Creating 'Office 365' Service Template (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86406.htm) for details. Then, add the Resource Type to all the Office 365 Service Templates and their Subscriptions. You can use instructions of the https://kb.odin.com/en/123749 KB article to do this.

  10. Update the OA 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 OA Billing Online Store (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86474.htm) and Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for OA Billing Control Panel (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86475.htm) for details.

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

  12. Configure the following new offers (optional but recommended):

    • Customer Lockbox for faculty
    • Customer Lockbox for students
    • Skype for Business PSTN Conferencing
    • Skype for Business PSTN Conferencing (Government Pricing)
    • Skype for Business PSTN Domestic Calling
    • Skype for Business PSTN Domestic (Government Pricing)
    • Skype for Business PSTN Domestic and International Calling
    • Skype for Business PSTN Domestic and International Calling (Government Pricing)

    Use the instructions of the https://kb.odin.com/en/126207 KB article.

Upgrade Procedure (From Version 16.8.0, 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.0. Upgrading from versions that are lower than 16.8.0 is not supported.
  • 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=86229.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.

    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 on your installation. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for OA Billing Online Store (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86301.htm) and Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for OA Billing Control Panel (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86303.htm) for details.

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

Upgrade Procedure (From Version 16.8.0, 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.0. Upgrading from versions that are lower than 16.8.0 is not supported.
  • 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=86383.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.

    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 on your installation. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for OA Billing Online Store (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86474.htm) and Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for OA Billing Control Panel (http://download.automation.odin.com/poa/Office365_APS2/doc/index.htm?fileName=86475.htm) for details.

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

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 OA Billing Control Panel (Customization Files)

Office 365 and Azure CSP Subdomain Form for OA Billing Online Store (Layout Template Customizations)

Search Words

ыа

Office 365 v16.8.1 upgrade

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF