BoxStarter Wiki Rss Feed

Updated Wiki: About Boxstarter.Chocolatey

gep13 — Thu, 16 May 2013 10:31:32 GMT

TOPIC
AboutBoxstarterChocolatey

SYNOPSIS
Describes how to use Boxstarter's Chocolatey module to setup a new
environment with your favorite Chocolatey packages.

DESCRIPTION
Boxstarter's Chocolatey module compliments the Boxstarter Bootstrap
module by augmenting its unattended script execution environment
with Chocolatey goodness making it easy to setup a new box with
Chocolatey packages.

Installing Chocolatey
Boxstarter will check to ensure if Chocolatey is installed. If
Chocolatey is not installed it will install it before running any
Chocolatey commands. Boxstarter will also check to see if the .Net
4.0 Framework is installed before installing Chocolatey since the
.Net 4 runtime is a prerequisite.

Chocolatey Boxstarter Packages
When calling Invoke-ChocolateyBoxstarter or just Boxstarter, a
BootstrapperPackage name must be passed to the command. This is a
special Chocolatey package provided by the user that boxstarter asks
Chocolatey to install and it contains the script that is intended to
install all the applications and settings the user wants setup on the
local machine.

This package script has access to all of the Chocolatey helper
functions as well as all Boxstarter logging, WinConfig and
Bootstrapper commands. See AboutBoxstarterBootstrapper and
AboutBoxstarterLogging for information regarding those comands.

Creating Packages
Boxstarter provides some functions to make creation and deployment of
packages easy. Use New-BoxstarterPackage to either create a skeleton
package with a minimal nuspec and ChocolateyInstall.ps1 or to import an
existing package into boxstarter. This will put the package source files
in $($Boxstarter.LocalRepo)\<package name>. To pack these source files
use Invoke-BoxstarterBuild <package name>. You may also pack all package
in your repo with Invoke-BoxstarterBuild -all. If you would like to make
your local repo a network share, use Set-BoxstarterShare.

Consuming Boxstarter Packages
The primary gateway to kicking off a Boxstarter.Chocolatey installation
session is Invoke-ChocolateyBoxstarter. While you may use this
powershell function, you can also call Boxstarter.bat which takes the
exact same parameters as Invoke-CocolateyBoxstarter. If you installed
Boxstarter.Chocolatey via Chocolatey or the setup.bat installer,
boxstarter.bat is placed in your path. Boxstarter.bat will import the
Boxstarter.Chocolatey module and create a powershell session bypassing
ExecutionPolicy. Boxstarter.bat is ideal for calling Boxstarter
remotely. Simply share the Boxstarter base directory and you can access
it via \\serverName\Boxstarter\Boxstarter.bat.

Package Sources
Invoke-ChocolateyBoxstarter (or Boxstarter) expects just the name of the
bootstrapping package - just like CINST or Nuget. Boxstarter will search
the following locations in this order:

- $Boxstarter.LocalRepo: This is the local repository that by default is
in the BuildPackages directory in the Boxstarter Base Boxstarter Module
directory ($Boxstarter.BaseDir). You can change the default by adding a
LocalRepo setting to $($Boxstarter.BaseDir)\Boxstarter.Config.

- Chocolatey.org: The public chocolatey feed at http://chocolatey.org/api/v2

- Myget: The Boxstarter Community Feed at http://www.myget.org/F/boxstarter/api/v2

The last two remote sources can be configured by editing
$($Boxstarter.BaseDir)\Boxstarter.Config.

Reboot Detection
Perhaps the most compelling feature of Boxstarter is its way to handle
reboots during an involved environment setup package. Especially when
you are running patches, installing services and downloading complex
applications. Boxstarter intercepts all calls to Chocolatey install
commands and checks for pending reboots prior to calling Chocolatey. If
a pending reboot exists, Boxstarter reboots the machine and automatically
logs on with the credentials you provided providing an unattended
installation session. After the Chocolatey package completes, if the
package fails and returns the common MSI reboot needed exit code of
3010, Boxstarter will reboot which will likely cause the package to
succeed on the next run. See aboutboxstarterbootstrapper for more
details about the rebooting logic and how you can disable or manually
invoke them.

Package Authoring Considerations
Boxstarter can run any Chocolatey package and any valid powershell
inside that package. However, there are a few things to consider
that may make a Boxstarter Chocolatey package a better installation
experience.

- Boxstarter Chocolatey packages should be repeatable. This is
especially true if you anticipate the need to reboot. When Boxstarter
reboots, it starts running the package from the beginning. So ensure
that there is nothing that would cause the package to break if run
twice.

- If you have several Chocolatey packages that you want to install
during the Boxstarter session, it is preferable to call CINST
directly from inside your ChocolateyInstall instead of declaring
them as dependencies. This is because Boxstarter cannot intercept
Chocolatey dependencies so those packages will not have any reboot
protections.

SEE ALSO

Invoke-ChocolateyBoxstarter
about boxstarter logging
Invoke-Boxstarter
Invoke-Reboot
New-BoxstarterPackage
Invoke-BoxstarterBuild
Set-BoxstarterShare
about the $boxstarter variable in bootstrapper
about boxstarter logging
about the $boxstarter variable in chocolatey

Updated Wiki: Invoke-ChocolateyBoxstarter

gep13 — Thu, 16 May 2013 10:24:17 GMT

Invoke-ChocolateyBoxstarter

SYNOPSIS

Invokes the installation of a Boxstarter package

SYNTAX

Invoke-ChocolateyBoxstarter [-bootstrapPackage <String>] [-localRepo
<String>] -DisableReboots <CommonParameters>

DESCRIPTION

This essentially wraps Chocolatey Install and provides these additional features

Installs chocolatey if it is not already installed
Installs the .net 4.0 framework if it is not installed which is a chocolatey requirement
Turns off the windows update service during installation to prevent installation conflicts and minimize the need for reboots
Imports the Boxstarter.WinConfig module that provides functions for customizing windows
Provides Reboot Resiliency by ensuring the package installation is immediately restarted up on reboot if there is a reboot during the installation.
Ensures everything runs under admin

The .nupkg file for the provided package name is searched in the following locations and order:

.\BuildPackages relative to the parent directory of the module file
The chocolatey feed
The boxstarter feed on myget

This can be configured by editing $($Boxstarter.BaseDir)\Boxstarter.Config

PARAMETER

BootstrapPackage

The package to be installed.
The .nupkg file for the provided package name is searched in the following locations and order:

.\BuildPackages relative to the parent directory of the module file
The chocolatey feed
The boxstarter feed on myget

Localrepo

This is the path to the local boxstarter repository where boxstarter
should look for .nupkg files to install. By default this is located
in the BuildPackages directory just under the root Boxstarter
directory.

DisableReboots

If set, reboots are suppressed.

EXAMPLE

Invoke-ChocolateyBoxstarter example

This invokes boxstarter and installs the example .nupkg. In pending
reboots are detected, boxstarter will restart the machine. Boxstarter
will prompt the user to enter a password which will be used for
automatic logins in the event a restart is required.

EXAMPLE

Invoke-ChocolateyBoxstarter win8Install -LocalRepo \\server\share\boxstarter

This installs the Win8Install .nupkg and specifies that it is ok to
reboot the macine if a pending reboot is needed. Boxstarter will look
for the Win8Install .nupkg file in the \\serer\share\boxstarter
directory.

LINK

about boxstarter.chocolatey
About the $Boxstarter Variable

Updated Wiki: Set-BoxstarterShare

gep13 — Thu, 16 May 2013 10:23:53 GMT

Set-BoxstarterShare

SYNOPSIS

Shares the Boxstarter root directory - $Boxstarter.BaseDir

SYNTAX

Set-BoxstarterShare [-shareName <String>] [-accounts <String[]>]
<CommonParameters>

DESCRIPTION

Shares the Boxstarter root directory - $Boxstarter.BaseDir - so that
it can be accessed remotely. This allows remote machines to Invoke
ChocolateyBoxstarter via \\server\shareName\Boxstarter.bat. Unless
specified otherwise, the share name is Boxstarter and Everyone is
given Read permisions.

PARAMETER

ShareName

The name to give to the share. This is the name by which other
machines can access it. Boxstarter is he default.

Accounts

A ist of accounts to be given read access to the share. Everyone is
the default.

EXAMPLE

Set-BoxstarterShare

Shares the Boxstarter root as Boxstarter to everyone.

EXAMPLE

Set-BoxstarterShare BuildRepo

Shares the Boxstrarter Root as BuildRepo to everyone.

EXAMPLE

Set-BoxstarterShare -Accounts "corp\mwrock","corp\gmichaels"

Shares the Boxstarter root as Boxstarter to mwrock and gmichaels in the corp domain.

LINK

