Best Practices

• Office web app features and functionality vary based on the operating system and browser in use, so the different permutations supported by the organization should be thoroughly tested prior to a production implementation of Office Web Apps.

• Organizations interested in using Office Web Apps in their environments still need to comply with Microsoft licensing policies, which can be found on the following site: http://www.microsoftvolumelicensing.com/userights/default.aspx.

• Due to limitations in support for older Office 2003 file formats, such as .doc., the SharePoint administration team may require that files be converted to the newer .docx, .xslx, and .pptx formats before being uploaded to SharePoint 2010 document libraries that will be enabled for use with the Office Web Apps feature and browser-based editing.

• It is generally recommended to leave the PowerPoint service application and Word Viewing service applications settings at their defaults unless the organization does not want to support legacy document types for Word and PowerPoint.

• Using the PowerPoint Broadcast service, as outlined in this chapter, is an easy way to share PowerPoint presentations with users on the network or accessing SharePoint 2010 remotely, and combined with a conference bridge can replace more expensive and complex options, such as WebEx.

• Compatible Excel documents and OneNote notebooks accessed by Office Web Apps are the only types of documents that can be edited by more than one user simultaneously.

• OneNote 2010 stores versioning information in the files; in general, it is recommended not to enable minor versioning in the document library that will be storing OneNote 2010 documents. Furthermore, if major versions are enabled for the document library, it is recommended that a limit is set to the number of major versions stored by using the Keep the Following Number of Major Versions tool and setting it to a number below 10.