SharePoint 2007 Suite:
- none
SharePoint 2010 Suite:
- Word Automation Services for SharePoint 2010
- Office Web Apps 2010
SharePoint 2013 Suite:
- Word Automation Services for SharePoint 2013
- Office Web Apps 2013
SharePoint 2016 Suite:
- Office Online Server 2016
See the security bulletin below for more details and KB number for the relevant fixes:
Permalink
Hello Stefan,
We experienced issue in Sharepoint server 2016. We create content type with single line of text column. We upload a word document and change the property to use our content type. When we open the document with word 2016 the fields from our content type are not visible. If we open the document with word 2013 , there is no issue with our content types. Is there any change or reported issue regarding the functionality of using Sharepoint 2016 content type document property in word 2016?
Georgi
Permalink
Hi Georgi,
if I understand you correct everything works fine with Word 2013 and not with Word 2016.
So that sounds like a problem with the client application.
If my understanding is correct I would recommend to open a support case with Microsoft to investigate why Word 2016 does not behave correct here.
Cheers,
Stefan
Permalink
Stefan, Do I need to re-bind office online server with SP2016 after installing this security update?
Permalink
Hi,
look here: https://technet.microsoft.com/en-us/library/jj966220(v=office.16).aspx
“To apply software updates to a multiple Office Online Server farm, you first remove one of the servers from the load balancer pool and from the farm, apply the software update, and create an updated Office Online Server farm.”
The cmdlets you need are in that article.
Permalink
Hi Piotr, Thanks for the link. The given technet link does not talk about binding to SharePoint server after security update.
What I am looking here is should I bind my office online server to SharePoint again?
Permalink
ah, you mean New-SPWOPIBinding. No, you don’t have to do anything on the SharePoint side. I can think of a situation when that could be needed – if they for example add a new endpoint or application action, but it’s not documented as a normal procedure, so I guess they would say that in the KB.
Permalink
Thank you. that helps 🙂
Permalink
Hi Stefan,
I have a question regarding Office Web Apps 2010 patches. We are in a process to install OWA security patches from this month. Last we had installed was the October 2014 security patch. If we install June 2016 OWA security patch, will it cover all the previous ones? Does it have Cumulative updates like SharePoint server?
Permalink
Hi Florencio,
yes, WAC uses cumulative updates as well.
Cheers,
Stefan
Permalink
I am not able to find a link for Office web apps 2010 CU. Is it possible for you to share the link from where it can be downloaded? I could not locate, i only found CU’s for SharePoint server.
Permalink
Hi Florencio,
here you go:
Security Update for Microsoft Web Applications (KB3115244)
http://www.microsoft.com/en-us/download/details.aspx?id=52871
Cheers,
Stefan
Permalink
Thank you so much Stefan, once i install this June 2016 patch, it will cover all my previous ones too right?
Thank you in again.
Permalink
Hi Florencio,
this is not the case for security updates!
Security updates address specific components only. E.g. the one here is for WAC and for Word Automation Service.
Previous security updates for other components (e.g. excel services security problems) are not included here.
If you would like to ensure that all fixes are included you should install the June CU.
Cheers,
Stefan
Permalink
Had to use ‘Get-SPProduct -local after application of this update before Config Manager could be run
Permalink
Stefan,
Hi, it looks like at least one user is having similar issues to the January list view patch problem: https://social.msdn.microsoft.com/Forums/office/en-US/70a56af4-3aa1-43c8-9abd-0fca082ee8ab/problem-after-june-2016-patch-applied?forum=sharepointadmin
Are you/Microsoft getting reports from anyone else about this?
Thank you – Chad
Permalink
Hi Chad,
just checked our system – I cannot find a related error report.
Please ensure to open a support case to ensure that this is investigated.
Cheers,
Stefan