In the Google App Engine launcher, highlight your application and then select 'Control' > 'Run', or click the run button in the main console. Once the status of the app turns green to show that it's running, click on the Browse button. Drag either an.app bundle or a disk image onto the application and it will locate a valid application bundle (.app) and build a new.pkg package installer from it and set the application's install destination to /Applications/. If you plan to deploy a large number of Chrome devices or deploy them in conjunction with G Suite for the first time, we recommend that you work with a Google Cloud partner. Manage Chrome devices Chrome devices can be configured to work in nearly any school or enterprise environment.

1. How To Deploy Google Chrome For Image For Mac Os X
2. How To Deploy Google Chrome For Image For Mac Os X 10.5.8

Follow these steps to deploy Chrome Browser on a fleet of managed Apple ® Mac ® computers. You can also use this guide to quickly set up a small Chrome Browser test deployment. To set up Chrome Browser on Mac, you create a configuration profile and deploy it using your preferred mobile device management (MDM) tool. The Chrome Browser for the enterprise bundle file contains a sample file that you can copy and customize for your own use. Overview of steps • Download the provided Chrome Disk Image (.dmg) file and the sample profile files. • Use your preferred editor to create configuration profiles with your corporate policies.

NRight-click Administrative Templates, and select Add/Remove Templates. NAdd the GoogleUpdate.adm template via the dialog. NOnce complete, a Google / Google Update folder will appear under Administrative Templates if it u0027s not there already. NEnforce the GPO object:* nFind Group Policy Management u003e Forest:chromeforwork.com u003e Domains u003e chromeforwork.com u003e Google Update for Work.

NRight-click Google Update for Work and select Enforce. N nAssign the Google Update GPO to the same set of users as the Chrome Browser GPO: nNavigate to the Google Update For Work GPO object in the Chrome Policy Management tool. NFind Group Policy Management u003e Forest:chromeforwork.com u003e Domains u003e chromeforwork.com u003e Google Update for Work and select it. NAssign the GPO object to all devices in the domain. NIn the Security Filtering pane, click Add. NIn the Select User, Computer, or Group window, type the name of the object you want to add, click Check Names (to verify the name you entered), and click OK.

• I then added it to the Policies mentioned in the original post of this discussion. In JSS, if you have more than 1 script in a Policy,. Just make sure the 'Google Chrome (Latest Version)' script is named alphabetically before the enable auto-update script. Thanks again and everyone else involved in this discussion!

• Chrome • Extend the Browser • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Web Store Publishing and Distribution • • • • • • • • • • • • • • • • • • • • • • • • • • Mobile Chrome • • • • • • • • • • • • • • • • • • • • Chrome OS • Apps • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Native Client • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Chrome APIs • Extensions APIs • • Apps APIs • •.

> > $logfile rm -rf '/Library/Google/Google Chrome Master Preferences' fi # Remove Existing User Template Preferences if the directory exists if [ -d '/System/Library/User Template/English.lproj/Library/Application Support/Google/Chrome' ]; then echo ' $(date +'%Y-%m-%d%H:%M:%S')' ':' 'Google Chrome $Ver Installer' ':' 'Removing existing Google Chrome folder from the user template.' > > $logfile rm -rf '/System/Library/User Template/English.lproj/Library/Application Support/Google/Chrome' fi The googleChromePostflight Script This script runs after the package has put our payload files into place. It makes quite a few changes, creates directories and moves files into place.

-r $logfile ] ] then touch $logfile fi echo ' $(date +'%Y-%m-%d%H:%M:%S')' ':' 'Google Chrome $Ver Installer' ':' '****************' > > $logfile echo ' $(date +'%Y-%m-%d%H:%M:%S')' ':' 'Google Chrome $Ver Installer' ':' 'Beginning Install' > > $logfile # Remove Existing Google Chrome app if it exists if [ -d '/Applications/Google Chrome.app' ]; then echo ' $(date +'%Y-%m-%d%H:%M:%S')' ':' 'Google Chrome $Ver Installer' ':' 'Removing existing Google Chrome application.' > > $logfile rm -rf '/Applications/Google Chrome.app' fi # Remove Existing Master Preferences File if it exists if [ -a '/Library/Google/Google Chrome Master Preferences' ]; then echo ' $(date +'%Y-%m-%d%H:%M:%S')' ':' 'Google Chrome $Ver Installer' ':' 'Removing existing Google Chrome Master Preferences file.'

