![]() Touch /Users/$3/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundleĬhown root /Users/$3/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundleĬhmod 644 Postflight, preflight, postinstall, preinstall scripts, and a couple of others technically refer to an embedded script within a. Rm -rf /Users/$3/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle I'd probably allow auto updates if they weren't trying to launch out of the User Library folder. For us, the issue was more about the error from config profile app folder restrictions stopping the SoftwareUpdate.bundle from launching and less about the actual updating happening. You could get away with once per user probably if you mainly had one user per machine, but we have student machines in carts where many login to the same machine.Įdit: this stops the auto update mechanism, I'm not sure if it stops updates if user goes to settings/about, you'd have to test that. To get around this, I removed it from current logged in user, then put back a dummy file with permissions that Google can't put its bundle back. In my testing, in the last year or so Google started putting the GoogleSoftwareUpdate bundle back even if you manually removed it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |