Downloads:

56

Downloads of v 10.1:

56

Last Update:

06 Jul 2022

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

ADK oscdimg imaging packer

Oscdimg.exe of Windows Assessment and Deployment Kit in PATH

  • 1
  • 2
  • 3

10.1 | Updated: 06 Jul 2022

Downloads:

56

Downloads of v 10.1:

56

Maintainer(s):

Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Oscdimg.exe of Windows Assessment and Deployment Kit in PATH 10.1

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Oscdimg.exe of Windows Assessment and Deployment Kit in PATH, run the following command from the command line or from PowerShell:

>

To upgrade Oscdimg.exe of Windows Assessment and Deployment Kit in PATH, run the following command from the command line or from PowerShell:

>

To uninstall Oscdimg.exe of Windows Assessment and Deployment Kit in PATH, 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

  • 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

3. Copy Your Script

choco upgrade windows-adk-oscdimg -y --source="'INTERNAL REPO 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 windows-adk-oscdimg -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install windows-adk-oscdimg
  win_chocolatey:
    name: windows-adk-oscdimg
    version: '10.1'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'windows-adk-oscdimg' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '10.1'
end

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


cChocoPackageInstaller windows-adk-oscdimg
{
    Name     = "windows-adk-oscdimg"
    Version  = "10.1"
    Source   = "INTERNAL REPO URL"
}

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


