Archive
On Office with App-V: Planning for a Virtual Office Deployment
Microsoft Office: A flagship product suite ubiquitous within the enterprise. The average enterprise IT environment runs multiple versions of Office not only as a suite of applications for the average information worker, but also as a platform for custom and mission critical LOB applications and workflows. As Office continues to grow or evolve, the question of whether or not to virtualize all or parts of one or more versions of Office are revisited on a regular basis.
Reasons to Use App-V with Office
There are many significant reasons why you would want to deploy office through App-V. Some of the more common are:
-
Legacy Add-in Version Isolation through Virtualization: Office is also constantly evolving. As a new version is released, applications that work with or interact with an Office application may not work on a new version of an Office application. For example, you may have a legacy Add-in that works on Excel 2007, but does not work on Excel 2013. For that reason you create an App-V package that contains Excel 2007 along with that legacy add-in (or linked through connection groups.) This allows the application add-in/plug-in to continue to be used alongside of the newer deployment.
-
Temporary Coexistence: Multiple versions of most Office applications can run side-by-side with a few caveats smoother with App-V than with native deployments. While App-V can be used with many applications to run multiple versions of the same applications, Office has some additional guidance [which will be discussed in a later blog in much greater depth.]
-
Package Modernization Strategy Alignment: App-V allows for Office to be delivered via streaming in a flexible, portable format and take advantage of features of App-V such as the Shared Content Store.
In many cases, the version of Office you choose to virtualize will align with the reasoning. For example, you may be involved with a deployment of Windows 8.1 with Office 2013, and to ease transition, deliver an App-V package of Office 2010 applications for temporary use. You could also deploy Office 2013 via App-V to an existing Windows 7 base running Office 2010 due to a change in packaging strategy.
A Little History
A common question asked revolves around which versions of Office can be virtualized and what specific limitations will be encountered. To answer this – even at a 50,000 foot level – involves a historical discussion to better understand how the process and guidelines evolved with customer desires. As a result, the history affects version capabilities when running under App-V.
Office 2003/2007
Back in the day, when App-V was called Softgrid, prescriptive guidance documents were published on how to sequence Office 2003 and Office 2007 with Softgrid. It was a complicated process, but the isolation allowed for the resolution of some compatibility issues. There were a few caveats:
-
Applications could not self-heal.
-
Integration was limited without disabling some virtual subsystems.
-
Volume-licensed installation media was required.
There were other limitations involving client-server capabilities as well. When App-V 4.x and 5.x were released, no additional integration was developed due to the age of these products. Still generally, in most cases, these versions of Office are virtualized primarily for legacy add-in scenarios where only specific Office applications are packaged with App-V (Excel, Access, etc.) and they can still be done with success.
Office 2010
With Office 2010 came a few changes that would affect how Office would be deployed with App-V. First, Office moved over to the software protection platform that previously only used for operating system product activation. As with previous versions of Office, only volume-licensed media was supported for sequencing. In addition, a special component needed to be laid down natively in order to allow the activation of Office through either MAK (Multiple Activation Keys) keys or through a KMS (Key Management Server) Server. Hosts activated via a KMS have to report back to that key server once every 180 days. Like with the native Office format, you could also verify activation status with the OSPP.VBS script.
In addition to the software protection platform, the native component (which would become known as the ODK – Office Deployment Kit) included special virtualization handlers (or proxies) that would allow for better Office integration than we had before (MAPI, Search, SharePoint, OneNote) with previous versions of Office with App-V. This special integration allowed for the base applications to remain isolated but have better native integration with enterprise components. This would become a fine line to walk. Isolation is the opposite of integration. It is impossible to fully have both. The ODK would become the best solution.
2010 – App-V was not Click-2-Run
Beginning with Office 2010, a new format that was based on App-V technology was introduced for only Microsoft Office Home and Student 2010, Microsoft Office Home and Business 2010, and Microsoft Office Starter 2010. This was a portable streaming solution called Click-2-Run or Click-to-Run. Click-to-Run was not available in the Enterprise initially and was not to be confused with the enterprise deployment of Office using App-V. Click-to-Run behaved like a native Office installation to the introduction of dynamic virtualization technologies thus, in essence, it was simply an alternative installation format that allowed for speedy quick deployment and/or upgrades to Office 2010 for consumer users.
2013 – App-V IS Click-2-Run
Well, kind of. It comes from Click-2-Run. With the success of Office 2010 Click-to-Run, the birth of Office 365 and subscription-based deployments, and the desire for better virtual integration within the Windows shell on top of the existing integration components brought forth the solution for Office 2013 – flattened Click-to-Run.
The ODT
Instead of having to manually sequence the Office package, you will use the ODT (Office Deployment Toolkit) to download and create (flatten) the APPV package. The Click-to-Run download from Microsoft will serve as the APPV package once it has been flattened. The packaging process with flattening involves converted the STREAM.DAT file into the AppV package format alongside of generating the registries and manifests. Finally an INTEGRATOR.EXE component is embedded into the package and configure to deploy automatically via a package script when the APPV package is deployed. This integrator is the next generation of the virtualization handlers that were introduced with App-V 4 and Office 2010 integration.
The Office Deployment Toolkit is periodically updated and is also the primary tool for updating the App-V package. The flattener component puts in a permanent package GUID that simplifies updating and allows for updating with the Office 365 update cycle which is in line with patch Tuesday. The Office Deployment Toolkit is also the mechanism for determining which Office applications are part of your overall Office package.
While the Office 2013 AppV package originates with Click-to-Run from the Office365 CDN, starting with Service Pack 2 of App-V 5, the App-V package can also be activated via Volume Licensing as well as Office 365 subscription licensing. This means that the Office AppV package is now the most flexible option for licensing as it is the only package format that can be activated through either subscription or volume licensing. Bear in mind the activation method will be embedded into the package upon flattening.
Dynamic Virtualization
The Office 2013 APPV package was also the first introduction to JITV (Just-in-Time Virtualization) or what is known as “dynamic virtualization.” This allowed for better shell integration and enhanced the behavior of the virtualization handler components through tighter integrated extension points. This would be available for other AppV applications beginning with App-V 5 Service Pack 2.
In Essence, the newer the version of Office is, the tighter the integration options are. This allows for Office to be incorporated into your overall App-V application factory where the new Office can be leveraged for primary use under App-V while legacy versions can be leveraged (and) isolated for special circumstances.
Office 2013: Deployment and Migration Resources
Now that Office 2013 is generally available, it is time for many organizations who are currently using a virtualized instance of Office to start considering a move to Office 2013. As you may have read in the following Microsoft KB article http://support.microsoft.com/kb/2772509 (Supported scenarios for deploying Microsoft Office as a sequenced App-V Package) Office 365 ProPlus will be leveraging the Office Deployment Tool for Click-to-Run so administrators will be importing the Office ProPlus (Click-To-Run) .APPV package right into App-V 5.0. No sequencing is required because App-V 5.0 provides integration with local applications natively through native Virtual Application Extensions.
UPDATE: As of App-V 5 SP2 – This is extended to Volume License ProPlus as well.
I have compiled the following resources into one simple location so you can proceed to read up on getting to migrate and deploy the new version of Office in the Enterprise whether you decide to install it locally or virtual through Click-to-Run. I've been using the new Office for a year now and I love it!
UPDATE: This page has been updated as new resources come available. I'm now almost two years into it and I still love it!
Description of Microsoft Office 2013 Service Pack 1 (SP1)
http://support.microsoft.com/kb/2817430
Service Pack 1 for Microsoft Office 2013 (KB2817430) 32-Bit Edition
http://www.microsoft.com/en-us/download/details.aspx?id=42017
Service Pack 1 for Microsoft Office 2013 (KB2817430) 64-Bit Edition
http://www.microsoft.com/en-us/download/details.aspx?id=42006
App-V 5.0 SP2 Support for Office 2013 Volume Licensing Editions
http://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx
What’s New in Office Professional Plus 2013?
http://www.microsoft.com/en-us/download/details.aspx?id=36191
What's New in Lync 2013?
http://www.microsoft.com/en-us/download/details.aspx?id=36181
What's New in Excel 2013?
http://www.microsoft.com/en-us/download/details.aspx?id=36185
What's New in PowerPoint 2013?
http://www.microsoft.com/en-us/download/details.aspx?id=36193
What’s New in Access 2013?
http://www.microsoft.com/en-us/download/details.aspx?id=36189
What's New in Outlook 2013?
http://www.microsoft.com/en-us/download/details.aspx?id=36187
Office 2013 Technical Library in Compiled Help
http://www.microsoft.com/en-us/download/details.aspx?id=30389
Changes in Office 2013
http://technet.microsoft.com/library/cc178954(v=office.15)
Setup properties in Office 2013
http://technet.microsoft.com/en-us/library/cc179018.aspx
Configuring a Silent Install of Office 2013
http://msdn.microsoft.com/en-us/subscriptions/dd630736.aspx
Office 2013 Administrative Template files (ADMX/ADML) and Office Customization Tool
http://www.microsoft.com/en-us/download/details.aspx?id=35554
Office Customization Tool (OCT) in Office 2013
http://technet.microsoft.com/en-us/library/cc179097(office.15).aspx
Planning for Group Policy in Office 2013
http://technet.microsoft.com/en-us/library/cc179077.aspx
Integrating additional cloud storage services in Office 2013
http://www.microsoft.com/en-us/download/details.aspx?id=35474
Downloadable eBook: Deployment guide for Office 2013
http://www.microsoft.com/en-us/download/details.aspx?id=30388
Telemetry in Office 2013: A new way to Assess Office Compatibility
http://www.microsoft.com/en-us/download/details.aspx?id=34991
Microsoft Office 2013 Discovery and Risk Assessment Preview
http://www.microsoft.com/en-us/download/details.aspx?id=30444
Office Migration Planning Manager (OMPM): Office Compatibility
http://www.microsoft.com/en-us/download/details.aspx?id=11454
Configure user settings for Office 2013
http://technet.microsoft.com/en-us/library/cc178990.aspx
Microsoft Office 2013 Volume License Pack
http://www.microsoft.com/en-us/download/details.aspx?id=35584
Deployment Options for Office 2013
http://technet.microsoft.com/en-us/library/ee624360.aspx#Virtualization
Download: Office Customization Tool for Click-to-Run
http://www.microsoft.com/en-us/download/details.aspx?id=36778
Customizing Office 2013 using the Office Click-to-Run Deployment Tool
http://technet.microsoft.com/en-us/library/jj219424(v=office.15)
Customization Overview for Click-to-Run
http://technet.microsoft.com/en-us/library/jj219428(v=office.15)
Identity and Authentication in the cloud: Office 2013 and Office 365 (Poster)
http://www.microsoft.com/en-us/download/details.aspx?id=38193
Supported scenarios for deploying Microsoft Office as a sequenced App-V Package
http://support.microsoft.com/kb/2772509
Microsoft Office Support in Microsoft User Experience Virtualization (UE-V)
http://support.microsoft.com/kb/2841206
Office 365
Managing Updates for Office 365 ProPlus – Part 1
http://blogs.technet.com/b/office_resource_kit/archive/2014/01/21/managing-updates-for-office-365-proplus-part-1.aspx
Managing Updates for Office 365 ProPlus – Part 2
http://blogs.technet.com/b/office_resource_kit/archive/2014/01/28/managing-updates-for-office-365-proplus-part-2.aspx
Test Lab Guide: Configuring and Office 365 Subscription
http://www.microsoft.com/en-us/download/details.aspx?id=41548
FastTrack Office 365 Deployment Guide
http://www.microsoft.com/en-us/download/details.aspx?id=41678
SkyDrive Pro for Windows Download
http://www.microsoft.com/en-us/download/details.aspx?id=39050
Office Scrub – Cleaning Up Older Versions of Office and Remnants
http://blogs.technet.com/b/odsupport/archive/2011/04/08/how-to-obtain-and-use-offscrub-to-automate-the-uninstallation-of-office-products.aspx
Must Have App-V 5.0 Migration Resources!
Yes, there is a learning curve with the new release of App-V. This is why it is extremely important that – Before you embark on and App-V 5.0 deployment or migration, that you look to the following resources for assistance in migrating to App-V 5.0.
App-V 5.0 Published Whitepapers:
App-V 5.0 Trial Guide:
App-V 5.0 Sequencing Guide:
Managing App-V 5.0 with Configuration Manager 2012 SP1
Integrating App-V with Microsoft VDI White Paper
App-V and Citrix Integration Overview
App-V 5 SP2 Publishing and Client Interaction
http://www.microsoft.com/en-us/download/details.aspx?id=41635
App-V 5.0 Supplemental Downloads
Microsoft Application Virtualization Server 5.0 Best Practice Analyzer
http://www.microsoft.com/en-us/download/details.aspx?id=38844
System Center Management Pack for Microsoft Application Virtualization Server 5.0
http://www.microsoft.com/en-us/download/details.aspx?id=38418
Microsoft Desktop Optimization Pack Administrative Templates 2.0
http://www.microsoft.com/en-us/download/details.aspx?id=41183
TechNet Resources:
Online App-V 5.0 Administrator’s guide:
http://technet.microsoft.com/en-us/library/jj713487.aspx
Deploying the App-V 5.0 Sequencer and Client
http://technet.microsoft.com/en-us/library/jj713463.aspx
TechNet Forum
http://social.technet.microsoft.com/Forums/en-US/mdopappv/threads
Technet Virtual Lab:
https://cmg.vlabcenter.com/default.aspx?moduleid=61991289-6281-43f6-bc7c-22a7696b3c6d
Main Resource page:
http://technet.microsoft.com/en-us/windows/hh826068.aspx?ocid=wc-int-news
How to Install the App-V Client for Shared Content Store Mode
http://technet.microsoft.com/en-us/library/jj713455.aspx
Blog Posts:
Microsoft Application Virtualization 5.0 Integration
Scripting and Embedded Scripting for AppV 5.0 (Dynamic Deployment and User Configuration Scripting)
Sequencing for Connection Groups
http://blogs.technet.com/b/appv/archive/2012/11/29/sequencing-for-connection-groups.aspx
App-V 5.0 Client PowerShell Deep Dive
http://blogs.technet.com/b/appv/archive/2012/12/03/app-v-5-0-client-powershell-deep-dive.aspx
How to Collect App-V 5.0 Debug Traces
http://blogs.technet.com/b/appv/archive/2013/01/23/how-to-collect-app-v-5-0-debug-traces.aspx
App-V Scripting
http://blogs.technet.com/b/gladiatormsft/archive/2013/05/02/app-v-5-scripting-change.aspx
How to run processes inside the App-V Virtual Bubble
Knowledge Base Articles:
Known issues when using App-V v5 Package Converter
http://support.microsoft.com/kb/2774436
Important changes in the App-V v5 Sequencer
http://support.microsoft.com/kb/2777777
How to remove a cached copy of an unpublished package in Microsoft App-V v5
http://support.microsoft.com/kb/2768945
Five common App-V v5 implementation scenarios
http://support.microsoft.com/kb/2780807
Supported Configuration Manager and Microsoft Application Virtualization scenarios
http://support.microsoft.com/kb/2780810
How To Use Microsoft User Experience Virtualization With App-V Applications
http://support.microsoft.com/kb/2850582
Known issues when creating or using an App-V 5.0 Office 2010 package
http://support.microsoft.com/kb/2828619
How to adjust the App-V v5 Publishing Server Refresh schedule
http://support.microsoft.com/kb/2780177/en-us
How to use PowerShell to find packages in App-V v5 client connection groups
http://support.microsoft.com/kb/2780809/en-us
How to troubleshoot publishing server refresh failures in App-V v5
http://support.microsoft.com/kb/2778168/en-us
Add-on Downloads
Microsoft App-V 5.0 Client UI Application Download
http://www.microsoft.com/en-us/download/details.aspx?id=41186
Microsoft App-V 5.0 Server Best Practice Analyzer
http://www.microsoft.com/en-us/download/details.aspx?id=38844
Office 2013 and APP-V 5.0
Supported scenarios for deploying Microsoft Office as a sequenced App-V Package
http://support.microsoft.com/kb/2772509
Download: Office Customization Tool for Click-to-Run
http://www.microsoft.com/en-us/download/details.aspx?id=36778
Customizing Office 2013 using the Office Click-to-Run Deployment Tool
http://technet.microsoft.com/en-us/library/jj219424(v=office.15)
Customization Overview for Click-to-Run
http://technet.microsoft.com/en-us/library/jj219428(v=office.15)
Deployment Options for Office 2013
http://technet.microsoft.com/en-us/library/ee624360.aspx#Virtualization
Office 2010 and App-V 5.0
Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0
http://www.microsoft.com/en-us/download/details.aspx?id=38399
How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0
http://support.microsoft.com/kb/2830069
App-V: Description of Feature Flags When Configuring the Office 2010 Deployment Kit for App-V
32-bit:
ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core
64-bit:
ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core,OSppWoW64
The options here:
- Click2runMapi: For MAPI Overrides
- Click2runOWSSupp: Microsoft SharePoint Client Support
- Click2runWDS: Search MAPI Protocol Handler and Host Search MAPI Protocol Handler Manager Overrides. This allows for Fast Search in Outlook
- OSpp: Microsoft KMS Client.
- OSpp_Core: Office Software Protection Platform
- OSppWoW64: Microsoft KMS Client for x64.
Then on the client, we deploy the handlers which place in the host-side handlers. This will expose the proxies.
ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies
- Click2runOneNoteProxy: Send to OneNote printer Proxy
- Click2runOutlookProxies: All MAPI and Mail control panel applet
- Click2runWDSProxy: Search Proxy and Office Document indexing
- Click2runOWSSuppProxies: Sharepoint Client
madvirtualizer
The Mad Virtualizer at Microsoft 