Contents. Chapter 1 Introducing virtualized Microsoft Office Chapter 2 Packaging Microsoft Office... 5

Transcription

1 Contents Chapter 1 Introducing virtualized Microsoft Office About virtualized Microsoft Office... 3 Use cases... 3 Chapter 2 Packaging Microsoft Office... 5 About preparing a packaging system... 5 About packaging Office About Visual C++ runtime dependencies... 8 Chapter 3 Preparing to deploy Office Licensing virtualized Microsoft Office 2010 with a KMS or MAK... 9 Setting up a service in a layer Rearming the 30-day token renew timer Running Office 2010 with multiple layers Running Office 2010 with MUI layers Chapter 4 Configuring additional options Optimizing virtualized Office Configuring administrator permissions About running two versions of Office... 18

2 2 Contents

3 Chapter 1 Introducing virtualized Microsoft Office 2010 This chapter includes the following topics: About virtualized Microsoft Office Use cases About virtualized Microsoft Office This guide provides a collection of best practices when you virtualize Microsoft Office Office is one of the most virtualized applications with Symantec Workspace Virtualization. However, certain issues arise due to the diverse ways that customers virtualize Office along with the Microsoft licensing features unique to Office These instructions help you navigate these realities. This guide is meant to document specific steps for Office However, you can also use virtualization to run two versions of Office concurrently. For information on running Office 2007 and 2010 concurrently: See About running two versions of Office on page 18. Furthermore, this guide is not intended to present all aspects of packaging and deploying in Wise Virtual Composer (WVC). Instead, the guide provides information on the unique aspects and necessary steps for packaging Office Use cases The process that you follow to virtualize Office 2010 depends on your environment and your end use goals. Choose the appropriate virtualization process for your organization based on the most similar use case.

4 4 Introducing virtualized Microsoft Office 2010 Use cases Before beginning the packaging process, you may want to review guidelines of packaging Office: See About preparing a packaging system on page 5. See About packaging Office 2010 on page 6. Table 1-1 Use cases Use cases Packaging and Deploying Microsoft Office 2010 in a single layer. Instructions To complete this process, do the following: See About packaging Office 2010 on page 6. See Setting up a service in a layer on page 11. See Rearming the 30-day token renew timer on page 11. Packaging and Deploying Microsoft Office 2010 in multiple layers. To complete this process, do the following: See About packaging Office 2010 on page 6. See Setting up a service in a layer on page 11. See Rearming the 30-day token renew timer on page 11. See Running Office 2010 with multiple layers on page 12. Packaging and Deploying Microsoft Offce 2010 with Multiple User Interfaces (MUIs) To complete this process, do the following: See About packaging Office 2010 on page 6. See Setting up a service in a layer on page 11. See Rearming the 30-day token renew timer on page 11. See Running Office 2010 with MUI layers on page 15. Refer to the following for information on virtualizing Office 2010 with a Key Management Server (KMS) or Multiple Activation Key (MAK). See Licensing virtualized Microsoft Office 2010 with a KMS or MAK on page 9.

5 Chapter 2 Packaging Microsoft Office This chapter includes the following topics: About preparing a packaging system About packaging Office 2010 About Visual C++ runtime dependencies About preparing a packaging system Consider the following guidelines to set up a packaging system: Capture on a virtual machine. After your virtual machine is set up, take a snapshot of the entire virtual machine. After you package applications, you can revert to the snapshot and have a clean virtual machine ready for capture. If you use a virtual machine, allocate 1.5 GB of RAM for the image and at least 1 GB for Wise Virtual Composer. In addition, allocate 20 GB for the virtual machine and 15 GB to store captured applications. The 20-GB requirement for the virtual machine includes 4 GB to 5 GB for the operating system. Symantec recommends that you only install a Windows operating system and service pack or patches to your packaging computer. Do not include any other applications such as antivirus scanners or backup utilities. Turn off Automatic Updates, Firewall, Security Notifications, User Access Control, Windows Defender, and similar programs. Do not connect to your production network. Capture on a system where the Office installation program has not executed. If you attempt to capture on a system where an Office installation program has been executed, you might receive a sharing violation with Office If.NET is not installed on the target endpoints, capture on a computer that does not have.net installed. Windows Vista and Windows 7 include.net by default.

6 6 Packaging Microsoft Office About packaging Office 2010 If you only distribute to a corporate environment, you can use the base desktop image as the packaging computer. The base desktop image has all of the same components and libraries that are installed as the client images. Therefore, even if the installer skips files, no problem results. Use different computers to test packaging. Refer to the following for information on packaging Microsoft Office See About packaging Office 2010 on page 6. About packaging Office 2010 Symantec Workspace Virtualization uses Wise Virtual Composer to package applications such as Office Packaging is the process that converts an installation program into a format that can be virtualized on an endpoint. For a complete overview, please refer to the following Wise Virtual Composer 6.1 SP1 User Guide at the following URL: Consider the following unique guidelines when you package Office 2010: The most common capture issue with Office products is the dependency on the Visual C++ runtimes. Typically, this dependency only becomes an issue when you package and deploy on XP computers. By default, the necessary runtimes are automatically installed and active on Vista and Windows 7. See About Visual C++ runtime dependencies on page 8. Use Wise Virtual Composer if the package is intended for a streaming environment. Wise Virtual Composer provides better handling of advertised shortcuts and the template feature enables additional packaging options. All Office products that you want to stream should be distributed in a single package. Office products use a number of shared resources that can cause conflicts when accessed by multiple virtualized applications. Symantec Workspace Streaming and Symantec Workspace Virtualization 6.1 SP6 or later provide support for virtualizing and streaming Office Set up exclude entries for Office, either by location or file type. If you want to set them up by file type, Symantec recommends using LayerExcludeFinder to automatically generate the exclude entries. When you deploy Office 2010 you need to perform the capture on the same operating system on which you plan to deploy. This capture is required due to the significant differences in paths and installed components between

7 Packaging Microsoft Office About packaging Office platforms. If you use Workspace Streaming, you can select a preinstallation script to install the Visual C++ runtimes before the application is streamed. If you capture on Windows Vista or Windows 7, ensure that the Visual C SP1 runtime libraries are available on each endpoint. If you use 32-bit Office, install the 32-bit runtimes. If you use 64-bit Office 2010, install the 64-bit runtimes. For more information on packaging Office with Windows 7, see the article at the following URL: Table 2-1 Potential issues Potential issue Work around If you save Microsoft Word files in Windows 7 to the desktop, the file does not show until you refresh the desktop. You receive an error message BCSSync.exe - Unable to locate Component Body: This application has failed to start because mscoree.dll was not found. Refresh the desktop or access the file by opening Windows Explorer. Install.NET on the endpoint where this error occurs or recapture on a Windows XP computer that does not have.net installed. For more information, see the article at the following URL: and-swvbcssyncexe-unable-locate-componenterror-thrown-when-layer-activated SWVAdmin displays an error when you attempt to export a.vsa file of Office 2010 on 64-bit operating systems. Use SWVCmd to export a.vsa file, or use SWVAdmin, SWVCmd, or Wise Virtual Composer to export an.xpf file. Microsoft does not support two versions of Microsoft Outlook on the same computer. If you have a version of Outlook already installed or virtualized, you might not be able to launch another version. Due to the number of shared resources that different versions of Outlook use, two versions of Microsoft Outlook is an unsupported configuration. Refer to the following for information on specific use cases for packaging and deploying Microsoft Office See Use cases on page 3.

