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

Boxstarter Azure Module

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Requires exemption due to dependency on dotnet4.5.2 which causes reboot

Details

Scan Testing Successful:

No detections found in any package files

Details
WARNING

This package was rejected on 01 May 2017. The reviewer chocolatey-ops has listed the following reason(s):

mwrock (maintainer) on 27 Mar 2017 02:46:12 +00:00:

User 'mwrock' (maintainer) submitted package.

chocolatey-ops (reviewer) on 27 Mar 2017 03:19:51 +00:00:

Boxstarter.Azure has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
  • The package id includes dots (.). Usually the package id is separated by '-' instead of dots (except in the case of *.install and *.portable). The reviewer will ensure this is not a new package. More...

chocolatey-ops (reviewer) on 27 Mar 2017 05:42:33 +00:00:

Boxstarter.Azure has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/a42edfe0226cf7f6e09f5aa3b51f474e for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 16 Apr 2017 05:47:19 +00:00:

We've found Boxstarter.Azure v2.9.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 01 May 2017 05:47:34 +00:00:

Unfortunately there has not been progress to move Boxstarter.Azure v2.9.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

Boxstarter's Azure module includes functionality for targeting Azure VMs with the ability to save and restore checkpoints leveraging blob snapshots.


tools\Boxstarter.Azure.PreInstall.ps1
# we no longer use a dependeny on WindowsAzureLibsForNet
# Currently we MUST use version 2.5 and dependencies 
# broke if the user has a more recent version

if(Test-Path "$env:ProgramFiles\Microsoft SDKs\Azure\.NET SDK\v2.5") {
    Write-Host "Windows Azure Libraries for .net v2.5 is already installed."
    return
}
Install-ChocolateyPackage 'Boxstarter.WindowsAzureLibsForNet'`
                          'msi' '/quiet /norestart'`
                          'http://download.microsoft.com/download/9/F/7/9F7D3299-9AE1-40BE-B24F-C0E9EB0BE61E/MicrosoftAzureLibsForNet-x86.msi'`
                          'http://download.microsoft.com/download/9/F/7/9F7D3299-9AE1-40BE-B24F-C0E9EB0BE61E/MicrosoftAzureLibsForNet-x64.msi'
tools\Boxstarter.Azure\Boxstarter.Azure.psd1
@{
Description = 'Provides Cmdlets that will install a boxstarter package on a Windows Azure VM'
# Script module or binary module file associated with this manifest.
ModuleToProcess = './boxstarter.Azure.psm1'

# Version number of this module.
ModuleVersion = '2.9.0'

# ID used to uniquely identify this module
GUID = 'bbdb3e8b-9daf-4c00-a553-4f3f88fb6e59'

# Author of this module
Author = 'Matt Wrock'

# Copyright statement for this module
Copyright = '(c) 2016 Matt Wrock'

# Minimum version of the Windows PowerShell engine required by this module
PowerShellVersion = '3.0'

# Minimum version of the .NET Framework required by this module
DotNetFrameworkVersion = '4.0'

RequiredAssemblies = @( "$env:ProgramW6432\Microsoft SDKs\Azure\.NET SDK\v2.5\bin\plugins\Caching\Microsoft.WindowsAzure.StorageClient.dll" )

# Modules to import as nested modules of the module specified in RootModule/ModuleToProcess
NestedModules = @('..\Boxstarter.Common\Boxstarter.Common.psd1','..\Boxstarter.Chocolatey\Boxstarter.Chocolatey.psd1')

# Functions to export from this module
FunctionsToExport = '*'

# Cmdlets to export from this module
CmdletsToExport = '*'

# Variables to export from this module
VariablesToExport = '*'

# Aliases to export from this module
AliasesToExport = '*'

# List of all modules packaged with this module.
# ModuleList = @()

# List of all files packaged with this module
# FileList = @()

# Private data to pass to the module specified in RootModule/ModuleToProcess
PrivateData = '514b445ca7d1f7e8c16acaf7336eeb1aeca1a562'

# Default prefix for commands exported from this module. Override the default prefix using Import-Module -Prefix.
# DefaultCommandPrefix = ''

}

tools\Boxstarter.Azure\BoxStarter.Azure.psm1
$unNormalized=(Get-Item "$PSScriptRoot\..\Boxstarter.Chocolatey\Boxstarter.Chocolatey.psd1")
Import-Module $unNormalized.FullName -global -DisableNameChecking -Force
Resolve-Path $PSScriptRoot\*-*.ps1 | 
    % { . $_.ProviderPath }

#There is a bug where the storage module will not load if loaded after the azure module
try {Get-Module Storage -ListAvailable | Import-Module -global} catch { Log-BoxstarterMessage $_ }

Import-AzureModule

Export-ModuleMember Enable-BoxstarterVM,`
                    Get-AzureVMCheckpoint,`
                    Remove-AzureVMCheckpoint,`
                    Restore-AzureVMCheckpoint,`
                    Set-AzureVMCheckpoint,`
                    Test-VMStarted
tools\Boxstarter.Azure\Boxstarter.Azure.pssproj
 
