Like I said this isn't a big deal for my environment and the solution is to remove the other Google Chrome.app applications on the system. In another thread here I saw someone mentioning what sounds like a similar issue that they're experiencing. The same occurs if someone were to deploy this Google's package to a system that has the Google Chrome.app in ~/Applications or if a user were to have copied the app to ~/Desktop or ~/Downloads from the dmg still available to the general public.Īt least on my machine it behaves this way. The logs of the Chrome installer thinks that Google Chrome.app was relocated there. I don't see this as a big issue in my environment and I only learned of this because I have autopkg installed on my system creating packages to deploy.one of them is Google Chrome where it has Google Chrome.app located in their cache directory. Oddly enough it obviously worked the first time but after that is when it failed continously during the time that another Google Chrome.app was on my machine. I was unable to test on other systems since I'm doing the work from home thing now.
#Updating chrome on mac update#
Lrwxr-xr-x 1 root wheel 1B Oct 29 17:21 Macintosh -> /Īn update on the issue I mentioned turns out that the Google Chrome package provided by Google does not like it when there is a Google Chrome.app anywhere else in addition to or in place of /Applications on my system.
#Updating chrome on mac software#
Under /Volumes I have these 2 folders (probably after reinstalling Google Software Update right?)ĭrwxr-xr-x 7 myuser staff 306B GoogleSoftwareUpdate-1.ĭrwxr-xr-x 6 myuser staff 272B Jul 10 04:09 GoogleSoftwareUpdate-1.3.16.180 KSOutOfProcessFetcher could not create download temp location. KSTempDirectoryAdditions failed to create temp directory. package but I still hit the same problem.Įrror details: KSTempDirectoryAdditions failed to create temp directory. I use one Configuration Profile in Jamf Īnd in the Google Admin Console > Devices > Chrome > Settings > Users & Browsers - I have set Chrome Browser Updates - Automatic Updates Only & Component Updates - Enable Updates for all components.
#Updating chrome on mac pro#
Update - The Chrome for Enterprise Team has published a new kBase on Managing Chrome Browser Updates with Jamf Pro (macOS) This work comes from user feedback and from the Chrome for Enterprise Team is joining this thread to hear your thoughts!Ĭhrome Enterprise Browser Support can be reached here. Google simplified the process of deploying the enrollment token by leveraging Jamf's new Application & Custom Settings payload. Initial Support for Application & Custom Settings - Chrome Browser Cloud Management (CBCM) is a a single location to set Chrome policies on multiple platforms.
This is the preferred installer format for mass distribution, and is available from the Chrome Browser Enterprise Installers website. Updates to the installer - Chrome is now available as a PKG in addition to the standard DMG.
Look for more information in the form of a blog, but here are the highlights: Our work with the Google Chrome for Enterprise Team is ongoing, and this first release benefits not only Jamf Pro admins, but everyone who manages Mac at scale. We are excited about recent updates that make Chrome on macOS easier to deploy and manage.
0 kommentar(er)
