Downloads:

275

Downloads of v 1.0.0:

275

Last Update:

6/11/2019

Package Maintainer(s):

Software Author(s):

  • Maurice Kevenaar

Tags:

chocolatey unofficial extension iso mount isomount admin

Chocolatey ISO helpers extension

1.0.0 | Updated: 6/11/2019

Downloads:

275

Downloads of v 1.0.0:

275

Maintainer(s):

Software Author(s):

  • Maurice Kevenaar

Chocolatey ISO helpers extension 1.0.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Chocolatey ISO helpers extension, run the following command from the command line or from PowerShell:

>

To upgrade Chocolatey ISO helpers extension, run the following command from the command line or from PowerShell:

>

To uninstall Chocolatey ISO helpers extension, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade chocolatey-isomount.extension -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade chocolatey-isomount.extension -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure chocolatey-isomount.extension installed
  win_chocolatey:
    name: chocolatey-isomount.extension
    state: present
    version: 1.0.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'chocolatey-isomount.extension' do
  action    :install
  version  '1.0.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: chocolatey-isomount.extension,
    Version: 1.0.0,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller chocolatey-isomount.extension
{
   Name     = 'chocolatey-isomount.extension'
   Ensure   = 'Present'
   Version  = '1.0.0'
   Source   = 'STEP 3 URL'
}

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


