Article ID: 125348, created on Apr 30, 2015, last review on Sep 8, 2015

  • Applies to:
  • Operations Automation 6.0

Release Notes

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

Dependencies and Pre-Requisites

The Microsoft Office 365 Application Package requires:

  • Operations Automation 6.0.3 or later
  • Business Automation 6.0.1 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-11727 autoconf.py does not work on RHEL/CentOS 5.
  • APSA-11718 Office 365 CSP: Empty list of parent offers for 'Office 365 Extra File Storage' add-on in PCP and invalid task error.
  • APSA-11656 Subscription cannot be synced due to 'POWER_BI_STANDARD' subscription in Microsoft cloud.
  • APSA-11452 Voice Anywhere Plug-in for Office 365: 'Work PhoneNr' is not propagated to Service Automation (Contact Info subtab of CCP).
  • APSA-11353 UI on Office 365 'License' screen in CCP does show 'Action' column even when Business Automation integration is not configured.
  • APSA-11026 Incorrect number format is used when estimated prices are displayed in 'Adjust License Limit' pop-up.
  • APSA-10954 Mistake in serviceplans.json.
  • APSA-10868 Voice Anywhere Plug-in for Office 365: Changes of Office phone (Work Phone Number) made in Microsoft Online Services Portal are not propagated to Voice Anywhere Plug-in.
  • APSA-10672 'UsageLocation' for country 'Isle of Man' ('IM') should be supported by Microsoft Office 365 application.
  • APSA-10645 'User creation' Wizard hangs if 'Back' is pressed.
  • APSA-10638 Subdomain availability checker reports domains that belong to customers w/o subscriptions as available.
  • APSA-9411 'Serbia' country is not supported by Microsoft Office 365 application.
  • APSA-1163 Add parameter --dont-add-billing-resource for upgrade scripts.
  • APSA-9658 'Office 365 Business Essentials' cannot be purchased twice within 90 days.

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

New Features and Changes

  • CREST API is Supported
  • License Priority is Added
  • Japanese Language 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.1 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/83531.htm. Also, you can download the PDF version.

Obtaining

Contact your Parallels 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. Upgrading the Office 365 Application End-point.
  4. Upgrading the Microsoft Office 365 Application.
  5. Updating the offer compatibility checker.
  6. Updating the script3.js file on the Business Automation Application Server.
  7. Configuring Office 365 welcome messages.
Important:
  1. The upgrade procedure is not reversible.
  2. Upgrade steps 1-6 are mandatory. Step 7 is optional.
  3. Make sure the current version of the Microsoft Office 365 Application is 6.0.x. Upgrading from versions that are lower than 6.0.x is not supported.
  4. 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. 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.
    7. Notes:
    8. 1. 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.
    9. 2. 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.
  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. Update the offer compatibility checker:
    1. Find all the branding sites where the check.php offer compatibility checker script is installed (see the SITE_ROOT_DIRECTORY\o365 directory). You must check all branding sites on all existing Branding Servers.
    2. Replace each check.php file with the file provided in Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Filtration of Incompatible Offers. Specify the corresponding values for BA_API, BA_VERSION, BA_USERNAME, BA_PASSWORD.
  6. Update the script3.js file on the Business Automation Application Server. The new content of the file and its location on the Business Automation Application Server are provided in Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Business Automation Customer Control Panel for Trial Subscriptions.
  7. Configure Office 365 welcome messages (optional):
    1. Prepare Office 365 welcome message templates. See Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deployment Architecture > Preparing Office 365 Welcome Message Templates for details.
    2. Run setup.cmd from step 3 with the following additional parameters:
    3. - SMTPHost – The IP address or hostname of the SMTP server which will be used for sending welcome messages to newly created Office 365 users.
    4. - SMTPPort – The port of the SMTP server.
    5. - SMTPFrom – The e-mail address which will be specified in the From: field of welcome messages.
    6. - SMTPFromPassword – The password which will be used for SMTP authentication (the value of the SMTPFrom parameter will be used as a login). This parameter must be specified if SMTP authentication is required.
    7. - SMTPDoNotUseSsl – If this parameter is specified, SSL will not be used.
    8. Update the configuration of your firewall. See Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Firewall Requirements > Office 365 Application End-point Host for details.
    9. Specify the Welcome Message Templates Download URL global setting of the required Office 365 Application Instance. See Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deploying 'Microsoft Office 365' Application > Creating 'Microsoft Office 365' Application Instance for details.

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. Upgrading the Office 365 Application End-point.
  3. Upgrading the Microsoft Office 365 Application.
  4. Configuring Office 365 welcome messages.
Important:
  1. The upgrade procedure is not reversible.
  2. Upgrade steps 1-3 are mandatory. Step 4 is optional.
  3. Make sure the current version of the Microsoft Office 365 Application is 6.0.x. Upgrading from versions that are lower than 6.0.x is not supported.
  4. 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. 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. Check if the C:\inetpub\wwwroot\csp-screenscrapper directory exists on the Office 365 Application End-point Host. If this directory exists, remove the Office 365 AET Component (csp-cp-robot):
      1. Log on to the Office 365 Application End-point Host as Administrator
      2. Open Command Prompt and go to the C:\SeleniumServer directory
      3. Execute the nssm.exe remove SeleniumServer confirm command
      4. Remove the C:\SeleniumServer directory
      5. Remove the C:\inetpub\wwwroot\csp-screenscrapper directory
      Then prepare the prerequisites for CSP over CREST deployment (See the Preparing Office 365 Application End-point Host (CSP over CREST) section in the Provider's Guide) and deploy the up-to-date version of the CSP Agent (see KB Article #126003)
    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. 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.
  3. 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.
  4. Configure Office 365 welcome messages (optional):
    1. Prepare Office 365 welcome message templates. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing Office 365 Welcome Message Templates for details.
    2. Run setup.cmd from step 2 with the following additional parameters:
    3. - SMTPHost – The IP address or hostname of the SMTP server which will be used for sending welcome messages to newly created Office 365 users.
    4. - SMTPPort – The port of the SMTP server.
    5. - SMTPFrom – The e-mail address which will be specified in the From: field of welcome messages.
    6. - SMTPFromPassword – The password which will be used for SMTP authentication (the value of the SMTPFrom parameter will be used as a login). This parameter must be specified if SMTP authentication is required.
    7. - SMTPDoNotUseSsl – If this parameter is specified, SSL will not be used.
    8. Update the configuration of your firewall. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Firewall Requirements > Office 365 Application End-point Host for details.
    9. Specify the Welcome Message Templates Download URL global setting of the required Office 365 Application Instance. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deploying 'Microsoft Office 365' Application > Creating 'Microsoft Office 365' Application Instance for details.

Help Resources

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

All Office 365 Integration Release Notes

Supported APS Application Packages Versions in Operations Automation

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF