Home
%3CLINGO-SUB%20id%3D%22lingo-sub-571617%22%20slang%3D%22en-US%22%3ESharePoint%20Tidbit%20-%20Changing%20farm%20default%20document%20behavior%20for%20the%20farm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571617%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Sep%2026%2C%202017%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20Hello%20All%2C%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20These%20days%20I%20am%20working%20with%20one%20of%20my%20customers%20to%20deploy%2Fmigrate%20to%20SharePoint%202016.%26nbsp%3B%20And%20last%20week%20we%20installed%20Office%20Online%20Servers%2C%20and%20connected%20them%20using%20'New-SPWOPIBinding'%20command.%26nbsp%3B%20At%20that%20point%20he%20discovered%20that%20default%20value%20was%20to%20Open%20Online%20and%20he%20wanted%20the%20farm%20to%20default%20to%20the%20Client%20on%20the%20PC.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20After%20he%20dug%20thru%20the%20Internet%2C%20he%20came%20to%20me%20asking%20about%20how%20to%20do%20it.%26nbsp%3B%20I%20was%20surprised%20to%20find%20that%20I%20was%20not%20pleased%20by%20the%20answers%20I%20found%20so%20decided%20to%20publish%20this%20blog%20for%20my%20records%20and%20your%20knowledge.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20First%20to%20connect%20SharePoint%20to%20OOS%20farm%20you%20run%20the%20command%20%3CBR%20%2F%3E%3CP%3ENew-SPWOPIBinding%20-ServerName%20%22Server.domain.com%22%20-AllowHTTP%3C%2FP%3E%3CBR%20%2F%3E%20NOTE%3A%20There%20are%20several%20other%20switches%20in%20the%20command%2C%20for%20a%20better%20understanding%20please%20read%20the%20TechNet%20article%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj219441.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj219441.aspx%3C%2FA%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Second%20to%20set%20the%20default%20action%20to%20'Open%20in%20Client'%20for%20all%20extensions%20on%20all%20Sites%2C%20then%20run%20the%20following%20command%20%3CBR%20%2F%3E%3CP%3EGet-SPWOPIBinding%20%7C%20Set-SPWOPIBinding%20-Defaultaction%3A%24False%3C%2FP%3E%3CBR%20%2F%3E%20NOTE%3A%20Site%20Collection%20Owners%20and%20Admins%20will%20be%20able%20to%20change%20this%20behavior%20on%20the%20Site%20or%20List%20just%20follow%20this%20article%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fee837425.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fee837425.aspx%3C%2FA%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Pax%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-571617%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Sep%2026%2C%202017%20Hello%20All%2CThese%20days%20I%20am%20working%20with%20one%20of%20my%20customers%20to%20deploy%2Fmigrate%20to%20SharePoint%202016.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-571617%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Edefaultaction%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPowerShell%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esharepoint%20tidbit%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewopi%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
First published on TECHNET on Sep 26, 2017
Hello All,

These days I am working with one of my customers to deploy/migrate to SharePoint 2016.  And last week we installed Office Online Servers, and connected them using 'New-SPWOPIBinding' command.  At that point he discovered that default value was to Open Online and he wanted the farm to default to the Client on the PC.

After he dug thru the Internet, he came to me asking about how to do it.  I was surprised to find that I was not pleased by the answers I found so decided to publish this blog for my records and your knowledge.

First to connect SharePoint to OOS farm you run the command

New-SPWOPIBinding -ServerName "Server.domain.com" -AllowHTTP


NOTE: There are several other switches in the command, for a better understanding please read the TechNet article https://technet.microsoft.com/en-us/library/jj219441.aspx

Second to set the default action to 'Open in Client' for all extensions on all Sites, then run the following command

Get-SPWOPIBinding | Set-SPWOPIBinding -Defaultaction:$False


NOTE: Site Collection Owners and Admins will be able to change this behavior on the Site or List just follow this article https://technet.microsoft.com/en-us/library/ee837425.aspx

Pax