Sequencing Google Chrome using App-V 5.1

1)  Launch the Microsoft Application Virtualization Sequencer from Start->Programs

2)  Select the "Standard application" type in the Type of Application to be Virtualized

3)  Select "Perform a custom installation" in the select installer screen

Provide the virtual application name as Google Chrome and click next.

4)  Before the application is installed, make sure that the below registy entries are placed to disable the updates.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update]

"UpdateDefault=dword:00000000

"AutoUpdateCheckPeriodMinutes"=dword:0000000

5)  Start the installation during monitoring phase.Install the package using source "GoogleChromeStandaloneEnterprise.msi"

After installation, perform the following steps.

- Delete the services : Google Update service (gupdate, gupdatem) using the below command in CMD ;

SC DELETE gupdate

SC DELETE gupdatem

- Remove the shortcut from desktop

- Remove the folder Update from Program Files (x86) during monitoring phase, after installation and unpin the application from taskbar after first launch.

6) Click "I am finished Installing"

7) Launch the shortcut in the configure phase and perform any additional post configuration if needed.

To customize further like adding home page, start screen etc.. check this link.

http://app2pack.blogspot.com/2016/02/sequence-customize-google-chrome-480.html



8) Ensure that all the buttons are clicked and opened so that Maximum functions are captured in the "Feature block One" itself.

9) Click next.Select the OS as per the requirement and select continue to modify using package editor option.

10) Create a powershell script to add a registry in the local machine for single signon. Add the below script ( AddSigninreg.ps1 )  under the Package Files --> scripts tab in package editor.

set-location hklm:

new-itemproperty -path "HKLM:\software\policies\Google\Chrome\" -name "SigninAllowed" -propertytype dword -value 0 

Similarly  add the below script ( RemoveReg.ps1 ) 

Remove-Item -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome' -Recurse

11) Save the package.

12) To execute the above scripts,  edit the Google Chrome_DeploymentConfig.xml file.

<MachineScripts>

      <AddPackage>

        <Path>powershell.exe</Path>

        <Arguments>-ExecutionPolicy Bypass -File ".\AddSigninreg.ps1"</Arguments>

        <Wait RollbackOnError="true"/>

      </AddPackage>

      <RemovePackage>

        <Path>powershell.exe</Path>

        <Arguments>-ExecutionPolicy Bypass -File ".\RemoveReg.ps1"</Arguments>

        <Wait RollbackOnError="true" />

      </RemovePackage>

    </MachineScripts>

13) Save the Google Chrome_DeploymentConfig.xml file.

14) Testing the package using standalone powershell.

Enable script execution in the App-V client using the below command in powershell.

Set-AppvClientConfiguration -EnablePackageScripts 1

Publish the Google Chrome App-V package:

Add-AppvClientPackage "path to .appv file" -Dynamicdeploymentconfiguration "path to Google Chrome_DeploymentConfig.xml" | Publish-AppvClientPackage -Global | mount-AppvClientPackage

Virtual Google Chrome and Local o365 issues - Solution

After publishing Google Chrome App-V package in windows 7, logging into portal.office.com and opening a word or excel document and trying to edit it with locally installed Office 0365 fails. When checked with procmon, we can see that Google Chrome virtual package is able to see the local o365 package and tries to open it but the winword.exe process closes soon with exit code 1.

As in last blog,  I have detailed about the same issue happening with Appv-d Mozilla Firefox package and local o365.The solutions are still the same for the current scenario too. 

Solution 1:

Create the AllowJitvInAppvVirtualizedProcess registry key as shown below to fix this known issue.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClickToRun\OverRide]
"AllowJitvInAppvVirtualizedProcess"=dword:00000001

If it doesn't work try in wow6432Node registry.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ClickToRun\OverRide]
"AllowJitvInAppvVirtualizedProcess"=dword:00000001

Solution 2:

If Solution 1 doesn't work , try with the latest App-V 5.1 Hot Fix. Always make sure to use the latest App-V 5.1 Hot Fix. (A minimum of Hot Fix 4 is required for this issue to be resolved.)

You can download the latest Hot Fix here: KB4018510

Tested the same scenario in Windows 10 1607, only the AllowJitvInAppvVirtualizedProcess registry key is required.

NOTE: Fixes that are delivered to the “out-of-box” versions of App-V and UE-V are first delivered for the “in-box” versions of App-V and UE-V in the monthly Windows 10 cumulative updates.Since updates are provided to windows 10 in-box App-V client first, it will not require the installation of the latest Hot-Fix.

From Windows 10 1703, this AllowJitvInAppvVirtualizedProcess registry key will be automatically added when any of the Office product starts.