Downloads:

728,946

Downloads of v 2.4.67:

674

Last Update:

30 Jul 2014

Package Maintainer(s):

Software Author(s):

  • Matt Wrock

Boxstarter Common Module

This is not the latest version of Boxstarter Common Module available.

  • 1
  • 2
  • 3

2.4.67 | Updated: 30 Jul 2014

Downloads:

728,946

Downloads of v 2.4.67:

674

Maintainer(s):

Software Author(s):

  • Matt Wrock

  • 1
  • 2
  • 3
 Boxstarter Common Module 2.4.67

This is not the latest version of Boxstarter Common Module available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files

Details

To install Boxstarter Common Module, run the following command from the command line or from PowerShell:

>

To upgrade Boxstarter Common Module, run the following command from the command line or from PowerShell:

>

To uninstall Boxstarter Common Module, 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade boxstarter.common -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 boxstarter.common -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 boxstarter.common installed
  win_chocolatey:
    name: boxstarter.common
    state: present
    version: 2.4.67
    source: STEP 3 URL

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


chocolatey_package 'boxstarter.common' do
  action    :install
  version  '2.4.67'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: boxstarter.common,
    Version: 2.4.67,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller boxstarter.common
{
   Name     = 'boxstarter.common'
   Ensure   = 'Present'
   Version  = '2.4.67'
   Source   = 'STEP 3 URL'
}

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


package { 'boxstarter.common':
  provider => 'chocolatey',
  ensure   => '2.4.67',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install boxstarter.common version="2.4.67" 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 as a trusted package on 27 Nov 2014.

Description

Provides common functions used by multiple Boxstarter Modules.

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.

Version Downloads Last Updated Status
Boxstarter Common Module 2.13.0 66499 Thursday, October 15, 2020 Approved
Boxstarter Common Module 2.12.0 395913 Tuesday, October 30, 2018 Approved
Boxstarter Common Module 2.11.0 66581 Wednesday, May 16, 2018 Approved
Boxstarter Common Module 2.10.3 54946 Thursday, July 27, 2017 Approved
Boxstarter Common Module 2.9.27 2633 Wednesday, June 21, 2017 Approved
Boxstarter Common Module 2.9.26 5488 Monday, June 19, 2017 Approved
Boxstarter Common Module 2.9.24 685 Sunday, June 18, 2017 Approved
Boxstarter Common Module 2.9.14 6905 Friday, May 5, 2017 Approved
  • copy the root path passed to New_BoxstarerPackage
    - add a DisableRestart parameter which will suppress the restart file and UAC enabling
    - Greatly improve progress messaging during windows updates runs
    - Fix hang scenarios when waiting for remote machine to reboot and landing in a pending reboot state shortly after reboot
    - Support for auto login and restart in winrm sessions
    - Fix issue with remote check causing an indefinite loop
    - Silencing some handled errors and keep them from leaking to the pipeline
    - Reduce WMI calls and Improve performance of testing if the current session is remote
    - When forcing the install of the outer boxstarter package, make sure to delete the last install from the right repo
    - Check scheduled task output for pending reboots after a remote windows update since 32 bit processes cant read the wsus registry keys
    - Fix Remote check when running as a servise
    - System user logs to programdata
    - when accessing a 64 bit machine from a 32bit process, the windowsupdate reg key is hidden so skip it
    - Bubble up errors from windows update
    - Provide the same scheduled task wrapping for winrm as we do for ps remoting
    - fix explorer restart when there is no explorer process
    - Correcting fallback Chocolatey install path to match release 0.9.8.24
    - Fixing typo param name in redirect call to set-WindowsExplorerOptions
    - Fix InvalidArgument from Set-TaskbarOptions when using lock or unlock params
    - Fix issues where explorer terminates and cannot restart after caling one of the winconfig functions
    - Import azure module from the pipeline to avoid errors when loading Boxstarter.azure
    - Suppress errors when reenabling windows update in case they had alrady been reenabled
    - Fix mis encoded dash in Install-Boxstarterackage
    - Fix issues when Chocolatey packages create a new module and call chocolatey functions from that module
    - When building packages, skip folders without a nuspec instead of throwing an error
    - Only restart the explore process of the current user when calling windows config functions
    - Fixing .net 4.5 install for local installs
    - Fixing TestRunner module loading for PSv2 clients
    - Add the following windows config features:
    - Enable/Disable showing charms when mouse is in the upper right corner
    - Enable/Disable switching apps when pointing in the upper left corner
    - Enable/Disable the option to launch powershell from win-x
    - Enable/Disable boot to desktop
    - Enable/Disable desktop background on the start screen
    - Enable/Disable showing the start screen on the active display
    - Enable/Disable showing the Apps View by default on the start screen
    - Enable/Disable searching everywhere in apps view. Not just apps.
    - Enable/Disable showing desktop apps first in results
    - Lock/Unlock task bar
    - Change taskbar icon size
    - Change location of taskbar docking
    - Add test and publish automation that can point to remote deployment targets
    - Provide build scripts for integration of tests and publishing in CI servers
    - Include configured nuget sources and local repo to all chocolatey install calls and not just the initial package
    - Fix enabling powershell remoting via WMI when password has ampersands
    - Avoid explorer.exe crashes when configuring explorer options
    - Fix Hyper-V heartbeat check in non US locales
    - Fix Azure module loading in 32 bit consoles
    - Fix shell shortcuts when user name has a space
    - Fix Azure VM Checkpoint listing when there are more than one VM in a service
    - Install .net 4.5 ONLY without affecting IIS settings when .net 4 is not present
    - Fix Azure VM integration when multiple subscriptions are present
    - Allow remote installs to be run by a non amin user

This package has no dependencies.

Discussion for the Boxstarter Common Module Package

Ground Rules:

  • This discussion is only about Boxstarter Common Module and the Boxstarter Common Module 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 Boxstarter Common Module, 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