about boxstarter.chocolatey
Invoke-ChocolateyBoxstarter
New-BoxstarterPackage
Invoke-BoxstarterBuild

Updated Wiki: Home

mwrock — Sun, 12 May 2013 04:57:53 GMT

BoxStarter

Creates a fresh .Net developer environment from a bare OS utilizing powershell and chocolatey.

Windows development environment creation made easy!

100% Unattended Install with pending reboot detection and automatic logon.
Lots of Windows configuration utilities including installing critical updates, changing windows explorer options, and more.
Easily installs to a Thumb drive or Set-BoxstarterShare to share it on your network.

Build your Uber Geek Environment

#After extracting Boxstarter.1.0.0.zip on MYCOMPUTER
.\setup.bat
Import-Module $env:appdata\boxstarter\Boxstarter.Chocolatey\Boxstarter.Chocolatey.psd1
#Create minimal nuspec and chocolateyInstall
New-BoxstarterPackage MyPackage
#Edit Install script to customize your environment
Notepad (Join-Path $Boxstarter.LocalRepo "MyPackage\tools\ChocolateyInstall.ps1")
#Pack nupkg
Invoke-BoxstarterBuild MyPackage

#share Repo
Set-BoxstarterShare
#Or Copy to thumb drive G
Copy-Item $Boxstarter.BaseDir G:\ -Recurse

#on new bare os
\\MYCOMPUTER\Boxstarter\Boxstarter Mypackage
 
#Enter password when prompted and come back later to new box

Here is an example developer chocolateyInstall.ps1:

Install-WindowsUpdate -AcceptEula
Update-ExecutionPolicy Unrestricted
Move-LibraryDirectory "Personal" "$env:UserProfile\skydrive\documents"
Set-ExplorerOptions -showHidenFilesFoldersDrives -showProtectedOSFiles -showFileExtensions
Set-TaskbarSmall
Enable-RemoteDesktop

cinstm VisualStudio2012Ultimate
if((Get-Item "$($Boxstarter.programFiles86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe").VersionInfo.ProductVersion -lt "11.0.60115.1") {
    if(Test-PendingReboot){Invoke-Reboot}
    Install-ChocolateyPackage 'vs update 2 ctp2' 'exe' '/passive /norestart' 'http://download.microsoft.com/download/8/9/3/89372D24-6707-4587-A7F0-10A29EECA317/vsupdate_KB2707250.exe'
}
cinstm fiddler
cinstm mssqlserver2012express
cinstm git-credential-winstore
cinstm console-devel
cinstm sublimetext2
cinstm skydrive
cinstm poshgit
cinstm dotpeek
cinstm googlechrome
cinstm Paint.net
cinstm windirstat
cinstm sysinternals
cinstm NugetPackageExplorer
cinstm resharper
cinstm windbg

cinst Microsoft-Hyper-V-All -source windowsFeatures
cinst IIS-WebServerRole -source windowsfeatures
cinst IIS-HttpCompressionDynamic -source windowsfeatures
cinst IIS-ManagementScriptingTools -source windowsfeatures
cinst IIS-WindowsAuthentication -source windowsfeatures
cinst TelnetClient -source windowsFeatures

$sublimeDir = "$env:programfiles\Sublime Text 2"

Install-ChocolateyPinnedTaskBarItem "$env:windir\system32\mstsc.exe"
Install-ChocolateyPinnedTaskBarItem "$env:programfiles\console\console.exe"
Install-ChocolateyPinnedTaskBarItem "$sublimeDir\sublime_text.exe"
Install-ChocolateyPinnedTaskBarItem "$($Boxstarter.programFiles86)\Google\Chrome\Application\chrome.exe"
Install-ChocolateyPinnedTaskBarItem "$($Boxstarter.programFiles86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe"

Install-ChocolateyFileAssociation ".txt" "$env:programfiles\Sublime Text 2\sublime_text.exe"
Install-ChocolateyFileAssociation ".dll" "$($Boxstarter.ChocolateyBin)\dotPeek.bat"

