The exact step by step method from Google is here Īfter running Composer you will need to remove some of the stuff that Composer captures and limit it to the files in the picture below. The only way to have that all automatically happen is to use a Composer SnapShot to capture Google Chrome, the Launch Agents, Daemons, and GoogleSoftwareUpdate in /Library (you run Compsoer from when you install Chrome until after automatic updates are setup for all users.) The system will move GoogleSoftwareUpdate to the /Library/Google folder and remove it from the current user's Library, it will also update and create all relevant LaunchAgents and Daemons to point to GoogleSoftwareUpdate in /Library/Google. When you click "Set up automatic updates" from that prompt. If anyone else logs in, the prompt will appear again. This causes the prompt if the app is not owned by that user.Ĭhanging ownership of Google Chrome to the user will only fix the problem for that user. On first launch, Chrome will install GoogleSoftwareUpdate in the current user's Library. In newer versions of Google Chrome, GoogleSoftwareUpdate is not downloaded until Chrome has been launched once. The problem has to do with GoogleSoftrwareUpdate. bin/echo "`date`: Downloading latest version." > $ ******" Logfile="/Library/Logs/GoogleChromeInstallScript.log" You can put 40 or 50 installers in the folder, and they will all be installed one after the other - a perfect vanilla install of them on each Mac, with no extras or bits missing. This method comes in particularly handy when it comes to things like Logic's samples, there are about 800 of them. pkg files it finds in there and finally clean up after its self. tar.gz archive gets put in composer, and I add a post install script to it to expand the archive and then run any. And for a lot of applications, I tend to put the installer pkg in a folder on the build Mac and then. I install Chrome via script, and then keep it updated via script.
I rarely use composer for snapshots now, I find it can get me into all sorts of trouble. When I edited it all and changed the plist to use ~ rather than /Users/Administrator/ it all fixed and worked better. What then happened was the users accounts were populated with a plist that was attempting to access the Admin accounts Chrome updater. It turned out that I was using the fill existing users and fill user templates on install.
I ran into a problem with Chrome, from a composer snapshot. # This script should be ran in Jamf when Chrome is deployed # Create plist for default Chrome settings, homepage, etc. I also run this script to create the global settings plist: #!/bin/bash Have you tried running this script yet? In my process, I install chrome and then run this script that's in one of the comments from GitHub.
0 kommentar(er)
