The Practical Administrator - Page 19 of 19 - Lessons of a Datacenter Administrator

Shaun Cassell does a very nice job explaining what can go wrong HERE. One thing he doesn’t spell out is that you cannot have ANY spaces. For those of you who don’t know, when you install/upgrade ConfigMgr 2007. The setup wizard actually has to contact MS servers to download required components. You can do this ahead of time by running.

<path>setup.exe /download <path>

If you run the above command and nothing happens.. goto %SYSTEMDRIVE%ConfigMgrSetup.txt, if that log file contains.

<07-13-2008 10:02:24> Download folder F:SCCMUPDATES” does not exist
<07-13-2008 10:02:24> Failed to download prerequisite components (0x80070003)

Stop… you have spaces somewhere, the most sure fire way around this is to map a drive. Map a drive to the source and target destination folders. Furthermore if you start downloading updates, and it “fails” check your destination. If any updates at all have successfully downloaded. Start it back up, that is a network timeout.

p class=”headermaintitle”>Will work:
\servershareSCConfigMgr07SMSSETUPBINI386setup.exe /download c:SCCMUpdates
D:SCConfigMgr07SMSSETUPBINI386setup.exe /download c:SCCMUpdates
S:setup.exe /download T:

p class=”headermaintitle”>Will NOT work:
\serversome shareSCConfigMgr07SMSSETUPBINI386setup.exe /download c:SCCMUpdates
D:SCConfigMgr07SMSSETUPBINI386setup.exe /download c:SCCM Updates

OR… A little POSH goodness. Before I figured out what was going on. I wrote this quick Powershell script to download them for me. 😉

$manifestturl = 'http://go.microsoft.com/fwlink/?LinkId=104106'

function Download-File ([string]$URL,[string]$savepath)
{
    $web = New-Object System.Net.WebClient
    $web.headers.Add("User-agent", "Powershell")
    $web.DownloadFile($URL,$savepath)
}

function Get-SCCMPrereq
{
    param([string]$path, [switch]$verbose)
    $holdverbose = $VerbosePreference

    if ($verbose) { $VerbosePreference = 'Continue'}

    if ((Test-Path $path) -ne $TRUE) {
    <span style="white-space:pre">  </span>Write-Verbose "$path not found, Attempting to create it."
        mkdir $path | Out-Null
    }

    $tempdir = ([system.IO.Path]::GetTempFileName()).Replace('.tmp',''); mkdir $tempdir | out-null
    Write-Verbose "Downloading ConfigMgr.manifest.cab"

    Download-File $manifestturl "$($path)ConfigMgr.Manifest.cab"
    Write-Verbose "Decompressing ConfigMgr.manifest.cab"
    $destFolder = $((new-object -com Shell.Application).NameSpace($tempdir))
    $destFolder.CopyHere((new-object -com Shell.Application).NameSpace("$($path)ConfigMgr.Manifest.cab").items())
    [xml]$configManifest = gc "$($tempdir)ConfigMgr.Manifest.xml"

    #process the ConfigMgr.Manifest.xml
    $manifest = $configManifest.SCCM2007.Group | % { $_.File } | % {
        $obj = New-Object PSObject
        $obj | Add-Member NoteProperty "URL" $_.Source
        $obj | Add-Member NoteProperty "File" $_.CopyName
        $obj | Add-Member NoteProperty "MD5" $_.MD5
        Write $obj
    }
    $manifest | foreach-object -begin {clear-host;$i = 0} `
    -process {
        Download-File $_.URL "$($path)$($_.File)" ; `
        $i = $i + 1;`
         write-progress -activity "Downloading ConfigMgr Prerequisits" `
        -status "Progress:" -currentOperation $_.file -percentcomplete ($i / $manifest.count * 100) `
    } `
    -end {
        if ((((ls 'C:SCCM_UPDATES').count) - 1) -eq $manifest.count){
            Write-Host "Operation Completed Successfully $i out of $($manifest.count) Downloaded."
        } else {
            Write-error "ERROR only $i out of $($manifest.count) Successfully downloaded."
        }
    }
}

