Errors and exceptions in PowerShell are structured objects. The error message you see printed on the console is actually a formatted message with information from several elements of the error/exception object. You can (re-)construct it yourself like this: $formatstring = “{0} : {1}`n{2}`n” + ” + CategoryInfo : {3}`n” + ” + FullyQualifiedErrorId : {4}`n” … Read more
Starting in PowerShell version 4, this is easy to do for files out of the box with the Get-FileHash cmdlet: Get-FileHash <filepath> -Algorithm MD5 This is certainly preferable since it avoids the problems the solution for older PowerShell offers as identified in the comments (uses a stream, closes it, and supports large files). If the … Read more
Since you mention upgrade code, it must mean that you are talking about an MSI file (Windows Installer). As stated by others such an uninstall is normally performed auto-magically by a properly authored MSI package – it is referred to as a major upgrade – which is essentially an uninstall of the existing version of … Read more
This isn’t the answer why your specific script doesn’t work under the SYSTEM account but explains how you might troubleshoot your (or any other) PowerShell Script under the SYSTEM account. Give a man a fish, and you feed him for a day. Teach a man to fish, and you feed him for a lifetime. The … Read more
Variables defined in the global scope of your script are not available inside the scriptblock unless you use the using qualifier: $code = { Get-WmiObject -Class “Win32_ComputerSystem” -Namespace “root\cimv2” -ComputerName $using:h } or pass them in as arguments, like this: $code = { Param($hostname) Get-WmiObject -Class “Win32_ComputerSystem” -Namespace “root\cimv2” -ComputerName $hostname } $jobstate = Wait-Job … Read more
This is true when using “using” because the definition of using states, Beginning in PowerShell 3.0, you can use the Using scope modifier to identify a local variable in a remote command Anytime you use the $using, you have to provide -ComputerName or -Session arguments whether the target server is localhost or remote. Ex. $myServerName=”www.google.com” … Read more
By design, double-clicking (opening) *.ps1 files from the Windows [GUI] shell (in this case: Desktop, File Explorer, and the taskbar, via pinned items) does not execute them – instead they’re opened for editing in Notepad or in the PowerShell ISE, depending on the Windows / PowerShell version. However, since at least Windows 7, the shortcut … Read more
The accepted answer won’t do a multipart/form-data request, but rather a application/x-www-form-urlencoded request forcing the Content-Type header to a value that the body does not contain. One way to send a multipart/form-data formatted request with PowerShell is: $ErrorActionPreference=”Stop” $fieldName=”file” $filePath=”C:\Temp\test.pdf” $url=”http://posttestserver.com/post.php” Try { Add-Type -AssemblyName ‘System.Net.Http’ $client = New-Object System.Net.Http.HttpClient $content = New-Object System.Net.Http.MultipartFormDataContent $fileStream … Read more
Double quotes allow variable expansion while single quotes do not: PS C:\Users\Administrator> $mycolor=”red” PS C:\Users\Administrator> write-output -inputobject ‘My favorite color is $mycolor’ My favorite color is $mycolor Source: http://www.techotopia.com/index.php/Windows_PowerShell_1.0_String_Quoting_and_Escape_Sequences (I know version 1.0 but the principle is still the same)
You have to create the password string on the same computer and with the same login that you will use to run it.