Sorry for the format here, but I wanted to get this out ASAP to help the requester.

Create a cmd file using the code below:

START /WAIT C:\Temp\GoogleChromeStandaloneEnterprise.MSI ALLUSERS=TRUE /QB-
RD /Q /S "%ProgramFiles%\Google\Chrome\Application\37.0.2062.120\Installer"
ROBOCOPY "%ProgramFiles%\Google\Chrome\Application\37.0.2062.120" "%ProgramFiles%\Google\Chrome\Application" /mov /e
COPY C:\Temp\master_preferences "%ProgramFiles%\Google\Chrome\Application\master_preferences
COPY "C:\Temp\First Run" "%ProgramFiles%\Google\Chrome\Application\First Run"
REG ADD HKLM\SOFTWARE\Policies\Google\Update /v AutoUpdateCheckPeriodMinutes /d 0 /t REG_SZ /f
REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations /d "" /t REG_MULTI_SZ /f

This will be used now and going forward whenever you need to sequence a new version of Chrome.  You will just need to change the version number to match that of the version of Google Chrome Enterprise you download.

Note:  This script assumes that you have a master_preferences andFirst Run file you are using, which you will copy into the C:\Temp directory on your sequencer. 

Also, normally I install into a dummy PVAD, but for Chrome I install into the PVAD:

Primary Virtual Application Directory:  C:\Program Files\Google\Chrome

Do not run the application during sequencing, you want it to stream fault.   I also checked all three Advanced options (on the Advanced tab).

Sequencing Domink Reichel's Keepass (from www.keepass.info) casused two issues on an App-V 5 Client. Here is how to resolve them.

Issues

1. Keepass can't be added on the client, throwing an error code including 0C80070057
2. After fixing the first issue, the app can be added to a client, but Keepass crashes with anAppCrash error

Both issues can be addressed quite easily

1. Sequencing Keepass creates a UserProgramFiles folder (with a Common subfolder) inside the package. As nicely described at http://blogs.technet.com/b/virtualvibes/archive/2013/06/13/0c80070057-app-v-error-code.aspx, deleting the UserProgramFiles folder from the package solves that issue.

2. KeePass crashes with an AppCrash error. Though there is no soultion for App-V realted KeePass crashes, it apparently has anissue with UE-V, too. As described in http://support.microsoft.com/kb/2802058,  adding some information into the keepass.exe.config file might help - and it did for App-V, too.

Because KeePass is a simple-to-sequence application and your previous package does not work anyway, you shouldcreate a new package from scratch (instead of trying to fix it)

