Ansible
PS DSC
Downloads:
1,073,549
Downloads of v 2.4.93:
825
Last Update:
12 Sep 2014
Package Maintainer(s):
Software Author(s):
- Matt Wrock
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Boxstarter Common Module
This is not the latest version of Boxstarter Common Module available.
- 1
- 2
- 3
2.4.93 | Updated: 12 Sep 2014
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,073,549
Downloads of v 2.4.93:
825
Maintainer(s):
Software Author(s):
- Matt Wrock
Boxstarter Common Module 2.4.93
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
Validation Testing Unknown
Verification Testing Unknown
Scan Testing Successful:
No detections found in any package files
Deployment Method: Individual Install, Upgrade, & Uninstall
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:
>
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download boxstarter.common --internalize --version=2.4.93 --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade boxstarter.common -y --source="'INTERNAL REPO URL'" --version="'2.4.93'" [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="'INTERNAL REPO URL'" --version="'2.4.93'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install boxstarter.common
win_chocolatey:
name: boxstarter.common
version: '2.4.93'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'boxstarter.common' do
action :install
source 'INTERNAL REPO URL'
version '2.4.93'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller boxstarter.common
{
Name = "boxstarter.common"
Version = "2.4.93"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'boxstarter.common':
ensure => '2.4.93',
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 as a trusted package on 27 Nov 2014.
Description
Provides common functions used by multiple Boxstarter Modules.
Files
tools\Boxstarter.Common\boxstarter.common.psd1
tools\Boxstarter.Common\Boxstarter.Common.psm1
Resolve-Path $PSScriptRoot\*.ps1 |
% { . $_.ProviderPath }
Export-ModuleMember Write-BoxstarterMessage, Start-TimedSection, Stop-TimedSection, Enter-BoxstarterLogable, Out-BoxstarterLog, Log-BoxstarterMessage, Test-Admin, Invoke-FromTask, Get-IsRemote, Confirm-Choice, Create-BoxstarterTask, Remove-BoxstarterTask, Write-BoxstarterLogo, Get-CurrentUser, Get-IsMicrosoftUpdateEnabled, Invoke-RetriableScript
Export-ModuleMember -Variable Boxstarter
tools\Boxstarter.Common\Boxstarter.Common.pssproj
tools\Boxstarter.Common\Boxstarter.Common.pssproj.user
tools\Boxstarter.Common\Confirm-Choice.ps1
function Confirm-Choice {
<#
.SYNOPSIS
Prompts the user to choose a yes/no option.
.DESCRIPTION
The message parameter is presented to the user and the user is then prompted to
respond yes or no. In environments such as the PowerShell ISE, the Confirm param
is the title of the window presenting the message.
.Parameter Message
The message given to the user that tels them what they are responding yes/no to.
.Parameter Caption
The title of the dialog window that is presented in environments that present
the prompt in its own window. If not provided, the Message is used.
.LINK
http://boxstarter.codeplex.com
#>
param (
[string]$Message,
[string]$Caption = $Message
)
$yes = new-Object System.Management.Automation.Host.ChoiceDescription "&Yes","Yes";
$no = new-Object System.Management.Automation.Host.ChoiceDescription "&No","No";
$choices = [System.Management.Automation.Host.ChoiceDescription[]]($yes,$no);
$answer = $host.ui.PromptForChoice($caption,$message,$choices,0)
switch ($answer){
0 {return $true; break}
1 {return $false; break}
}
}
tools\Boxstarter.Common\Create-BoxstarterTask.ps1
function Create-BoxstarterTask{
<#
.SYNOPSIS
Creates a Scheduled Task for Boxstarter operations that require a local
administrative token
.DESCRIPTION
Create-BoxstarterTask creates a scheduled task. This task is present
throughout a boxstarter installation process and is used when Boxstarter
needs to complete a task that cannot use a remote token. This function
does not run the task. It simply creates it.
.Parameter Credential
The credentials under which the task will run.
.LINK
http://boxstarter.codeplex.com
Invoke-FromTask
Remove-BoxstarterTask
#>
param([Management.Automation.PsCredential]$Credential)
if($Credential.GetNetworkCredential().Password.length -gt 0){
schtasks /CREATE /TN 'Temp Boxstarter Task' /SC WEEKLY /RL HIGHEST `
/RU "$($Credential.UserName)" /IT /RP $Credential.GetNetworkCredential().Password `
/TR "powershell -noprofile -ExecutionPolicy Bypass -File $env:temp\BoxstarterTask.ps1" /F |
Out-Null
#Give task a normal priority
$taskFile = Join-Path $env:TEMP RemotingTask.txt
Remove-Item $taskFile -Force -ErrorAction SilentlyContinue
[xml]$xml = schtasks /QUERY /TN 'Temp Boxstarter Task' /XML
$xml.Task.Settings.Priority="4"
$xml.Save($taskFile)
schtasks /CREATE /TN 'Boxstarter Task' /RU "$($Credential.UserName)" /IT /RP $Credential.GetNetworkCredential().Password /XML "$taskFile" /F | Out-Null
schtasks /DELETE /TN 'Temp Boxstarter Task' /F | Out-Null
}
elseif(!((schtasks /QUERY /TN 'Boxstarter Task' /FO LIST 2>&1) -contains 'Logon Mode: Interactive/Background')) { #For testing
schtasks /CREATE /TN 'Boxstarter Task' /SC WEEKLY /RL HIGHEST `
/RU "$($Credential.UserName)" /IT `
/TR "powershell -noprofile -ExecutionPolicy Bypass -File $env:temp\BoxstarterTask.ps1" /F |
Out-Null
}
if($LastExitCode -gt 0){
throw "Unable to create scheduled task as $($Credential.UserName)"
}
}
tools\Boxstarter.Common\en-US\about_boxstarter_logging.help.txt
TOPIC
About_Boxstarter_Logging
SYNOPSIS
Describes how to the different Boxstarter Logging functions to log to
the console, log file or both.
DESCRIPTION
Boxstarter provides several logging logging functions to make it easy
to deliver messages to script consumers and provide detailed debugging
information to log files. Here is a description of each of these
functions:
Write-BoxstarterMessage
Writes a message to both the Boxstarter log file and to the screen.
These messages are output in Green to make them stand out from
other messages.
Log-BoxstarterMessage
Only writes a message to the Boxstarter log file. The message is
not logged to the console.
Out-BoxtarterLog
This is identical to Write-BoxstarterMessage but the text written
to the screen is not in green. It is formatted normally.
Enter-BoxstarterLogable
This executes a script block and redirects the standard output
stream and standard error stream to both the console and the
Boxstarter log file. This is similar to Out-Boxstarterlog but it
includes the output from standard command line utilities.
Start-TimedSection and Stop-TimedSection
These functions surround all script in between the start and end
functions with a header and footer message and time the script
execution. The footer message includes the total elapsed time.
These sections can be nested.
SEE ALSO
http://boxstarter.codeplex.com
Write-BoxstarterMessage
Out-BoxtarterLog
Enter-BoxstarterLogable
Start-TimedSection
Stop-TimedSection
tools\Boxstarter.Common\Format-BoxStarterMessage.ps1
tools\Boxstarter.Common\Get-CurrentUser.ps1
function Get-CurrentUser {
<#
.SYNOPSIS
Returns the domain and username of the currently logged in user.
#>
$identity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$parts = $identity.Name -split "\\"
return @{Domain=$parts[0];Name=$parts[1]}
}
tools\Boxstarter.Common\Get-IsMicrosoftUpdateEnabled.ps1
function Get-IsMicrosoftUpdateEnabled {
<#
.SYNOPSIS
Returns $True if Microsoft Update is currently enabled
.LINK
http://boxstarter.codeplex.com
#>
# Default response to false, unless proven otherwise
$installed = $false
$serviceManager = New-Object -ComObject Microsoft.Update.ServiceManager -Strict
$serviceManager.ClientApplicationID = "Boxstarter"
foreach ($service in $serviceManager.Services) {
if( $service.Name -eq "Microsoft Update") {
$installed = $true;
break;
}
}
return $installed
}
tools\Boxstarter.Common\Get-IsRemote.ps1
function Get-IsRemote {
param (
[switch]$PowershellRemoting
)
<#
.SYNOPSIS
Returns $True if the current PowerShell session is running remotely
.LINK
http://boxstarter.codeplex.com
#>
if($PSSenderInfo -ne $null) {return $true}
if($PowershellRemoting) {return $false}
if($env:IsRemote -ne $null) { return [bool]::Parse($env:IsRemote) }
else {
$env:IsRemote = Test-ChildOfWinrs
return [bool]::Parse($env:IsRemote)
}
}
function Test-ChildOfWinrs($ID = $PID) {
$parent = (Get-WmiObject -Class Win32_Process -Filter "ProcessID=$ID").ParentProcessID
if($parent -eq $null) { return $false } else {
try {$parentProc = Get-Process -ID $parent -ErrorAction Stop} catch {
$global:error.RemoveAt(0)
return $false
}
if($parentProc.Name -eq "winrshost") {return $true}
elseif($parentProc.Name -eq "services") {return $false}
else {
return Test-ChildOfWinrs $parent
}
}
}
tools\Boxstarter.Common\Init-Settings.ps1
if(!$Global:Boxstarter) {
$Global:Boxstarter = @{}
$Boxstarter.SuppressLogging=$false
}
$Boxstarter.BaseDir=(Split-Path -parent ((Get-Item $PSScriptRoot).FullName))
tools\Boxstarter.Common\Invoke-FromTask.ps1
function Invoke-FromTask {
<#
.SYNOPSIS
Invokes a command inside of a scheduled task
.DESCRIPTION
This invokes the boxstarter scheduled task.
The task is run in an elevated session using the provided
credentials. If the processes started by the task become idle for
more that the specified timeout, the task will be terminated. All
output and any errors from the task will be streamed to the calling
session.
.PARAMETER Command
The command to run in the task.
.PARAMETER IdleTimeout
The number of seconds after which the task will be terminated if it
becomes idle. The value 0 is an indefinite timeout and 120 is the
default.
.PARAMETER TotalTimeout
The number of seconds after which the task will be terminated whether
it is idle or active.
.EXAMPLE
Invoke-FromTask Install-WindowsUpdate -AcceptEula
This will install Windows Updates in a scheduled task
.EXAMPLE
Invoke-FromTask "DISM /Online /Online /NoRestart /Enable-Feature /Telnet-Client" -IdleTimeout 20
This will use DISM.exe to install the telnet client and will kill
the task if it becomes idle for more that 20 seconds.
.LINK
http://boxstarter.codeplex.com
Create-BoxstarterTask
Remove-BoxstarterTask
#>
param(
$command,
$idleTimeout=60,
$totalTimeout=3600
)
Write-BoxstarterMessage "Invoking $command in scheduled task" -Verbose
Add-TaskFiles $command
$taskProc = start-Task
if($taskProc -ne $null){
write-debug "Command launched in process $taskProc"
$waitProc=get-process -id $taskProc -ErrorAction SilentlyContinue
Write-Debug "Waiting on $($waitProc.Id)"
}
Wait-ForTask $waitProc $idleTimeout $totalTimeout
try{$errorStream=Import-CLIXML $env:temp\BoxstarterError.stream} catch {$global:error.RemoveAt(0)}
$str=($errorStream | Out-String)
if($str.Length -gt 0){
throw $errorStream
}
}
function Get-ChildProcessMemoryUsage {
param($ID=$PID)
[int]$res=0
Get-WmiObject -Class Win32_Process -Filter "ParentProcessID=$ID" | % {
if($_.ProcessID -ne $null) {
$proc = Get-Process -ID $_.ProcessID -ErrorAction SilentlyContinue
if($proc -ne $null){
$res += $proc.PrivateMemorySize + $proc.WorkingSet
Write-Debug "$($_.Name) $($proc.PrivateMemorySize + $proc.WorkingSet)"
}
}
}
Get-WmiObject -Class Win32_Process -Filter "ParentProcessID=$ID" | % {
if($_.ProcessID -ne $null) {
$proc = Get-Process -ID $_.ProcessID -ErrorAction SilentlyContinue
if($proc -ne $null){
$res += Get-ChildProcessMemoryUsage $_.ProcessID;
Write-Debug "$($_.Name) $($proc.PrivateMemorySize + $proc.WorkingSet)"
}
}
}
$res
}
function Add-TaskFiles($command) {
$encoded = [Convert]::ToBase64String([System.Text.Encoding]::Unicode.GetBytes("`$ProgressPreference='SilentlyContinue';$command"))
$fileContent=@"
Start-Process powershell -Wait -RedirectStandardError $env:temp\BoxstarterError.stream -RedirectStandardOutput $env:temp\BoxstarterOutput.stream -ArgumentList "-noprofile -ExecutionPolicy Bypass -EncodedCommand $encoded"
Remove-Item $env:temp\BoxstarterTask.ps1 -ErrorAction SilentlyContinue
"@
Set-Content $env:temp\BoxstarterTask.ps1 -value $fileContent -force
new-Item $env:temp\BoxstarterOutput.stream -Type File -Force | out-null
new-Item $env:temp\BoxstarterError.stream -Type File -Force | out-null
}
function start-Task{
$tasks=@()
$tasks+=gwmi Win32_Process -Filter "name = 'powershell.exe' and CommandLine like '%-EncodedCommand%'" | select ProcessId | % { $_.ProcessId }
Write-Debug "Found $($tasks.Length) tasks already running"
$taskResult = schtasks /RUN /I /TN 'Boxstarter Task'
if($LastExitCode -gt 0){
throw "Unable to run scheduled task. Message from task was $taskResult"
}
write-debug "Launched task. Waiting for task to launch command..."
do{
if(!(Test-Path $env:temp\BoxstarterTask.ps1)){
Write-Debug "Task Completed before its process was captured."
break
}
$taskProc=gwmi Win32_Process -Filter "name = 'powershell.exe' and CommandLine like '%-EncodedCommand%'" | select ProcessId | % { $_.ProcessId } | ? { !($tasks -contains $_) }
Start-Sleep -Second 1
}
Until($taskProc -ne $null)
return $taskProc
}
function Test-TaskTimeout($waitProc, $idleTimeout) {
if($memUsageStack -eq $null){
$script:memUsageStack=New-Object -TypeName System.Collections.Stack
}
if($idleTimeout -gt 0){
$lastMemUsageCount=Get-ChildProcessMemoryUsage $waitProc.ID
Write-Debug "Memory read: $lastMemUsageCount"
Write-Debug "Memory count: $($memUsageStack.Count)"
$memUsageStack.Push($lastMemUsageCount)
if($lastMemUsageCount -eq 0 -or (($memUsageStack.ToArray() | ? { $_ -ne $lastMemUsageCount }) -ne $null)){
$memUsageStack.Clear()
}
if($memUsageStack.Count -gt $idleTimeout){
Write-BoxstarterMessage "Task has exceeded its timeout with no activity. Killing task..."
KillTree $waitProc.ID
throw "TASK:`r`n$command`r`n`r`nIs likely in a hung state."
}
}
Start-Sleep -Second 1
}
function Wait-ForTask($waitProc, $idleTimeout, $totalTimeout){
$reader=New-Object -TypeName System.IO.FileStream -ArgumentList @(
"$env:temp\BoxstarterOutput.Stream",
[system.io.filemode]::Open,[System.io.FileAccess]::ReadWrite,
[System.IO.FileShare]::ReadWrite)
try{
$procStartTime = $waitProc.StartTime
while($waitProc -ne $null -and !($waitProc.HasExited)) {
$timeTaken = [DateTime]::Now.Subtract($procStartTime)
if($totalTimeout -gt 0 -and $timeTaken.TotalSeconds -gt $totalTimeout){
Write-BoxstarterMessage "Task has exceeded its total timeout. Killing task..."
KillTree $waitProc.ID
throw "TASK:`r`n$command`r`n`r`nIs likely in a hung state."
}
$byte = New-Object Byte[] 100
$count=$reader.Read($byte,0,100)
if($count -ne 0){
$text = [System.Text.Encoding]::Default.GetString($byte,0,$count)
$text | Out-File $boxstarter.Log -append
$text | write-host -NoNewline
}
else {
Test-TaskTimeout $waitProc $idleTimeout
}
}
Start-Sleep -Second 1
Write-Debug "Proc has exited: $($waitProc.HasExited) or Is Null: $($waitProc -eq $null)"
$byte=$reader.ReadByte()
$text=$null
while($byte -ne -1){
$text += [System.Text.Encoding]::Default.GetString($byte)
$byte=$reader.ReadByte()
}
if($text -ne $null){
$text | out-file $boxstarter.Log -append
$text | write-host -NoNewline
}
}
finally{
$reader.Dispose()
if($waitProc -ne $null -and !$waitProc.HasExited){
KillTree $waitProc.ID
}
}
}
function KillTree($id){
Get-WmiObject -Class Win32_Process -Filter "ParentProcessID=$ID" | % {
if($_.ProcessID -ne $null) {
kill $_.ProcessID -ErrorAction SilentlyContinue -Force
Write-Debug "Killing $($_.Name)"
KillTree $_.ProcessID
}
}
Kill $id -ErrorAction SilentlyContinue -Force
}
tools\Boxstarter.Common\Invoke-RetriableScript.ps1
function Invoke-RetriableScript{
<#
.SYNOPSIS
Retries a script 5 times or until it completes without terminating errors.
All Unnamed arguments will be passed as arguments to the script
#>
param([ScriptBlock]$RetryScript)
$currentErrorAction=$ErrorActionPreference
try{
$ErrorActionPreference = "Stop"
for($count = 1; $count -le 5; $count++) {
try {
Write-BoxstarterMessage "Attempt #$count..." -Verbose
$ret = Invoke-Command -ScriptBlock $RetryScript -ArgumentList $args
return $ret
break
}
catch {
if($global:Error.Count -gt 0){$global:Error.RemoveAt(0)}
if($count -eq 5) { throw $_ }
else { Sleep 10 }
}
}
}
finally{
$ErrorActionPreference = $currentErrorAction
}
}
tools\Boxstarter.Common\Log-BoxStarterMessage.ps1
tools\Boxstarter.Common\Out-BoxstarterLog.ps1
function Enter-BoxstarterLogable{
<#
.SYNOPSIS
Logs the output and error streams of the script to the
console and Boxstarter log.
.DESCRIPTION
Boxstarter runs the provided script and redirects the
standard output and standard error streams to the host
console and to the Boxstarter log. This will include both
PowerShell write-output and errors as well as the output
from any standard command line executables that use
standard output and error streams.
.PARAMETER script
The script to execute.
.EXAMPLE
Enter-BoxstarterLogable{
Get-Process Chrome
Netstat
}
This sends both the out put of the PowerShell Get-Process
cmdlet and the Netstat command line utility to the screen
as well as th boxstarter log.
.LINK
http://boxstarter.codeplex.com
about_boxstarter_logging
#>
param([ScriptBlock] $script)
& ($script) 2>&1 | Out-BoxstarterLog
}
function Out-BoxstarterLog {
<#
.SYNOPSIS
Logs provided text or objects to the console and
Boxstarter log.
.DESCRIPTION
This is essentially identical to Tee-Object with the PS 3.0
only parameter -Append. This will work in either PS 2.0 or
PS 3.0.
.PARAMETER object
Object to log.
.EXAMPLE
Out-BoxstarterLog "This can be seen on the screen and in the log file"
.EXAMPLE
"This can be seen on the screen and in the log file" | Out-BoxstarterLog
.LINK
http://boxstarter.codeplex.com
about_boxstarter_logging
#>
param(
[Parameter(position=0,ValueFromPipeline=$True)]
[object]$object,
[switch]$Quiet
)
process {
if(!$Quiet -and !$Boxstarter.SuppressLogging){write-host $object}
if($Boxstarter -and $BoxStarter.Log -and $object){
$object >> $Boxstarter.Log
}
}
}
tools\Boxstarter.Common\Remove-BoxstarterTask.ps1
function Remove-BoxstarterTask {
<#
.SYNOPSIS
Deletes the Boxstarter task.
.DESCRIPTION
Deletes the Boxstarter task. Boxstarter calls this when an
installation session completes.
.LINK
http://boxstarter.codeplex.com
Create-BoxstarterTask
Invoke-BoxstarterTask
#>
Write-BoxstarterMessage "Removing Boxstarter Scheduled Task..." -Verbose
$result = schtasks /DELETE /TN 'Boxstarter Task' /F 2>&1
Write-BoxstarterMessage "Removed Boxstarter Scheduled Task with this result: $result" -Verbose
}
tools\Boxstarter.Common\Start-TimedSection.ps1
function Start-TimedSection {
<#
.SYNOPSIS
Begins a timed section
.DESCRIPTION
A timed section is a portion of script that is timed. Used
with Stop-TimedSection, the beginning and end of the section
are logged to both the console and the log along with the
amount of time elapsed.
The function returns a guid that is used to identify the
section when stopping it.
.PARAMETER SectionName
The Title or Label of the section being timed. This string
is used in the logging to identify the section.
.PARAMETER Verbose
Instructs Start-TimedSection to write to the Verbose stream. Although
this will always log messages to the Boxstarter log, it will only log
to the console if the session's VerbosePreference is set to capture
the Verbose stream or the -Verbose switch was set when calling
Install-BoxstarterPackage.
.EXAMPLE
$session=Start-TimedSection "My First Section"
Stop-TimedSection $session
This creates a block as follows:
+ Boxstarter starting My First Section
Some stuff happens here.
+ Boxstarter finished My First Section 00:00:00.2074282
.EXAMPLE
Timed Sections can be nested or staggered. You can have
multiple sections running at once.
$session=Start-TimedSection "My First Section"
$innerSession=Start-TimedSection "My Inner Section"
Stop-TimedSection $innerSession
Stop-TimedSection $session
This creates a block as follows:
+ Boxstarter starting My First Section
Some stuff happens here.
++ Boxstarter starting My Inner Section
Some inner stuff happens here.
++ Boxstarter finished My Inner Section 00:00:00.1074282
Some more stuff happens here.
+ Boxstarter finished My First Section 00:00:00.2074282
Note that the number of '+' chars indicate nesting level.
.EXAMPLE
$session=Start-TimedSection "My First Section" -Verbose
Stop-TimedSection $session
This will write the start and finish messages to the
Boxstarter log but will not write to the console unless the
user has the the VerbosePreference variable or used the
Verbose switch of Install-BoxstarterPackage.
.NOTES
If the SuppressLogging setting of the $Boxstarter variable is true,
logging messages will be suppressed and not sent to the console or the
log.
.LINK
http://boxstarter.codeplex.com
Stop-TimedSection
about_boxstarter_logging
#>
param(
[string]$sectionName,
[switch]$Verbose)
$stopwatch = [System.Diagnostics.Stopwatch]::StartNew()
$guid = [guid]::NewGuid().ToString()
$timerEntry=@{title=$sectionName;stopwatch=$stopwatch;verbose=$Verbose}
if(!$script:boxstarterTimers) {$script:boxstarterTimers=@{}}
$boxstarterTimers.$guid=$timerEntry
$padCars="".PadLeft($boxstarterTimers.Count,"+")
Write-BoxstarterMessage "$padCars Boxstarter starting $sectionName" -NoLogo -Verbose:$Verbose
return $guid
}
tools\Boxstarter.Common\Stop-TimedSection.ps1
function Stop-TimedSection {
<#
.SYNOPSIS
Ends a timed section
.DESCRIPTION
A timed section is a portion of script that is timed. Used
with Start-TimedSection, the beginning and end of the section
are logged to both the console and the log along with the
amount of time elapsed.
.PARAMETER SectionId
The guid that was generated by Start-TimedSection and
identifies which section is ending.
.EXAMPLE
$session=Start-TimedSection "My First Section"
Stop-TimedSection $session
This creates a block as follows:
+ Boxstarter starting My First Section
Some stuff happens here.
+ Boxstarter finished My First Section 00:00:00.2074282
.EXAMPLE
Timed Sections can be nested or staggered. You can have
multiple sections running at once.
$session=Start-TimedSection "My First Section"
$innerSession=Start-TimedSection "My Inner Section"
Stop-TimedSection $innerSession
Stop-TimedSection $session
This creates a block as follows:
+ Boxstarter starting My First Section
Some stuff happens here.
++ Boxstarter starting My Inner Section
Some inner stuff happens here.
++ Boxstarter finished My Inner Section 00:00:00.1074282
Some more stuff happens here.
+ Boxstarter finished My First Section 00:00:00.2074282
Note that the number of '+' chars indicate nesting level.
.LINK
http://boxstarter.codeplex.com
Start-TimedSection
about_boxstarter_logging
#>
param([string]$SectionId)
$timerEntry=$script:boxstarterTimers.$SectionId
if(!$timerEntry){return}
$padCars="".PadLeft($boxstarterTimers.Count,"+")
$script:boxstarterTimers.Remove($SectionId)
$stopwatch = $timerEntry.stopwatch
Write-BoxstarterMessage "$padCars Boxstarter finished $($timerEntry.Title) $($stopwatch.Elapsed.ToString())" -NoLogo -Verbose:$timerEntry.Verbose
$stopwatch.Stop()
}
tools\Boxstarter.Common\Test-Admin.ps1
function Test-Admin {
<#
.SYNOPSIS
Determines if the console is elevated
#>
$identity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$principal = New-Object System.Security.Principal.WindowsPrincipal( $identity )
return $principal.IsInRole( [System.Security.Principal.WindowsBuiltInRole]::Administrator )
}
tools\Boxstarter.Common\Write-BoxstarterLogo.ps1
function Write-BoxstarterLogo {
$boxMod=(IEX (Get-Content (join-path $Boxstarter.Basedir Boxstarter.Common\Boxstarter.Common.psd1) | Out-String))
write-BoxstarterMessage "Boxstarter Version $($boxMod.ModuleVersion)" -nologo -Color White
write-BoxstarterMessage "$($boxMod.Copyright) http://boxstarter.org`r`n" -nologo -Color White
}
tools\Boxstarter.Common\Write-BoxstarterMessage.ps1
tools\chocolateyinstall.ps1
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) {
$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") {
$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'`""
$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
}
}
Virus Scan Results
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 History
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| Boxstarter Common Module 3.0.3 | 105819 | Monday, October 9, 2023 | Approved | |
| Boxstarter Common Module 3.0.2 | 36387 | Monday, June 12, 2023 | Approved | |
| Boxstarter Common Module 3.0.1 | 4289 | Tuesday, June 6, 2023 | Approved | |
| Boxstarter Common Module 3.0.0 | 93251 | Thursday, July 14, 2022 | Approved | |
| Boxstarter Common Module 3.0.0-beta-20220427-21 | 149 | Wednesday, April 27, 2022 | Approved | |
| Boxstarter Common Module 2.13.0 | 157468 | Thursday, October 15, 2020 | Approved | |
| Boxstarter Common Module 2.12.0 | 396932 | Tuesday, October 30, 2018 | Approved | |
| Boxstarter Common Module 2.11.0 | 66762 | Wednesday, May 16, 2018 | Approved | |
| Boxstarter Common Module 2.10.3 | 55206 | Thursday, July 27, 2017 | Approved | |
| Boxstarter Common Module 2.9.27 | 2771 | Wednesday, June 21, 2017 | Approved | |
| Boxstarter Common Module 2.9.26 | 5656 | Monday, June 19, 2017 | Approved | |
| Boxstarter Common Module 2.9.24 | 889 | Sunday, June 18, 2017 | Approved | |
| Boxstarter Common Module 2.9.14 | 7067 | Friday, May 5, 2017 | Approved | |
| Boxstarter Common Module 2.8.29 | 32068 | Sunday, May 22, 2016 | Approved | |
| Boxstarter Common Module 2.8.27 | 561 | Sunday, May 22, 2016 | Approved | |
| Boxstarter Common Module 2.8.21 | 1096 | Thursday, April 28, 2016 | Approved | |
| Boxstarter Common Module 2.8.18 | 800 | Tuesday, April 26, 2016 | Approved | |
| Boxstarter Common Module 2.8.12 | 1178 | Thursday, April 21, 2016 | Approved | |
| Boxstarter Common Module 2.8.0 | 1237 | Friday, April 15, 2016 | Approved | |
| Boxstarter Common Module 2.7.0 | 2125 | Sunday, April 3, 2016 | Approved | |
| Boxstarter Common Module 2.6.41 | 3909 | Sunday, February 28, 2016 | Approved | |
| Boxstarter Common Module 2.6.25 | 6755 | Friday, December 18, 2015 | Approved | |
| Boxstarter Common Module 2.6.20 | 611 | Thursday, December 17, 2015 | Approved | |
| Boxstarter Common Module 2.6.16 | 778 | Tuesday, December 15, 2015 | Approved | |
| Boxstarter Common Module 2.6.2 | 787 | Monday, December 14, 2015 | Approved | |
| Boxstarter Common Module 2.6.0 | 515 | Sunday, December 13, 2015 | Approved | |
| Boxstarter Common Module 2.5.21 | 9612 | Thursday, August 13, 2015 | Approved | |
| Boxstarter Common Module 2.5.19 | 2022 | Sunday, July 26, 2015 | Approved | |
| Boxstarter Common Module 2.5.10 | 1842 | Friday, July 10, 2015 | Approved | |
| Boxstarter Common Module 2.5.3 | 1424 | Wednesday, July 1, 2015 | Approved | |
| Boxstarter Common Module 2.5.1 | 610 | Wednesday, July 1, 2015 | Approved | |
| Boxstarter Common Module 2.4.209 | 4693 | Sunday, April 26, 2015 | Approved | |
| Boxstarter Common Module 2.4.205 | 2832 | Sunday, April 5, 2015 | Approved | |
| Boxstarter Common Module 2.4.196 | 1542 | Friday, March 20, 2015 | Approved | |
| Boxstarter Common Module 2.4.188 | 1400 | Monday, March 9, 2015 | Approved | |
| Boxstarter Common Module 2.4.183 | 907 | Wednesday, March 4, 2015 | Approved | |
| Boxstarter Common Module 2.4.180 | 604 | Tuesday, March 3, 2015 | Approved | |
| Boxstarter Common Module 2.4.179 | 519 | Tuesday, March 3, 2015 | Approved | |
| Boxstarter Common Module 2.4.159 | 2862 | Sunday, January 18, 2015 | Approved | |
| Boxstarter Common Module 2.4.157 | 817 | Thursday, January 15, 2015 | Approved | |
| Boxstarter Common Module 2.4.152 | 895 | Monday, January 12, 2015 | Approved | |
| Boxstarter Common Module 2.4.149 | 1393 | Friday, December 26, 2014 | Approved | |
| Boxstarter Common Module 2.4.146 | 557 | Friday, December 26, 2014 | Approved | |
| Boxstarter Common Module 2.4.128 | 2034 | Thursday, November 27, 2014 | Approved | |
| Boxstarter Common Module 2.4.123 | 3908 | Wednesday, September 24, 2014 | Approved | |
| Boxstarter Common Module 2.4.110 | 920 | Wednesday, September 17, 2014 | Approved | |
| Boxstarter Common Module 2.4.93 | 825 | Friday, September 12, 2014 | Approved | |
| Boxstarter Common Module 2.4.88 | 1131 | Wednesday, September 3, 2014 | Approved | |
| Boxstarter Common Module 2.4.87 | 546 | Wednesday, September 3, 2014 | Approved | |
| Boxstarter Common Module 2.4.80 | 2890 | Monday, August 4, 2014 | Approved | |
| Boxstarter Common Module 2.4.76 | 620 | Sunday, August 3, 2014 | Approved | |
| Boxstarter Common Module 2.4.70 | 783 | Thursday, July 31, 2014 | Approved | |
| Boxstarter Common Module 2.4.67 | 782 | Wednesday, July 30, 2014 | Approved | |
| Boxstarter Common Module 2.4.61 | 715 | Monday, July 28, 2014 | Approved | |
| Boxstarter Common Module 2.4.57 | 519 | Sunday, July 27, 2014 | Approved | |
| Boxstarter Common Module 2.4.54 | 739 | Wednesday, July 23, 2014 | Approved | |
| Boxstarter Common Module 2.4.53 | 493 | Wednesday, July 23, 2014 | Approved | |
| Boxstarter Common Module 2.4.51 | 530 | Wednesday, July 23, 2014 | Approved | |
| Boxstarter Common Module 2.4.48 | 600 | Tuesday, July 22, 2014 | Approved | |
| Boxstarter Common Module 2.4.46 | 692 | Saturday, July 19, 2014 | Approved | |
| Boxstarter Common Module 2.4.41 | 736 | Sunday, July 13, 2014 | Approved | |
| Boxstarter Common Module 2.4.39 | 532 | Sunday, July 13, 2014 | Approved | |
| Boxstarter Common Module 2.4.38 | 460 | Saturday, July 12, 2014 | Approved | |
| Boxstarter Common Module 2.4.35 | 506 | Saturday, July 12, 2014 | Approved | |
| Boxstarter Common Module 2.4.32 | 547 | Friday, July 11, 2014 | Approved | |
| Boxstarter Common Module 2.4.29 | 1311 | Friday, July 4, 2014 | Approved | |
| Boxstarter Common Module 2.4.26 | 1082 | Monday, June 23, 2014 | Approved | |
| Boxstarter Common Module 2.4.15 | 3181 | Sunday, April 20, 2014 | Approved | |
| Boxstarter Common Module 2.4.12 | 542 | Saturday, April 19, 2014 | Approved | |
| Boxstarter Common Module 2.4.4 | 905 | Saturday, April 5, 2014 | Approved | |
| Boxstarter Common Module 2.4.0 | 539 | Friday, April 4, 2014 | Approved | |
| Boxstarter Common Module 2.3.24 | 2023 | Saturday, February 1, 2014 | Approved | |
| Boxstarter Common Module 2.3.15 | 644 | Monday, January 27, 2014 | Approved | |
| Boxstarter Common Module 2.3.13 | 547 | Saturday, January 25, 2014 | Approved | |
| Boxstarter Common Module 2.3.8 | 613 | Thursday, January 23, 2014 | Approved | |
| Boxstarter Common Module 2.3.0 | 594 | Monday, January 20, 2014 | Approved | |
| Boxstarter Common Module 2.2.78 | 791 | Thursday, January 9, 2014 | Approved | |
| Boxstarter Common Module 2.2.59 | 874 | Sunday, December 29, 2013 | Approved | |
| Boxstarter Common Module 2.2.23 | 951 | Saturday, December 14, 2013 | Approved | |
| Boxstarter Common Module 2.2.16 | 554 | Friday, December 13, 2013 | Approved | |
| Boxstarter Common Module 2.2.15 | 581 | Friday, December 13, 2013 | Approved | |
| Boxstarter Common Module 2.2.12 | 549 | Friday, December 13, 2013 | Approved | |
| BoxStarter Common Module 2.2.0 | 540 | Thursday, December 12, 2013 | Approved | |
| BoxStarter Common Module 2.1.0 | 649 | Saturday, November 30, 2013 | Approved | |
| BoxStarter Common Module 2.0.25 | 597 | Wednesday, November 20, 2013 | Approved | |
| BoxStarter Common Module 2.0.11 | 606 | Monday, November 11, 2013 | Approved | |
| BoxStarter Common Module 2.0.4 | 534 | Saturday, November 9, 2013 | Approved | |
| BoxStarter Common Module 2.0.1 | 519 | Friday, November 8, 2013 | Approved | |
| BoxStarter Common Module 1.1.40 | 682 | Tuesday, October 1, 2013 | Approved | |
| BoxStarter Common Module 1.1.35 | 683 | Monday, August 12, 2013 | Approved | |
| BoxStarter Common Module 1.1.30 | 535 | Sunday, August 11, 2013 | Approved | |
| BoxStarter Common Module 1.1.22 | 554 | Thursday, August 8, 2013 | Approved | |
| BoxStarter Common Module 1.1.18 | 537 | Tuesday, August 6, 2013 | Approved | |
| BoxStarter Common Module 1.1.12 | 577 | Sunday, August 4, 2013 | Approved | |
| BoxStarter Common Module 1.1.0 | 540 | Thursday, August 1, 2013 | Approved | |
| BoxStarter Common Module 1.0.33 | 633 | Thursday, April 18, 2013 | Approved | |
| BoxStarter Common Module 1.0.20 | 578 | Monday, April 15, 2013 | Approved | |
| BoxStarter Common Module 1.0.13 | 599 | Monday, March 25, 2013 | Approved | |
| BoxStarter Common Module 1.0.3 | 601 | Wednesday, March 13, 2013 | Approved |
Release Notes
- Fix for all write-host calls being logged to Boxstarter log file even when there is no install session in progress
- fixing issue where auto login is not disabled after boxstarter run
- fixing wait for published version to retry for a minute if the new version is not yet marked published
- Improve initial connectin performance by skipping remoting check if it has already been tested in enable-BoxstarterVM
- provide messaging for some winconfig functions
- fix the setting of azure storage account by looking for https endpoints
- load storage module before azure to workaround bug with the storage module loading
- 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
Dependencies
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.