Figure A • Launch Terminal and type in the following command, replacing the paths as necessary ( Figure B). Sudo pkgbuild —install-location /Applications —component /Volumes/Google Chrome/Google Chrome.app./Desktop/Google Chrome.pkg Figure B • After authenticating, your package will commence building ( Figure C). Figure C • The process will take several minutes, depending on the file size ( Figure D). Figure D • Upon completion, the pkg will save to your desktop, ready for deployment ( Figure E).

I'm using Composer to package chrome: • Open composer and Take Snapshot • Install chrome set default home page and activate automatic update • Take Final Snapshot At this point all is well, but I noticed under users is the username of the account I used to take the snapshot with in this case is 'DesktopAdmin'. My question is, how can I build a package that I can configure and it will deploy under another user account in this case it will be 'User1' and still keep the configurations I made? I just want to add that I literally have started using JAMF SUITE for 1 week only and I only had the 2 day training. I would strongly suggest you separate your application files and your application settings.

Below is the script that I am using. Text msiexec /qn /norestart /i '%~dp0chrome.msi' if exist 'c: Program Files Google Chrome Application ' copy /y '%~dp0master_preferences' 'C: Program Files Google Chrome Application ' if exist 'c: Program Files (x86) Google Chrome Application ' copy /y '%~dp0master_preferences' 'C: Program Files (x86) Google Chrome ' reg add HKLM Software Policies Google Update /f /v AutoUpdateCheckPeriodMinutes /d 0 copy /y '%~dp0SpecialIcon.lnk' 'C: Users Public Desktop ' call 'c: users public desktop SpecialIcon.lnk' exit Here is the master_preferences file (Name of site changed for security). Text @echo off msiexec /qn /norestart /i '%~dp0chrome.msi' if exist 'c: Program Files Google Chrome Application ' copy /y '%~dp0master_preferences' 'C: Program Files Google Chrome Application ' if exist 'c: Program Files (x86) Google Chrome Application ' copy /y '%~dp0master_preferences' 'C: Program Files (x86) Google Chrome ' reg add HKLM Software Policies Google Update /f /v AutoUpdateCheckPeriodMinutes /d 0 del 'C: Users Public Desktop Google Chrome.lnk' copy /y '%~dp0DoVac Elite.lnk' 'C: Users Public Desktop ' call 'C: Users Public Desktop DoVac Elite.lnk' exit Master_Preferences.

I recently found myself with the need to push Google Chrome out across all machines in a WDS (Windows Deployment Services) group using MDT (Microsoft Deployment Tools) Deployment Workbench Task Sequences. I needed to do a silent, unattended install of Google Chrome from an offline installer. I still want it to auto-update. This turns out to be badly documented and the method appears to have changed repeatedly, but once you find the right resources it works well. Downloading the standard Chrome offline installer and trying the usual command line help options wasn't much use. Instead of reporting a usage page, it responds to unrecognised command line options with 'Google Update installation failed with error 0x80040c01'. There's lots of info on the 'net, but it appears that the Chrome installer has gone through several iterations, so much of the advice is wrong.

• Chrome • Extend the Browser • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Web Store Publishing and Distribution • • • • • • • • • • • • • • • • • • • • • • • • • • Mobile Chrome • • • • • • • • • • • • • • • • • • • • Chrome OS • Apps • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Native Client • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Chrome APIs • Extensions APIs • • Apps APIs • •.

By the way, if you're doing WDS deployments, you owe it to yourself to use MDT thin installs. MDT will merge drivers into PE images for you, create installation scripts, and largely 'just works'. It can do things like, doing all that tedious rebooting and updating for you completely unattended. Since Microsoft has no plans to release a Service Pack 2 for Windows 7, that's going to become rather important as the update load continues to grow. Until Microsoft backflip and release SP2 anyway, of course; we've heard all this before with XP and SP3. Use MDT 2012.

Agreed on the advice above. There's really no need to use a Composer snapshot for something like Google Chrome, and most applications for that matter. I can count of one hand the number of times I use a snapshot per year, and some of them are for just determining what files get modified or created during some system level changes, not to actually build a package from. I would also say to look at AutoPkg and AutoPkgr as well, especially for items that are being revved frequently to new versions. It will make things much easier to deal with for these apps. As an aside, I just put up a small application I built using Platypus and some bash/Applescript scripting, which is based on this very good hint from on this Feature Request thread - I named it 'App Packager' and you can find it. Its designed as a simple alternative to using Composer for these simple drag and drop apps.

The is for Microsoft Windows administrators who want to deploy the Chrome Browser to their organization. In this guide • Evaluate Chrome Browser for your organization • Integrate Chrome Browser into your existing Windows IT environment • Run a test deployment with your Windows users • Roll out Chrome Browser to your organization using the MSI installer • Configure policies for users, via Windows Group Policy or cloud policies • Continue support for your legacy Internet Explorer apps • See examples of how different sized organizations deploy Chrome Browser Related topics • •.

