KACE Product Support

Each user installed instance of Google Chrome contains a unique ID that identifies its user. In the Registry it lives in HKEY_CURRENT_USER. Rather than running an uninstall string from within HKCU it works best to upgrade to Chrome Enterprise not only will it self clean the other instances you get a better browser... https://www.google.com/intl/en/chrome/business/browser/

If your intention was to remove it then now your job is easy. If you have approved it for limited use then Chrome for enterprise is what you want.

With KACE deploying, managing and removing Chrome and other Applications is easily done.

Here is an example uninstall for v14.3.x of Chrome MsiExec.exe /X{54DF35BD-4A36-35DA-B029-A0C083C88614}

Here is an Example install for v64.240.x of Chrome MsiExec.exe /i /qn GoogleChromeStandaloneEnterprise.msi

zookdj,

This is what I've been using in our enviorement to find chrome.

RegistryKeyExists(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome)

The only bad thing about HKCU, is that it gets reloaded every-time a different user logs in.

So if you have people sharing machines (with different logins) the information could be off.

Everytime I've installed Chrome it has put it's self into the Users profile directory so a disk search would only need to look at your user profiles directory to see if it exists. Another way I could think of doing it would be to write a report to look for the Chrome process running on the computer, this would allow you to see who is using it in your environment but not give the the location of the uninstall files.

SCCM (SMS) lists it under "products" rather than "Software Registered in Add Remove Programs"; so I normally do a search for Products and exclude those with the current version to target for an upgrade.

You could use "Custom Inventory Rules" to potentially find what you are looking for.

http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=525&artlang=en&highlight=custom%20inventory%20rules

http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=524&artlang=en&highlight=custom%20inventory%20rules

You should be able to reference HKCU in the registry using a custom inventory rule.

For Enterprise deplooyment of Chrome, please follow this link:
http://msiworld.blogspot.com.au/2012/06/packaging-google-chrome-for-enterprise.html