Planning for Using App-V with Office

Use the following information to plan how to deploy Office by using App-V. This article includes:

App-V support for Language Packs

You can use the App-V 5.0 Sequencer to create plug-in packages for Language Packs, Language Interface Packs, Proofing Tools and ScreenTip Languages. You can then include the plug-in packages in a Connection Group, along with the Office 2013 package that you create by using the Office Deployment Toolkit. The Office applications and the plug-in Language Packs interact seamlessly in the same connection group, just like any other packages that are grouped together in a connection group.

Note
Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack.

Supported versions of Microsoft Office

The following table lists the versions of Microsoft Office that App-V supports, methods of Office package creation, supported licensing, and supported deployments.

Supported Office Version Supported App-V Versions Package Creation Supported Licensing Supported Deployments

Office 365 ProPlus

Also supported:

  • Visio Pro for Office 365

  • Project Pro for Office 365

  • App-V 5.0

  • App-V 5.0 SP1

  • App-V 5.0 SP2

Office Deployment Tool

Subscription

  • Desktop

  • Personal VDI

  • Pooled VDI

  • RDS

Office Professional Plus 2013

Also supported:

  • Visio Professional 2013

  • Project Professional 2013

  • App-V 5.0

  • App-V 5.0 SP1

  • App-V 5.0 SP2

Office Deployment Tool

Volume Licensing

  • Desktop

  • Personal VDI

  • Pooled VDI

  • RDS

Planning for using App-V with coexisting versions of Office

You can install more than one version of Microsoft Office side by side on the same computer by using “Microsoft Office coexistence.” You can implement Office coexistence with combinations of all major versions of Office and with installation methods, as applicable, by using the Windows Installer-based (MSi) version of Office, Click-to-Run, and App-V 5.0 SP2. However, using Office coexistence is not recommended by Microsoft.

Microsoft’s recommended best practice is to avoid Office coexistence completely to prevent compatibility issues. However, when you are migrating to a newer version of Office, issues occasionally arise that can’t be resolved immediately, so you can temporarily implement coexistence to help facilitate a faster migration to the latest product version. Using Office coexistence on a long-term basis is never recommended, and your organization should have a plan to fully transition in the immediate future.

Before you implement Office coexistence

Before implementing Office coexistence, review the following Office documentation. Choose the article that corresponds to the newest version of Office for which you plan to implement coexistence.

Office version Link to guidance

Office 2013

Information about how to use Office 2013 suites and programs (MSI deployment) on a computer that is running another version of Office

Office 2010

Information about how to use Office 2010 suites and programs on a computer that is running another version of Office

The Office documentation provides extensive guidance on coexistence for Windows Installer-based (MSi) and Click-to-Run installations of Office. This App-V topic on coexistence supplements the Office guidance with information that is more specific to App-V deployments.

Supported Office coexistence scenarios

The following tables summarize the supported coexistence scenarios. They are organized according to the version and deployment method you’re starting with and the version and deployment method you are migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience.

Note
Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.

Windows integrations & Office coexistence

The Windows Installer-based and Click-to-Run Office installation methods integrate with certain points of the underlying Windows operating system. When you use coexistence, common operating system integrations between two Office versions can conflict, causing compatibility and user experience issues. With App-V, you can sequence certain versions of Office to exclude integrations, thereby “isolating” them from the operating system.

Mode in which App-V can sequence this version of Office

Office 2007

Always non-integrated. App-V does not offer any operating system integrations with a virtualized version of Office 2007.

Office 2010

Integrated and non-integrated mode.

Office 2013

Always integrated. Windows operating system integrations cannot be disabled.

Microsoft recommends that you deploy Office coexistence with only one integrated Office instance. For example, if you’re using App-V to deploy Office 2010 and Office 2013, you should sequence Office 2010 in non-integrated mode. For more information about sequencing Office in non-integration (isolated) mode, see How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0.

Known limitations of Office coexistence scenarios

The following sections describe some issues that you might encounter when using App-V to implement coexistence with Office.

Limitations common to Windows Installer-based/Click-to-Run and App-V Office coexistence scenarios

The following limitations can occur when you install the following versions of Office on the same computer:

  • Office 2010 by using the Windows Installer-based version

  • Office 2013 by using App-V

After you publish Office 2013 by using App-V side by side with an earlier version of the Windows Installer-based Office 2010 might also cause the Windows Installer to start. This is because the Windows Installer-based or Click-to-Run version of Office 2010 is trying to automatically register itself to the computer.

To bypass the auto-registration operation for native Word 2010, follow these steps:

  1. Exit Word 2010.

  2. Start the Registry Editor by doing the following:

    • In Windows 7: Click Start, type regedit in the Start Search box, and then press Enter.

    • In Windows 8, type regedit press Enter on the Start page and then press Enter.

    If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.

  3. Locate and then select the following registry subkey:

    HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Options
    
  4. On the Edit menu, click New, and then click DWORD Value.

  5. Type NoReReg, and then press Enter.

  6. Right-click NoReReg and then click Modify.

  7. In the Valuedata box, type 1, and then click OK.

  8. On the File menu, click Exit to close Registry Editor.

How Office integrates with Windows when you use App-V to deploy Office

When you deploy Office 2013 by using App-V, Office is fully integrated with the operating system, which provides end users with the same features and functionality as Office has when it is deployed without App-V.

The Office 2013 App-V package supports the following integration points with the Windows operating system:

Extension Point Description

Lync meeting Join Plug-in for Firefox and Chrome

User can join Lync meetings from Firefox and Chrome

Sent to OneNote Print Driver

User can print to OneNote

OneNote Linked Notes

OneNote Linked Notes

Send to OneNote Internet Explorer Add-In

User can send to OneNote from IE

Firewall Exception for Lync and Outlook

Firewall Exception for Lync and Outlook

MAPI Client

Native apps and add-ins can interact with virtual Outlook through MAPI

SharePoint Plug-in for Firefox

User can use SharePoint features in Firefox

Mail Control Panel Applet

User gets the mail control panel applet in Outlook

Primary Interop Assemblies

Support managed add-ins

Office Document Cache Handler

Allows Document Cache for Office applications

Outlook Protocol Search handler

User can search in outlook

Active X Controls:

For more information on ActiveX controls, refer to ActiveX Control API Reference.

Groove.SiteClient

Active X Control

PortalConnect.PersonalSite

Active X Control

SharePoint.openDocuments

Active X Control

SharePoint.ExportDatabase

Active X Control

SharePoint.SpreadSheetLauncher

Active X Control

SharePoint.StssyncHander

Active X Control

SharePoint.DragUploadCtl

Active X Control

SharePoint.DragDownloadCtl

Active X Control

Sharepoint.OpenXMLDocuments

Active X Control

Sharepoint.ClipboardCtl

Active X control

WinProj.Activator

Active X Control

Name.NameCtrl

Active X Control

STSUPld.CopyCtl

Active X Control

CommunicatorMeetingJoinAx.JoinManager

Active X Control

LISTNET.Listnet

Active X Control

OneDrive Pro Browser Helper

Active X Control]

OneDrive Pro Icon Overlays

Windows Explorer shell icon overlays when users look at folders OneDrive Pro folders

Shell extensions

Shortcuts

Windows Search

Got a suggestion for App-V?

Add or vote on suggestions here. For App-V issues, use the App-V TechNet Forum.