package { 'chocolatey-isomount.extension':
  provider => 'chocolatey',
  ensure   => '1.0.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install chocolatey-isomount.extension version="1.0.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator Pauby on 6/12/2019.

Description

This package provides helper functions useful for deploying software from ISO files.
These functions may be used in Chocolatey install/uninstall scripts by declaring this package a dependency in your package's nuspec.

NOTE: This package requires PowerShell 3 or higher


extensions\chocolatey-isomount.psm1
# Export functions that start with capital letter, others are private
# Include file names that start with capital letters, ignore others
$ScriptRoot = Split-Path $MyInvocation.MyCommand.Definition

$pre = Get-ChildItem Function:\*
Get-ChildItem "$ScriptRoot\*.ps1" | Where-Object { $_.Name -cmatch '^[A-Z]+' } | ForEach-Object { . $_  }
$post = Get-ChildItem Function:\*
$funcs = Compare-Object $pre $post | Select-Object -Expand InputObject | Select-Object -Expand Name
$funcs | Where-Object { $_ -cmatch '^[A-Z]+'} | ForEach-Object { Export-ModuleMember -Function $_ }

#Export-ModuleMember -Alias *
extensions\Install-ChocolateyIsoInstallPackage.ps1
function Install-ChocolateyIsoInstallPackage {
<#
.SYNOPSIS
    **NOTE:** Administrative Access Required.

    Installs software into "Programs and Features" based on a remote ISO file download.
    Use Install-ChocolateyIsoPackage when the ISO needs to be downloaded first.

.DESCRIPTION
    This will mount an ISO file, and executes the specified native installer.
    Has error handling built in.
    If you need to download the ISO file first, use Install-ChocolateyIsoPackage instead.

.NOTES
    This command will assert UAC/Admin privileges on the machine.

    If you are embedding ISO files into a package, ensure that you have the
    rights to redistribute those files if you are sharing this package
    publicly (like on the community feed). Otherwise, please use
    Install-ChocolateyIsoPackage to download those resources from their
    official distribution points.

    This is a wrapper around several existing Chocolatey commandlets.

    Chocolatey is copyrighted by its rightful owners. See: https://chocolatey.org

.INPUTS
    None

.OUTPUTS
    None

.PARAMETER PackageName
    The name of the package - while this is an arbitrary value, it's
    recommended that it matches the package id.

.PARAMETER FileType
    This is the extension of the file. This can be 'exe', 'msi', or 'msu'.
    Licensed editions of Chocolatey use this to automatically determine
    silent arguments. If this is not provided, Chocolatey will
    automatically determine this using the downloaded file's extension.

.PARAMETER SilentArgs
    OPTIONAL - These are the parameters to pass to the native installer,
    including any arguments to make the installer silent/unattended.
    Licensed editions of Chocolatey will automatically determine the
    installer type and merge the arguments with what is provided here.

    Try any of the to get the silent (unattended) installer -
    `/s /S /q /Q /quiet /silent /SILENT /VERYSILENT`. With msi it is always
    `/quiet`. Please pass it in still but it will be overridden by
    Chocolatey to `/quiet`. If you don't pass anything it could invoke the
    installer with out any arguments. That means a nonsilent installer.

    Please include the `notSilent` tag in your Chocolatey package if you
    are not setting up a silent/unattended package. Please note that if you
    are submitting to the community repository, it is nearly a requirement
    for the package to be completely unattended.

    When you are using this with an MSI, it will set up the arguments as
    follows:
    `"C:\Full\Path\To\msiexec.exe" /i "$downloadedFileFullPath" $silentArgs`,
    where `$downloadedfileFullPath` is `$url` or `$url64`, depending on what
    has been decided to be used.

    When you use this with MSU, it is similar to MSI above in that it finds
    the right executable to run.

    When you use this with executable installers, the
    `$downloadedFileFullPath` will also be `$url`/`$url64` SilentArgs is
    everything you call against that file, as in
    `"$fileFullPath" $silentArgs"`. An example would be
    `"c:\path\setup.exe" /S`, where
    `$downloadedfileFullPath = "c:\path\setup.exe"` and `$silentArgs = "/S"`.

.PARAMETER File
    The locatation of the 32bit file inside the ISO.

.PARAMETER File64
    The locatation of the 64bit file inside the ISO.

.PARAMETER ValidExitCodes
    Array of exit codes indicating success. Defaults to `@(0)`.

.PARAMETER UseOnlyPackageSilentArguments
    Do not allow choco to provide/merge additional silent arguments and
    only use the ones available with the package. Available in 0.9.10+.

.PARAMETER IsoFile
    The location of the ISO file.
    If embedding in the package, you can get it to the path with
    `"$(Split-Path -parent $MyInvocation.MyCommand.Definition)\\ISO_FILE"`

.PARAMETER IgnoredArguments
    Allows splatting with arguments that do not apply. Do not use directly.

.EXAMPLE
    >
    $packageName= 'bob'
    $toolsDir   = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
    $fileLocation = Join-Path $toolsDir 'ISO_EMBEDDED_IN_PACKAGE'

    $packageArgs = @{
        packageName   = $packageName
        fileType      = 'msi'
        file          = 'setup.msi'
        file64        = 'x64\setup64.msi'
        silentArgs    = "/qn /norestart"
        validExitCodes= @(0, 3010, 1641)
        softwareName  = 'Bob*'
        isoFile       = $fileLocation
    }

    Install-ChocolateyIsoInstallPackage @packageArgs

.LINK
    Install-ChocolateyPackage

.LINK
    Uninstall-ChocolateyPackage

.LINK
    Get-UninstallRegistryKey

.LINK
    Start-ChocolateyProcessAsAdmin
#>
param(
    [parameter(Mandatory=$true, Position=0)][string] $packageName,
    [parameter(Mandatory=$true, Position=1)][string] $isoFile,
    [parameter(Mandatory=$false, Position=2)]
    [alias("installerType","installType")][string] $fileType = 'exe',
    [parameter(Mandatory=$false, Position=3)][string[]] $silentArgs = '',
    [alias("fileFullPath")][parameter(Mandatory=$false, Position=4)][string] $file = '',
    [alias("fileFullPath64")][parameter(Mandatory=$false)][string] $file64 = '',
    [parameter(Mandatory=$false)] $validExitCodes = @(0),
    [parameter(Mandatory=$false)]
    [alias("useOnlyPackageSilentArgs")][switch] $useOnlyPackageSilentArguments = $false,
    [parameter(ValueFromRemainingArguments = $true)][Object[]] $ignoredArguments
)
    # POSH3 is required for `Mount-DiskImage`
    if ($PSVersionTable.PSVersion -lt (New-Object 'Version' 3,0)) {
        throw 'This function requires PowerShell 3 or higher'
    }

    [string]$silentArgs = $silentArgs -join ' '

    Write-FunctionCallLogMessage -Invocation $MyInvocation -Parameters $PSBoundParameters

    $mountResult = Mount-DiskImage -ImagePath $isoFile -StorageType ISO -PassThru
    $isoVolume = $mountResult | Get-Volume
    $isoDrive = "$($isoVolume.DriveLetter):"

    if (Get-ProcessorBits 64) {
        if ($file64 -ne $null -and $file64 -ne '') {
            $file64 = "$($isoDrive)\$file64"
        }
    }

    $file = "$($isoDrive)\$file"

    Install-ChocolateyInstallPackage -PackageName $packageName `
                                     -FileType $fileType `
                                     -SilentArgs $silentArgs `
                                     -File $file `
                                     -File64 $file64 `
                                     -ValidExitCodes $validExitCodes `
                                     -UseOnlyPackageSilentArguments:$useOnlyPackageSilentArguments

    Dismount-DiskImage -ImagePath $isoFile

}
extensions\Install-ChocolateyIsoPackage.ps1
function Install-ChocolateyIsoPackage {
<#
.SYNOPSIS
    **NOTE:** Administrative Access Required.

    Installs software into "Programs and Features" based on a remote ISO file download.
    Use Install-ChocolateyIsoInstallPackage when using a local or embedded file.

.DESCRIPTION
    This will download an ISO file from an URL, mounts it and executes the specified native installer.
    Has error handling built in.
    If you are embedding the file(s) directly in the package (or do not need to download a file first),
    use Install-ChocolateyIsoInstallPackage instead.

.NOTES
    This command will assert UAC/Admin privileges on the machine.

    It will download the ISO file to the 'IsoCache' folder, if it is not already there.
    This will prevent downloading the same ISO file over and over again. This function can be disabled
    on a per package base by setting the 'NoCache' parameter to $true

    This is a wrapper around several existing Chocolatey commandlets.

    Chocolatey is copyrighted by its rightful owners. See: https://chocolatey.org

.INPUTS
    None

.OUTPUTS
    None

.PARAMETER PackageName
    The name of the package - while this is an arbitrary value, it's
    recommended that it matches the package id.

.PARAMETER FileType
    This is the extension of the file. This can be 'exe', 'msi', or 'msu'.
    Licensed editions of Chocolatey use this to automatically determine
    silent arguments. If this is not provided, Chocolatey will
    automatically determine this using the downloaded file's extension.

.PARAMETER SilentArgs
    OPTIONAL - These are the parameters to pass to the native installer,
    including any arguments to make the installer silent/unattended.
    Licensed editions of Chocolatey will automatically determine the
    installer type and merge the arguments with what is provided here.

    Try any of the to get the silent (unattended) installer -
    `/s /S /q /Q /quiet /silent /SILENT /VERYSILENT`. With msi it is always
    `/quiet`. Please pass it in still but it will be overridden by
    Chocolatey to `/quiet`. If you don't pass anything it could invoke the
    installer with out any arguments. That means a nonsilent installer.

    Please include the `notSilent` tag in your Chocolatey package if you
    are not setting up a silent/unattended package. Please note that if you
    are submitting to the community repository, it is nearly a requirement
    for the package to be completely unattended.

    When you are using this with an MSI, it will set up the arguments as
    follows:
    `"C:\Full\Path\To\msiexec.exe" /i "$downloadedFileFullPath" $silentArgs`,
    where `$downloadedfileFullPath` is `$url` or `$url64`, depending on what
    has been decided to be used.

    When you use this with MSU, it is similar to MSI above in that it finds
    the right executable to run.

    When you use this with executable installers, the
    `$downloadedFileFullPath` will also be `$url`/`$url64` SilentArgs is
    everything you call against that file, as in
    `"$fileFullPath" $silentArgs"`. An example would be
    `"c:\path\setup.exe" /S`, where
    `$downloadedfileFullPath = "c:\path\setup.exe"` and `$silentArgs = "/S"`.

.PARAMETER Url
    This is the url to download the resource from.

    Prefer HTTPS when available. Can be HTTP, FTP, or File URIs.

.PARAMETER ValidExitCodes
    Array of exit codes indicating success. Defaults to `@(0)`.

.PARAMETER Checksum
    The checksum hash value of the Url resource. This allows a checksum to
    be validated for files that are not local. The checksum type is covered
    by ChecksumType.

    **NOTE:** Checksums in packages are meant as a measure to validate the
    originally intended file that was used in the creation of a package is
    the same file that is received at a future date. Since this is used for
    other steps in the process related to the community repository, it
    ensures that the file a user receives is the same file a maintainer
    and a moderator (if applicable), plus any moderation review has
    intended for you to receive with this package. If you are looking at a
    remote source that uses the same url for updates, you will need to
    ensure the package also stays updated in line with those remote
    resource updates. You should look into [automatic packaging](https://chocolatey.org/docs/automatic-packages)
    to help provide that functionality.

    **NOTE:** To determine checksums, you can get that from the original
    site if provided. You can also use the [checksum tool available on
    the community feed](https://chocolatey.org/packages/checksum) (`choco install checksum`)
    and use it e.g. `checksum -t sha256 -f path\to\file`. Ensure you
    provide checksums for all remote resources used.

.PARAMETER ChecksumType
    The type of checkum that the file is validated with - valid
    values are 'md5', 'sha1', 'sha256' or 'sha512' - defaults to 'md5'.

    MD5 is not recommended as certain organizations need to use FIPS
    compliant algorithms for hashing - see
    https://support.microsoft.com/en-us/kb/811833 for more details.

    The recommendation is to use at least SHA256.

.PARAMETER Options
    OPTIONAL - Specify custom headers. Available in 0.9.10+.

.PARAMETER File
    The locatation of the 32bit file inside the ISO.

.PARAMETER File64
    The locatation of the 64bit file inside the ISO.

.PARAMETER UseOnlyPackageSilentArguments
    Do not allow choco to provide/merge additional silent arguments and only
    use the ones available with the package. Available in 0.9.10+.

.PARAMETER IsoCache
    OPTIONAL - Full path to a cache location. Defaults to `$env:Temp`.

.PARAMETER IgnoredArguments
    Allows splatting with arguments that do not apply. Do not use directly.

.EXAMPLE
    >
    $packageName= 'bob'
    $toolsDir   = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
    $url        = 'https://somewhere.com/file.iso'

    $packageArgs = @{
        packageName   = $packageName
        fileType      = 'msi'
        url           = $url
        file          = 'setup.msi'
        file64        = 'x64\setup64.msi'
        silentArgs    = "/qn /norestart"
        validExitCodes= @(0, 3010, 1641)
        softwareName  = 'Bob*'
        checksum      = '12345'
        checksumType  = 'sha256'
    }

    Install-ChocolateyIsoPackage @packageArgs

.LINK
    Install-ChocolateyIsoInstallPackage

.LINK
    Get-ChocolateyWebFile

.LINK
    Install-ChocolateyInstallPackage

.LINK
    Get-UninstallRegistryKey

.LINK
    Install-ChocolateyZipPackage
#>

param(
    [parameter(Mandatory=$true, Position=0)][string] $packageName,
    [parameter(Mandatory=$true, Position=1)][string] $url,
    [parameter(Mandatory=$false, Position=2)]
    [alias("installerType","installType")][string] $fileType = 'exe',
    [parameter(Mandatory=$false, Position=3)][string[]] $silentArgs = '',
    [parameter(Mandatory=$false)] $validExitCodes = @(0),
    [parameter(Mandatory=$false)][string] $checksum = '',
    [parameter(Mandatory=$false)][string] $checksumType = '',
    [parameter(Mandatory=$false)][hashtable] $options = @{[email protected]{}},
    [alias("fileFullPath")][parameter(Mandatory=$false)][string] $file = '',
    [alias("fileFullPath64")][parameter(Mandatory=$false)][string] $file64 = '',
    [parameter(Mandatory=$false)]
    [alias("useOnlyPackageSilentArgs")][switch] $useOnlyPackageSilentArguments = $false,
    [parameter(Mandatory=$false)][string] $isoCache = $env:TEMP,
    [parameter(ValueFromRemainingArguments = $true)][Object[]] $ignoredArguments
)
    # POSH3 is required for `Mount-DiskImage`
    if ($PSVersionTable.PSVersion -lt (New-Object 'Version' 3,0)) {
        throw 'This function requires PowerShell 3 or higher'
    }

    [string]$silentArgs = $silentArgs -join ' '

    Write-FunctionCallLogMessage -Invocation $MyInvocation -Parameters $PSBoundParameters

    if (![System.IO.Directory]::Exists($isoCache)) { [System.IO.Directory]::CreateDirectory($isoCache) | Out-Null }
    $downloadFileName = "$($packageName)Image.iso"
    if ($url.EndsWith(".iso")) {
        $downloadFileName = $url.Substring($url.LastIndexOf("/") + 1)
    }

    $downloadFilePath = Join-Path $isoCache $downloadFileName

    $isoPath = Get-ChocolateyWebFile -PackageName $packageName `
                                     -FileFullPath $downloadFilePath `
                                     -Url $url `
                                     -Checksum $checksum `
                                     -ChecksumType $checksumType `
                                     -Options $options `
                                     -GetOriginalFileName

    Install-ChocolateyIsoInstallPackage -PackageName $packageName `
                                        -IsoFile $isoPath `
                                        -FileType $fileType `
                                        -SilentArgs $silentArgs `
                                        -File $file `
                                        -File64 $file64 `
                                        -ValidExitCodes $validExitCodes `
                                        -UseOnlyPackageSilentArguments:$useOnlyPackageSilentArguments
}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Discussion for the Chocolatey ISO helpers extension Package

Ground Rules:

  • This discussion is only about Chocolatey ISO helpers extension and the Chocolatey ISO helpers extension 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 Chocolatey ISO helpers extension, 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