8 8 Packaging Microsoft Office About Visual C++ runtime dependencies About Visual C++ runtime dependencies A common issue that is associated with deployment of Office 2010 is the handling of the dependency on the Microsoft Visual C SP1 runtime. To successfully capture Office and avoid recurring repair installations, ensure that Visual C SP1 runtime (version ) is installed. This runtime version is installed and active by default on Windows Vista and Windows 7. Additionally, Visual C SP1 runtime is installed with the Wise Virtual Composer (WVC) installation. Note: More than one version of Visual C++ Runtime can be present simultaneously on a computer, and it is not backward-compatible. Check the control panel to ensure that the correct version of Microsoft Visual C SPI Redistributable is installed. During Office installation, if the Visual C++ runtime is not available on the computer, Office installs it. The correct version of Microsoft Visual C Redistributable can be downloaded directly from Microsoft at the following URL: To avoid this issue, distribute the Visual C++ runtime as part of your base image or as its own virtual layer. Refer to the following for information on specific use cases for packaging and deploying Microsoft Office See Use cases on page 3.

9 Chapter 3 Preparing to deploy Office 2010 This chapter includes the following topics: Licensing virtualized Microsoft Office 2010 with a KMS or MAK Setting up a service in a layer Rearming the 30-day token renew timer Running Office 2010 with multiple layers Running Office 2010 with MUI layers Licensing virtualized Microsoft Office 2010 with a KMS or MAK When virtualized Microsoft Office 2010 is volume licensed, you can use a Key Management Server (KMS) or Multiple Activation Key (MAK).

10 10 Preparing to deploy Office 2010 Licensing virtualized Microsoft Office 2010 with a KMS or MAK To activate the license with a KMS 1 Open the config.xml file in a text editor, such as Notepad. For information from Microsoft on editing the config.xml please see the following link: 2 Add the following command: <Setting ID="KMSSERVICENAME" Value="YOUR KMS SERVER HERE" /> <SettingId="KMSSERVICEPORT" Value="YOUR KMS PORT HERE" /> The KMS Port entry is optional and only needed if you are not using the default port. Sample File: <Configuration Product="ProPlus"> <Display Level="none" CompletionNotice="no" SuprressModal="yes" AcceptEula="yes" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <Setting Id="KMSSERVICENAME" Value="YOUR KMS SERVER HERE" /> <Setting Id="AUTO_ACTIVATE" Value="1" /> </Configuration> 3 Capture a command prompt and run something similar to the following command: setup.exe /config myconfig.xml To activate the license with a MAK 1 After streaming the package, open a command prompt and browse to the folder: C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform 2 Execute the prompt: mofcomp.exe OSPPWMI.MOF 3 Manually invoke activation by opening another command prompt. 4 Run the following command: cscript ospp.vbs /act

11 Preparing to deploy Office 2010 Setting up a service in a layer 11 For more information on the ospp.vbs script reference, please see the following link: For information from Microsoft on using a KMS or MAK with Office, see the videos at the following URL: 7fc4bc9a-794b-46c2-833c-265b3be4ed92&from=mscomoffice Setting up a service in a layer The different OSPPSvc services can cause issues within the layer, especially when you use KMS or MAK. However, these steps need to be completed regardless of whether you use KMS, MAK, or a single registry code. To set up services in a layer 1 In the layer, navigate to HKLM\system\osppsvc. 2 Set the Start value to 2. 3 In the base, navigate to HKLM\system\CurrentControlSet\Services\FSLX\Parameters\FSL\<layer magic number>\services\fsl_osppsvc. 4 Set the Start value to 2. Additionally, it may be necessary to rearm the 30 day token renew timer. See Rearming the 30-day token renew timer on page 11. Rearming the 30-day token renew timer Make sure that you rearm the 30-day token renew timer after packaging. Do not trigger the timer during packaging.

12 12 Preparing to deploy Office 2010 Running Office 2010 with multiple layers To rearm the token renew timer 1 Capture the application. 2 Run the rearm command. After you run the rearm command, do not do anything in the layer. Anything you do in the layer starts the 30-day timer. For information on running the rearm command and troubleshooting Key Management Servers, see the video from Microsoft at the following URL: 3 Package and export the layer. If you are running Microsoft Office in a single layer, you are ready to deploy or stream the package. If you are running Microsoft Office in multiple layers, See Running Office 2010 with multiple layers on page 12. Running Office 2010 with multiple layers If you run virtualized Office 2010 and standalone Microsoft applications in multiple layers, remove the Office Software Protection Platform Services (OSPPSvc) from the layers. Each layer has its own OSPPSvc instance. If this instance is not removed, token key conflicts may occur every time the layer is activated. These conflicts cause the layer to pull a new token from the Key Management Server (KMS) and slow application startup. To include OSPPSvc without conflicts, use the Microsoft Office 2010 deployment kit for App-V to put OSPPSvc in its own layer. The App-V deployment kit is a licensing component that also creates token keys in advance. You can deploy the App-V deployment kit layer before you deploy your Office layers to shorten application start times. If you deploy this layer in advance, you do not need to use the rearm command. Table 3-1 describes the process for running Office 2010 with multiple layers.

13 Preparing to deploy Office 2010 Running Office 2010 with multiple layers 13 Table 3-1 Process for running Office 2010 with multiple layers Step Step 1 Step 2 Step 3 Task Prepare your computer. Delete files. Capture the App-V deployment kit. Description Prepare your computer by capturing Office 2010 in a layer and by copying files. See To prepare your computer on page 13. Remove all instances of OSPPSvc from each standalone layer and the Office 2010 layer. See To remove OSPPSvc from a layer on page 14. Capture the Office 2010 deployment kit for App-V in a layer. See To capture the App-V deployment kit on page 15. To prepare your computer 1 Capture Office 2010 in a layer and then deactivate the layer. 2 Copy the file OSPPrun.exe from MSSharedTools to a convenient location, and then delete the file from MSSharedTools. You need this file in another procedure. 3 Copy the files from MSSharedTools\office14\officesoftwareprotectionplatform to a convenient location. You need these files in another procedure.

14 14 Preparing to deploy Office 2010 Running Office 2010 with multiple layers To remove OSPPSvc from a layer 1 Delete the following files: System/[AllUsersProfile]/Microsoft/officeprotectionplatform System\currentcontrolset\osppsvc HKLM\software\microsoft\officesoftwareprotectionplatform HKUSERS\s (or any similar short GUID) 2 In HKLM\system\currentcontrolset\services, delete any instance of OSPPSvc and CLR_optimization. 3 In the registry, delete any instance of MUICache. 4 In MSSharedTools, delete the following files: office14\liclula office14\office setup controller, pidgenx.dll, and pkeyconfig officesoftwareprotectionplatform userprofile\microsoft\officesoftwareprotectionplatform 5 In the program files\office14 folder, delete the following files: slerror.xml npspwrap 6 In SWVAdmin, double-click the layer. 7 In the Layer Properties dialog box, click the Delete entries tab. 8 In the Delete Entries tab, clear out all of the deleted entries. 9 Click Start and select Run. Type regedit and click OK. 10 Navigate to HKLM\system\currentcontrolset\services\fslx\parameters\fsl\1\services. 11 Delete HKLM\system\currentcontrolset\services\fslx\parameters\fsl\1\services\FSL_osppsvc 12 Go through the following folders and delete any folder that lists osppsvc: HKLM\system\currentcontrolset\services\fslx\parameters\fsl\1\services\Postactivate\x HKLM\system\currentcontrolset\services\fslx\parameters\fsl\1\services\Postdeactivate\x HKLM\system\currentcontrolset\services\fslx\parameters\fsl\1\services\Predeactivate\x HKLM\system\currentcontrolset\services\fslx\parameters\fsl\1\services

15 Preparing to deploy Office 2010 Running Office 2010 with MUI layers 15 To capture the App-V deployment kit 1 Download the App-V deployment kit installer from the following location: 49f12f e-bce1-682b3ece Build an msiexec string in a text file with all the token keys that the App-V deployment kit should populate from your KMS. For information on generating an msiexec string, see the article at the following URL: 3 On a clean virtual machine with Symantec Workspace Virtualization SP7, capture the App-V Licensing Component using the command line and the msiexec string. 4 Close the command prompt window to end the capture and then deactivate the layer. 5 Replace the files that you removed when you prepared your computer. 6 In SVSAdmin, right-click the layer. 7 Check Hide other layers from this layer and Keep file changes in layer. Refer to the following for additional information on optimizing virtualized Microsoft Office 2010 See Optimizing virtualized Office 2010 on page 17. Running Office 2010 with MUI layers To support Multilingual User Interfaces (MUIs), you must capture all of the MUI components in a different layer than Office However, you cannot capture the MUIs from a virtualized version of Office. You must create MUI layers. To run Office 2010 with MUI layers 1 On a clean virtual machine, install Symantec Workspace Virtualization SP7. 2 Install Office 2010 in the base exactly the way that you would in a layer. Make sure that you apply any of the same patches, admin files, or proofing tools. 3 Take a snapshot of your virtual machine. You need to revert to this snapshot each time you create a new MUI layer. 4 Capture the MUI language installation through the command prompt. 5 Once the setup is finished, use the command prompt to navigate to C:\program files\microsoft office\office14.

16 16 Preparing to deploy Office 2010 Running Office 2010 with MUI layers 6 Run setlang.exe to configure the language layer. Save the settings as the default. 7 Close the command prompt window to end the capture, and then deactivate the layer. 8 In SWVAdmin, right-click the new layer and then click Properties. 9 On the Layer Properties window, click the Autorun Applications tab. 10 Right-click inside the tab, and then click New Autorun Entry. 11 Type in or browse to the following application paths, and then click OK. C:\program files\microsoft office\office14\clview.exe C:\program files\microsoft office\office14\setlang.exe 12 Before you export, clear out the OSPPSvc instances. See Running Office 2010 with multiple layers on page 12.

17 Chapter 4 Configuring additional options This chapter includes the following topics: Optimizing virtualized Office 2010 Configuring administrator permissions About running two versions of Office Optimizing virtualized Office 2010 After you capture the Office layer or Office Multilingual User Interfaces (MUI) layers, you can optimize virtualized Office by generating an initial HashCache. Generating an initial HashCache decreases the time the layer takes to activate for the first time on a user s computer. To optimize virtualized Office Activate the layer. 2 Deactivate the layer. 3 Reset the layer. Refer to the following for information on specific use cases for packaging and deploying Microsoft Office See Use cases on page 3. Configuring administrator permissions You can configure the proper administrator permissions to ensure that users do not experience errors.

18 18 Configuring additional options About running two versions of Office For example, an error may occur when you try to launch Office 2010 as a user without administrator privileges. This error occurs because Office writes to an area that needs administrator privileges by default. To work around this issue, set the permissions in the registry to allow users without these privileges to access the files. To set the permissions in the registry 1 Activate the layer on which you want to set the permissions. 2 Open regedit and navigate to HKEY_LOCAL_MACHINE\_SWV_ LAYER_[number of the read only layer]. 3 Navigate to the registry key that needs to be modified. 4 Right-click the registry key and select Permissions. 5 Set the permissions for the keys that you want to modify About running two versions of Office Virtualization of Office lets you run two or more versions of Office concurrently. However, this configuration may cause file conflicts since Microsoft files are automatically saved as short names that become indistinguishable when virtualized. For example, a captured version of Office becomes registered in the layer as MICROS~1, its version 8.3 name. However, every install of Windows XP includes a folder in the Program Files directory named Microsoft Frontpage. This Frontpage folder is registered with the XP system as MICROS~1 by default. Therefore, when you import or capture a layer, a conflict occurs with 8.3 names. You can avoid this issue by installing Office into a different, non-microsoft directory that is not named MICROS: for example, Office2007 or MSOffice. For more information about running multiple versions of Office, see the article at the following URL: Refer to the following for information on running Office 2010 with multiple layers. See Running Office 2010 with multiple layers on page 12.