App Volumes, Google Chrome and AppStacks
Google Chrome and AppStacks
When packaging Google Chrome for App Volumes 2.6, a few conditions should be met when also working with Writable Volumes. Chrome expects the temp directory to have a drive letter, so if the user profile is in the writable volume you will want it to have a drive letter but it is hidden (meaning that it doesn’t show up in Windows Explorer or File Open menu of apps, but it doesn’t actually have a drive letter).
- Install Google Chrome on AppStack like normal
- If you will be presenting this AppStack to VDI users you will need to create a GPO that includes the following registry entry:
reg.exe add HKLM\SYSTEM\CurrentControlSet\services\svdriver\Parameters /v DriveLetterSettings /t REG_DWORD /d 6
The above registry key is required because when using a writable volume the %userProfile% tmp data is obscured which Chrome needs.
- Login so stacks attach.
Note: If you use template_uia_only writable template and the profile is preserved by some other means (persona management, roaming profiles, folder redirection, etc.) then use the following command:
reg.exe add HKLM\SYSTEM\CurrentControlSet\services\svservice\parameters /t REG_DWORD /v VolDelayLoadTime /d 0 /f