Sequencing Google Chrome 36.0.1985.125 with App-V 5.0 SP2 HF4
My personal lab setup-
Windows Server 2008 R2 SP1 – fully patched as of 7/25/14
App-V version: 5.0 SP2 HF4
Windows 8.1 – fully patched as of 7/25/14
App-V version: 5.0 SP2 HF5
Download Google Chrome for Business – The IT manager (MSI) download
You should now have GoogleChromeStandaloneEnterprise.msi
If you want to use Microsoft best practices, here is the default installation directory: C:\Program Files (x86)\Google
Run – GoogleChromeStandaloneEnterprise.msi
The only way you will know the install is complete is by the new Google Chrome icon on the desktop.
Disable the following services:
- Google Update Service (gupdate)
- Google Update Service (gupdatem)
Save and deploy your sequence.
You can catch me at BriForum Boston this year from July 21 – 23, 2014. I will be speaking with my colleague Rory Monaghan (App-V MVP) on sequencing for success.
We will discuss the best practices to get the best results with App-V. Ryan will detail how to use symbolic links, shims and other methods to enable you to produce a disposable application ready for us with any potential client. Sequencing once for many. Rory will discuss some sequencing best practices and give food for thought regarding planning. Just because an application can be sequenced, should it? Just because Microsoft says something like drivers can’t work or DCOM, that doesn’t mean you’re dead in the water yet. There may be a way to get around this. Also, Rory will cover some sample case studies of his successes for clients versus some failures.
Attendees will learn:
• How to produce an application that can be used for all of your customers who need it despite possible unique settings for each
• Examples of where this can be useful and required. e.g. Cloud Services
• Case studies of different client projects and success versus failures
• An idea of what set of applications may be better delivered as a local traditionally installed application
• How to decide to deliver applications which have been reported to have issues during Sequencing e.g. an application with DCOM, an application with Drivers, an application with COM+
• Learn some sequencing best practices and possible gotchas
Find more information on our session here