tools\Boxstarter.Azure\Enable-BoxstarterVM.ps1
function Enable-BoxstarterVM {
<#
.SYNOPSIS
Finds the PowerShell Remote ConnectionURI of an Azure VM and ensures it can be accessed

.DESCRIPTION
Ensures that an Azure VM can be accessed by Boxstarter. Checks the Azure PowerShell 
SDK settings are set correctly and also examines the VM endpoints to ensure the correct 
settings for PowerShell remoting. If necessary and if running with administrative 
privileges, the WinRM certificate of the VM is downloaded and installed. If not running 
with admin privileges, a PowerShell SessionOption is used that skips the CA and CN 
check. The VM's PowerShell remoting ConnectionURI is located and returned via a 
BoxstarterConfig instance.

Enable-BoxstarterVM will also restore the VM to a specified 
checkpoint or create a new checkpoint if the given checkpoint 
does not exist.

.Parameter Provider
The VM Provider to use.

.PARAMETER CloudServiceName
The name of the Azure Cloud Service associated with the VM.

.PARAMETER VMName
The name of the VM to enable.

.PARAMETER Credential
The Credential to use to test PSRemoting.

.PARAMETER CheckpointName
If a Checkpoint exists by this name, it will be restored. Otherwise one will be created.

.NOTES
Boxstarter uses Azure Blob snapshots to create and manage VM checkpoints. These 
will not be found in the Azure portal, but you can use Boxstarter's checkpoint 
commands to manage them: Set-AzureVMCheckpoint, Get-AzureVMCheckpoint, 
Restore-AzureVMCheckpoint and Remove-AzureVMCheckpoint.

The Windows Azure PowerShell SDK and the .NET Libraries SDK are both used to 
manage the Azure VMs and Blobs.

.OUTPUTS
A BoxstarterConnectionConfig that contains the ConnectionURI of the VM Computer and 
the PSCredential needed to authenticate.

.EXAMPLE
$cred=Get-Credential AzureAdmin
New-AzureQuickVM -ServiceName MyService -Windows -Name MyVM `
  -ImageName 3a50f22b388a4ff7ab41029918570fa6__Windows-Server-2012-Essentials-20131217-enus `
  -Password $cred.GetNetworkCredential().Password -AdminUsername $cred.UserName `
  -Location "West US" -WaitForBoot
Enable-BoxstarterVM -Provider Azure -CloudServiceName MyService -VMName MyVM $cred NewSnapshot | Install-BoxstarterPackage MyPackage

Uses the Azure PowerShell SDK to create a new VM. Enable-BoxstarterVM 
then installs the WinRM certificate and obtains the VM's ConnectionURI 
which is piped to Install-BoxstarterPackage to install MyPackage.

.EXAMPLE
Enable-BoxstarterVM -Provider Azure -CloudServiceName MyService -VMName MyVM $cred

Installs the WinRM certificate associated with the VM and locates its ConnectionURI

.EXAMPLE
Enable-BoxstarterVM -Provider Azure -CloudServiceName MyService -VMName MyVM $cred | Install-BoxstarterPackage MyPackage

Obtains the VM ConnectionURI and uses that to install MyPackage

.EXAMPLE
Enable-BoxstarterVM -Provider Azure -CloudServiceName MyService -VMName MyVM $cred ExistingSnapshot | Install-BoxstarterPackage MyPackage

Gets MyVM's ConnectionURI, restores it to the state stored in ExistingSnapshot 
and then installs MyPackage

.EXAMPLE
Enable-BoxstarterVM -Provider Azure -CloudServiceName MyService -VMName MyVM $cred NewSnapshot | Install-BoxstarterPackage MyPackage

Gets MyVM's ConnectionURI, creates a new snapshot named NewSnapshot and 
then installs MyPackage

.LINK
http://boxstarter.org
Install-BoxstarterPackage
Set-AzureVMCheckpoint
Get-AzureVMCheckpoint
Restore-AzureVMCheckpoint
Remove-AzureVMCheckpoint

#>
    [CmdletBinding()]
    [OutputType([BoxstarterConnectionConfig])]
    param(
        [parameter(Mandatory=$true, Position=0)]
        [string]$CloudServiceName,
        [parameter(Mandatory=$true, ValueFromPipeline=$True, Position=1)]
        [string[]]$VMName,
        [parameter(Mandatory=$true, Position=2)]
        [Management.Automation.PsCredential]$Credential,
        [parameter(Mandatory=$false, Position=3)]
        [string]$CheckpointName
    )
    Begin {
        $CurrentVerbosity=$global:VerbosePreference

        $subscription=Get-AzureSubscription -Current
        if($subscription -eq $null){
            throw @"
Your Azure subscription information has not been sent.
Run Get-AzurePublishSettingsFile to download your Publisher settings.
Then run Import-AzurePublishSettingsFile with the settings file.
Once that is done, please run Enable-BoxstarterVM again.
"@
            return
        }

        if($PSBoundParameters["Verbose"] -eq $true) {
            $global:VerbosePreference="Continue"
        }
    }

    Process {
        try {
            $VMName | % { 
                Write-BoxstarterMessage "Locating Azure VM $_..."
                $vm = Invoke-RetriableScript { Get-AzureVM -ServiceName $args[0] -Name $args[1] } $CloudServiceName $_
                if($vm -eq $null){
                    throw New-Object -TypeName InvalidOperationException -ArgumentList "Could not find VM: $_"
                }

                if($subscription.CurrentStorageAccountName -eq $null) {
                    Write-BoxstarterMessage "Getting OS Disk" -Verbose
                    $disk=Invoke-RetriableScript { Get-AzureOSDisk -VM $args[0] } $vm
                    $endpoint="https://$($disk.MediaLink.Host)/"
                    Write-BoxstarterMessage "Getting Azure Storage Account" -Verbose
                    $storageAccount=Invoke-RetriableScript { Get-AzureStorageAccount } | ? { $_.Endpoints -contains $endpoint }
                    Set-AzureSubscription -SubscriptionName $subscription.SubscriptionName -CurrentStorageAccountName $storageAccount.Label
                }

                if($CheckpointName -ne $null -and $CheckpointName.Length -gt 0){
                    $snapshot = Get-AzureVMCheckpoint -VM $vm -CheckpointName $CheckpointName
                    if($snapshot -ne $null) {
                        Restore-AzureVMCheckpoint -VM $vm -CheckpointName $CheckpointName
                        $restored=$true
                    }
                }

                if($vm.InstanceStatus -ne "ReadyRole"){
                    Write-BoxstarterMessage "Starting Azure VM $_..."
                    Invoke-RetriableScript { Start-AzureVM -Name $args[0] -ServiceName $args[1] } $_ $CloudServiceName | Out-Null
                    Wait-ReadyState -ServiceName $CloudServiceName  -VMName $_
                }

                if(!(Test-Admin)) {
                    $PSSessionOption = New-PSSessionOption -SkipCACheck -SkipCNCheck
                }
                else {
                    Install-WinRMCert $vm | Out-Null
                }

                Write-BoxstarterMessage "Getting connection URI" -Verbose
                $uri = Invoke-RetriableScript { Get-AzureWinRMUri -serviceName $args[0] -Name $args[1] } $CloudServiceName $_
                if($uri -eq $null) {
                    throw New-Object -TypeName InvalidOperationException -ArgumentList "WinRM Endpoint is not configured on VM. Use Add-AzureEndpoint to add PowerShell remoting endpoint and use Enable-PSRemoting -Force on the VM to enable PowerShell remoting."
                }
                Write-BoxstarterMessage "URI: $uri" -Verbose
                $ComputerName=$uri.Host
                Enable-BoxstarterClientRemoting $ComputerName | out-Null
                Write-BoxstarterMessage "Testing remoting access on $ComputerName..."
                try {
                    Invoke-RetriableScript { Invoke-Command $args[0] { Get-WmiObject Win32_ComputerSystem } -Credential $args[1] -ErrorAction Stop | Out-Null } $uri $Credential 
                }
                catch {
                    Write-BoxstarterMessage "Failed to establish a remote connection with $uri. Use Enable-PSRemoting -Force on the VM to enable PowerShell remoting. Install will continue since this may be a transient error. The error encountered was $($_.ToString())" -Verbose
                }
        
                if(!$restored -and $CheckpointName -ne $null -and $CheckpointName.Length -gt 0) {
                    Write-BoxstarterMessage "Creating Checkpoint $CheckpointName for service $CloudServiceName VM $_ at $CheckpointFile"
                    Set-AzureVMCheckpoint -VM $vm -CheckpointName $CheckpointName | Out-Null
                }

                $res=new-Object -TypeName BoxstarterConnectionConfig -ArgumentList $uri,$Credential,$PSSessionOption
                return $res
            }
        }
        finally {
            $global:VerbosePreference=$CurrentVerbosity
        }
    }
}

function Wait-ReadyState($ServiceName, $vmName) {
    do {
        Start-Sleep -milliseconds 100
        Write-BoxstarterMessage "Checking VM for ReadyRole status...Hey VM!, are you ready to roll?..." -Verbose
    } 
    until (( Invoke-RetriableScript { (Get-AzureVM -ServiceName $args[0] -Name $args[1]).InstanceStatus } $ServiceName $vmName ) -eq "ReadyRole")
}
tools\Boxstarter.Azure\Get-AzureVMCheckpoint.ps1
function Get-AzureVMCheckpoint {
<#
.SYNOPSIS
Retrieves Azure Blob Snapshots for a VM

.DESCRIPTION
Blob snapshots created for a VM are returned. This command can return all 
snapshots for a specific VM or for a single checkpoint specified by name.

.PARAMETER $VM
The VM Instance of the Azure Virtual Machine to query for checkpoints.

.PARAMETER $CheckpointName
The Name of a specific checkpoint to return. If not provided, all 
checkpoints for the VM will be returned.

.EXAMPLE
$VM = Get-AzureVM -ServiceName "mycloudService" -Name "MyVM"
Get-AzureVMCheckpoint -VM $VM -CheckpointName "Clean"

Retrieves the "clean" checkpoint associated with the MyVM VM

.EXAMPLE
$VM = Get-AzureVM -ServiceName "mycloudService" -Name "MyVM"
Get-AzureVMCheckpoint -VM $VM

Retrieves all checkpoints associated with the MyVM VM

.LINK
http://boxstarter.org
Set-AzureVMCheckpoint
Remove-AzureVMCheckpoint
Restore-AzureVMCheckpoint
#>
    [CmdletBinding()]
    param (
        [parameter(Mandatory=$true, Position=0)]
        [Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM]$VM,
        [parameter(Mandatory=$false, Position=1)]
        [string]$CheckpointName
    )
    $blob=Get-Blob $VM
    if($CheckpointName -ne $null -and $CheckpointName.Length -gt 0){
        $CheckpointName = "$(Get-CheckpointPrefix $VM)-$CheckpointName"
    }

    $options = New-Object Microsoft.WindowsAzure.StorageClient.BlobRequestOptions
    $options.BlobListingDetails = "Snapshots,Metadata"
    $options.UseFlatBlobListing = $true
    $snapshots = Query-BlobSnapshots $blob $options

    return $snapshots | ? { 
        ($CheckpointName -eq $null -or $CheckpointName.Length -eq 0 -or $_.Metadata["name"] -eq $CheckpointName) -and $_.SnapshotTime -ne $null
    } | % { 
        if($_.Metadata["name"].ToLower().StartsWith((Get-CheckpointPrefix $VM).ToLower())) {
            New-Object PSObject -Prop @{
                Name=$_.Metadata["name"].Substring((Get-CheckpointPrefix $VM).Length+1)
                Snapshot=$_
            } 
        }
    }
 }

 function Query-BlobSnapshots($blob, $options) {
    return $blob.Container.ListBlobs($options)
 }
tools\Boxstarter.Azure\Get-Blob.ps1
function Get-Blob {
    param (
        [Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM]$VM
    )
    $ServiceName=$vm.ServiceName

    $storageAccount = (Get-AzureSubscription -current).CurrentStorageAccountName
    if($storageAccount -eq $null){
        throw New-Object -TypeName InvalidOperationException -ArgumentList "The CurrentStorageAccountName has not been set. Use Set-AzureSubscription to set your current storage account"
    }

    Write-BoxstarterMessage "Getting azure storage key..." -Verbose
    $key = Invoke-RetriableScript { (Get-AzureStorageKey -StorageAccountName $args[0]).Primary } $storageAccount
    $creds = New-Object Microsoft.WindowsAzure.StorageCredentialsAccountAndKey($storageAccount,$key)

    Write-BoxstarterMessage "Getting OS disk..." -Verbose
    $vmOSDisk=Invoke-RetriableScript { Get-AzureOSDisk -vm $args[0] } $VM
    $blobURI = $vmOSDisk.MediaLink
    $blobPath = $BlobUri.LocalPath.Substring(1)
    $blobClient = New-Object Microsoft.WindowsAzure.StorageClient.CloudBlobClient("http://$($blobUri.Host)", $creds)
    return $blobClient.GetBlobReference($blobPath)
 }
tools\Boxstarter.Azure\Get-CheckpointPrefix.ps1
function Get-CheckpointPrefix{
    param (
        [Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM]$VM
    )
        return "$($VM.ServiceName)-$($VM.Name)"

}
tools\Boxstarter.Azure\Import-AzureModule.ps1
function Import-AzureModule {
    $azureMod = Get-Module Azure -ListAvailable
    if(!$azureMod) {
        if(${env:ProgramFiles(x86)} -ne $null){ $programFiles86 = ${env:ProgramFiles(x86)} } else { $programFiles86 = $env:ProgramFiles }
        $modulePath="$programFiles86\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\Azure.psd1"
        if(Test-Path $modulePath) {
            Import-Module $modulePath -global
        }
    }
    else {
        $azureMod | Import-Module -global
    }
}
tools\Boxstarter.Azure\Install-WinRMCert.ps1
function Install-WinRMCert($VM)
{
 $winRMCert = ($VM | select -ExpandProperty vm).DefaultWinRMCertificateThumbprint
 if($winRMCert -eq $null){ 
    $X509=Get-AzureCertificate -ServiceName $vm.serviceName -ThumbprintAlgorithm sha1
    if($X509){
        $winRMCert=$X509.Thumbprint
    }
    else {
        Write-BoxstarterMessage "Could not find Certificate" -Verbose
        return
    } 
}

 Write-BoxstarterMessage "Installing WinRM Certificate"
 $AzureX509cert = Get-AzureCertificate -ServiceName $vm.serviceName -Thumbprint $winRMCert -ThumbprintAlgorithm sha1
 
 $certTempFile = [IO.Path]::GetTempFileName()
 $AzureX509cert.Data | Out-File $certTempFile
 
 # Target The Cert That Needs To Be Imported
 $CertToImport = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $certTempFile
 
 $store = New-Object System.Security.Cryptography.X509Certificates.X509Store "Root", "LocalMachine"
 $store.Certificates.Count
 $store.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite)
 $store.Add($CertToImport)
 $store.Close()
 
 Remove-Item $certTempFile
}
tools\Boxstarter.Azure\Remove-AzureVMCheckpoint.ps1
function Remove-AzureVMCheckpoint {
<#
.SYNOPSIS
Deletes an Azure Blob checkpoint associated with a VM

.DESCRIPTION
Deletes an Azure Blob checkpoint associated with a VM.

.PARAMETER $VM
The VM instance of the Azure Virtual Machine associated with the checkpoint to delete

.PARAMETER $CheckpointName
The Name of a the checkpoint to delete

.EXAMPLE
$VM = Get-AzureVM -ServiceName "mycloudService" -Name "MyVM"
Remove-AzureVMCheckpoint -VM $VM -CheckpointName "Clean"

Deletes the "clean" checkpoint associated with the MyVM VM

.LINK
http://boxstarter.org
Get-AzureVMCheckpoint
Set-AzureVMCheckpoint
Restore-AzureVMCheckpoint
#>    
    [CmdletBinding()]
    param (
        [parameter(Mandatory=$true, Position=0)]
        [Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM]$VM,
        [parameter(Mandatory=$true, Position=1)]
        [string]$CheckpointName
    )
    $checkpoint=Get-AzureVMCheckpoint @PSBoundParameters

    if($checkpoint -eq $null) {
        throw New-Object -TypeName ArgumentException -ArgumentList "CheckpointName","No checkpoint found with name $checkpointname for VM $($VM.Name)"
    }

    $checkpoint.Snapshot.Delete()
}
tools\Boxstarter.Azure\Restore-AzureVMCheckpoint.ps1
function Restore-AzureVMCheckpoint {
<#
.SYNOPSIS
Restores an Azure VM with a previously set checkpoint

.DESCRIPTION
Restores the state of a VM with a Blob snapshot previously created with Set-AzureVMCheckpoint.

.PARAMETER $VM
The VM instance of the Azure Virtual Machine to restore

.PARAMETER $CheckpointName
The Name of a the checkpoint to apply

.EXAMPLE
$VM = Get-AzureVM -ServiceName "mycloudService" -Name "MyVM"
Restore-AzureVMCheckpoint -VM $VM -CheckpointName "Clean"

Restores MyVM to the state it was in when the "clean" checkpoint was created

.LINK
http://boxstarter.org
Set-AzureVMCheckpoint
Get-AzureVMCheckpoint
Remove-AzureVMCheckpoint
#>    
    [CmdletBinding()]
    param (
        [parameter(Mandatory=$true, Position=0)]
        [Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM]$VM,
        [parameter(Mandatory=$true, Position=1)]
        [string]$CheckpointName
    )
    $checkpoint = Get-AzureVMCheckpoint $vm $CheckpointName
    if($checkpoint -eq $null) {
        throw New-Object -TypeName ArgumentException -ArgumentList "CheckpointName","No checkpoint found with name $checkpointname for VM $($VM.Name)"
    }

    $blob=Get-Blob $vm
    $exportPath = "$env:temp\boxstarterAzureCheckpoint$($vm.Name).xml"
    write-boxstartermessage "Getting OS Disk" -verbose
    $vmOSDisk=Invoke-RetriableScript { Get-AzureOSDisk -VM $args[0] } $VM

    Write-BoxstarterMessage "Exporting VM configuration for $($vm.ServiceName) of $serviceName service to $exportPath..."
    $exportResult = Export-AzureVM -ServiceName $vm.serviceName -Name $vm.Name -Path $exportPath
    if($exportResult -eq $null) {
        throw "Unable to export VM"
    }

    Write-BoxstarterMessage "Removing Azure VM $($vm.Name)..."
    Invoke-RetriableScript { Remove-AzureVM -ServiceName $args[0].serviceName -Name $args[0].Name } $VM| Out-Null

    Write-BoxstarterMessage "Waiting for disk $($vmOSDisk.DiskName) to be free..."
    do {
        write-BoxstarterMessage "Still waiting..." -verbose
        Start-Sleep -milliseconds 100
    } 
    until ((Invoke-RetriableScript { (Get-AzureDisk -DiskName $args[0]).AttachedTo } $vmOSDisk.DiskName ) -eq $null)

    Write-BoxstarterMessage "Removing disk $($vmOSDisk.DiskName)..."
    Invoke-RetriableScript { Remove-AzureDisk -DiskName $args[0] } $vmOSDisk.DiskName | Out-Null

    Write-BoxstarterMessage "Copying $($checkpoint.snapshot.Uri) to blob..."
    $blob.CopyFromBlob($checkpoint.snapshot)

    Write-BoxstarterMessage "Creating new disk from blob..."
    Invoke-RetriableScript { Add-AzureDisk -DiskName $args[0] -MediaLocation $args[1] -OS Windows } $vmOSDisk.DiskName $blob.Uri | Out-Null

    Write-BoxstarterMessage "Creating new VM at Checkpoint..."
    Invoke-RetriableScript { Import-AzureVM -path $args[0] | New-AzureVM -ServiceName $args[1] -WaitForBoot } $exportPath $vm.serviceName | Out-Null
 }
tools\Boxstarter.Azure\Set-AzureVMCheckpoint.ps1
function Set-AzureVMCheckpoint {
<#
.SYNOPSIS
Creates an Azure Blob checkpoint to capture the state of a VM

.DESCRIPTION
Creates an Azure Blob checkpoint to capture the state of a VM. This checkpoint can 
be later used to restore a VM to the state of the VM when the checkpoint was saved.

.PARAMETER $VM
The VM instance of the Azure Virtual Machine to checkpoint

.PARAMETER $CheckpointName
The Name of a the checkpoint to save

.EXAMPLE
$VM = Get-AzureVM -ServiceName "mycloudService" -Name "MyVM"
Set-AzureVMCheckpoint -VM $VM -CheckpointName "Clean"

Checkpoints MyVM with the label "clean" which can restore the VM to its current state

.LINK
http://boxstarter.org
Get-AzureVMCheckpoint
Remove-AzureVMCheckpoint
Restore-AzureVMCheckpoint
#>    
    [CmdletBinding()]
    param (
        [parameter(Mandatory=$true, Position=0)]
        [Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM]$VM,
        [parameter(Mandatory=$true, Position=1)]
        [string]$CheckpointName
    )
    $blob=Get-blob $VM

    $existingBlob = Get-AzureVMCheckpoint -VM $VM -CheckpointName $CheckpointName
    if($existingBlob -ne $null) {
        $existingBlob.Snapshot.Delete()
    }
    $CheckpointName = "$(Get-CheckpointPrefix $VM)-$CheckpointName"
    $attributes = New-Object System.Collections.Specialized.NameValueCollection
    $attributes.Add("name",$CheckpointName)
    return $blob.CreateSnapshot($attributes, $null)
}
tools\Boxstarter.Azure\Test-VMStarted.ps1
function Test-VMStarted {
<#
.SYNOPSIS
Checks if an Azure VM is in a running state

.DESCRIPTION
If the VM is running, Test-VMStarted returns $true

.PARAMETER CloudServiceName
The name of the Azure Cloud Service associated with the VM.

.PARAMETER VMName
The name of the VM to enable.

.EXAMPLE
$isStarted = Test-VMStarted -ServiceName "mycloudService" -Name "MyVM"

$isStarted will be $true if MyVM is running

.LINK
http://boxstarter.org
Enable-BoxstarterVM
#>
    [CmdletBinding()]
    param(
        [parameter(Mandatory=$true, Position=0)]
        [string]$CloudServiceName,
        [parameter(Mandatory=$true, ValueFromPipeline=$True, Position=1)]
        [string[]]$VMName
    )

    Process {
        $VMName | % { 
            $vm = Invoke-RetriableScript { Get-AzureVM -ServiceName $args[0] -Name $args[1] } $CloudServiceName $_
            if($vm -eq $null){
                throw New-Object -TypeName InvalidOperationException -ArgumentList "Could not find VM: $_"
            }
            if($vm.InstanceStatus -eq "ReadyRole"){
                Write-BoxStarterMessage "Testing service $CloudServiceName vm $_. VM is in ReadyRole." -verbose
                return $true
            }
            else {
                Write-BoxStarterMessage "Testing service $CloudServiceName vm $_. VM is not in ReadyRole. Role: $($vm.InstanceStatus)" -verbose
                return $false
            }
        }
    }
}
tools\chocolateyinstall.ps1
$tools = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. (Join-Path $tools Setup.ps1)
try { 
    $ModuleName = (Get-ChildItem $tools | ?{ $_.PSIsContainer }).BaseName
    $preInstall = Join-Path $tools "$modulename.preinstall.ps1"
    if(Test-Path $preInstall) { .$preInstall }
    Install-Boxstarter $tools $ModuleName $env:chocolateyPackageParameters
} catch {
    write-output $_ | fl * -force
    throw $_.Exception
}
tools\LICENSE.txt
                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.
tools\setup.ps1
function Install-Boxstarter($here, $ModuleName, $installArgs = "") {
    $boxstarterPath=Join-Path $env:AppData Boxstarter
    if(!(test-Path $boxstarterPath)){
        mkdir $boxstarterPath
    }
    $packagePath=Join-Path $boxstarterPath BuildPackages
    if(!(test-Path $packagePath)){
        mkdir $packagePath
    }    
    foreach($ModulePath in (Get-ChildItem $here | ?{ $_.PSIsContainer })){
        $target=Join-Path $boxstarterPath $modulePath.BaseName
        if(test-Path $target){
            Remove-Item $target -Recurse -Force
        }
    }
    Copy-Item "$here\*" $boxstarterPath -Recurse -Force -Exclude ChocolateyInstall.ps1, Setup.*

    PersistBoxStarterPathToEnvironmentVariable "PSModulePath"
    PersistBoxStarterPathToEnvironmentVariable "Path"
    $binPath =  "$here\..\..\..\bin"
    $boxModule=Get-Module Boxstarter.Chocolatey
    if($boxModule) {
        if($boxModule.Path -like "$env:LOCALAPPDATA\Apps\*") {
            $clickonce=$true
        }
    }
    if(!$clickonce){
        Import-Module "$boxstarterPath\$ModuleName" -DisableNameChecking -Force -ErrorAction SilentlyContinue
    }
    $successMsg = @"
The $ModuleName Module has been copied to $boxstarterPath and added to your Module path. 
You will need to open a new console for the path to be visible.
Use 'Get-Module Boxstarter.* -ListAvailable' to list all Boxstarter Modules.
To list all available Boxstarter Commands, use:
PS:>Import-Module $ModuleName
PS:>Get-Command -Module Boxstarter.*

To find more info visit http://Boxstarter.org or use:
PS:>Import-Module $ModuleName
PS:>Get-Help Boxstarter
"@
    Write-Host $successMsg

    if($ModuleName -eq "Boxstarter.Chocolatey" -and !$env:appdata.StartsWith($env:windir)) {
        $desktop = $([System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::DesktopDirectory))
        $startMenu=$("$env:appdata\Microsoft\Windows\Start Menu\Programs\Boxstarter")
        if(!(Test-Path $startMenu)){
            mkdir $startMenu
        }
        $target="powershell.exe"
        $targetArgs="-ExecutionPolicy bypass -NoExit -Command `"&'$boxstarterPath\BoxstarterShell.ps1'`""

		if($installArgs -inotcontains "nodesktopicon") {
			$link = Join-Path $desktop "Boxstarter Shell.lnk"
			Create-Shortcut $link $target $targetArgs $boxstarterPath
		}
        $link = Join-Path $startMenu "Boxstarter Shell.lnk"
        Create-Shortcut $link $target $targetArgs $boxstarterPath

        Set-Content -Path "$binPath\BoxstarterShell.bat" -Force -Value "$target $TargetArgs"
    }
}

