Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem in Write-CMLogEntry function #97

Open
Ginolard opened this issue Jan 8, 2019 · 2 comments
Open

Problem in Write-CMLogEntry function #97

Ginolard opened this issue Jan 8, 2019 · 2 comments

Comments

@Ginolard
Copy link

Ginolard commented Jan 8, 2019

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
`

@NickolajA
Copy link
Member

Could you please provide a visual example of what you mean?

@Ginolard
Copy link
Author

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 ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants