Issues with Powershell Invoke-Command

Question

I am trying to get an application to install on a remote server using powershell. Here is the script I am using:

$cred = Get-Credential
$s = New-PSSession -ComputerName $ServerName -Credential $cred

Invoke-Command -Session $s -ScriptBlock {Start-Process -FilePath "c:\windows\system32\msiexec.exe" -ArgumentList "/i \\computer\e$\installer.msi /qn" -Wait}

Remove-PSSession -ComputerName $ServerName

If I run the following on the remote computer directly, it executes beautifully:

Start-Process -FilePath "c:\windows\system32\msiexec.exe" -ArgumentList "/i \\computer\e$\installer.msi /qn" -Wait

But when I run it remotely as a part of the Invoke-Command, the PS Session is opened, the script runs, msiexec starts on the remote computer, then the PS Session closes but the application never installs and msiexec never closes.

Any help would be appreciated.

Thanks,

Zach

Just a user · Accepted Answer · 2014-08-20 15:20:34Z

4

You'll need to copy the package locally first. Once you start remoting you can no longer UNC.

The destination can be anywhere on the server/computer. I use the temp but it's whatever you like.
Also I like to use $env:windir\temp, just in case.

    Copy-item "\\servershare\File.msi" -conatiner -recurse `
               \\$Computer\c$\windows\temp\

    Invoke-Command -Computername $Computer -credential $cred -ScriptBlock {
        Start-Process -FilePath `
        "c:\windows\system32\msiexec.exe" `
        -ArgumentList "/i `
        \\computer\e$\installer.msi /qn" -Wait
        }

I hope it helps.

edited Aug 20, 2014 at 15:20

answered Aug 20, 2014 at 15:03

Just a user

6292 gold badges10 silver badges20 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Zachary Wheeler Over a year ago

I had it copied locally originally but it wasn't working so I switched to UNC. Turns out the reason locally wasn't working was because msiexec didn't like a space in the file path for the .msi that was being passed in the "ArgumentList". Once I moved the .msi to a different path, and referenced the new path in my script, it worked perfectly. Thanks for your help, Remy.

Collectives™ on Stack Overflow

Issues with Powershell Invoke-Command

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related