if(!(Test-Path("$sublimeDir\data")){mkdir "$sublimeDir\data"}
copy-item (Join-Path (Get-PackageRoot($MyInvocation)) 'sublime\*') -Force -Recurse "$sublimeDir\data"
move-item "$sublimeDir\data\Pristine Packages\*" -Force "$sublimeDir\Pristine Packages"
copy-item (Join-Path (Get-PackageRoot($MyInvocation)) 'console.xml') -Force $env:appdata\console\console.xml

Install-ChocolateyVsixPackage xunit http://visualstudiogallery.msdn.microsoft.com/463c5987-f82b-46c8-a97e-b1cde42b9099/file/66837/1/xunit.runner.visualstudio.vsix
Install-ChocolateyVsixPackage autowrocktestable http://visualstudiogallery.msdn.microsoft.com/ea3a37c9-1c76-4628-803e-b10a109e7943/file/73131/1/AutoWrockTestable.vsix
Install-ChocolateyVsixPackage vscommands http://visualstudiogallery.msdn.microsoft.com/a83505c6-77b3-44a6-b53b-73d77cba84c8/file/74740/18/SquaredInfinity.VSCommands.VS11.vsix

Leveraging Chocolatey Goodness

The BoxStarter code base has undergone a major reorganization over the past few months in collaboration with Rob Reynolds' awesome Windows Package manager: Chocolatey. Much of BoxStarter's functionality has been improved and ported over directly into the Chocolatey repository as of release 0.9.8.20.

Functionality now in Chocolatey includes:

Creating task bar shortcuts, file associations and windows explorer context menu items.
Adding any "windows feature" available to the OS
Installing Visual Studio extensions

You can create and save BoxStarter packages for different types of installations to suit your distinct needs. The package format follows the Nuget specification so you can save them on your favorite public or private feed. By default, boxstarter searches the local "BuildPackages" folder in the Boxstarter repo, the Chocolatey Nuget Feed, and the MyGet Boxstarter feed.

Get More Information

See the Documentation

Import-Module Boxstarter.Chocolatey
Get-Help Boxstarter

Updated Wiki: Test-PendingReboot

mwrock — Thu, 28 Mar 2013 06:47:58 GMT

Test-PendingReboot

SYNOPSIS

Checks to see if Windows is pending a reboot

!!SYNTAX
Test-PendingReboot <CommonParameters>

DESCRIPTION

Uses a script from Brian Wilhite
http://gallery.technet.microsoft.com/scriptcenter/Get-PendingReboot-Query-bdb79542
that queries the registry, Windows Update and System C
onfiguration Manager to determine if a pending reboot is
required.

One may want to check this before installing software
or doing anything that may fail if there is a pending
reboot. If this command returns $true, one may want to
call Invoke-Reboot to restart the local machine.

LINK

http://gallery.technet.microsoft.com/scriptcenter/Get-PendingReboot-Query-bdb79542
Invoke-Reboot
about boxstarter bootstrapper

Updated Wiki: Documentation

mwrock — Thu, 14 Mar 2013 05:25:21 GMT

Boxstarter Commands

Boxstarter.Chocolatey

Boxstarter.Bootstrapper

Boxstarter.WinConfig

Boxstarter.Common

Updated Wiki: Write-BoxstarterMessage

mwrock — Thu, 14 Mar 2013 05:24:52 GMT

Write-BoxstarterMessage

SYNOPSIS

Writes a message to the console and the log

SYNTAX

Write-BoxstarterMessage [-message <String>] -nologo
<CommonParameters>

DESCRIPTION

Formats the message in green. This message is also logged to the
Boxstarter log file with a timestamp.

PARAMETER

Message

The string to be logged

NoLogo

If ommited, the message will be preceeded with "Boxstarter: "

EXAMPLE

code:powershell}
Write-BoxstarterMessage "I am logging a message."
[code:powershell}
This creates the following console output:
Boxstarter: I am Logging a Message

