Editing Google Chrome
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 11: | Line 11: | ||
In December 2010, Google announced that to make it easier for businesses to use Chrome they would provide an official Chrome [[Windows Installer|MSI package]]. For business use it is helpful to have full-fledged MSI packages that can be customized via transform files (.mst){{snd}}but the MSI provided with Chrome is only a very limited [[MSI wrapper]] fitted around the normal installer, and many businesses find that this arrangement does not meet their needs.<ref>{{cite web|url=https://code.google.com/p/chromium/issues/detail?id=68519 |title=Change MSI from a wrapper to "full" MSI |date=January 4, 2011 |access-date=April 8, 2012}}</ref> The normal downloaded Chrome installer puts the browser in the user's local app data directory and provides invisible background updates, but the MSI package will allow installation at the system level, providing system administrators control over the update process<ref>{{cite web |first=Ryan |last=Paul |title=Google offering MSI to simplify Chrome enterprise deployment |url=https://arstechnica.com/information-technology/2010/12/google-offering-msi-to-simplify-chrome-enterprise-deployment/ |website=[[Ars Technica]] |publisher=[[Condé Nast]] |date=December 16, 2010 |access-date=March 9, 2017}}</ref>{{snd}}it was formerly possible only when Chrome was installed using [[Google Pack]]. Google also created [[Group Policy|group policy objects]] to fine-tune the behavior of Chrome in the business environment, for example by setting automatic updates intervals, disabling auto-updates, and configuring a home page.<ref>{{cite web|url=https://www.google.com/support/installer/bin/answer.py?&answer=146164 |title=Google Update for Enterprise – Google Help |access-date=July 11, 2012}}</ref> Until version 24 the software is known not to be ready for enterprise deployments with roaming profiles or Terminal Server/Citrix environments.<ref>{{cite web|url=https://code.google.com/p/chromium/issues/detail?id=2423 |title=Issue 2423 – chromium – Windows Roaming Profile support – An open-source browser project to help move the web forward. – Google Project Hosting |date=September 17, 2008 |access-date=April 8, 2012}}</ref> | In December 2010, Google announced that to make it easier for businesses to use Chrome they would provide an official Chrome [[Windows Installer|MSI package]]. For business use it is helpful to have full-fledged MSI packages that can be customized via transform files (.mst){{snd}}but the MSI provided with Chrome is only a very limited [[MSI wrapper]] fitted around the normal installer, and many businesses find that this arrangement does not meet their needs.<ref>{{cite web|url=https://code.google.com/p/chromium/issues/detail?id=68519 |title=Change MSI from a wrapper to "full" MSI |date=January 4, 2011 |access-date=April 8, 2012}}</ref> The normal downloaded Chrome installer puts the browser in the user's local app data directory and provides invisible background updates, but the MSI package will allow installation at the system level, providing system administrators control over the update process<ref>{{cite web |first=Ryan |last=Paul |title=Google offering MSI to simplify Chrome enterprise deployment |url=https://arstechnica.com/information-technology/2010/12/google-offering-msi-to-simplify-chrome-enterprise-deployment/ |website=[[Ars Technica]] |publisher=[[Condé Nast]] |date=December 16, 2010 |access-date=March 9, 2017}}</ref>{{snd}}it was formerly possible only when Chrome was installed using [[Google Pack]]. Google also created [[Group Policy|group policy objects]] to fine-tune the behavior of Chrome in the business environment, for example by setting automatic updates intervals, disabling auto-updates, and configuring a home page.<ref>{{cite web|url=https://www.google.com/support/installer/bin/answer.py?&answer=146164 |title=Google Update for Enterprise – Google Help |access-date=July 11, 2012}}</ref> Until version 24 the software is known not to be ready for enterprise deployments with roaming profiles or Terminal Server/Citrix environments.<ref>{{cite web|url=https://code.google.com/p/chromium/issues/detail?id=2423 |title=Issue 2423 – chromium – Windows Roaming Profile support – An open-source browser project to help move the web forward. – Google Project Hosting |date=September 17, 2008 |access-date=April 8, 2012}}</ref> | ||
| − | In 2010, Google first started supporting Chrome in enterprise environments by providing an MSI wrapper around the Chrome installer. Google starting providing group policy objects, with more added each release,<ref>{{Cite web|url=https://support.google.com/chrome/a/answer/7679408?hl=en|title=Chrome Enterprise release notes - Google Chrome Enterprise Help|website=support.google.com}}</ref> and today there are more than 500 | + | In 2010, Google first started supporting Chrome in enterprise environments by providing an MSI wrapper around the Chrome installer. Google starting providing group policy objects, with more added each release,<ref>{{Cite web|url=https://support.google.com/chrome/a/answer/7679408?hl=en|title=Chrome Enterprise release notes - Google Chrome Enterprise Help|website=support.google.com}}</ref> and today there are more than 500 policies available to control Chrome's behavior in enterprise environments.<ref>{{Cite web|url=https://cloud.google.com/docs/chrome-enterprise/policies|title=Chrome Enterprise Policy List & Management | Documentation|website=Google Cloud}}</ref> |
In 2016, Google launched Chrome Browser Enterprise Support, a paid service enabling IT admins access to Google experts to support their browser deployment.<ref>{{Cite web|url=https://social.techcrunch.com/2017/08/22/google-launches-chrome-enterprise-for-businesses-that-want-to-use-chrome-os/|title=Google launches Chrome Enterprise subscription service for Chrome OS}}</ref> In 2019, Google launched ''Chrome Browser Cloud Management'', a dashboard that gives business IT managers the ability to control content accessibility, app usage and browser extensions installed on its deployed computers.<ref>{{cite web|url = https://siliconangle.com/2019/04/11/google-intros-centralized-controls-chrome-browser-deployments/|title = Google debuts centralized controls for Chrome browser deployments |access-date = May 6, 2020|last = Wheatley|first = Mike |work = siliconangle.com|date = April 11, 2019|archive-url = https://web.archive.org/web/20190412194815/https://siliconangle.com/2019/04/11/google-intros-centralized-controls-chrome-browser-deployments/|archive-date =April 12, 2019 }}</ref> | In 2016, Google launched Chrome Browser Enterprise Support, a paid service enabling IT admins access to Google experts to support their browser deployment.<ref>{{Cite web|url=https://social.techcrunch.com/2017/08/22/google-launches-chrome-enterprise-for-businesses-that-want-to-use-chrome-os/|title=Google launches Chrome Enterprise subscription service for Chrome OS}}</ref> In 2019, Google launched ''Chrome Browser Cloud Management'', a dashboard that gives business IT managers the ability to control content accessibility, app usage and browser extensions installed on its deployed computers.<ref>{{cite web|url = https://siliconangle.com/2019/04/11/google-intros-centralized-controls-chrome-browser-deployments/|title = Google debuts centralized controls for Chrome browser deployments |access-date = May 6, 2020|last = Wheatley|first = Mike |work = siliconangle.com|date = April 11, 2019|archive-url = https://web.archive.org/web/20190412194815/https://siliconangle.com/2019/04/11/google-intros-centralized-controls-chrome-browser-deployments/|archive-date =April 12, 2019 }}</ref> | ||
Advertising:
