Link to home
Start Free TrialLog in
Avatar of rmclar14
rmclar14

asked on

Chrome Enterprise Uninstall

Hey

We have encoutered a problem when attempting to deploy the lastest release of google chrome  via SCCM as the chrome msi refuses to intall over the top of the existing version. This seems to be due to Chrome being part of the image build so in other words i need to identify a way of completely removing Chrome from the assets and deleting it's associated registry keys, For example with the use of a script

any ideas?

cheers
Avatar of jcimarron
jcimarron
Flag of United States of America image

rmclar14--
Have you tried Control Panel|Programs and Features and uninstalling Google Chrome from there?

Using RevoUninstall might be more likely to get all the Registry entries when you allow step four to run
"C:\Program Files (x86)\VS Revo Group\Revo Uninstaller\Revouninstaller.exe"
Avatar of rmclar14
rmclar14

ASKER

thanks for your reply jcimarron however i was looking for a solution that could be applied to over 500 assets

Thanks
Avatar of David Johnson, CD
Chrome being part of the image build There will be no uninstall points. One reason why I don't do thick installs. you are going to have to script a removal that removes the registry entries and the program files and other items in the \programdata %appdata% folders.
Hi rmclar14, lets see if more info can help us to help you:

Can I ask what you mean by "the chrome msi refuses to install over the top of the existing version"  ?

What is the exit code returned?  Any errors?

Is this installing / upgrading as SYSTEM or another admin user?

What is the command line you are using to install (or what switches are you piping through)?

Have you checked the Application Event log and looked for errors with the Chrome install package?  What are the errors?

Regards,
Darren.
ASKER CERTIFIED SOLUTION
Avatar of rmclar14
rmclar14

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Through trial and error, the above registry change solved the issue