You can capture Google Chrome using the Omnissa ThinApp Setup Capture wizard.
Currently, Google Chrome is supported in a no sandbox mode and to run Google Chrome after capture, following command line options --js-flags="--no-freeze-flags-after-init", --no-sandbox, and --test-type are required.
Procedure
-
On a clean Windows 10 virtual machine, download the desired (32-bit or 64-bit) Google Chrome version.
-
Install ThinApp on this virtual machine.
-
Create a system image using the Prescan process of the Setup Capture wizard.
-
Install Google Chrome.
-
(Optional) Configure the browser by opening the newly installed native Google Chrome.
-
Rescan the system using the Postscan process of the Setup Capture wizard.
-
Configure the project and package in the subsequent Setup Capture windows.
-
In the
package.inifile, modify the following:-
In the BuildOptions section, add
DisableWriteDAC=1,ExternalCOMObjects={9BA05972-F6A8-11CF-A442-00A0C90A8F39};{682159d9-c321-47ca-b3f1-30e36b2ec8b9};{9aa46009-3ce0-458a-a354-715610a075e6},ExternalDLLs=d3d12.dll, andManageHeapLocks=1. -
In the Google Chrome.exe entry point section, below the
Sourcekey, create aCommandLinekey. The value of this key must be as follows:<chrome.exe path as per the Source key> --js-flags="--no-freeze-flags-after-init" --no-sandbox --test-type.The following code blocks are examples for the Google Chrome entry points in the
package.inifile:-
For 64-bit Google Chrome
[Google Chrome.exe] Source=%ProgramFilesDir(x64)%\Google\Chrome\Application\chrome.exe CommandLine=%ProgramFilesDir(x64)%\Google\Chrome\Application\chrome.exe --js-flags="--no-freeze-flags-after-init" --no-sandbox --test-type WorkingDirectory=%ProgramFilesDir(x64)%\Google\Chrome\Application -
For 32-bit Google Chrome
[Google Chrome.exe] Source=%ProgramFilesDir%\Google\Chrome\Application\chrome.exe CommandLine=%ProgramFilesDir%\Google\Chrome\Application\chrome.exe --js-flags="--no-freeze-flags-after-init" --no-sandbox --test-type WorkingDirectory=%ProgramFilesDir%\Google\Chrome\Application
-
For more information about the package parameters, see the Omnissa ThinApp Package.ini Parameters Reference Guide at Omnissa Product Documentation.
-
-
Was this page helpful?