function Create-Shortcut($location, $target, $targetArgs, $boxstarterPath) {
    $wshshell = New-Object -ComObject WScript.Shell
    $lnk = $wshshell.CreateShortcut($location)
    $lnk.TargetPath = $target
    $lnk.Arguments = "$targetArgs"
    $lnk.WorkingDirectory = $boxstarterPath
    $lnk.IconLocation="$boxstarterPath\BoxLogo.ico"
    $lnk.Save()

	$tempFile = "$env:temp\TempShortcut.lnk"
		
	$writer = new-object System.IO.FileStream $tempFile, ([System.IO.FileMode]::Create)
	$reader = new-object System.IO.FileStream $location, ([System.IO.FileMode]::Open)
		
	while ($reader.Position -lt $reader.Length)
	{		
		$byte = $reader.ReadByte()
		if ($reader.Position -eq 22) {
			$byte = 34
		}
		$writer.WriteByte($byte)
	}
		
	$reader.Close()
	$writer.Close()
				
	Move-Item -Path $tempFile $location -Force
}
function PersistBoxStarterPathToEnvironmentVariable($variableName){
    $value = [Environment]::GetEnvironmentVariable($variableName, 'User')
    if($value){
        $values=($value -split ';' | ?{ !($_.ToLower() -match "\\boxstarter$")}) -join ';'
        $values+=";$boxstarterPath"
    } 
    elseif($variableName -eq "PSModulePath") {
        $values=[environment]::getfolderpath("mydocuments")
        $values +="\WindowsPowerShell\Modules;$boxstarterPath"
    }
    else {
        $values ="$boxstarterPath"
    }
    if(!$value -or !($values -contains $boxstarterPath)){
        $values = $values.Replace(';;',';')
        [Environment]::SetEnvironmentVariable($variableName, $values, 'User')
        $varValue = Get-Content env:\$variableName
        $varValue += ";$boxstarterPath"
        $varValue = $varValue.Replace(';;',';')
        Set-Content env:\$variableName -value $varValue
    }
}

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
Boxstarter Azure Module 3.0.2 294 Monday, June 12, 2023 Approved
Boxstarter Azure Module 3.0.1 60 Tuesday, June 6, 2023 Approved
Boxstarter Azure Module 3.0.0 298 Thursday, July 14, 2022 Approved
Boxstarter Azure Module 3.0.0-beta-20220427-21 74 Wednesday, April 27, 2022 Approved
Boxstarter Azure Module 2.13.0 804 Thursday, October 15, 2020 Approved
Boxstarter Azure Module 2.12.0 1229 Tuesday, October 30, 2018 Approved
Boxstarter Azure Module 2.11.0 375 Wednesday, May 16, 2018 Approved
Boxstarter Azure Module 2.9.26 1185 Monday, June 19, 2017 Approved
Boxstarter Azure Module 2.9.24 428 Sunday, June 18, 2017 Approved
Boxstarter Azure Module 2.9.14 484 Friday, May 5, 2017 Approved
Boxstarter Azure Module 2.9.5 474 Thursday, March 30, 2017 Approved
Boxstarter Azure Module 2.9.2 464 Monday, March 27, 2017 Approved
Boxstarter Azure Module 2.8.29 986 Sunday, May 22, 2016 Approved
Boxstarter Azure Module 2.8.27 444 Sunday, May 22, 2016 Approved
Boxstarter Azure Module 2.8.21 494 Thursday, April 28, 2016 Approved
Boxstarter Azure Module 2.8.18 449 Tuesday, April 26, 2016 Approved
Boxstarter Azure Module 2.8.12 424 Thursday, April 21, 2016 Approved
Boxstarter Azure Module 2.8.0 442 Friday, April 15, 2016 Approved
Boxstarter Azure Module 2.7.0 507 Sunday, April 3, 2016 Approved
Boxstarter Azure Module 2.6.41 524 Sunday, February 28, 2016 Approved
Boxstarter Azure Module 2.6.25 567 Friday, December 18, 2015 Approved
Boxstarter Azure Module 2.6.20 488 Thursday, December 17, 2015 Approved
Boxstarter Azure Module 2.6.16 443 Tuesday, December 15, 2015 Approved
Boxstarter Azure Module 2.6.2 394 Monday, December 14, 2015 Approved
Boxstarter Azure Module 2.6.0 473 Sunday, December 13, 2015 Approved
Boxstarter Azure Module 2.5.21 670 Thursday, August 13, 2015 Approved
Boxstarter Azure Module 2.5.19 530 Sunday, July 26, 2015 Approved
Boxstarter Azure Module 2.5.10 475 Friday, July 10, 2015 Approved
Boxstarter Azure Module 2.5.3 545 Wednesday, July 1, 2015 Approved
Boxstarter Azure Module 2.5.1 480 Wednesday, July 1, 2015 Approved
Boxstarter Azure Module 2.4.209 639 Sunday, April 26, 2015 Approved
Boxstarter Azure Module 2.4.205 500 Sunday, April 5, 2015 Approved
Boxstarter Azure Module 2.4.196 585 Friday, March 20, 2015 Approved
Boxstarter Azure Module 2.4.188 525 Monday, March 9, 2015 Approved
Boxstarter Azure Module 2.4.183 473 Wednesday, March 4, 2015 Approved
Boxstarter Azure Module 2.4.180 477 Tuesday, March 3, 2015 Approved
Boxstarter Azure Module 2.4.179 481 Tuesday, March 3, 2015 Approved
Boxstarter Azure Module 2.4.159 578 Sunday, January 18, 2015 Approved
Boxstarter Azure Module 2.4.157 479 Thursday, January 15, 2015 Approved
Boxstarter Azure Module 2.4.152 560 Monday, January 12, 2015 Approved
Boxstarter Azure Module 2.4.149 558 Friday, December 26, 2014 Approved
Boxstarter Azure Module 2.4.146 481 Friday, December 26, 2014 Approved
Boxstarter Azure Module 2.4.128 646 Thursday, November 27, 2014 Approved
Boxstarter Azure Module 2.4.123 860 Wednesday, September 24, 2014 Approved
Boxstarter Azure Module 2.4.110 475 Wednesday, September 17, 2014 Approved
Boxstarter Azure Module 2.4.93 481 Friday, September 12, 2014 Approved
Boxstarter Azure Module 2.4.88 488 Wednesday, September 3, 2014 Approved
Boxstarter Azure Module 2.4.87 439 Wednesday, September 3, 2014 Approved
Boxstarter Azure Module 2.4.80 507 Monday, August 4, 2014 Approved
Boxstarter Azure Module 2.4.76 468 Sunday, August 3, 2014 Approved
Boxstarter Azure Module 2.4.70 449 Thursday, July 31, 2014 Approved
Boxstarter Azure Module 2.4.67 500 Wednesday, July 30, 2014 Approved
Boxstarter Azure Module 2.4.61 460 Monday, July 28, 2014 Approved
Boxstarter Azure Module 2.4.57 492 Sunday, July 27, 2014 Approved
Boxstarter Azure Module 2.4.54 516 Wednesday, July 23, 2014 Approved
Boxstarter Azure Module 2.4.53 461 Wednesday, July 23, 2014 Approved
Boxstarter Azure Module 2.4.51 474 Wednesday, July 23, 2014 Approved
Boxstarter Azure Module 2.4.48 503 Tuesday, July 22, 2014 Approved
Boxstarter Azure Module 2.4.46 447 Saturday, July 19, 2014 Approved
Boxstarter Azure Module 2.4.41 484 Sunday, July 13, 2014 Approved
Boxstarter Azure Module 2.4.39 425 Sunday, July 13, 2014 Approved
Boxstarter Azure Module 2.4.38 423 Saturday, July 12, 2014 Approved
Boxstarter Azure Module 2.4.35 469 Saturday, July 12, 2014 Approved
Boxstarter Azure Module 2.4.32 440 Friday, July 11, 2014 Approved
Boxstarter Azure Module 2.4.29 466 Friday, July 4, 2014 Approved
Boxstarter Azure Module 2.4.26 521 Monday, June 23, 2014 Approved
Boxstarter Azure Module 2.4.15 558 Sunday, April 20, 2014 Approved
Boxstarter Azure Module 2.4.12 506 Friday, April 18, 2014 Approved
Boxstarter Azure Module 2.4.4 494 Saturday, April 5, 2014 Approved
Boxstarter Azure Module 2.4.0 499 Friday, April 4, 2014 Approved
Boxstarter Azure Module 2.3.24 569 Saturday, February 1, 2014 Approved
Boxstarter Azure Module 2.3.15 507 Monday, January 27, 2014 Approved
Boxstarter Azure Module 2.3.13 470 Saturday, January 25, 2014 Approved
Boxstarter Azure Module 2.3.8 511 Thursday, January 23, 2014 Approved
Boxstarter Azure Module 2.3.0 526 Monday, January 20, 2014 Approved

  • Update vendored Chocolatey to 0.10.4 beta
  • Add Icon toggling of task bar notifications in Set-TaskbarOptions
  • Fix registry key name in Set-TaskbarOptions on some Windows 10 versions
  • Fix Default of RebootOk in boxstarter shell
  • Stop powershell profile loading when in powershell v2
Discussion for the Boxstarter Azure Module Package

Ground Rules:

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