Downloads:

547

Downloads of v 0.0.1:

547

Last Update:

16 Feb 2018

Package Maintainer(s):

Software Author(s):

  • bcurran3

Tags:

bcurran3 windows browser homepage config

Browser Homepages (Config)

0.0.1 | Updated: 16 Feb 2018

Downloads:

547

Downloads of v 0.0.1:

547

Maintainer(s):

Software Author(s):

  • bcurran3

Browser Homepages (Config) 0.0.1

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade homepages-winconfig -y --source="'STEP 3 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="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure homepages-winconfig installed
  win_chocolatey:
    name: homepages-winconfig
    state: present
    version: 0.0.1
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'homepages-winconfig' do
  action    :install
  version  '0.0.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: homepages-winconfig,
    Version: 0.0.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller homepages-winconfig
{
   Name     = 'homepages-winconfig'
   Ensure   = 'Present'
   Version  = '0.0.1'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install homepages-winconfig version="0.0.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

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

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.

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