• Deploy Chrome Apps To Multiple Students Mac Os Download
• Deploy Chrome Apps To Multiple Students Mac Os 10

WhatsaByte may collect a share of sales or other compensation from the links on this page.

Like Mozilla Firefox, the Google Chrome browser profile folder stores all information related to your browser, including settings, bookmarks, saved passwords, history, cookies, extensions, apps and much more.

The Google Chrome profile folder is separate from the application folder, which will protect your data if anything goes wrong. If you ever run into any issue with your Google Chrome browser, a new installation can help you resolve the issue.

By doing that, you need to know where your Google Chrome browser profile locates and then backup and restore user data after installing a new copy of the browser.

This two-session series, presented by Google, covers how Chrome OS, Chrome Browser, and Chrome devices such as CloudReady can empower your remote workforce. Learn how to deploy Chrome devices quickly, get started with the Google Admin console, and hear best practices to keep your workforce secure. Watch on demand now →. Chrome OS is a Linux kernel-based operating system designed by Google.It is derived from the free software Chromium OS and uses the Google Chrome web browser as its principal user interface. Google announced the project in July 2009, conceiving it as an operating system in which both applications and user data reside in the cloud: hence Chrome OS primarily runs web applications.

Find Your Google Chrome Profile Folders On Windows, Mac, And Linux

We would not recommend to manually backup your Google Chrome profile because sometimes it doesn’t work properly. You should try to backup and restore entire Google Chrome settings with this guide, instead of doing it manually.

But if you still want to backup these user data and settings manually, then please follow locations below to find your Google Chrome profile folder on each platform.

• Google Chrome profile folder on Windows 7, Windows 8, 8.1 and Windows 10: C:Users(username)AppDataLocalGoogleChromeUser DataDefault

• Your Google Chrome profile folder on Mac OS X: Users/(username)/Library/Application Support/Google/Chrome/Default
• The Google Chrome profile folder on Linux: /home/(username)/.config/google-chrome/default

Just replace (username) with your username, and copy the whole folder to backup your Google Chrome profile.

However, if you have created and been using multiple profiles on Google Chrome, the profile folders may differ and not like the locations we mentioned above.

Don’t worry! You still can find the exact location of your Google Chrome profile folder with a simple trick.

Firstly, you need to switch to the profile you want to get the place of the profile folder.

Next, copy “chrome://version” and paste it into the Google Chrome’s address bar and press Enter.

It will show you information about your Google Chrome profile, including version number, revision, operating system, Javascript version, Flash version, and profile path.

In order to backup your Google Chrome profile, just copy the “Default” or “Profile X” folder, depending on which profile you want to backup – and save the copied folder to somewhere safe.

• The “X” is the number of the profile.

If you want to restore your Google Chrome user data, just overwrite the backup folder to the existing folder of the browser.

If you want to erase all user data of your Google Chrome browser, simply delete the “User Data” folder. The next time you launch the Chrome browser, this folder will be automatically generated with a fresh default profile.

We hope you can find the location of your Google Chrome profile folder and backup your user data to keep it safe. If you have any question about this guide, just leave your comment below.

If you are using Mozilla Firefox and want to find the location of its profile folder, we also have published a guide to show you how to find it here.

The following is a post from the most excellent Nick McSpadden. It is very well written and I am proud that it is the first article published on this site using the new submissions page. Looks like it’s time to change the banner from my Notes from the Underground, er, I mean, Field, to just Notes from the Field!

Greetings!This is a sort of follow-up to my guide on managing Firefox, this time focusing on managing Google Chrome. I’m working on current Chrome version 18 (which just today got updated to 19), and I don’t know for sure how far back this will work, but I think anything higher than v16 properly supports the MCX policies.The good news about Google Chrome is that it supports MCX! Unlike Firefox, which requires specific and somewhat obtuse procedures for managing it (including depending upon an add-on that is independently maintained by a hard working individual), the most important parts of Chrome management can be done with already-existing MCX controls.First let me start off with a link to a very helpful set of information: http://www.chromium.org/administratorsThat link covers just about everything you’ll need to know about Chrome policies and management, though some of it is buried. I discovered (much to my chagrin) that the Chromium site is much more thoroughly documented that Google’s official “Chrome for Administrators” site.Some important notes about Chrome MCX: all Chrome policies are required to be set to “Always.” They’re like Profiles from Profile Managers – there’s no middle ground. Even if you set it to “Once” or “Often,” Chrome will treat the policy as permanent and prevent the user from changing it. Any policy being managed by MCX in Chrome will be grayed out to user interaction (and there will be a message in the “Options” window about how some settings are being managed by the administrator). So you’re going to have to “Always” manage these settings whether you like it or not.The good news is, there’s an alternative, the Master Preferences. The downside is that the Master Preferences is a “once” option, and doesn’t prevent the user from changing it. It’s a good way to provide default settings without restricting the users’ ability to personalize it later on. More on that later.So, following the Mac Quick Start Guide: (http://www.chromium.org/administrators/mac-quick-start)1. Inside a fresh copy of Google Chrome is a nice fresh copy of the manifest. Access it here: /Applications/Google Chrome.app/Contents/Resources/com.google.Chrome.manifest/Contents/Resources/com.google.Chrome.manifest2. Load this manifest into WGM3. Here’s the full description of all policies in the Chrome manifest: http://www.chromium.org/administrators/policy-list-34. There are some particularly important settings that will be relevant to most. Here’s what my plist looks like for a lab computer (no individual users):

Deploy Chrome Apps To Multiple Students Mac Os Download

