Fix KSAdmin

[technicholas]

I have a question, I have our student one to one computers restricted so they can only open things from the Applications folder and nothing in the Utility's and nothing elsewhere.

When they open Google Chrome it pops up is there any quick script I could roll out that fixes this?

Nicholas

[Eric_linneweber]

run the following script for every user.

#!/bin/sh

#this script stops the google updater app from being recreated
sudo rm ~/Library/LaunchAgents/com.google.keystone.agent.plist
sudo rm /Library/LaunchAgents/com.google.keystone.agent.plist
rm -rf ~/Library/Application/Support/Google
rm -rf ~/Library/Google
sudo mkdir ~/Library/Google

[tkimpton · Accepted solution]

https://jamfnation.jamfsoftware.com/discussion.html?id=4692

[steventhemacman]

So what exactly is the fix here? I checked out the solution link. I can't seem to figure it out (I am new at this whole thing...). Is there a way to put the steps down for us less intelligent? (OK, maybe just me). Just need ksadmin to go away...could care less about keeping Chrome up to date for now.

[marktaylor]

If it helps, we just run this command to stop the checking and keep the error away!

defaults write com.google.Keystone.Agent checkInterval 0

[NightFlight]

Google Software update is EVIL! A button to turn it off would solve much.

If you have execution blocked at the $HOME directory via MCX like we do, the end user is still annoyed with ~20 minute notifications that GoogleSoftwareUpdate and ksadmin cannot be executed.

This will resolve via the users login hook or system wide user LaunchAgent.
-----

#!/bin/bash

# Remove Google Software Update Agent - GSU is evil!
# This leaves the LaunchAgent in place and disabled. # Google Chrome isn't smart enough (yet) to check the content so long as the Agent .plist file exists.

if [ -e ~/Library/LaunchAgents/com.google.keystone.agent.plist ]; then defaults write ~/Library/LaunchAgents/com.google.keystone.agent.plist RunAtLoad -bool false
fi