@Flaurian It looks like you're creating your own LaunchAgent to update Chrome. If you deploy Chrome via the .pkg Google created for Enterprise deployments it automatically configures auto updates during the install: https://chromeenterprise.google/browser/download/#mac-tab (AutoPkg uses this download for the GoogleChrome.pkg recipe)
Hey @sdagley
thanks for ur answer. Actually it is the Google Enterprise pkg.
Hey @sdagley
thanks for ur answer. Actually it is the Google Enterprise pkg.
If you're using the Enterprise GoogleChrome.pkg there is no com.test.google.softwareupdatecheck.plist LaunchAgent created by it. Is that something you were creating on your own before Google started offering the Enterprise installer?
If you're using the Enterprise GoogleChrome.pkg there is no com.test.google.softwareupdatecheck.plist LaunchAgent created by it. Is that something you were creating on your own before Google started offering the Enterprise installer?
No it’s already worked with the enterprise pkg and yes the launch agent is created by myself to trigger the update service from google
No it’s already worked with the enterprise pkg and yes the launch agent is created by myself to trigger the update service from google
The Enterprise Chrome package from Google automatically configures automatic updates when it installs, you don't need to do anything else to trigger it. Or are you trying to check more frequently than Google configures their automatic update check?
The Enterprise Chrome package from Google automatically configures automatic updates when it installs, you don't need to do anything else to trigger it. Or are you trying to check more frequently than Google configures their automatic update check?
Exactly this what I do - every 6 hours
Exactly this what I do - every 6 hours
Looking at the latest Google LaunchAgents and LaunchDaemons it appears that the com.google.keystone... LaunchAgents are no longer used, and the old com.google.keystone.daemon.plist LaunchDaemon has been replaced by com.google.GoogleUpdater.wake.system.plist which has a StartInterval of 1 hour so having a secondary check every 6 hours isn't really necessary.
Looking at the latest Google LaunchAgents and LaunchDaemons it appears that the com.google.keystone... LaunchAgents are no longer used, and the old com.google.keystone.daemon.plist LaunchDaemon has been replaced by com.google.GoogleUpdater.wake.system.plist which has a StartInterval of 1 hour so having a secondary check every 6 hours isn't really necessary.
Okay but why the client is not updating the old version if google enterprise pkg has everything included? (Chrome was open the whole time and browsing.)
Okay but why the client is not updating the old version if google enterprise pkg has everything included? (Chrome was open the whole time and browsing.)
If you select "About Google Chrome" from the Google Chrome menu to force an update check does it then find an update (or show that an update is pending)?
If you select "About Google Chrome" from the Google Chrome menu to force an update check does it then find an update (or show that an update is pending)?
It will show the update and this exactly what I try to avoid for the user because this will not work. I don’t want someone has to click to get the update.
It will show the update and this exactly what I try to avoid for the user because this will not work. I don’t want someone has to click to get the update.
If Chrome is open it won't apply an update until the user quits the app, or if the user clicks the notification an update is pending and asking that they allow a relaunch to install it.
If Chrome is open it won't apply an update until the user quits the app, or if the user clicks the notification an update is pending and asking that they allow a relaunch to install it.
Yes this is actually the basic setting from Google and this not what I want because user will not quit any app to do the update rather they got any notification and this is what I do with ...
<key>RelaunchNotification</key>
<integer>2</integer>
<key>RelaunchNotificationPeriod</key>
<integer>3600000</integer>Don't get me wrong I'm happy about every answer but actually we talking to about the real issue what I've - the launch agent which will not open, start or whatever
Yes this is actually the basic setting from Google and this not what I want because user will not quit any app to do the update rather they got any notification and this is what I do with ...
<key>RelaunchNotification</key>
<integer>2</integer>
<key>RelaunchNotificationPeriod</key>
<integer>3600000</integer>Don't get me wrong I'm happy about every answer but actually we talking to about the real issue what I've - the launch agent which will not open, start or whatever
The real issue is that Google appears to have changed the fundamental behavior of their update mechanism and your previous approach of using an additional LaunchAgent to trigger it on your preferred schedule no longer works. I'll end my participation in this thread with the suggestion you look at the contents of the com.google.GoogleUpdater.wake.system.plist LaunchDaemon to see how the new update mechanism is triggered and see if that provides any clue how you can apply your own schedule/behavior.
&& ! /loginwindow/ { print $3 }')