get-sccmprereq 'C:SCCM_UPDATES' -verbose

$manifestturl = 'http://go.microsoft.com/fwlink/?LinkId=104106'

function Download-File ([string]$URL,[string]$savepath)

{

$web = New-Object System.Net.WebClient

$web.headers.Add("User-agent", "Powershell")

$web.DownloadFile($URL,$savepath)

}

function Get-SCCMPrereq

{

param([string]$path, [switch]$verbose)

$holdverbose = $VerbosePreference

if ($verbose) { $VerbosePreference = 'Continue'}

if ((Test-Path $path) -ne $TRUE) {

<span style="white-space:pre"> </span>Write-Verbose "$path not found, Attempting to create it."

mkdir $path | Out-Null

}

$tempdir = ([system.IO.Path]::GetTempFileName()).Replace('.tmp',''); mkdir $tempdir | out-null

Write-Verbose "Downloading ConfigMgr.manifest.cab"

Download-File $manifestturl "$($path)ConfigMgr.Manifest.cab"

Write-Verbose "Decompressing ConfigMgr.manifest.cab"

$destFolder = $((new-object -com Shell.Application).NameSpace($tempdir))

$destFolder.CopyHere((new-object -com Shell.Application).NameSpace("$($path)ConfigMgr.Manifest.cab").items())

[xml]$configManifest = gc "$($tempdir)ConfigMgr.Manifest.xml"

#process the ConfigMgr.Manifest.xml

$manifest = $configManifest.SCCM2007.Group | % { $_.File } | % {

$obj = New-Object PSObject

$obj | Add-Member NoteProperty "URL" $_.Source

$obj | Add-Member NoteProperty "File" $_.CopyName

$obj | Add-Member NoteProperty "MD5" $_.MD5

Write $obj

}

$manifest | foreach-object -begin {clear-host;$i = 0} `

-process {

Download-File $_.URL "$($path)$($_.File)" ; `

$i = $i + 1;`

write-progress -activity "Downloading ConfigMgr Prerequisits" `

-status "Progress:" -currentOperation $_.file -percentcomplete ($i / $manifest.count * 100) `

} `

-end {

if ((((ls 'C:SCCM_UPDATES').count) - 1) -eq $manifest.count){

Write-Host "Operation Completed Successfully $i out of $($manifest.count) Downloaded."

} else {

Write-error "ERROR only $i out of $($manifest.count) Successfully downloaded."

}

get-sccmprereq 'C:SCCM_UPDATES' -verbose

~ Glenn

Okay, so I know what .Net is, but how was I supposed to know it was this powerful. For anyone who has every worked with xml in VBScript… I feel your pain. With that knowledge of the headache, that was the “Msxml2.DOMDocument” com object. I have avoided XML like the plague. Problem is I was completely oblivious to what “.Net support” really meant! I have several projects at work where I use PowerShell to “interact” with REST based web services. Not wanting to take that XML dive, I requested “PowerShell hooks”, and was obliged.

When our programmers asked me, what I wanted returned? I told them to give me a CSV in the format of a custom PS Object. At the time, this seemed a no brainier. Not only do I not have to worry about WSDL/ADO/XML, but also the data would stay objectized.

It worked GREAT that was until I started to manipulate large data sets. Then my simple system fell apart. Downloading and saving that CSV file, before I could import that data. Was simply too much, and was drastically degrading performance. Therefore, I asked the question on the PowerShell community forums about optimizing such a task. The response I got lead me to crack open Bruce’s PowerShell in Action. Low and behold, where has .Net been all my life!

Posted By bsonposh on 07/06/2008 10:51 AM
Actually… the *-clixml are meant for serializing and deserializing objects. Import-cliXML expects a VERY specific format.

If you want to “import” XML you can just type it
[XML]$myxml = < some data >

That is it… Just by type casting your object with [xml] the .net framework does the rest. Not only is it easier then my custom CSV’s but its twice as fast!

~Glenn Sizemore

ConfigMgr 2007 SP1 downloading prerequisite components

VMware Tools on Server Core

VMworld 2008 BABY!!

XML vs CSV