Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

3,136

Downloads of v 0.0.1:

3,136

Last Update:

16 Feb 2018

Package Maintainer(s):

Software Author(s):

  • bcurran3

Tags:

bcurran3 windows browser homepage config

Browser Homepages (Config)

  • 1
  • 2
  • 3

0.0.1 | Updated: 16 Feb 2018

Downloads:

3,136

Downloads of v 0.0.1:

3,136

Maintainer(s):

Software Author(s):

  • bcurran3

Browser Homepages (Config) 0.0.1

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Browser Homepages (Config), run the following command from the command line or from PowerShell:

>

To upgrade Browser Homepages (Config), run the following command from the command line or from PowerShell:

>

To uninstall Browser Homepages (Config), run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade homepages-winconfig -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade homepages-winconfig -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install homepages-winconfig
  win_chocolatey:
    name: homepages-winconfig
    version: '0.0.1'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'homepages-winconfig' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.0.1'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller homepages-winconfig
{
    Name     = "homepages-winconfig"
    Version  = "0.0.1"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'homepages-winconfig':
  ensure   => '0.0.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved by moderator gep13 on 28 Feb 2018.

Description

Do you want to set the homepage for all browsers at once?

This is the easy way!

WHY DO I NEED THIS?

This is all about quick and easy scripted new computer configurations. I want all browsers set to the same home page, be it www.google.com or www.mybusiness.com - I want them all set to open up to the same location. If you want this too, you found the right place. Yes some of this can be configured through GPO and other methods but not everyone has these other methods. This lets you do it via a Chocolatey package to automate in your scripts. This is part of a series of "-winconfig" packages for configuration automation. Others include desktopicons-winconfig, explorer-winconfig, and taskbar-winconfig

Features:

  • Change default homepage for Microsoft Edge
  • Change default homepage for Internet Explorer
  • Change default homepage for Firefox
  • Change default homepage for Chrome - coming soon
  • Change default homepage for Chromium - coming soon
  • Change default homepage for Opera - maybe/maybe not coming

INSTALL INSTRUCTIONS:

You can set the browser homepage(s) by running choco install homepages-winconfig --params "'/BROWSERNAME:YES /URL:website'". Below is the list of browser names and features you can use as parameters:

  • /ALL:YES - change the homepage for all supported browsers
  • /EDGE:YES - change the homepage for Microsoft Edge
  • /IE:YES - change the homepage for Internet Explorer
  • /FF:YES - change the homepage for Firefox
  • setting any browser to NO will reset it to https://www.google.com

INSTALL EXAMPLES:

  • choco install homepages-winconfig --params "'/ALL:YES /URL:www.chocolatey.org'"
  • choco install homepages-winconfig --params "'/ALL:NO'"
  • choco install homepages-winconfig --params "'/IE:YES /EDGE:YES /FF:NO /URL:www.chocolatey.org'"
  • choco install homepages-winconfig --params "'/IE:YES /EDGE:YES /FF:NO /URL:www.chocolatey.org'"
  • choco install homepages-winconfig --params "'/IE:NO /EDGE:NO /FF:NO'"

There is no upgrade path for this package. homepages-winconfig is a "one and done" package. It is recommended you uninstall this package after install (settings will NOT revert) so that you can install it again under a different user account if necessary. Settings changes only effect the currently logged in user. Of course, you could reinstall it again with -force to change the options.

If you find homepages-winconfig useful, please consider donating: https://www.paypal.me/bcurran3donations

PACKAGE NOTES


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'
$packageName = 'homepages-winconfig'
$pp          = Get-PackageParameters
$defaultURL  = "https://www.google.com"
$setURL      = $pp["URL"]

if ($pp["URL"] -eq $null -or $pp["url"] -eq '')
     { 
      Write-Host * homepages-winconfig: No URL provided. -foreground magenta
     } else {
       Write-Host * homepages-winconfig: Using $pp["URL"] for homepages.  -foreground magenta
	   }

if ($pp["ALL"] -eq 'yes' -or $pp["ALL"] -eq 'YES' -or $pp["ALL"] -eq 'Yes')
     {
	  Set-ItemProperty -Path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings" -Name "ProvisionedHomePages" -Value $setURL
	  Set-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\Main" -Name "Start Page" -Value $setURL
	  $EdgeReady = (Test-path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings")
      If ($EdgeReady -ne "True")
        {
         New-Item -Path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings" -Name "ProvisionedHomePages" –Force
        }
	  $NewData = @()	 
	  $Prefsjsfile = Get-Item -Path ($env:SystemDrive+"\Users\*\AppData\Roaming\Mozilla\Firefox\Profiles\*\prefs.js")
	  Copy-Item $Prefsjsfile $Prefsjsfile".bak"
      $Update = "user_pref(""browser.startup.homepage"", ""$setURL"");"
      $Prefsjs = (Get-Content $Prefsjsfile)
      foreach ($line in $Prefsjs)
	    {
         if ($line -like 'user_pref("browser.startup.homepage",*')
            {
	         $line = $Update
             $NewData+= $line
	        } else {
	          $NewData+= $line
	        }
        }
      Clear-Content $Prefsjsfile
      Add-Content $Prefsjsfile $NewData
	  exit
     } else {
	   if ($pp["ALL"] -eq 'no' -or $pp["ALL"] -eq 'NO' -or $pp["ALL"] -eq 'No')
	     {
		  Set-ItemProperty -Path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings" -Name "ProvisionedHomePages" -Value $defaultURL
          Set-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\Main" -Name "Start Page" -Value $defaultURL
		  $EdgeReady = (Test-path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings")
          If ($EdgeReady -ne "True")
            {
             New-Item -Path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings" -Name "ProvisionedHomePages" –Force
            }
		  $NewData = @()	 
	      $Prefsjsfile = Get-Item -Path ($env:SystemDrive+"\Users\*\AppData\Roaming\Mozilla\Firefox\Profiles\*\prefs.js")
	      Copy-Item $Prefsjsfile $Prefsjsfile".bak"
          $Update = "user_pref(""browser.startup.homepage"", ""$defaultURL"");"
          $Prefsjs = (Get-Content $Prefsjsfile)
          foreach ($line in $Prefsjs)
	        {
             if ($line -like 'user_pref("browser.startup.homepage",*')
               {
	            $line = $Update
                $NewData+= $line
	           } else {
	             $NewData+= $line
	           }
           }
         Clear-Content $Prefsjsfile
         Add-Content $Prefsjsfile $NewData	
		 exit
        }
	 }
	   
# Internet Explorer
if ($pp["IE"] -eq "yes" -or $pp["IE"] -eq "YES" -or $pp["IE"] -eq "Yes")
     {
      Set-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\Main" -Name "Start Page" -Value $setURL
	 } else {
	   if ($pp["IE"] -eq 'no' -or $pp["Ie"] -eq 'NO' -or $pp["IE"] -eq 'No')
	     {
	      Set-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\Main" -Name "Start Page" -Value $defaultURL
		 }
	 }
# Microsoft Edge
$EdgeReady = (Test-path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings")
If ($EdgeReady -ne "True")
   {
    New-Item -Path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings" -Name "ProvisionedHomePages" –Force
   }
	 
if ($pp["EDGE"] -eq "yes" -or $pp["EDGE"] -eq "YES" -or $pp["EDGE"] -eq "Yes")
     {
	   Set-ItemProperty -Path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings" -Name "ProvisionedHomePages" -Value $setURL
	 } else {
	   if ($pp["EDGE"] -eq 'no' -or $pp["EDGE"] -eq 'NO' -or $pp["EDGE"] -eq 'No')
	     {
	      Set-ItemProperty -Path "HKCU:\Software\Policies\Microsoft\MicrosoftEdge\Internet Settings" -Name "ProvisionedHomePages" -Value $defaultURL
		 }
	 }	 
# FireFox 
if ($pp["FF"] -eq 'yes' -or $pp["FF"] -eq 'YES' -or $pp["FF"] -eq 'Yes')
     {
      $NewData = @()	 
	  $Prefsjsfile = Get-Item -Path ($env:SystemDrive+"\Users\*\AppData\Roaming\Mozilla\Firefox\Profiles\*\prefs.js")
	  Copy-Item $Prefsjsfile $Prefsjsfile".bak"
      $Update= "user_pref(""browser.startup.homepage"", ""$setURL"");"
      $Prefsjs = (Get-Content $Prefsjsfile)
      foreach ($line in $Prefsjs)
	    {
         if ($line -like 'user_pref("browser.startup.homepage",*')
            {
	         $line = $Update
             $NewData+= $line
	        } else {
	          $NewData+= $line
	        }
           }
        Clear-Content $Prefsjsfile
        Add-Content $Prefsjsfile $NewData
	} else {
	  if ($pp["FF"] -eq 'no' -or $pp["FF"] -eq 'NO' -or $pp["FF"] -eq 'No')
	     {
          $NewData = @()	 
	      $Prefsjsfile = Get-Item -Path ($env:SystemDrive+"\Users\*\AppData\Roaming\Mozilla\Firefox\Profiles\*\prefs.js")
	      Copy-Item $Prefsjsfile $Prefsjsfile".bak"
          $Update = "user_pref(""browser.startup.homepage"", ""$defaultURL"");"
          $Prefsjs = (Get-Content $Prefsjsfile)
          foreach ($line in $Prefsjs)
	        {
             if ($line -like 'user_pref("browser.startup.homepage",*')
            {
	         $line = $Update
             $NewData+= $line
	        } else {
	          $NewData+= $line
	        }
           }
         Clear-Content $Prefsjsfile
         Add-Content $Prefsjsfile $NewData	
        }
	}

# Chrome - hopefully coming soon
# edit C:\Users\username\AppData\Local\Google\Chrome\User Data\Default\Preferences

# Chromium - hopefully coming soon

# Opera - hopefully coming soon
# Preferences - "startup_list", restore_on_startup":4, "urls_signature" (Google signature the same on all machines?)
# https://github.com/CoderDojoPotsdam/software/blob/master/linux-update/set_startup_homepage.sh

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Discussion for the Browser Homepages (Config) Package

Ground Rules:

  • This discussion is only about Browser Homepages (Config) and the Browser Homepages (Config) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Browser Homepages (Config), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus