Sequencing multiple versions of the VMWare vSphere client (and reducing the size of the final sequence) RRS feed

  • General discussion

  • Application Name:  vSphere client

    Application Version:  4.1, 5.0, and 5.5 (all in one package)

    Company Name:  VMWare

    Sequencer Version:  5.0 SP1 or SP2

    App-V Client Version Tested On:  5.0, 5.0 SP1, 5.0 SP2

    Operating System Sequenced On:  Windows 7 (64bit)

    Pre-requisites:  Orca

    Client Operating Systems Successfully Deployed To:  Windows 7 (64bit), Windows Server 2008 (64bit)

    *Posted by non-Microsoft Employee:  Cody Lambert (a Fortune 100 company)

    If Posted by Microsoft Employee, the Corresponding KB Article Reference:  N/A

    Steps to Prepare and Sequence the Application:

    Phase 1:  Prepare vSphere install to be used in your sequence (to be performed prior to sequencing)

    1. Clear %TEMP% directory on machine you are using to prepare the install
    2. Create a folder that will be referred to as "vSphereInstDir" that install files are copied to
    3. Download the vSphere 5.5 client from your vSphere management server
    4. Run the installer for the vSphere Client
    5. Once at the Language Selection portion of the installer, using windows explorer browse to the %temp% directory and copy the files that were just created when the vSphere installer extracted to a directory (name it vSphereInstDir)
    6. Kill the installer
    7. Find VMware-viclient.exe in the files you just copied and run it
    8. Once at the "Welcome to the installation wizard" stage of the installer, using windows explorer browse to the %temp% directory and copy the files that were just created into the vSphereInstDir
    9. Kill the installer
    10. Find the VMware vSphere Client 5.5.msi in the vSphereInstDir, in the second set of files you copied over
    11. Using Orca, open the VMware vSphere Client 5.5.msi
    12. Drop the following rows from the msi (some of the rows may have additional text at the end of the names) (InstallExecuteSequence/VM_InstallHcmon, InstallExecuteSequence/VM_InstallHcmon_SetData, InstallExecuteSequence/VM_InstallUSB, InstallExecuteSequence/VM_InstallUSB_SetData, InstallExecuteSequence/VM_InstallUSBArbritrator, InstallExecuteSequence/VM_InstallUSBArbritratorSetData, InstallExecuteSequence/VM_StartUSBArbSvc) 
    13. Save the VMware vSphere 5.5.msi in place
    14. Copy the vSphereInstDir to a network location that can be used during sequencing on your Sequencer

    Phase 2:  Sequence the vSphere Client

    Pre-requisites:  All of the latest available VC++ redist (x64 and x86) are installed on the Sequencer VM

    1. Copy vSphereInstDir to your temporary install directory on your Sequencer (mine is C:\temp)
    2. Start up the Sequencer
    3. Click Create a New Virtual Application Package
    4. Click Next with Create Package (default) selected
    5. Click Next on the Prepare Computer screen, taking note of any findings
    6. Click Next with Standard Application (default) selected
    7. Choose Perform a custom installation, then click Next
    8. Input the Virtual Application name (vSphere Client 5.5 for example)
    9. Enter the Primary Virtual Application Directory (C:\vSphere55 for example) and click Next
    10. Using Windows Explorer find the Visual J# install (vjredist64.exe) in the vSphereInstDir you copied over.  Install using defaults
    11. Using Windows Explorer, find and install the vSphere client using the VMware vSphere Client 5.0.msi located in the vSphereInstDir you copied over.  Change the installation directory to use the Primary Virtual Application Directory you configured above (C:\vSphere55 for example).  Install using defaults
    12. While the sequencer is still monitoring changes connect to the 4.1 environment to get the files needed.  To do this, launch the vSphere client and connect to your 4.1 environment.  When prompted, choose RUN to install the files needed for the 4.1 environment.
    13. While the sequencer is still monitoring changes connect to the 5.0 environment to get the files needed.  To do this, launch the vSphere client and connect to your 5.0 environment.  When prompted, choose RUN to install the files needed for the 5.0 environment.
    14. With the sequencer still monitoring changes, after the additional environments have been installed, delete all of the language folders from the install locations that are not required.  You will find that there are language folders in each of the different modules that are installed.  Make sure look in every folder.  This will free up approximately 300mb from the package.
    15. When done, check the box to finish the sequence and continue cleaning up the sequenced application.

    Known Issues/Limitations:  Functions that require the USB Arbritration Service will not work

    Approximate Sequencing Time:  20 minutes

    Descriptive Tags:  App-V, 5.0, VMWare, vSphere, Recipe, Guidance

    Credit Due:  Thanks to Rorymon and Aaron Parker for accurate information that allowed for me to put together this recipe.

    • Edited by CodyLambert Wednesday, March 26, 2014 7:15 PM
    Wednesday, March 26, 2014 7:13 PM

All replies

  • I m a beginner in packaging.I have tried doing the above steps but still the driver is installing.Can you help me troubleshoot it.


    Thanks in Advance

    Aravinth Mathan

    Saturday, July 26, 2014 2:02 PM
  • Can you double check the that the following were removed from the MSI:








    Monday, August 4, 2014 3:16 AM
  • Thanks for this info but unfortunately after following this we still get the error 'Specified module could not be found (Exception from HRESULT: 0x8007007E)'. This is with Appv 5.1and occurs when the user attempts to log in.

    VMware vSphere version 5.5

    Sequencer - Windows 7 64-bit OS - Sequencer version

    During sequence this error does not prompt during first run and optimization steps and only occurs once presented. Also gave full permissions in Advanced options of package.

    Attempted multiple variations of packaging this including using PVAD so any recommendations are appreciated.

    • Edited by AAAyala Thursday, September 8, 2016 6:44 PM
    Thursday, September 8, 2016 6:41 PM
  • Can you get some more information on which module it's trying to find?
    Monday, February 13, 2017 5:36 PM