• AutoFillEnabled – False (disables the ability to store autofill information)
• BookmarkBarEnabled – True (forces the bookmark bar to show up on all tabs, all the time)
• HideWebStorePromo – True (prevents the web store from trying to sell you things, but does not disable the web store)
• HomePageIsNewTabPage – False (if you don’t disable this, the homepage will be set to the default Chrome tab page, which opens up the “Most Visited/Apps” switcher)
• HomepageLocation – URL (even if you set this, if HomePageIsNewTabPage is set to true, this URL gets ignored)
• PasswordManagerEnabled – False (for lab machines, I don’t want them saving passwords, intentionally or accidentally)
• RestoreOnStartup – 0 (0 forces it to open the homepage URL on startup)
• SyncDisabled – True (same reason as Password Manager – I don’t want these personalized at any time).

That gives you a basic setup for most things you’ll need to worry about. If you deploy this, you’ll notice a few problems, though. The first time you launch Chrome, it gives you an undismissable dialogue box asking you if you want to make Chrome the default or submit other info. That’s bad. The above manifest also provides no way to control the auto update mechanism, if that’s something you want to do.This is where the Master Preferences file comes in – http://www.chromium.org/administrators/configuring-other-preferences. By specifying a Master Preferences file, we can load up default preferences for user accounts *when they are created.* Note that the Master Preferences file has absolutely no effect on already existing Chrome profiles – only upon new-user generation does Chrome load this file. It literally copies and pastes the settings in here into the appropriate places in ~/Library/Application Support/Google/Chrome/Default/Preferences.On Mac OS X, the Master Preferences file must be located at:/Library/Google/Google Chrome Master Preferences(yes, really – the file must be named “Google Chrome Master Preferences” with no extension), and must obviously be readable by any user who can launch Chrome (i.e. use 644 permissions).The Master Preferences file is a JSON file that can contain any of the preferences normally used by Chrome. If you want the full list of all possible preferences, load up a default Chrome profile and take a look at the Preferences file I mentioned at the path above. It has everything you’d ever want (and a lot of stuff you probably don’t). To save you some time, here are some important ones you’ll want to use specifically for deploying Chrome:{'homepage_is_newtabpage' : false,'browser' : {'show_home_button' : true,'check_default_browser' : false},'bookmark_bar' : {'show_on_all_tabs' : true},'distribution' : {'skip_first_run_ui' : true,'show_welcome_page' : false,'import_bookmarks' : false,'import_bookmarks_from_file' : '/Library/Google/chrome_bookmarks.html','make_chrome_default' : false},'sync_promo' : {'user_skipped' : true}}The chromium.org page I linked above goes into a bit more detail about this, but I want to give a quick note about the interaction between preferences and MCX. MCX always wins. Any policy managed by the MCX and also specified in the Master Prefs will always go the MCX policy. In the example above, if I had set “homepage_is_newtabpage” to true, it would still be false because MCX sets it to false, and that policy is always enforced.The really import part is the “distribution” section. “skip_first_run_ui” will get rid of that annoying dialog box that comes up when you first launch Chrome. The “import_bookmarks” option asks the user through a UI dialog box if the user wishes to import bookmarks from another browser. Obviously, we want to suppress that. There’s an option instead to silently import bookmarks from an HTML file. You can create this bookmarks HTML file by setting up the bookmarks the way you want, and then Exporting them in the Bookmark Manager. I place that bookmarks file in /Library/Google/ because it’s already used, but you can put it anywhere. There is, however, a known bug that has now been assigned a milestone and a solver in Chromium’s bug list – the “import_bookmarks_from_file” is actually ignored if the “skip_first_run_ui” is set to true. So right now, you can’t silently import your bookmarks in.The “sync_promo” item doesn’t seem to be necessary if you disable Sync in the MCX settings above, but since MCX policy always wins over Master Prefs, there’s no penalty or downside to including it.Note that your JSON syntax has to be perfect for this to work. Any incorrect comma placements, and it simply ignores your master prefs file. If you find that your Master Prefs isn’t loading up as expected, run Chrome from the Terminal with the debug log turned on to see what’s happening:/Applications/Google Chrome.app/Contents/MacOS/Google Chrome –enable-logging –v=1This places a file called “chrome_debug.log” in ~/Library/Application Support/Google/Chrome/Default/ (i.e. default user data directory). The first line will tell you exactly what went wrong with your Master Prefs file.Now, there’s still one more problem here: new tabs open up to the default Chrome “New Apps / Most Visited” switcher page (called the newtab page). Unfortunately for us, there’s no way to change this behavior present in the UI. The good news is, this behavior annoys plenty of other users, and there are a million extensions you can use to get rid of it. More good news, is that you can silently include extensions in your MCX manifest!So simply add this to your MCX settings above (forgive the pseudo XML here, just to indicate type of key):<array> <string>lcncmkcnkcdbbanbjakcencbaoegdjlp;https://clients2.google.com/service/update2/crx</string> </array>

Deploy Chrome Apps To Multiple Students Mac Os 10

This silently forces the install of an extension called “Empty New Tab Page,” and specifies an update URL for it (required, since Chrome autoupdates its extensions too if they come from the Chrome Web Store / Extensions pages). The extension does what you think it does – you get a blank page. There are other extensions for customizing the new tab pages, or anything else, so as long as you get the extension ID (it’s the long block of letters in the beginning), you can load whatever you want in here.There you go! I’ve tested this using Local MCX on my 10.6 and 10.7 machines, and it works perfectly (deployed through Munki as well). On the whole, Chrome is a bit easier to manage and deploy than Firefox, just because it doesn’t require modifying the app itself to do this. Also, the Master Preferences file works for any instance of Google Chrome – even if the users install a copy somewhere other than /Applications. This also does work for Chromium, the open-source version of Chrome.Hope this helps someone.