Follow / Friend Us
Continuing on from Sequencing Office 2010 for App-V, Part 1 and Part 2, Matt and Jason from 43Tc to share their real world experiences with Office 2010 and App-V and provide guidance on sequencing Office for App-V. In part 3 we look at Sequencing Office 2010.
Note: for future reference, you can leverage Office customizations you maintain with tools like Office Customization Tool, however in this example we will explicitly customize the installation.
Note: Items cannot be set to "Install on First Use". The user will be unable to add any such marked items once the application is virtualized.
Note: It is a best practice to disable any automatic updates for virtual applications. When virtualizing applications, updates will be managed centrally and performed on the sequencer. This avoids application updates being placed in the User Package Volume file and unnecessarily growing the user profile.
Note: DO NOT Launch Outlook or One Note or access a SharePoint site due to user specific customizations that take place on first run/hit that we do not want to capture
In this section we will create individual virtual application entries for the Feature Proxies provided by the Office 2010 Deployment Kit for App-V. We are still on the Edit Shortcuts screen from the last step.
IMPORTANT: entries are cAsE SeNsItIvE. To make each entry easier we recommend copy/pasting the Application Path lines if you are able. Once the Application Path line is entered, the other fields will auto propagate. Add each bullet item below separately. See the below screen shot for an example.
Description: Instant Search (Virtual Search Host) using Windows Desktop Search (WDS)
Application Path: %commonprogramfiles%\microsoft shared\virtualization handler\VirtualSearchHost.exe.
Name: Search MAPI Protocol Handler Host
Description: Virtual SharePoint Proxy
Application Path: %commonprogramfiles%\microsoft shared\virtualization handler\VirtualOWSSuppManager.exe
Name: Microsoft SharePoint Client Support Manager
Description: Simple MAPI
Application Path: %commonprogramfiles%\microsoft shared\virtualization handler\MapiServer.exe.
Name: Microsoft Virtual Office Simple Mapi Proxy Server
Description: Virtual Mail Control Panel Applet
Application Path: %windir%\system32\Control.exe %SFT_MNT%\Office2010_x86\Office14\mlcfg32.cpl
Name: Windows Control Panel
Description: Office Document Cache
Application Path: Q:\Office2010_x86\Office14\MSOSync.exe
Name: Microsoft Office Document Cache
Office 2010 will be a very large package (in the area of 2 gigabytes). As such the next steps will walk you through splitting the package in to Feature Blocks. Feature blocks separate the specific bits of the package that are most commonly used and needed to launch the application from lesser used bits. The result is that on first launch, rather than the user getting the entire package, they will only receive the most commonly used bits (in the area of only a few hundred Megs). The remaining bits will remain on the server until they are used by the user.
IMPORTANT: DO NOT launch OneNote, Outlook, or SharePoint due to their automatic user specific customization settings.
REMEMBER: DO NOT launch OneNote, Outlook, or SharePoint due to their automatic user specific customization settings.
Note: To further reduce the amount of network traffic during streaming, you can elect to compress the package. This can sometimes impact first-launch performance by a couple of seconds as the client must decompress each block it receives.
You should now have:
Stay tuned for Part 4, in which we prepare the clients to receive the Office 2010 package.