Downloads:

668,518

Downloads of v 2.3.8:

441

Last Update:

23 Jan 2014

Package Maintainer(s):

Software Author(s):

  • Matt Wrock

Tags:

Boxstarter chocolatey environment setup

Boxstarter

This is not the latest version of Boxstarter available.

2.3.8 | Updated: 23 Jan 2014

Downloads:

668,518

Downloads of v 2.3.8:

441

Maintainer(s):

Software Author(s):

  • Matt Wrock

Tags:

Boxstarter chocolatey environment setup

Boxstarter 2.3.8

This is not the latest version of Boxstarter available.

All Checks are Unknown

2 Test of Unknown Status

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Unknown

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

>

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

>

To uninstall Boxstarter, 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 boxstarter -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 -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 installed
  win_chocolatey:
    name: boxstarter
    state: present
    version: 2.3.8
    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 'boxstarter' do
  action    :install
  version  '2.3.8'
  source   'STEP 3 URL'
end

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


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

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


cChocoPackageInstaller boxstarter
{
   Name     = 'boxstarter'
   Ensure   = 'Present'
   Version  = '2.3.8'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install boxstarter version="2.3.8" 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

Repeatable, reboot resilient windows environment installations made easy using Chocolatey packages. When its time to repave either bare metal or virtualized instances, locally or on a remote machine, Boxstarter can automate both trivial and highly complex installations. Compatible with all Windows versions from Windows 7/2008 R2 forward.

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 2.13.0 20059 Thursday, October 15, 2020 Approved
Boxstarter 2.12.0 397278 Tuesday, October 30, 2018 Approved
Boxstarter 2.11.0 65112 Wednesday, May 16, 2018 Approved
Boxstarter 2.10.3 52570 Thursday, July 27, 2017 Approved
Boxstarter 2.9.26 5951 Monday, June 19, 2017 Approved
Boxstarter 2.9.24 641 Sunday, June 18, 2017 Approved
Boxstarter 2.9.14 6446 Friday, May 5, 2017 Approved
Boxstarter 2.9.5 3527 Thursday, March 30, 2017 Approved
  • Adds Windows Azure VM Integration
    - Supports VM Checkpoints using Azure Blob Snapshots
    - Adds Graceful failure to Enable-RemoteDesktop for Home versions of Windows 7
    - Adds support for unattended install of Boxstarter
Discussion for the Boxstarter Package

Ground Rules:

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