How to sequence Office 2010 in App-V 4.5 SP2 or App-V 4.6

This document describes one method that you can use to sequence Microsoft Office 2010 for use together with Microsoft Application Virtualization (App-V).

Note This document serves as a guide for the App-V 4.5 SP2 sequencer and for the App-V 4.6 sequencer and not for the App-V 4.6 SP1 sequencer. If you use the App-V 4.6 SP1 sequencer, we recommend that you see the following article in the Microsoft Knowledge Base:  The method that is described in this article is not the only method that is available. You may have to adjust the information in the article as appropriate for your particular environment.

Important Before you start to sequence, we strongly suggest that you read through this article several times to become familiar with your configuration options.

Introduction

Office 2010 uses the Office Software Protection Platform (SPP) service. This service uses the same activation technology that is used to activate volume editions of Windows Vista and Windows 7. This service in contained in the Office 2010 Deployment Kit for App-V. Before you sequence Office 2010, this service must be installed and configured on the sequencer. It must also be installed on any client computers to which you want to stream Office 2010.

Prerequisites

The prerequisites for installing and sequencing Office 2010 for use together with App-V are as follows:

• Microsoft Application Virtualization version 4.6 or version 4.5 SP2: When you deploy Office 2010 together with App-V 4.5 SP2, you must also install the Microsoft Visual C++ 2008 SP1 package (http://www.microsoft.com/downloads/details.aspx?FamilyID=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en
  (http://www.microsoft.com/downloads/details.aspx?FamilyID=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en)
  ).
• Microsoft Office 2010 volume SKU (32-bit or 64-bit): Proxies are not supported on 64-bit versions of Office 2010. However, sequencing and deployment of 32-bit Office 2010 and of 32-bit proxies together with 64-bit computers are supported.
• Microsoft Office 2010 Deployment Kit for App-V: The deployment kit contains the required Office 2010 licensing service and optional proxies to enable integration features.

How to sequence Office 2010

To sequence Office 2010 together with App-V, follow these steps.

Step 1: Determine whether you have to sequence Office 2010 together with proxies

Before you start to sequence Office 2010, it is important to determine the sequencing path that you should follow. If your organization must be able to open and edit documents that are located on a Microsoft SharePoint site, or if you must have Fast Search functionality in Outlook Search, you will have to follow the instructions in this document for sequencing together with proxies. (This is the most common scenario.) If this functionality is not important to you, you should sequence without proxies. For help in determining the path that you should follow, see the following document:
On the sequencing computer, follow these steps:

Step 2: Prepare a reference computer for sequencing

1. Prepare the sequencing computer by following the guidelines that are provided in the following document. If you do not follow the guidelines in the sequencing document, you may experience errors in functionality.
   
   Best Practices for the Application Virtualization Sequencer

   (http://go.microsoft.com/fwlink/?LinkId=169345)
2. On App-V 4.6, add the value VSL to the multi-string value for the following registry subkey:
   
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Sequencer\SxSAppExtensions
   
   On 64-bit sequencer systems, use the following registry subkey:
   
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Sequencer\SxSAppExtensions
   
   Note Add this value to the list of entries in this key. Do not remove any existing values.
3. For this plan, we recommend the following settings. These settings comply with the best practices document.
   • Make sure that you have Windows Search 4.0
     (http://go.microsoft.com/fwlink/?LinkId=169358)
     installed, and then set the Windows Search service to Manual or to Automatic.
   • By default, Windows Search is installed on Windows 7. You can enable it through Windows Features in Add Or Remove Programs.
   
   
4. Download the XPS Viewer by installing the Microsoft XML Paper Specification Essentials Pack
   (http://go.microsoft.com/fwlink/?LinkId=169359)
   .
   
   Note By default, the XPS Viewer is installed on Windows Vista and Windows 7.
5. Set the Windows Update service to Disabled.
6. Install the App-V sequencer, if you have not already done this.

Step 3: Install the Office 2010 Deployment Kit for App-V

1. Download and then install the Microsoft Office 2010 Deployment Kit for App-V
   (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=479f12f2-5678-493e-bce1-682b3ece5431)
   . Setup will extract the Office 2010 Deployment Kit for App-V and then ask you where you want to save the files. 
2. Open an elevated command prompt. To do this, right-click Start\All Programs\Accessories\Command Prompt, and then select Run as administrator.
3. At the command prompt, browse to the directory that contains Offvirt.msi. (For example, CD c:\offvirt.)
4. At the command prompt, run the following command:
   msiexec /i OffVirt.msi [feature flags][licensing flags]
   Use feature flags for the architecture that matches your sequencing station operating system:
   
   32-bit:ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core
   64-bit:ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core,OSppWoW64
   
   You must enter one of the licensing flags in the following list to correctly configure the deployment kit. Otherwise, functionality may be incorrect.
   
   To learn more about which activation and licensing flags to use, go to the following Microsoft website:
   
   Office 2010 volume activation

   (http://blogs.technet.com/office2010/archive/2009/08/24/volume-activation.aspx)
   
   

   KMS activation

   Setting any of these flags to 1 will install the KMS client key for the specified product.
   
   Properties for Office 2010 suites
   
   
   Collapse this tableExpand this table

   Flag	Value	Product for which licensing is enabled
   PROPLUS	0 or 1	Microsoft Office Professional Plus
   SMALLBUSBASICS	0 or 1	Microsoft Office Small Business Basics
   STANDARD	0 or 1	Microsoft Office Standard

   Properties for Office 2010 stand-alone applications
   Collapse this tableExpand this table

   Flag	Value	Product for which licensing is enabled
   ACCESS	0 or 1	Microsoft Access
   EXCEL	0 or 1	Microsoft Excel
   GROOVE	0 or 1	Microsoft SharePoint Workspace
   INFOPATH	0 or 1	Microsoft InfoPath
   ONENOTE	0 or 1	Microsoft OneNote
   OUTLOOK	0 or 1	Microsoft Outlook
   POWERPOINT	0 or 1	Microsoft PowerPoint
   PROJECTPRO	0 or 1	Microsoft Project Professional
   PROJECTSTD	0 or 1	Microsoft Project Standard
   PUBLISHER	0 or 1	Microsoft Publisher
   SPD	0 or 1	Microsoft SharePoint Designer
   VISIOPREM	0 or 1	Microsoft Visio Premium
   VISIOPRO	0 or 1	Microsoft Visio Professional
   VISIOSTD	0 or 1	Microsoft Visio Standard
   WORD	0 or 1	Microsoft Word

   Properties for KMS host configuration
   Collapse this tableExpand this table

   Flag	Value	Description
   KMSSERVICENAME	[Host]	Enter KMS host name (not required if KMS host is registered on DNS and port = 1688.)
   KMSSERVICEPORT	[Port]	Not required if KMS host is registered on DNS and port = 1688.

   Example 1
   
   KMS activation, default KMS host settings, on a 32-bit sequencing station:
   
   msiexec /i OffVirt.msi [featureflags] PROPLUS=1 VISIOPREM=1
   
   Example 2
   
   KMS activation, user-defined KMS host settings, on a64-bit sequencing station:
   
   msiexec /i OffVirt.msi [featureflags] PROPLUS=1 PROJECTPRO=1 KMSSERVICENAME=”kms.contoso.com” KMSSERVICEPORT=1689
   
   MAK activation
   
   Option 1
   
   Use VAMT 2.0 (recommended) to install product keys on client computers that are streaming Office 2010.
   
   Option 2
   Collapse this tableExpand this table

   Flag	Value
   PIDKEYS Multiple product keys are semicolon delimited. For example: PIDKEYS=X-X-X-X-X; Y-Y-Y-Y-Y;	XXXXX-XXXXX-XXXXX-XXXXX-XXXXXX
   USEROPERATIONS	0 or 1

   
   Important You must set USEROPERATIONS to 1 (USEROPERATIONS=1) to let a user activate licensing on the client computer. 
   
   The following is an example of a command for MAK activation on a 64-bit App-V sequencer server:
   
   
   msiexec /i OffVirt.msi [featureflags] PIDKEYS=XXXXX-XXXXX-XXXXX-XXXXX;YYYYY-YYYYY-YYYYY-YYYYY-YYYYY USEROPERATIONS=1
   
   
   
   • Mixed activation (KMS/MAK): If you want some client computers to use KMS activation but other client computers to use MAK, follow these steps:
     1. Use the KMS flags to install KMS client keys.
     2. Use VAMT 2.0 to install the MAK key after the deployment
   
   

Step 4: Sequence Office 2010

1. Start the App-V sequencer.
2. Click Create Package.
3. Create a name for the package.
4. For the installation folder, install to a new directory that has an 8.3 format (for example, Q:\Temp123.wxp), and then click OK.
5. Click Begin Monitoring.
6. Start the Setup program for Office 2010. Important: If you are sequencing Visio 2010 you will need to perform the following numbered steps to ensure it is licensed correctly. This must be applied during installation and these steps apply to Visio 2010 only.
7. 1. Within the Sequencer, choose a custom installation.
   2. When prompted, choose Run...
   3. Open a command prompt with Administrative rights and locate the setup executable for Visio 2010.
   4. Open Notepad, and enter the following text:
   5. <Configuration Product="Visio">
       <PIDKEY Value="xxxxxxxxxxxxxxxxxxxx" />
      </Configuration>
   6. Replace the xxx's with the appropriate 25-digit KMS or MAK key, depending on your licensing model and version of Visio. A list of KMS keys can be found at http://technet.microsoft.com/en-us/library/ee624355.aspx 
      (http://technet.microsoft.com/en-us/library/ee624355.aspx)
   7. For further guidance with these parameters, see http://technet.microsoft.com/en-us/library/cc179195.aspx#BKMK_PIDKEY_MAK
      (http://technet.microsoft.com/en-us/library/cc179195.aspx#BKMK_PIDKEY_MAK)
   8. Save the file as config.xml in the same directory as the Visio setup executable
   9. From the open command prompt, run the following command: setup.exe /config <absolute file path to config.xml>
8. At the Choose the installation that you want screen, click Customize. In the Office install procedure, make sure that you select Install to hard drive if you want that feature installed.
9. Click the File Location tab, and then change the path so that it matches the directory that you selected for installation when you started monitoring (for example, Q:\Temp123.wxp).
10. Click Install Now.
    

Step 5 (optional): While you are still in monitoring mode, start the virtual applications

This step configures the first-start use settings. For example, to customize user settings, you must browse to actual path of the virtual application.

1. Click Start, and then click Run.
2. Browse to the executable virtual file that you want to start. For example, to start Microsoft Word, type the following command, and then press Enter:
   Q:\Temp123.wxp\Office14\WINWORD.EXE
3. If you are sequencing without proxies, click Stop Monitoring, and then go to step 5d. If you are sequencing with proxies, follow the instructions under Configure Additional Proxies before you go to step 5d. 
4. Click Next to end the monitoring.

Important If you performed the optional "Start virtual applications during monitoring" procedure, go to the next step.

Step 6: Start applications to create primary feature block

We do not recommend that you start Microsoft OneNote, Microsoft Outlook, or Microsoft SharePoint. If you do not start these applications, the customization settings are better preserved.

1. On the Application page, click Next.
2. Select and start your preferred applications to generate the primary feature block for each application.
3. Click Next.
4. After sequencing is complete, click Finish.
5. Save the package. To do this, on the menu toolbar, click Save As under Package.
6. Configure additional proxies (optional). To do this, follow these steps on the sequencer:
   
   Important The following step must be performed during monitoring to have these keys correctly persisted in a deleted state in the virtual registry.
   
   1. Make sure that the sequencer is still monitoring. If it is still monitoring, go to step 2 . If the sequencer is not monitoring, go to steps 1a and 1b before you go to step 2.
      1. Click Back to return to the previous step.
      2. Click Begin Monitoring.
   2. Create the following virtual registry keys, and then delete them so that the sequencer monitors the deletion of the newly added keys.
      
      If you are sequencing on a 32-bit operating system, the keys are as follows:
      • KEY_CLASSES_ROOT\CLSID\{9203C2CB-1DC1-482d-967E-597AFF270F0D}\TreatAs
      • HKEY_CLASSES_ROOT\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F}\TreatAs
        
      
      If you are sequencing on a 64-bit operating system, the keys are as follows:
      • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9203C2CB-1DC1-482d-967E-597AFF270F0D}\TreatAs
      • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F}\TreatAs
        
      
      
      
      
7. Determine the version of Office 2010 Setup.exe that was used to install Office 2010. To do this, follow these steps:
   
   
   1. Right-click the Setup.exe file for the Office installation file, and then select Properties.
   2. Click the Version tab.
   3. Note this version. We will change the version of all the new proxy OSD files to match that version in the steps in step 6h.
   
   For example, if the version of Setup.exe is 14.0.4763.1000, make sure that the version number of all proxy application OSDs and all Office OSDs are set to 14.0.4763.1000. We will do this in step 6h.
   
8. Add new proxy applications for proxy support. To do this, follow these steps:
   1. Stop monitoring, move into the Configure Applications page, and then select the Applications root directory.
   2. Click Add, and then add the following applications.
      
      Note To quickly locate the path, click Browse, and then copy and paste the application path into the File name field.
      
      Application (OSD) files to add are described in the following table: 
      
      
      Collapse this tableExpand this table

      Application name	Application path	Version	OSD file name
      Search MAPI Protocol Handler Host	%commonprogramfiles%\microsoft shared\virtualization handler\VirtualSearchHost.exe	As mentioned in step 6G. For example, 14.0.4763.1000	Update version into file name
      Microsoft SharePoint Client Support Manager	%commonprogramfiles%\microsoft shared\virtualization handler\VirtualOWSSuppManager.exe	As mentioned in step 6G. For example, 14.0.4763.1000	Update version into file name
      Microsoft Virtual Office Simple Mapi Proxy Server	%commonprogramfiles%\microsoft shared\virtualization handler\MapiServer.exe	As mentioned in step 6G. For example, 14.0.4763.1000	Update version into file name
      Virtual Mail Control Panel	%windir%\system32\Control.exe %SFT_MNT%\short path\Office14\mlcfg32.cpl Note To add the parameter %SFT_MNT%\short path\Office14\mlcfg32.cpl to the application path, browse to the Control.exe application path, and then click OK. Then, append the parameter in the Application Path field.	As mentioned in step 6G. For example, 14.0.4763.1000	Update version into file name
      Microsoft Office Document Cache	Q:\short path\Office14\MSOSync.exe Note The short path is the 8.3 directory to which you installed Office 2010. For example, if you installed Office 2010 to Q:\Temp123.wxp, the short path would be Temp123.wxp.	As mentioned in step 6G. For example, 14.0.4763.1000	Update version into file name

      
      
   
   
   
   
   
9. Set the Office Document Cache application to start automatically.
   
   
   1. Expand the Office Document Cache element in the Applications tree under Configure Applications.
   2. Select Shortcuts.
   3. Edit the shortcut location to be Start Menu\Programs\Startup.
10. Start applications to create Primary Feature Block.
    
    Important We do not recommend starting OneNote, Outlook, or SharePoint during sequencing to avoid setting default values that may not be appropriate for all users. Other Office applications (Word, Excel, PowerPoint, and so on) should be started during sequencing to optimize initial startup.
    
    
    1. On the Launch Applications page, select and start all desired applications to generate the primary feature block for each application.
    2. Click Next.
    3. After sequencing is complete, click Finish.
11. Configure the Office 2010 registry setting.
    
    After the Sequencing Wizard is finished, select the Virtual Registry tab, and then verify that the following virtual registry key is set to Merge with Local.
    
    If you are sequencing on a 32-bit operating system, the key is as follows:
    
    MACHINE\Software\Microsoft\Office\14.0

    
    
    If you are sequencing on a 64-bit operating system, the key is as follows:
    
    MACHINE\Software\Wow6432Node\Microsoft\Office\14.0
    
    To perform the verification, follow these steps:
    1. Right-click the key, select Key, and then verify that the Merge with Local Key check box is selected.
       
       Very important If you are deploying Office 2010 to computers that already have 2007 Office installed (2007 Office and Office 2010 coexistence), go to step 6k2. Otherwise, skip step 6k2 and go to step 6k3. Also, refer to the note on Microsoft Outlook coexistence in the following article in the Microsoft Knowledge Base:  
       2481474

       (http://support.microsoft.com/kb/2481474/ )

        Known issues and limitations when using virtualized Office 2010 applications on App-V 4.6 and App-V 4.5 SP2 clients 
    2. During monitoring, create the following registry subkey:
       
       
       HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
       
       If you are sequencing on a 64-bit version of Windows, also create the following subkey:
       
       
       HKEY_CURRENT_USER\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
       
       For App-V 4.6, make sure that the subkey is set to Override local key.
       
       For App-V 4.5, follow these steps: 
       1. Set the parent key (…\CurrentVersion\Windows Messaging Subsystem) to Merge with local key.
       2. Set the subkey (…\CurrentVersion\Windows Messaging Subsystem\Profiles) to Merge with local key.
       
       
       
    3. Important Follow these steps during monitoring to have the key persist in a deleted state in the virtual registry:
       1. On the Tools menu, click Sequencing Wizard.
       2. Click Next.
       3. Click Begin Monitoring.
       4. Start Registry Editor, create the following virtual registry subkey, and then delete the subkey so that the sequencer monitors the deletion of the newly added key:
          
          
          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\Microsoft.OMSAddin
          
          
       5. Exit Registry Editor, and then return to the sequencer. 
       6. Click Stop Monitoring and continue to click Next and then click Finish to return to the advanced sequencer properties page.
       
       
12. Configure virtual applications to interact with the local environment.
    
    Note You may have to add some of these XML nodes if they currently do not exist. 
    
    For each OSD, add TRUE to the following Element field of the tag:
    
    SOFTPKG -> IMPLEMENTATION -> VIRTUALENV -> POLICIES -> LOCAL_INTERACTION_ALLOWED
    
13. Configure a client computer to run virtualized Office 2010. To do this, follow these steps on the client computer:
    1. Prepare the client computer.
       
       
       1. Install the App-V client if you have not already done this. 
       2. Download the Deployment Kit, and then extract the executable (*.exe). After you extract the executable, you should have a file that is named OffVirt.msi.
       
       
    2. Install the Microsoft Office 2010 Deployment Kit.
       1. Open a command prompt with administrative permissions.
          
          Note If you open the command prompt without elevation and then run the msiexec command, an installation dialog box will not be displayed, and the installation will fail. 
       2. Browse to the directory that contains the Offvirt.msi file.
       3. At the command prompt, run the following command:
          
          msiexec /i OffVirt.msi [licensing flags]
          
          
          You must enter correct licensing flags to correctly configure the Deployment Kit. Otherwise, functionality may be incorrect. For example, type the following command:
          msiesec /I Offvirt.msi PROPLUS=1 USEROPPERATIONS=1
          
          Licensing flags
          
          Learn more about Office 2010 volume activation
          (http://blogs.technet.com/office2010/archive/2009/08/24/volume-activation.aspx)
          to determine which activation and licensing flags to use.
          
          KMS activation
          
          Setting these flags to 1 will install the KMS client key for the specified products.
          
          Properties for Office 2010 suites
          Collapse this tableExpand this table

          Flag	Value	Products for which licensing is enabled
          PROPLUS	0 or 1	Office Professional Plus
          SMALLBUSBASICS	0 or 1	Small Business Basics
          STANDARD	0 or 1	Standard

          
          Properties for Office 2010 stand-alone applications
          Collapse this tableExpand this table

          Flag	Value	Products for which licensing is enabled
          ACCESS	0 or 1	Access
          EXCEL	0 or 1	Excel
          GROOVE	0 or 1	SharePoint Workspace
          INFOPATH	0 or 1	InfoPath
          ONENOTE	0 or 1	OneNote
          OUTLOOK	0 or 1	Outlook
          POWERPOINT	0 or 1	PowerPoint
          PROJECTPRO	0 or 1	Project Professional
          PROJECTSTD	0 or 1	Project Standard
          PUBLISHER	0 or 1	Publisher
          SPD	0 or 1	SharePointDesigner
          VISIOPREM	0 or 1	Visio Premium
          VISIOPRO	0 or 1	Visio Professional
          VISIOSTD	0 or 1	Visio Standard
          WORD	0 or 1	Word

          
          
          MAK activation
          
          Option 1: Use VAMT 2.0
          (http://www.microsoft.com/en-us/download/details.aspx?id=11936)
          (recommended) to install product keys on client computers streaming Office 2010.
          
          Option 2:
          Collapse this tableExpand this table

          Flag	Value
          PIDKEYS Multiple product keys are semicolon-delimited. For example: PIDKEYS=X-X-X-X-X; Y-Y-Y-Y-Y;	XXXXX-XXXXX-XXXXX-XXXXX-XXXXXX
          USEROPERATIONS	0 or 1

          
          Very Important You must set USEROPERATIONS to 1 (USEROPERATIONS=1) to let a user activate licensing on the client computer. 
          
          The following is an example of a command for MAK activation on a 64-bit App-V sequencer server:
          
          msiexec /i OffVirt.msi PIDKEYS=XXXXX-XXXXX-XXXXX-XXXXX;YYYYY-YYYYY-YYYYY-YYYYY-YYYYY USEROPERATIONS=1
          
          Mixed activation (KMS/MAK): If you want some client computers to use KMS activation but other client computers to use MAK, follow these steps:
          1. Use the KMS flags to install KMS client keys.
          2. Use VAMT 2.0 to install the MAK key after the deployment.
          
          
          
       
       
    
    
14. Configure proxies on the client (optional).
    
    Important Perform this optional step only if you configured proxies during the sequencing step.
    
    To enable the proxies on the client, open a command prompt as an administrator. You have to run msiexec again after you run msiexec with the license flags if you want proxies with the flags mentioned here. (Or you can run all the flags together in one execution.)
    
    For example, you could use the following commands:
    
    msiexec /i Path to the OffVirt.msi\OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PACKAGEGUID={SFT package GUID} PACKAGEVERSION=versions found in OSD files for proxies, Outlook, and OneNote OUTLOOKNAME=app name for Outlook from OSD ONENOTENAME=app name for OneNote from OSD MAPISERVER=MAPI proxy app name VIRTUALSEARCHHOST=Search proxy app name MLCFG32CPL=app name for virtual mail configuration OWSSUPPServer=app name for SharePoint proxy
    
    Specifically, you could use the following commands:
    
    msiexec /i c:\OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PACKAGEGUID={5971AF75-7831-4AE9-906F-0F30C7DD0CA5} PACKAGEVERSION=14.0.4763.1000 OUTLOOKNAME="Microsoft Outlook 2010" ONENOTENAME="Microsoft OneNote 2010" MAPISERVER="Microsoft Virtual Office Simple Mapi Proxy Server" VIRTUALSEARCHHOST="Search MAPI Protocol Handler Host" MLCFG32CPL="Windows Control Panel" OWSSUPPServer="Microsoft SharePoint Client Support Manager" 
    
    Note The registration of each component as shown earlier is required because of dependencies between proxy components.

Known issues when you sequence Office 2010

Issue 1: You cannot start x64 Visio 2010 during the monitoring phase of sequencing on an x64 Windows Vista-based computer

To resolve this issue, restart monitoring. To do this, click Stop monitoring, click Start monitoring, and then start Visio.

Issue 2: Saving the sequenced Office 2010 package fails with the message "A sharing violation occurred"

To resolve this issue, add an exclusion item to the App-V Sequencer. To do this, follow these steps:

1. Open the App-V 4.5 SP2 Sequencer.
2. On the Tools menu, click Options.
3. Click the Exclusion Items tab.
4. Add a new exclusion item for the following path:
   %CSIDL_COMMON_APPDATA%\Microsoft\Search

Known issues and limitations when you use Office 2010 virtualized

For a list of known issues and limitations that you may encounter when you use Office 2010 virtualized on App-V, click the following article number to view the article in the Microsoft Knowledge Base: