none
Sequencing MUIs for Microsoft Office 2007

    General discussion

  • This provides general instructions for sequencing Microsoft Office 2007 and multiple languages in order to deploy each language separately from the main package.  The outcome of these sequencing steps will provide a minimum of two packages:

    1. A core Office 2007 virtualized application.

    2. At least one virtualized language pack for Office 2007.

    When deployed together by using App-V's Dynamic Suite Composition (DSC) this will allow the virtualized Office 2007 package to match the hosts operating language for the Office Interface, dictionaries, grammar, and all other language changeable components; if more than one virtualized language is deployed the user will be able to switch languages on the fly.

     

    Application Name: Microsoft Office 2007 Multiple Language Pack

    Application Version: Office 2007

    Company Name:Microsoft

    Sequencer Version: 4.5 Service Pack 1

    App-V Client Version Tested On:4.5 Service Pack 1

    Operating System Sequenced On: Windows XP

    Pre-requisites: It is assumed throughout this document that all best practices are followed and that the person doing the sequencing is familiar with App-V and sequencing.

    Client Operating Systems Successfully Deployed To:Windows XP Service Pack 2

    Posted by Microsoft Employee: Justin Zarb

    Corresponding KB Article Reference: http://blogs.technet.com/b/appv/archive/2009/01/20/sequencing-microsoft-office-2007-core-with-multiple-language-packs-via-dsc.aspx

    Steps to Sequence the Application:

    Base sequencing

    It is assumed throughout this document that all best practices are followed and that the person doing the sequencing is familiar with App-V and sequencing.

    Sequencing the Core Office 2007 package

    Sequence Office 2007 and customize as normal for your organization.  A sample recipe can be found here.  The following are assumed:

    · Office 2007 is sequenced to Q:\off2k7en.001 and is the English core language

    · Installation of the components required and configuration is already known.

    Post installation steps

    1. File System: Remove Q:\MSOcache

    2. Sequencer Files Tab: Delete VFS\CSIDL_WINDOWS\Installer directory

    3. Sequencer Virtual Registry Tab: Delete the following hives:

    User\%SFT_SID%\Software\Microsoft\Windows\CurrentVersion\Internet Settings

    User\%SFT_SID%\Software\Microsoft\Internet Explorer

    4. Sequencer Virtual File System Tab: Ensure that no files are present under:

    CSIDL_WINDOWS\Installer and SFT_MNT\MSOCache

    Sequencing an Office 2007 Language package

    Sequencing each Office 2007 language pack should be performed on a clean sequencer with the following changes:

    · Office 2007 is installed to Q:\off2k7en.001

    Note: This should be the same installation configuration as the sequenced version with the exception that this is a native install

    · For this document, the French language is assumed and will be deployed to Q:\off2k7fr.001

    Post installation steps

    1. File System: Remove Q:\MSOcache

    2. Sequencer Files Tab: Delete VFS\CSIDL_WINDOWS\Installer directory

    3. Sequencer Virtual Registry Tab: Delete the following hives:

    User\%SFT_SID%\Software\Microsoft\Windows\CurrentVersion\Internet Settings

    User\%SFT_SID%\Software\Microsoft\Internet Explorer

    4. Sequencer Virtual File System Tab: Ensure that no files are present under:

    CSIDL_WINDOWS\Installer and SFT_MNT\MSOCache

    Updates made outside the Sequencer for the Office 2007 Core virtualized application

    1. Modify the OSD files to include the following section after the tag “ENVLIST” (items in red are specific to the sequence and shown for reference purposes only)

    <DEPENDENCIES><CODEBASE 

    HREF="RTSPS://%server%:322/off2k7fr.001/OfficeMUIName.sft" 

    GUID="06A77DB2-C140-4BFA-B96E-3D54FD10E4EB" 

    SYSGUARDFILE="off2k7fr.001\osguard.cp" MANDATORY="TRUE"/> 

    </DEPENDENCIES>

    2. Multiple CODEBASE sections can be added for more languages

    3. This change can be scripted and performed dynamically which will allow for web site customization and automation of language deployments.

     

     

    This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

    Some examples depicted herein are provided for illustration only and are fictitious.  No real association or connection is intended or should be inferred.

    This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.

     

    Tuesday, June 22, 2010 9:32 AM