This will appear in the log:
[2013-02-11T00:59:44.9768457-08:00 Boxstarter: I am Logging a Message

NOTES

If the SuppressLogging setting of the $Boxstarter variable is true,
logging mesages will be suppresed and not sent to the console or the
log.

LINK

about boxstarter logging

Updated Wiki: Documentation

mwrock — Thu, 14 Mar 2013 05:22:15 GMT

Boxstarter Commands

Boxstarter.Chocolatey

Boxstarter.Bootstrapper

Boxstarter.WinConfig

Boxstarter.Common

Updated Wiki: Stop-TimedSection

mwrock — Thu, 14 Mar 2013 05:21:36 GMT

Stop-TimedSection

SYNOPSIS

Ends a timed section

SYNTAX

Stop-TimedSection [-SectionId <String>] <CommonParameters>

DESCRIPTION

A timed section is a portion of script that is timed. Used
with Start-TimedSection, the beginning and end of the section
are loged 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

Start-TimedSection
about boxstarter logging

Updated Wiki: Documentation

mwrock — Thu, 14 Mar 2013 05:17:38 GMT

Boxstarter Commands

Boxstarter.Chocolatey

Boxstarter.Bootstrapper

Boxstarter.WinConfig

Boxstarter.Common

Updated Wiki: Start-TimedSection

mwrock — Thu, 14 Mar 2013 05:17:02 GMT

Start-TimedSection

SYNOPSIS

Begins a timed section

SYNTAX

Start-TimedSection [-sectionName <String>] <CommonParameters>

DESCRIPTION

A timed section is a portion of script that is timed. Used
with Stop-TimedSection, the beginning and end of the section
are loged 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.

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

NOTES

If the SuppressLogging setting of the $Boxstarter variable is true,
logging mesages will be suppresed and not sent to the console or the
log.

LINK

Stop-TimedSection
about boxstarter logging

Updated Wiki: Documentation

mwrock — Thu, 14 Mar 2013 05:03:27 GMT

Boxstarter Commands

Boxstarter.Chocolatey

Boxstarter.Bootstrapper

Boxstarter.WinConfig

Boxstarter.Common

Updated Wiki: Out-BoxstarterLog

mwrock — Thu, 14 Mar 2013 05:02:54 GMT

Out-BoxstarterLog

SYNOPSIS

Logs provided text or objects to the console and
Boxstarter log.

SYNTAX

Out-BoxstarterLog -object <Object> <CommonParameters>

DESCRIPTION

This is essentially identical to Tee-Object wih 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

about boxstarter logging

Updated Wiki: Documentation

mwrock — Thu, 14 Mar 2013 04:57:20 GMT

Boxstarter Commands

Boxstarter.Chocolatey

Boxstarter.Bootstrapper

Boxstarter.WinConfig

Boxstarter.Common

Updated Wiki: Enter-BoxstarterLogable

mwrock — Thu, 14 Mar 2013 04:55:32 GMT

Enter-BoxstarterLogable

SYNOPSIS

Logs the output and error streams of the script to the
console and Boxstarter log.

SYNTAX

Enter-BoxstarterLogable [-script <scriptblock>]

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 commandline 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 powershemm Get-Process
cmdlet and the Netstat command line utility to the screen
as well as th boxstarter log.

LINK

about boxstarter logging

Updated Wiki: Enter-BoxstarterLogable

mwrock — Thu, 14 Mar 2013 04:54:31 GMT

Enter-BoxstarterLogable

SYNOPSIS

Logs the output and error streams of the script to the
console and Boxstarter log.

SYNTAX

Enter-BoxstarterLogable [-script <scriptblock>]

DESCRIPTION

PARAMETER

script

The script to execute.

EXAMPLE

code:powershell
Enter-BoxstarterLogable{
Get-Process Chrome
Netstat
}
code:powershell
This sends both the out put of the powershemm Get-Process
cmdlet and the Netstat command line utility to the screen
as well as th boxstarter log.

LINK

about boxstarter logging

Updated Wiki: Documentation

mwrock — Thu, 14 Mar 2013 04:51:44 GMT

Boxstarter Commands

Boxstarter.Chocolatey

Boxstarter.Bootstrapper

Boxstarter.WinConfig

Boxstarter.Common

Updated Wiki: Log-BoxStarterMessage

mwrock — Thu, 14 Mar 2013 04:51:07 GMT

Log-BoxStarterMessage

SYNOPSIS

Logs a message to the Boxstarter Log File

SYNTAX

Log-BoxStarterMessage [-message <Object[]>] <CommonParameters>

DESCRIPTION

Logs a message to the log. The message does not render on the
console. Boxstarter timestamps the log message so that the file
entry has the time the message was writen. The log is located at
$Boxstarter.Log.

Parameter

Message

The message to be logged.

LINK

about boxstarter logging

Updated Wiki: Documentation

mwrock — Thu, 14 Mar 2013 04:46:45 GMT

Boxstarter Commands

Boxstarter.Chocolatey

Boxstarter.Bootstrapper

Boxstarter.WinConfig

Boxstarter.Common

About Boxstarter Logging

Updated Wiki: About Boxstarter Logging

mwrock — Thu, 14 Mar 2013 04:46:13 GMT

TOPIC
AboutBoxstarterLogging

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
Write-BoxstarterMessage
Out-BoxtarterLog
Enter-BoxstarterLogable
Start-TimedSection
Stop-TimedSection