How To Deploy Google Chrome For Image For Mac Os X

Great script! Worked for me! After installation and when Chrome opened for the first time, It gave me the Auto-Update alert. I had the option to either Enable or Cancel(?) the auto updater. When I hit enable, it prompted me to enter an Administrator password. Is there way to bypass the need for an Admin password for the auto updater?

NYou can type Domain Computers to add all workstations and servers joined to this domain (as in the example below) or you can specify a different group of computers. N n f nTest your installation nTest if Chrome is automatically installed on the target machine: n nStart the assigned client machine. NWhen the client computer restarts, the managed software package is automatically installed. NIf it does not install, open the command prompt and run the following command: u000bgpupdate /force nRestart the computer.

• Set up Chrome apps and extensions. • Push Chrome Browser and the configuration profiles to your users' Mac computers using your preferred MDM tool.

We have about 13,000 macs in our environment so it is important that we customize browser settings for our network/environment before pushing the package out to thousands of macbooks. I will walk you through how we customize and package Google Chrome for Mac OS X. Our goal here is to create a custom Google Chrome.pkg that installs the Google Chrome.app and sets the following preferences: • Set default home page to “• Show the home button by default • Stop Google Chrome from prompting the user to set it as the default browser. • Skip the first run welcome screen Here is what we are going to need: • A folder named “Chrome” with another folder inside of it named “Default”. Inside of that Default folder is where we will put the Preferences file. • A blank text document named “First Run”. • A Google Chrome Master Preferences file.

Please help me!!

Now you have a nice sensible MSI named GoogleChromeStandaloneEnterprise.msi. You can invoke installation with msiexec /i 'GoogleChromeStandaloneEnterprise.msi' /qn /quiet /norestart like any other MSI. As an MSI, it can also be deployed over Active Directory using Group Policy. File viewer for mac free download. It's a bizarre that Google make this so hard to find.

• A preflight script. (We will call it googleChromePreflight in this tutorial) • A postflight script (We will call it googleChromePostflight in this tutorial) • A Google Chrome Settings configuration profile. The preferences file This file will set some of the user default preferences for Google Chrome that don’t get set with the Google Chrome Master Preferences file for some reason. You can use the code below to create your own Preferences file. Note that this Preferences file is in JSON format. #!/bin/bash #Google Chrome version Ver= '51.0.2704.106' #Logfile logfile= /var /log /LISD-GoogleChromeInstaller.log if [ [!

It appears Adobe makes a prebuilt distributable PKG for Flash but not for the others. Also I have read that you have to use the Adobe Customization Wizard for Adobe Acrobat Reader to make the PKG which I have also downloaded. What I was hoping for is some details and steps on how to set all this up as I am thoroughly confused partially because the MacOS command lines are very foreign to me and I have no idea what they are actually doing. I am thinking for programs like AIR, Shockwave, and Chrome I am going to have to re-package them and I have read that MacOS has a repackager built in that can make a PKG file or whatever. I am going to try that but honestly I have no idea how to distribute even a PKG file if I upload it to the KACE.

NOn client machine, launch Chrome. The settings you applied in step 3 should be noticeable on the test machine. NTo further verify the policies being applied to Chrome and the user signed-in, go to the address: chrome://policy to see all policies being applied. N n* n nIf the policies have not propagated to the test machine / user, you may be able to run “gpupdate” to refresh policy settings.

/install triggers a non-interactive install with a GUI. Except that it still launches the interactive installer for Adobe Flash Player if it isn't already installed. It's actually easy to deploy Chrome centrally, but you wouldn't think so from searching the Google Chrome help pages and site. The key thing you need is the page on Chrome for Business. This finally explains that there's an MSI installer.

A management suite, such as to all managed OS X devices. But what happens when you use an alternative management suite that only supports PKG file types?

How To Deploy Google Chrome For Image For Mac Os X 10.5.8

In keeping with the sysadmin theme, I'd like to touch on the topic of creating your own installer packages to deploy apps, settings, or even scripts—complete with paths to the destination and security permissions. The magical functionality necessary to create most packages is built right in to Terminal with the, so there are no additional software licenses or costs. Let's jump right into the process below and create a deployable pkg file. • For the purposes of this tutorial, I've chosen Google Chrome to model the creation process, but feel free to substitute for an app of your choice. Start by mounting the application's DMG file. Take note of both the name of the mounted volume and the app itself ( Figure A).