Embed Size (px)
DESCRIPTION
The Microsoft Office Web Applications that were once configured and managed as a service application in SharePoint 2010 are configured and managed completely different in SharePoint 2013. The Office Web Applications (OWA) are now created in an Office Web Apps farm, which allows you to create a universal Office Web App environment that can host multiple SharePoint farms, as well as communicate with Lync and Exchange servers. The OWA farm allows users to create, edit, and share content using browser-based versions of Word, Excel, PowerPoint, and OneNote. Furthermore, OWA can be configured to enhance the users search experience by providing a document preview or thumbnail that is viewable from within the search result set. This session will discuss how and why you will want to implement the new Office Web Apps and the many benefits of doing so.
Citation preview
Integrating Office Web Apps (OWA) with SharePoint 2013
About the Speaker
• Brian Alderman (MCT / Consultant)
• CBT Nuggets – (www.cbtnuggets.com) @cbtnuggets
• www.microtechpoint.com – Brian’s Blog
• @brianalderman
• Co-Author SharePoint 2010 Administrator’s Companion
• Co-Author SharePoint 2013 Administration Inside Out
• Enjoy Travel and Golf
Mulletville, Vermont
Garden of the Gods with Pikes Peak
Arizona Golf
19th Hole
Overview of OWA Comparison of OWA 2010 and 2013 OWA Terminology
Pre-Installation Configuration Installation Process Troubleshooting Commands and Best Practices
Session Agenda
Office Web Apps Overview
Office Web Apps (OWA) – Browser-Based Office ApplicationsWordExcelPowerPoint OneNote
Accessible from SharePoint, Exchange, Lync, File Shares, and Web SitesAccessible from IE, Firefox, Chrome, Safari on PC’s and MAC’s, as well
as Tablets and Slates (View and Edit) and Smart Phones (View Only)Free to View These Document TypesOffice Licenses Required for End Users to Create or Modify DocumentsOnly Used by Claims-Based Authenticated Web Apps
Office Web Apps Overview
OWA 2010/2013 Comparison
2010 Deployed as SharePoint Service
Application
Multiple SharePoint Farms = Multiple Service Applications
Patching SharePoint Meant Patching OWA
2013 Separate Product Deployed in Separate
OWA Farm
Multiple SharePoint Farms use Single OWA Farm
Independent OWA Server Patching
Independent Scaling and Optimization
What’s New with OWA and SharePoint 2013
OWA Terminology
WOPI Protocol = Web application Open Platform Interface
Office Webs Contain Two Components WOPI Apps or Clients – (OWA Servers to Render Documents – Called WAC - Web
Application Companions)
WOPI Host or WOPI Servers – SharePoint, Lync, or Exchange Hosting Documents
Types of OWA Server Roles in Load Balanced Environment Front End Excel Back End Word Back End PowerPoint Back End
OWA WOPI Server Roles
Pre-Installation Configuration
Dedicated Server (No Microsoft Server Applications Using Port 80, 443, or 809)
All Servers in Same AD Domain NOT on Domain Controller No SQL Server or Database Required Virtualization of OWA Servers Allowed About 20,000 Typical Users per Server Single Server Farm – Can add More Servers for HA and Improved
Performance
OWA Server Specifications
Hardwear Requirements
Same Hardware Requirements as SharePoint 2013
Windows Server x64 2008 R2 SP1 or Windows Server 2012 .NET 4.5 Framework Windows Management Framework 3.0 If Windows 2008 R2 - Install KB2592525 Update IIS 7.0 (Web Server Role) PowerShell 3.0 (No OWA UI, all PowerShell) IE 8 or Later (IE 9 or Later Preferred)
OWA Software Prerequisites
Enter Following Windows PowerShell Command:Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-
Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support
Note: This is one Command, do not Press ‘Enter’ Until End of Command
Configure Server for OWA
No Installation on SharePoint Farm Use PowerShell to Connect SharePoint Farm to OWA Farm Use New-SPWOPIBinding -ServerName
mtpowa.microtechpoint.com –AllowHTTP Binds Entire SharePoint Farm to OWA Farm Run Only Once for All Apps in SharePoint Farm Can use –Application “AppName” Switch to Specify Particular
Applications (ie; -Application “Excel”)
OWA Connection to SharePoint
All Machines Identical in OWA Farm Any Machine can Play any Role Can Dedicate Machine to Specific Role Can Reconfigure Farm Without Removing Machines or
Reassigning Roles
Managing OWA Farm
Patch Independent of SharePoint Farm Must Disconnect Machine from OWA Farm to Patch Remove-OfficeWebAppsMachine
In-Place Major Version Upgrades not Supported – (Must Remove Old Version)
Minimal Downtime During Upgrade, but Should Upgrade During Low-Demand
Patching OWA Farm
Installation Process
1. Prepare Windows Server for OWA Installation2. Run OWA Setup to Install OWA3. Create OWA Farm using Windows PowerShell
Use New-OfficeWebAppsFarm to Create Master/First Server to Store OWA Configuration Information
Add Machines to OWA Farm using New-OfficeWebAppsMachine4. Configure SharePoint to use OWA Farm
Note: If Lose Master, Child Servers Still Function
OWA and SharePoint Farm Configuration
Server 2008 R2: Open Windows PowerShell as Administrator Import-Module ServerManager Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-
Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support
Server 2012: Open Windows PowerShell as Administrator Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-
WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices
1. Prepare Windows Server for OWA
1. Download Office Web Apps from the Microsoft Download Center
Server 2008 R2: Extract Files From .img File and Run Setup.exe Server 2012: Open the .img File and Run Setup.exe
2. Accept Licensing Agreement – Click ‘Continue’3. Specify Location for OWA Installation Files– Click ‘Install Now’ 4. Download and Install the OWA Server update KB28100075. Optionally – Download and Install OWA Language Packs
2. Install OWA
1. Create OWA Farm:New-OfficeWebAppsFarm -InternalUrl"https://mtpowa.microtechpoint.com" -ExternalUrl"https://mtpowaext.microtechpoint.com" -SSLOffloaded -EditingEnabled
(Note: EditingEnabled is only used by SharePoint)2. Verify OWA Farm Exists by Opening Browser:
https://mtpowa.microtechpoint.com/hosting/discovery(Specify name assigned to InternalUrl parameter used during OWA farm creation)
3. Execute Following Command to add Servers to OWA FarmNew-OfficeWebAppsMachine –MachineToJoin ”mtpowa.microtechpoint.com” [-roles] (If Want to Run Specific Application)
Note: To Remove Machine from OWA Farm use Remove-OfficeWebAppsMachine
3. Create OWA Farm Using Window’s PowerShell
1. Open SharePoint’s PowerShell as Administrator2. Create Binding Between SharePoint and OWA
New-SPWOPIBinding -ServerName <FQDNofOWAServer> -AllowHTTP(Only Specify if not using https)
3. View the WOPI Zones for SharePoint Bindings Get-SPWOPIZone (Verify use of internal https)
4. If External Access also Enter Following Command: Set-SPWOPIZone –zone “external-https”
Note: To disconnect SharePoint farm from OWA: Remove-SPWOPIBinding –All:$true
4. Configure SharePoint for OWA
Demonstration
Configuring Office Web Apps for SharePoint 2013
Troubleshooting
If During Install of KB2592525 Receive Error:“This update is not applicable to this computer”
Complete These Steps: Extract files from KB2592525.MSU-file with the command: Windows6.1-
KB2592525-x64.msu /extract:C:\KB2592525 In C:\KB2592525 folder run the command: pkgmgr.exe /n:Windows6.1-
KB2592525-x64.xml Do NOT Uninstall KB2670838 as Some Suggest If Receive 500 Web Server Exception Errors During Installation
Windows 2008 R2 – Run Following Command from Command Prompt and Then Perform IISRESET /restart /noforce%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
Windows 2012 – Run Following Command from Command Prompt:dism /online /enable-feature /featurename:IIS-ASPNET45
Installation Troubleshooting Tips
Ensure WOPI Zone Set Properly on OWA Farm and Compare to SharePoint Farm Check WOPI Zone by Entering:
https://mtpowa.microtechpoint.com/hosting/discovery Default OWA Log Location:
%ProgramData%\Microsoft\OfficeWebApps\Data\Logs\ULS Can Change Log Location Using Set-OfficeWebAppsFarm -
LogLocation Requires Restart of OWA Server
Troubleshooting Tips
Don’t Test Functionality of OWA Documents Using SharePoint’s System Account; Must use Non-System Account
Don’t Install Any Office Product on OWA Server Don’t Attempt Installation of OWA on Domain Controller Try Repair-OfficeWebAppsFarm to Resolve Issues with OWA
Farm
Troubleshooting Tips (Cont…)
Commands and Best Practices
OWA and WOPI PowerShell Commands◦ New-OfficeWebAppsFarm
◦ Get-OfficeWebAppsFarm
◦ New-OfficeWebAppsMachine
◦ Remove-OfficeWebAppsMachine
◦ Get-OfficeWebAppsMachine
◦ Set-OfficeWebAppsMachine
◦ New-OfficeWebAppsHost
◦ Get-OfficeWebAppsHost
◦ Remove-OfficeWebAppsHost
◦ New-SPWopiBinding
◦ Get-SPWopiBinding
◦ Remove-SPWopiBinding
◦ New-SPWopiApplication
◦ Set-SPWopiApplication
◦ Get-SPWopiApplication
◦ Remove-SPWopiApplication
◦ Get-SPWopiZone
◦ Set-SPWopiZone
◦ Remove-SPWopiZone
Setup and Configure OWA Setup and Configure WOPI’s
Deploy OWA in Multi-Server Load Balanced Farm using HTTPS Ensure Sufficient Memory on OWA Servers Encrypt Traffic Between Servers Using IPSec Turn off Microsoft Auto Updates on OWA Servers Create OU in AD Just for OWA Servers Check out OWA TechNet Article http://technet.microsoft.com/en-us/library/jj219458.aspx
Best Practices
Questions
Thank You For Attending
