Step 2 - Create Applications Layers for Office, Visio and Project Step 1 - Update Scripts in Your OS Layer Every setting for Office can be changed through the Microsoft GPO's. The easiest way to manage the actual configuration of Office itself is through the extensive list of GPO's provided by Microsoft Office. It is possible to use a different licensing structure than volume licensing however, it will be more difficult to manage as each license must be activated separately on each desktop. Volume licensing should also be considered a requirement for Office 2007 and earlier. KMS should be considered a requirement for VDI deployments of Office 2010 and higher.

User profile installations must be done in the end-user VM while logged in as the user. Note that some Office add-ons, like for Excel, are installed directly in the user profile, so can't be layered. When using add-ons in separate layers, it is recommended to include all previously included add-ons also as prerequisites to ensure that they will work together properly if they will ever be deployed together. If you use Office Add-ons, these should be included in the office layer, but can sometimes be installed in different layers with Office checked as a prerequisite layer during layer creation.

If your organization's requirements are more complicated, then there will be more things to keep in mind. Microsoft Office is an application that is generally easy to install into a layer, and, if it will be used by itself, there are no complexities other than activation. Citrix App Layering - Microsoft Office Overview

Install ms lync 2013