package { 'windows-adk-oscdimg':
  ensure   => '10.1',
  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.

This package was approved by moderator TheCakeIsNaOH on 10 Aug 2022.

Description

This package will install the chocolatey package windows-adk (if not already installed), and then add the path of oscdimg.exe to %PATH%.


tools\chocolateyinstall.ps1
$KitsRootReg1 = 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Kits\Installed Roots'
$KitsRootReg2 = 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots'
$Key11        = 'KitsRoot11'
$Key10        = 'KitsRoot10'

# The same Windows ADK may write it's KitsRoot10-key or KitsRoot11-key, telling where the ADK is installed - 
# to either $KitsRootReg1 or $KitsRootReg2. On Windows Server 2022 it seems to get written to the former, on 
# Windows 11 the latter. Try until found. 

# The line below doesn't work because of backwards compatibility - the Get-ItemPropertyValue does not exist on test system
# $KitsRoot = Get-ItemPropertyValue -Path $KitsRootReg1 -Name $Key -ErrorAction SilentlyContinue

$KitsRootKey = Get-Item -Path $KitsRootReg1 -ErrorAction SilentlyContinue
# ensure the .GetValue() method exists
if ($KitsRootKey -is [Microsoft.Win32.RegistryKey]) {
  # try the key 'KitsRoot11'
  $KitsRoot = $KitsRootKey.GetValue("$Key11")
  if ($null -eq $KitsRoot) {
    # try the key 'KitsRoot10'
    $KitsRoot = $KitsRootKey.GetValue("$Key10")
  }
}

# if $KitsRoot is still $null, move on to the wow6432Node key
if ($null -eq $KitsRoot) {
  $KitsRootKey = Get-Item -Path $KitsRootReg2 -ErrorAction SilentlyContinue
  if ($KitsRootKey -is [Microsoft.Win32.RegistryKey]) {
    # try the key 'KitsRoot11'
    $KitsRoot = $KitsRootKey.GetValue("$Key11")
    if ($null -eq $KitsRoot) {
      # try the key 'KitsRoot10'
      $KitsRoot = $KitsRootKey.GetValue("$Key10")
    }
  }
}

# all the previous should be able to run without any exceptions being thrown, but
# if $KitsRoot is still $null, en exception must be thrown at this point
if ($null -eq $KitsRoot) {
  throw "Unable to find installation of Windows ADK"
} 
else {
  $OscdimgSourceFolder = Join-Path -Path $KitsRoot -ChildPath "Assessment and Deployment Kit\Deployment Tools\$($env:PROCESSOR_ARCHITECTURE)\Oscdimg"
  $OscdimgSourcePath = Join-Path -Path $OscdimgSourceFolder -ChildPath 'oscdimg.exe'
  if (Test-Path -Path $OscdimgSourcePath -ErrorAction SilentlyContinue) {
    $PathType = [System.EnvironmentVariableTarget]::Machine
    Write-Host "The path '$OscdimgSourceFolder' will be added to PATH"
    Install-ChocolateyPath -pathToInstall $OscdimgSourceFolder -pathType $PathType
  }
  else {
    throw "Unable to find '$OscdimgSourcePath'"
  }
}
tools\chocolateyuninstall.ps1
$KitsRootReg1   = 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Kits\Installed Roots'
$KitsRootReg2   = 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots'
$Key11          = 'KitsRoot11'
$Key10          = 'KitsRoot10'

# The same Windows ADK may write it's KitsRoot11-key or KitsRoot10-key, telling where the ADK is installed - 
# to either $KitsRootReg1 or $KitsRootReg2. On Windows Server 2022 it seems to get written to the former, on 
# Windows 11 the latter. Try until found. 

# The line below doesn't work because of backwards compatibility - the Get-ItemPropertyValue cmdlet 
# was introduced in PowerShell 5, and does not exist on test system
# $KitsRoot = Get-ItemPropertyValue -Path $KitsRootReg1 -Name $Key -ErrorAction SilentlyContinue

$KitsRootKey = Get-Item -Path $KitsRootReg1 -ErrorAction SilentlyContinue
# ensure the .GetValue() method exists
if ($KitsRootKey -is [Microsoft.Win32.RegistryKey]) {
  # try the key 'KitsRoot11'
  $KitsRoot = $KitsRootKey.GetValue("$Key11")
  if ($null -eq $KitsRoot) {
    # try the key 'KitsRoot10'
    $KitsRoot = $KitsRootKey.GetValue("$Key10")
  }
}

# if $KitsRoot is still $null, move on to the wow6432Node key
if ($null -eq $KitsRoot) {
  $KitsRootKey = Get-Item -Path $KitsRootReg2 -ErrorAction SilentlyContinue
  if ($KitsRootKey -is [Microsoft.Win32.RegistryKey]) {
    # try the key 'KitsRoot11'
    $KitsRoot = $KitsRootKey.GetValue("$Key11")
    if ($null -eq $KitsRoot) {
      # try the key 'KitsRoot10'
      $KitsRoot = $KitsRootKey.GetValue("$Key10")
    }
  }
}

if ($null -eq $KitsRoot) {
  Write-Warning -Message "Unable to find installation of Windows ADK from the registry - trying the standard filesystem locations"
  
  $ProgramFilesx86 = ${env:ProgramFiles(x86)}
  $ProgramFiles = $env:ProgramFiles

  $PossibleADKPath1 = Join-Path -Path $ProgramFilesx86 -ChildPath "Assessment and Deployment Kit\Deployment Tools\$($env:PROCESSOR_ARCHITECTURE)\Oscdimg"
  $PossibleADKPath2 = Join-Path -Path $ProgramFiles -ChildPath "Assessment and Deployment Kit\Deployment Tools\$($env:PROCESSOR_ARCHITECTURE)\Oscdimg"

  if (Test-Path -Path $PossibleADKPath1 -ErrorAction Ignore) {
    [system.string]$ADKPath = $PossibleADKPath1
  }
  elseif (Test-Path -Path $PossibleADKPath2 -ErrorAction Ignore) {
    [system.string]$ADKPath = $PossibleADKPath2
  }
  else {
    throw "Unable to find the Path to ADK - remove the path manually"
  }
}
else {
  [system.string]$ADKPath = Join-Path -Path $KitsRoot -ChildPath "Assessment and Deployment Kit\Deployment Tools\$($env:PROCESSOR_ARCHITECTURE)\Oscdimg"
}


# Get the PATH variable
Update-SessionEnvironment
$EnvPath = $env:PATH
if ($EnvPath.ToLower().Contains($ADKPath.ToLower())) {
  # remove any instances of ';;' before we count elements
  $EnvPath = $EnvPath.replace(';;',';')
  
  # Create a control count. We're removing only one element, if for 
  # some reason that doesn't check out, abort the operation
  $ControlCount = (($envPath.split(';')).count-1)

  # remove the path
  $NewPath = $EnvPath.replace("$ADKPath",'')

  # remove the remaining double ';'
  $NewPath = $NewPath.replace(';;',';')
  
  # Make sure the new value contains only one less element than before
  if (($NewPath.split(';').count) -eq $ControlCount) {
    $VariableType = [System.EnvironmentVariableTarget]::Machine
    Install-ChocolateyEnvironmentVariable -variableName 'Path' -variableValue $NewPath -variableType $VariableType
  }
  else {
    throw "Unable to remove the path of oscdimg.exe from PATH environment variable, remove manually"
  }
}

Log in or click on link to see number of positives.

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

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Discussion for the Oscdimg.exe of Windows Assessment and Deployment Kit in PATH Package

Ground Rules:

  • This discussion is only about Oscdimg.exe of Windows Assessment and Deployment Kit in PATH and the Oscdimg.exe of Windows Assessment and Deployment Kit in PATH 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 Oscdimg.exe of Windows Assessment and Deployment Kit in PATH, 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