1. Start sequencing Keepass
2. During monitoring (before you hit 'I am finished installing...',modify the keepass.exe.config as described in the KB
3. Continue Sequencing. Ensure that you proceed to the Editor (and do not end sequencing earlier)
4. In the Sequencer's Editor, [Package Files] tab, find the folder Package / Root / VFS /UserProgramFiles. Delete that folder from the list. VirtualVibes' article gives some more info about that
5. Save the Keepass App-V package
6. Test the package on a client

Falko

Twitter @kirk_tn  |   Blog kirxblog  |   Web kirx.org  |   Fireside appvbook.com

Application Name: ArcGIS Desktop

Application Version: 10.1

Company Name: ESRI

Sequencer Version: 4.6 SP1

App-V Client Version Tested On: 4.6SP1 RDS

Operating System Sequenced On: Windows Server 2008 R2

Pre-requisites: .NET

Client Operating Systems Successfully Deployed To: Win2008R2 RDS

*Posted by non-Microsoft Employee: Justin Grote <jgrote@allieddigital.net>

Steps to Sequence the Application:

Installation Phase

1.       Choose custom installation path: Q:\ARCGIS_Desktop_10.1\
2.       Exclude 3d Analyst
3.       Choose custom python installation path: Q:\ARCGIS_Desktop_10.1\

Configure Phase

The Flexnet licensing service installs incorrectly in App-V with bad permissions. It has to be cleaned up and reset.

1.       Open command prompt
2.       sc sdset "FlexNet Licensing Service" D:(A;;CCDCLCSWRPWPDTLOCRGASDRCWDWO;;;WD)
3.       sc delete "FlexNet Licensing Service"
4.       sc create "FlexNet Licensing Service" binPath= "C:\Program Files (x86)\Common Files\Macrovision Shared\FLEXnet Publisher\FNPLicensingService.exe"
5.       Start ArcGIS Administrator and select "Advanced Concurrent Use"
6.       Define a License Manager and enter your arcgis server” for the licensing.

Customize Phase

1.       Delete ArcGIS 10.1 for Desktops Help
2.       Delete ArcGIS Document Defragmenter
3.       Delete ArcGIS File Handler
4.       Delete ArcGIS for Desktop Resource Center
5.       Delete ESRIRegAddin
6.       Delete Module Docs
7.       Delete MXD Doctor
8.       Delete SoftwareAuthorization.exe
9.       Delete Python Manuals
10.   Rename ArcCatalog 10.1 to ArcCatalog
11.   Rename ArcMap 10.1 to ArcMap
12.   Rename IDLE to ArcGIS Python GUI
13.   Rename Python (Command line) to ArcGIS Python CLI

Known Issues/Limitations: None after fixed Flexnet licensing service.                           

Approximate Sequencing Time: 40 minutes.

Other (Optional fields)

App-V friendly copy protection scheme?  Yes, if follow Flex Licensing service fixes above.

Additional Notes/Links:
You can create additoinal OSDs with pre-scripts that change registry licensing settings to have multiple licensed editions without having to recompile the application.

Removing ArcGISConnection.exe from the package will cause the app to boot much faster depending on your internet connection. This is a bug that will be fixed in SP1: http://forums.arcgis.com/threads/61365-Disabling-the-ArcGIS-Online-Connection-in-10.1

-- Justin Grote
Datacenter Solutions Architect
Allied Digital Services

I have Sequenced SQL2005 Client Tools  Successfully and here is the steps used.

1. Install .NET 2.0 before sequencing SQL 2005 Client tools.

2. Create SQL2005 folder ON Q:

3. Create SQL folder in Q:\SQL2005

4. Start  Sequencer> New Package ( used App-V 4.5 SP2 on Windows XP SP3) sequence to Q:\SQL2005

5. Give Name And Comments

6. Start monitoring

7. Run SQL Server 2005 setup

8. select Server components, tool, books online, and samples on setup screen

9. install pre requisites

10. IIS Feature Requirement will give a warning, click next to continue.

11. Check All Components(Workstation Components, Books Online and development tools etc)

12. Change installation path to Q:\SQL2005\SQL

13. Install SQL2005 SP2

14. Install Visual Studio 2005 Service Pack 1(VS80sp1-KB926601-X86-ENU)

15. Install hot fix 944478(VS80sp1-KB944478-X86-ENU)

16. Install the VKeyPackage.dll (hot fix package 945347). follow these steps:

a. Extract the pack &copy VKeyPackage.dll to  C:\Program Files\Microsoft Visual Studio 8

b.    Run this at command prompt regsvr32 "C:\Program Files\Microsoft Visual Studio8\VKeyPackage.dll"

17. Stop sequencing and Launch applications.

18. On deployment tab fill out required information needed and Uncheck "enforce security descriptors"

19. Save the Package.

20. Make sure that the Sequencer clients are having .NET 2.0 installed.

21. Copy the package to   ‘content ‘folder and import it.

Thanks

Sreekanth

Here's a really straight forward easy one. I use this for training purposes a lot. Based on 4.6SP1

Step 1 - Prepare the sequencing machine by adding the following Exclusions to the Exclusions list:

Launch the App-V Sequencer. Browse to Tools-->Options

%CSIDL_COMMON_PROGRAMS%\FileZilla FTP Client

%CSIDL_COMMON_APPDATA%\Microsoft\RAC

%CSIDL_WINDOWS%\Installer

\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings

\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall

\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings

\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

Ensure Windows Search and Windows Defender services have been stopped on the machine.

Step 2 - Sequence the Application

Choose all defaults in the App-V Sequencing Wizard until you get to the window prompting you to provide a Package name. Name the package accordingly e.g. FileZilla Client 5.3.3. Take note of the Primary Directory e.g. Q:\FileZilla Client 5.3.3 as you'll want to install the application here. Click Next.

Choose Perform a custom installation. Click Next.

Launch the installer. Ensure you select custom during the installation, ensure you choose to browse on the Dialog which allows you to choose what components to install, this will allow you to change the install directory. I allow this application to install to it's default directory. I also choose to un-check the checkbox for shell extensions.

You will need to browse to the install directory and find the file fzdefaults.xml.sample. Rename the file, remove .sample. Then modify the contents with Notepad to ensure the Check for updates option is disabled

Check the box to indicate the install has been completed once you have successfully installed the application.

I do not launch for first use tasks or to optimize the application as I want a clean first launch for each user and allow the app to see the local machine drives.

I ensure I only have one shortcut for FileZilla client and move on. When complete click next.

When complete you may select File-->SaveAs

Save the application to the relevant path (what you set in the Deployment tab)

Step 3 - Application Complete

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

Application Name:  UltraEdit

Application Version:  19, 20, and 21

Company Name:  IDM Computer Solutions, Inc.

Sequencer Version:  5.0 SP2

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

Operating System Sequenced On:  Windows 7 (32bit)

Pre-requisites:  You must download the Corporate Version of UltraEdit from the IDM Secure Website

Client Operating Systems Successfully Deployed To:  Windows 7 (32 and 64bit), Windows Server 2008 (32 and 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 Sequence the Application: 

  Steps to be performed prior to sequencing:

•Step 1:  Download the latest Corporate version of UltraEdit from the IDM Secure website
•Step 2:  Acquire the license file (uedit32.spl)
•Step 3:  Copy ue_english_enterprise.msi and uedit32.spl to your Sequencer machine

•Step 1:  Start Sequencer > Create package (default) > Standard Application (default) > Perform a custom installation > Primary Virtual Application Directory (C:\UltraEdit) > Next to start capture
•Step 2:  Copy the uedit32.spl to %AllUsersProfile%\UltraEdit\license\ (you will need to create this directory)
•Step 3:  Install UltraEdit (ALLUSERS).  Change installation directory to C:\UltraEdit when prompted.
•Step 4:  Continue thru the installation, then Check "I am finished installing" box and click Next
•Step 5:  Do not run any programs to manage first use tasks
•Step 6:  Save Package

Known Issues/Limitations:  Most of the user based settings are created when the application is first run, so in order to keep the user settings outside the package do not run the application during sequencing.                                

Approximate Sequencing Time:  20 minutes (includes preparation time for licensing model)

Descriptive Tags:  App-V, 5.0, UltraEdit, Recipe, Guidance

Application Name:  Toad for Oracle

Application Version:  12.1

Company Name:  Dell (formerly Quest Software) 

Sequencer Version:  5.0 SP2

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

Operating System Sequenced On:  Windows 7 (32bit)

Pre-requisites:  None (although the application will require that an Oracle client be available to work)

Client Operating Systems Successfully Deployed To: Windows 7 (32 and 64bit), Windows Server 2008 (32 and 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 Sequence the Application: 

  Steps to be performed prior to sequencing:

• Step 1:  Extract Toad for Oracle 12.1.msi from the Quest Installer package.  (This will also extract the QuestKey.reg template file)
• Step 2:  Configure the License File (QuestKey.reg)  http://documents.software.dell.com/DOC98822. 
• Step 3:  Copy the Toad for Oracle12.1.msi as well as the QuestKey.reg to the sequencer machine

  Steps to be performed during sequencing:

• Step 1:  Start Sequencer > Create package (default) > Standard Application (default) > Perform a custom installation > Primary Virtual Application Directory (C:\Quest Software\Toad for Oracle 12.1\) > Next to start capture
• Step 2:  Import the QuestKey.reg
• Step 3:  Install Toad for Oracle12.1.msi  (be sure to un-check the box to start Toad when installation finishes)
• Step 4:  Check "I am finished installing" box and click Next
• Step 5:  Do not run any programs to manage first use tasks
• Step 6:  Customize
• Step 7:  Run each program briefly to optimize package (Toad for Oracle will complain that there are no Oracle clients installed on the Sequencer machine.   That is normal)
• Step 8:  Proceed as normal thru the rest of the Sequencing UI. 

Known Issues/Limitations: Most of the user based settings are created when the application is first run, so in order to keep the user settings outside the package do not run the application during sequencing.                                 

Approximate Sequencing Time:  20 minutes (includes preparation time for licensing model)

Descriptive Tags:  App-V, 5.0, Toad for Oracle, Recipe, Guidance

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

Created an App-V recipe for SQL Management Studio 2012:

http://rorymon.com/blog/index.php/app-v-recipe-sql-management-studio-2012/

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

http://rorymon.com/blog/index.php/app-v-recipe-evernote/

For this one, personally I decided to deploy the application locally to desktop users but this recipe is useful for deploying with RemoteApp or XenApp

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

Please note for this recipe I will provide the instructions for 4.6 SP2. These instructions can also assist if using App-V 5.0. An important thing to note. You should ensure you have any and all application fixes provided by the vendor and also Crystal Reports is a pre-requisite for some of the reporting functions in this application 

Step 1 - Prepare the sequencing machine by adding the following Exclusions to the Exclusions list:

Launch the App-V Sequencer. Browse to Tools-->Options

%CSIDL_COMMON_APPDATA%\Microsoft\RAC

%CSIDL_WINDOWS%\Installer

\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings

\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall

\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings

\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

Step 2 - Sequence the Application

Choose all defaults in the App-V Sequencing Wizard until you get to the window prompting you to provide a Package name. Name the package accordingly e.g. FrontRange HEAT 2007. Take note of the Primary Directory e.g. Q:\FrontRange HEAT as you'll want to install the application here, if using 4.6. Click Next.

If you use App-V 5.0 your primary directory can be the Installdir for this applicaton which is C:\Program Files (x86)\FrontRange Solutions Choose Perform a custom installation. Click Next.

Install Crystal Reports required for your version of HEAT. Upon completion run Setup.exe. Ensure you select custom during the installation, For this application ensure it installs to the same directory as the Primary Directory. This installation should install both the Call Logging feature and also the Alert Monitor. If you have a single Data Source for your company you can configure this now. Next you should Check the box to indicate the install has been completed once you have successfully installed the application.

On the next screen If you set the Data Source for the application, I would not launch the application at all, this is because it may authenticate and pull down your own information which you will not want other users to use. If you do not configure the Data Sources as part of the sequence you should launch and Once at the login dialog you should close, this application requires authentication and you don't want to capture your own credentials. Click Next.

Next you can Edit the shortcuts if you require, for this I ensured only the Alert Monitor and Call Logging shortcuts were left in there and also ensured there's no Desktop Shortcuts.

Now you may launch to capture the Feature Block 1 (What will appear first to the user) Here I launch the application and then close them again, not much for this one because of the login as mentioned earlier.

You can then either save or continue to modify. Continue to modify. You will now see the Sequencer Interface with multiple tabs e.g. Deployment, Files, Virtual Registry etc. You should check your Virtual Registry for any hardcoded references or references to your machine name and username. Delete if they exist. If using App-V 5.0 it might be a good idea to select to download the application autmotically due to it's size.

When complete you may select File-->SaveAs

Save the application to the relevant path (what you set in the Deployment tab)

Step 3 - Application Complete

You can now deploy the application however you see fit. I hope this is helpful for somebody!

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

I have tried these three out in App-V recently in order to demonstrate isolation for a presentation and so I decided to create a proper Sequencing Recipe. I advise against sequencing such old version of Office for anything other that demonstration purposes, however if you do need an old version to run side by side with a newer release as a short term solution. This should do the trick.

http://rorymon.com/blog/index.php/app-v-recipe-office-xp-2007/

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

Application Name:  FileZilla

Application Version:  3.8.0

Company Name:  Filezilla-project.org

Sequencer Version:  5.0 SP2

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

Operating System Sequenced On: Windows 7 (32bit)

Pre-requisites:  None

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

*Posted by non-Microsoft Employee:  Cody Lambert

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

Steps to Sequence the Application: 

• Start sequencing > Create Package (default) > Standard Application (default) > Select the installer for the application
• Package Name:  FileZilla 3.8.0 (or however you wish to name it)
• Primary Virtual Application Directory:  C:\FileZilla
• Destination Folder for Installation:  C:\FileZilla (when you click next, it will change this to C:\FileZilla\FileZilla FTP Client)
• Choose defaults for the rest of the installation, but un-check the box for "Start FileZilla now" and click Finish
• While still sequencing, with notepad open the following file:  C:\FileZilla\FileZilla FTP Client\docs\fzdefaults.xml.example
• Update the file so that the following code is all that remains between <FileZilla3> and </FileZilla3>

<FileZilla3><Settings><Setting name="Disable update check">1</Setting></Settings></FileZilla3>

• Save the file as fzdefaults.xml in the following location:  C:\FileZilla\FileZilla FTP Client
• Check box to finish the sequencing process

Known Issues/Limitations:  You can use the fzdefaults.xml file to control other settings within the application as well.  In my example all that I am doing is disabling the applications ability to update.  Thanks to the recipe posted by Rorymon here that got me  going in the right direction.

Approximate Sequencing Time:  10 minutes

Descriptive Tags: App-V, 5.0, FileZilla, Recipe, Guidance

http://rorymon.com/blog/index.php/app-v-recipe-visual-foxpro-9-0-sp2/

I am no longer posting recipes in plain text on this forum. I will instead post links to my site which contains step by step instructions with images.

PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

• Application Name: Java
• Application Version: 6 update 19
• Company Name: Sun Microsysems
• Sequencer Version:  4.6
• App-V Client Version tested on:  4.6
• Operating System sequenced on:      Windows XP SP3 x86
• Pre-requisites: Copy any preference setting files to sequencer machine
• Client Operating Systems successfully deployed to:  Windows XP x86 / Windows 7 x64
• *Posted by non-Microsoft Employee: Jeffrey Crawford, Indiana University


• Steps to sequence the application:

(Steps 1-2 are optional and performing them will exclude Java cache files from being included inside of the bubble and one Java update service.)

1. Navigate to directory: 
   C:\Program Files\Microsoft Application Virtualization Sequencer\
2.  Modify the existing default.spjr using notepad so that you remove the following:
   <EXCLUSION Pattern="%CSIDL_APPDATA%\Sun\Java\Deployment\SystemCache" Context="VFS_EXC" Type="PSR_DataSystem"/>
   <EXCLUSION Pattern="%CSIDL_APPDATA%\Sun\Java\Deployment\cache" Context="VFS_EXC" Type="PSR_DataSystem"/>
   <EXCLUSION Pattern="R:\Java.000\bin\ssvagent.exe" Context="VFS_EXC" Type="PSR_DataSystem"/>
   ***Change this path to match what you intend on using.  IE: Q:\Java.000\bin\ssvagent.exe***
3. Open up internet explorer or your browser choice.  Navigate to the web page:
   http://www.java.com/en/download/manual.jsp
4. Click Windows 7/Xp/Vista/200/2003/2008 Offline
5. Click on the option save
6. Save file to desktop
7. Start the Microsoft Application Virtualization Sequencer and create a package
8. Fill in Package Name as you wish
9. Click Begin Monitoring create a directory in which the app-v package will be generated and stored.  IE: R:\Java.000
10. Double click on JRE Setup MSI and click run if a security box is presented
11. Select Change Destination Folder (lower left hand corner)
12. Click Intall
13. Click on Change :: Navigate to the path of the directory you created in step 10.  Root level:  IE.  R:\Java.000
14. Click Ok
15. Click next
16. (Optional:  Un-check Yes, I want Bing Toolbar for Internet Explorer)
17. Click Next
18. Click Close
    (Steps 18 - 22 are optional and can be skipped)
19. Navigate to the directory C:\WINDOWS\Sun\Java\Deployment
20. Copy or create deployment.config  (Instructs Java on what actions to perform)
    IE: deployment.system.config=file\:/C\:/WINDOWS/Sun/Java/Deployment/deployment.properties
    (Tells java where our deployment. Properties file is and to read and perform actions.)
21. Copy or create deployment.properties (Set what options you want java to have and lock the features so they cannot be changed by end user)
    IE:
    deployment.javaws.autodownload="NEVER"
    deployment.javaws.autodownload.locked
22. Add in these additional registry values or modify them:
    HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy", "EnableJavaUpdate", "REG_DWORD", "0"
    HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy", "NotifyDownload", "REG_DWORD", "0"
    HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy", "NotifyInstall", "REG_DWORD", "0"
    HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy", "UpdateSchedule", "REG_DWORD", "0"
23. Click stop monitoring
24. Click Next
25. Click Next
26. Click next
27. Select Finish
28. Click on Virtual Registry Tab
    (Steps 29 -33 are if you plan on running this on a system that is Windows Vista or greater because of permission changes and the way the virtual bubble work if you fail to remove these key’s an error will be produced on the client:
    Windows cannot access R:\Java.000\bin\jqsnotify.exe (Firefox)
    Windows cannot access R:\Java.000\bin\ssvagent.exe (Internet Explorer)
29. Check for the existence of Mozilla key under:
    Machine
    Software
    Delete key Mozilla
30. Check for the existence of {C8FE2181-CAE7-49EE-9B04-DB7EB4DA544A} {key under:
    Machine
    Software
    Microsoft
    Internet Explorer
    Low Rights
    ElevationPolicy
    Delete key: {C8FE2181-CAE7-49EE-9B04-DB7EB4DA544A}
    If only key under ElevationPolicy safe to delete the entire structure
    Important note: This guid may change
    from
    from version to version what you are looking for is that the value AppName: has ssvagent.exe in it.   This is the currently the only key required to be deleted.
31. Click on Files Tab
32. Navigate to directory Bin
33. Validate that ssvagent.exe is not present if present delete this file
34. Click on Virtual Registry Tab
35. Validate that settings under Internet Explorer have proper merges in place if you plan on using this package with a “Virtual Internet Explorer shortcut” failure to do so could result in this package not allowing key’s from current system to be read in.  This includes the user area as well.
36. Save the package and run on client system.

• Known Issues/limitations: The service that Sun Microsystems implemented inside of java doesn’t play nicely in a virtual bubble on Windows Vista or above machines due to security enhancements.  The solution is to remove this service from the package thus allowing java to operate without errors.  Only known side effect is that java will no longer check for updates when started.
• Approximate sequencing time: 10 minutes

Find the full recipe on my website:

http://ryanwill.com/sequence-app-v-5-0-sp2-dwg-trueview-2015/

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.