Difference between revisions of "Google Chrome"

From wikieduonline
Jump to navigation Jump to search
 
(24 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Draft}}
 
 
[[wikipedia:Google Chrome]] (2008) [[web browser]]
 
[[wikipedia:Google Chrome]] (2008) [[web browser]]
  
 +
* [[Google Chrome extensions|extensions]]
  
Extensions:
+
<code>[[brew install --cask google-chrome]]</code>
* Tab Resize - split screen layouts
 
 
 
 
 
 
 
  
 
== [[Windows]] [[command line]] installation ==
 
== [[Windows]] [[command line]] installation ==
 
  $Path = $env:TEMP; $Installer = “chrome_installer.exe”; Invoke-WebRequest “http://dl.google.com/chrome/chrome_installer.exe" -OutFile $Path\$Installer; Start-Process -FilePath $Path\$Installer -Args “/silent /install” -Verb RunAs -Wait; Remove-Item $Path\$Installer
 
  $Path = $env:TEMP; $Installer = “chrome_installer.exe”; Invoke-WebRequest “http://dl.google.com/chrome/chrome_installer.exe" -OutFile $Path\$Installer; Start-Process -FilePath $Path\$Installer -Args “/silent /install” -Verb RunAs -Wait; Remove-Item $Path\$Installer
  
=== Enterprise deployment ===
+
== [[Enterprise deployment]] ==
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 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 &#124; 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>
 
 
 
  
== Related terms ==
+
== Related ==
 
* Manage [[search engines]]
 
* Manage [[search engines]]
 
* [[F12]]
 
* [[F12]]
 
* [[Opera]]
 
* [[Opera]]
 +
* [[Terraform resource: googleworkspace_chrome_policy]]
 +
* <code>chrome://flags/#allow-insecure-localhost</code>
 +
* [[Google Chrome password manager]]
 +
* [[Google Chrome passkey]]
 +
* [[Safari]]
 +
* <code>[[Your connection is not private]]</code>
 +
* [[HTTP/3]]
  
 
== Activities ==
 
== Activities ==
* [[How to add Wikipedia as a Chrome search engine]]: https://justin.kelly.org.au/how-to-add-wikipedia-as-a-chrome-search-engin/
+
* [[How to add Wikipedia as a Chrome search engine]] <ref>https://justin.kelly.org.au/how-to-add-wikipedia-as-a-chrome-search-engin/</ref>
 +
* Use <code>[[Ctrl]] + Shift + M</code> [[Chrome profiles]]
 +
* [[How to create URL as an App]]
 +
* [[Set Chrome policies for users or browsers]]
  
 
== See also ==
 
== See also ==

Latest revision as of 16:16, 27 October 2024

Advertising: