Article ID: 126954, created on Sep 21, 2015, last review on Nov 16, 2015

Table of Contents

Release Notes

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

Dependencies and Pre-Requisites

The Microsoft 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-12978 Office 365 (Cloud Solution Provider): after provisioning new subscription, customer is forced to submit new password on attempt to log in to Microsoft Online Services Portal.
  • APSA-12923 Office 365 (Cloud Solution Provider): subscription events are prematurely removed from event queue.
  • APSA-12789 Office 365 (Cloud Solution Provider): Method 'Verify' of CSP Domain Controller prematurely marks domain as 'Verified'.
  • APSA-12710 Office 365 (Cloud Solution Provider): 'Provisioning "Subscription" for APS application Microsoft Office 365' task fails with 'Unable to add this domain because there are too many unverified domains' error.
  • APSA-12396 Reseller that squats onmicrosoft.com domain in system blocks provisioning Office 365 subscriptions.
  • APSA-12369 Incorrect help text is shown on Manage License / Assign License screen.
  • APSA-3291 State should be validated when customer account is created.
  • APSA-12929 Office 365 (Cloud Solution Provider): issues with sending welcome messages.
  • APSA-12941 Synchronization script of https://kb.odin.com/en/122526 KB article synchronizes only first 1000 subscriptions of application instance.
  • APSA-12751 Order successfully completed but task 'Provisioning subscription' failed.
  • APSA-12814 Ability not to synchronize license if it is directly ordered in Microsoft Online Services Portal and it does not belong to any of resources of Office 365 subscription.
  • APSA-13102 It is impossible to use Business Automation localization scheme for Microsoft Office 365 messages shown in 'New Order' Wizard.

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.3 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/84467.htm. Also, you can download the PDF version.

New Features and Changes

  • Mobile Device Enrollment DNS Records are Supported
  • Upgrading Office 365 Subscriptions through Provider/Reseller Control Panel is Supported

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.3 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/84467.htm. Also, you can download the PDF version.

Obtaining

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

Installation

To install the Microsoft 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 Microsoft Office 365 Application.
  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 Microsoft Office 365 Application is 6.2.x. Upgrading from versions that are lower than 6.2.x 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 Microsoft 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 Microsoft Office 365 Application.
    3. Select the Instances tab and click the target Application Instance.
    4. Select the General tab.
    5. Obtain the value of the Application API end-point URI setting. This is a URL that is structured in the following way: https://<Hostname_of_Office_365_Gateway_Site>/<Name_of_Office_365_Gateway_Application>/aps/.
    6. Write down the name of the directory from the URL. This is the name of the Office 365 Gateway Application.
    7. Write down the hostname from the URL. This is the hostname of the Office 365 Gateway Site.
    8. Resolve the hostname from the URL into the IP address. This is the IP address of the Office 365 Gateway Site. Write down this IP address.
    9. Log on to the Office 365 Application End-point Host as Administrator via RDP.
    10. Open 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 Microsoft 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 Microsoft Office 365 Application:

    1. Import the Microsoft Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Microsoft 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.

  7. Perform the following additional upgrade actions:

    1. Reconfigure the Office 365 subdomain form. See Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for Business Automation Online Store and Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for Business Automation Control Panel for details. Consider updating your firewall for the Office 365 Application End-point Host (see Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Firewall Requirements > Office 365 Application End-point Host, External Incoming Connections).
    2. Create the onmicrosoft.com domain under the provider account using the instruction provided in Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deploying 'Microsoft Office 365' Application > Creating onmicrosoft.com Domain.

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 Microsoft Office 365 Application.
  5. Starting provisioning Office 365 services.
  6. Performing additional upgrade actions.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-6 are mandatory.
  • Make sure the current version of the Microsoft Office 365 Application is 6.2.x. Upgrading from versions that are lower than 6.2.x 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 Microsoft 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 Microsoft Office 365 Application.
    3. Select the Instances tab and click the target Application Instance.
    4. Select the General tab.
    5. Obtain the value of the Application API end-point URI setting. This is a URL that is structured in the following way: https://<Hostname_of_Office_365_Gateway_Site>/<Name_of_Office_365_Gateway_Application>/aps/.
    6. Write down the name of the directory from the URL. This is the name of the Office 365 Gateway Application.
    7. Write down the hostname from the URL. This is the hostname of the Office 365 Gateway Site.
    8. Resolve the hostname from the URL into the IP address. This is the IP address of the Office 365 Gateway Site. Write down this IP address.
    9. Log on to the Office 365 Application End-point Host as Administrator via RDP.
    10. Open 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 Microsoft 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 Microsoft Office 365 Application:

    1. Import the Microsoft Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Microsoft 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.

  6. Perform the following additional upgrade actions:

    1. Reconfigure the Office 365 subdomain form. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Business Automation Online Store and Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Business Automation Control Panel for details.
    2. Create the onmicrosoft.com domain under the provider account using the instruction provided in Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deploying 'Microsoft Office 365' Application > Creating onmicrosoft.com Domain.

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

Email subscription for changes to this article
Save as PDF