Note: OWA may be referring to Office Web Apps and Outlook Web Access. Check context of an article if unsure.
Related blog posts
- Embedding Office docs in SharePoint
- SharePoint and Office Web Apps
- SharePoint Managed Metadata Overview
Files to download
- SharePoint Designer 64-bit download and 32-bit download
- Visio 2010 Viewer (works with Windows and IE 5+); Visio 2007 Viewer and Visio 2003 Viewer (retired)
Office Integration
Office Client
- MS whitepaper comparing SharePoint 2010 integration with Office 2010 and Office 2007 (PDF, 1.5Mb)
- If have problems opening Office docs, check Trust Center settings under Options
- To open the document information panel by default (is hidden by default in SharePoint 2010), need to specify per content type within SharePoint
- Quick Links (associating columns with fields in Office) are only editable once a document has been saved for the first time, i.e. they will be greyed out when first opening a template.
Office Web Apps
- See blog post for licensing details – SharePoint and Office Web Apps (July 10)
When installing, best approach is to install straight after installing SharePoint and before running the Config Wizard
Office Web Apps won’t run correctly when installed on a DC (if running a single server dev environment). Need to create and run a Powershell script to fix.
- MSDN blog post Installing SharePoint – no.11 contains the script
- Running PowerShell scripts – TechNet, how to enable scripts to run
- Configuring Office Web Apps – GJ Tech blog (includes notes on manual set-up)
Set-up for standalone demo on a DC:
- Powershell script contents: (create in Notepad, save as owafix.ps1)
$e = Get-SPServiceApplication | where {$_.TypeName.Equals("Word Viewing Service Application")}
$e.WordServerIsSandboxed = $false
$e.WordServerIsSandboxedGet-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedViewing $false
Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedEditing $false
- Open SharePoint 2010 Mangement Shell (Powershell)
- To be able to execute unsigned scripts (note: in production, should be signing scripts)
set-executionpolicy unrestricted
- To run the script, include full path – directory and file name e.g. c:\owafix.ps1
Follow prompts and finish with iisreset /noforce - Final step: need to activate the Office Web Apps feature in the site collection(s) that will be using it
Note: some other sites incl. editing a config file. Haven’t needed it and when tried, crashed IIS.
Outlook Web Access
OWA web part parameters:
- Use fpath to specify a subfolder in your inbox, e.g.: https://exchangeserver/owa/?cmd=contents&fpath=inbox%2fprojects
- Use module to specify one of the 4 default folders: Inbox, Calendar, Contacts, Tasks, Publicfolders, e.g.: http://exchangeserver/owa/?cmd=contents&module=calendar
- Use view to specify view to be displayed, e.g. weekly vs monthly view on calendar
- Source: http://technet.microsoft.com/en-us/library/bb232199.aspx
Troubleshooting tips:
- Check if using http://exchangeserver vs https://exchangeserver
- If get 404 error, clear the mailbox value (just enter server name)
- If get security error, add Exchange server OWA URL to Sites under Privacy tab (in IE)


