/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Google chrome deployment loop

12/11/2019 576 views

Hi everyone

We are deploying Chrome with the K1000 and the deployment works fine. Then it seems that Chrome updates itself. Then when the machine checks in again, the deployed version of chrome is no longer detected as installed, and the installation starts again down-grading chrome. Chrome then updates itself and the loop continues.

Does anyone have any suggestions for this? anyone experiencing the same thing?

1 Comment   [ + ] Show comment

Comments

  • This is happening for us with all software.... Distribution installs base software. Patching updates it, distribution overwrites patched version.

    Extremely frustrating and making me want to throw the K1 out the window, since I have to do a ton of manual work anyway.

All Answers

1

Hi Trahmah,

for Google Chrome i am using a CIR which i have bound to the executable (version independent).

FileExists(C:\Program Files (x86)\Google\Chrome\Application\chrome.exe)

Since KACE SMA is able to patch Google Chrome i am removing the auto updater through the google chrome admx templates with desktop authority.

Kind Regards

Timo

Answered 12/12/2019 by: Timokirch
3rd Degree Black Belt

1

If you want to ensure that machines have a specific version of Chrome, then you will need to disable auto updates. That can be done with Group Policy as Timokirch mentioned or via registry keys if that isn't an option.

If you just want to make sure machines have any version of Chrome, then you can make a smart label for machines where installed software does not contain Google Chrome and target those machines with your managed install. Once Chrome is installed machines will drop out of the label and the SMA will no longer try to re-install it.

Alternatively, you could also use the software catalog for the managed install instead of the software inventory. The catalog groups versions by major version, so it doesn't care if the version is 76.0.3809.87, 76.0.3809.132, or 76.0.3809.100 just as long as it's 76.x. Of course, once 77.x comes out you will need to update your managed install to that installer.

Answered 12/12/2019 by: chucksteel
Red Belt

0

Hey Trahmah, 


What I do when deploying versions of software is I create a label that looks for anything older than the version I am installing. So, only when it is lower than the version number I want will it use the distributed installation. Other than that the auto patch cycle will update the software.


Does this make sense?

Answered 12/16/2019 by: kbot_cache
Senior White Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