Back
Office Online

Office Online Server November release

Share on Facebook Share on Twitter Share on Linkedin Share via OneNote Share via Email Print

In May, we released Office Online Server (OOS), which allows organizations to provide your users with browser-based versions of Word, PowerPoint, Excel and OneNote, among other capabilities offered in Office Online, from your own datacenter. We will deliver most of new Office Online features to Office Online through regular updates.

Today, we are releasing our first significant update to Office Online Server that includes:

  • Performance improvements to co-authoring in Word Online.
  • Support for embedded Power View sheets in Excel Online.
  • Improvements when working with tables in Word Online and PowerPoint Online, including better drag-and-drop support.
  • Support for showing spelling errors inline in the PowerPoint editor.
  • Improved picture resizing in Word Online.
  • Copy and paste improvements in PowerPoint Online.
  • Support for shapes in Excel Online viewer.
  • Significant improvements for users that rely on assistive technologies—HTML markup updated to more fully support W3C accessibility standards.

We encourage Office Online Server customers to visit the Volume License Servicing Center to download the November release. You must uninstall the previous version of OOS to install the November release. Moving forward, we have a release planned every four months to ensure that we can continuously deliver new value to OOS users. We will only support the latest version of OOS with bug fixes and security patches, available via the Microsoft Updates. Finally, we will announce a more detailed timeline for future releases within the next two weeks.

Customers with a Volume Licensing account can download Office Online Server from the Volume License Servicing Center at no cost and will have view-only functionality, which includes PowerPoint sharing in Skype for Business. Customers that require document creation, edit and save functionality in Office Online Server need to have an on-premises Office Suite license with Software Assurance or an Office 365 ProPlus subscription. For more information on licensing requirements, please refer to our product terms.

Top

Join the conversation

10 comments
  1. “You must uninstall the previous version of OOS to install the November release.”
    Are you serious?
    I have to uninstall product to update?
    And have to make all configurations again from the begining?

    • Andrey, all configuration for OOS is done via PowerShell and is designed to be entirely scriptable. Even installing security patches requires that each machine in a farm be removed, updated and added back. However, we do this internally all the time using PowerShell scripts that make the process entirely hands off.

      • you do realize you’re pushing builds multiple times a week, and telling people who do it twice a year that it’s not that big of a deal?

        “rotating and balancing your tires is super easy. just use your 2 post hydraulic lift and your electric tire balancer like we do in the shop.”

        additionally, considering how portable and flexible powershell scripts are, why in the world aren’t you publishing them with the product? even if they’re hard-coded or only suitable for internal purposes, you’d have to think it would take someone far less time to make an internal script passable for a public OOS admin audience than it would to tell them to write their own from scratch.

        • Hi Robert,
          Microsoft along with the majority of the IT Pro industry have been encouraging the automated deployment of services. OOF and its predecessor required PowerShell to configure it, and if you have issues you would use it resolve (or rebuild) the application.
          I do strongly agree that working proof of concept scripts should be provided for single and multi server farms to aid IT Pros in using automation.

          Regards,
          Ivan

  2. “You must uninstall the previous version of OOS to install the November release.”
    Are you serious?

  3. Just installed this for use in Lync 2013. Thankfully I commissioned 2 servers accessed via VIP. Are you able to share the powershell commands in order to automate this task?

  4. Can someone please explain the licensing implications of moving Excel Services from SharePoint to OOS for service providers who are selling SharePoint to customers via SPLA program? Are service providers allowed to run OOS if they validate the customer has a valid O365 ProPlus licenses? It’s very confusing moving features to a different product with completely different licensing methods.

  5. I am also in the process of deploying OOS.

    Can you please confirm will Server 2016 be supported or not?

    Also please do share PS script, if you have that we can tweak and use it for automated deployment.

Comments are closed.