You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Write-CMLogEntry function you write the log text out to pipeline (the single $logtext) line.
Unfortunately, this pollutes the value returned by the Invoke-CMDownloadContent function when it is called by the line _`$DownloadInvocation = Invoke-CMDownloadContent -PackageID $($PackageList[0].PackageID) -DestinationLocationType Custom -DestinationVariableName "OSDBIOSPackage" -CustomLocationPath "%SMSTSMDataPath%\BIOSPackage"
Instead of returning the value of $ReturnCode (which, hopefully, should be 0!) it contains the log text that you echo out in Write-CMLogEntry.
I presume that single $logtext line was left in for debugging purposes
`
The text was updated successfully, but these errors were encountered:
Oh wow, sorry. I'd totally forgotten about this! Actually, you can close the issue. I re-downloaded the scripts a few weeks ago and that rogue $logcontent line was no longer present. I may have added it myself when testing something ;)
In the Write-CMLogEntry function you write the log text out to pipeline (the single $logtext) line.
Unfortunately, this pollutes the value returned by the Invoke-CMDownloadContent function when it is called by the line _`$DownloadInvocation = Invoke-CMDownloadContent -PackageID $($PackageList[0].PackageID) -DestinationLocationType Custom -DestinationVariableName "OSDBIOSPackage" -CustomLocationPath "%SMSTSMDataPath%\BIOSPackage"
Instead of returning the value of $ReturnCode (which, hopefully, should be 0!) it contains the log text that you echo out in Write-CMLogEntry.
I presume that single $logtext line was left in for debugging purposes
`
The text was updated successfully, but these errors were encountered: