Powershell with Robocopy and Arguments Passing

Question

I'm trying to write a script that uses robocopy. If I were just doing this manually, my command would be:

robocopy c:\hold\test1 c:\hold\test2 test.txt /NJH /NJS

BUT, when I do this from powershell, like:

$source = "C:\hold\first test"
$destination = "C:\hold\second test"
$robocopyOptions = " /NJH /NJS "
$fileList = "test.txt"

robocopy $source $destination $fileLIst $robocopyOptions

I get:

-------------------------------------------------------------------------------
   ROBOCOPY     ::     Robust File Copy for Windows
-------------------------------------------------------------------------------

  Started : Fri Apr 10 09:20:03 2015

   Source - C:\hold\first test\
     Dest - C:\hold\second test\

    Files : test.txt

  Options : /COPY:DAT /R:1000000 /W:30

------------------------------------------------------------------------------

ERROR : Invalid Parameter #4 : " /NJH /NJS "

However, if I change the robocopy command to

robocopy $source $destination $fileLIst  /NJH /NJS

everything runs successfully.

So, my question is, how can I pass a string as my robocopy command options (and, in a larger sense, do the same for any given external command)

Anton Z · Answer 1 · 2015-04-10T14:23:16.443

19

Start robocopy -args "$source $destination $fileLIst $robocopyOptions"
or
robocopy $source $destination $fileLIst $robocopyOptions.split(' ')

edited Apr 10 '15 at 14:23

answered Apr 10 '15 at 14:11

Anton Z

270
2
6

`Start-Process` is OK if you don't mind the separate console window. – Bill_Stewart Apr 10 '15 at 14:33
1

use `-NoNewWindow -PassThru -Wait` arguments to avoid separate console window – Anton Z Apr 10 '15 at 14:51
IIRC, `Start-Process` doesn't update `$LASTEXITCODE`. That may be important in some cases. – Bill_Stewart Apr 10 '15 at 15:42

beatcracker · Accepted Answer · 2019-06-10T21:46:00.540

12

Use the arrays, Luke. If you specify an array of values, PowerShell will automatically expand them into separate parameters. In my experience, this is the most reliable method. And it doesn't require you to mess with the Start-Process cmdlet, which is in my opinion is overkill for such tasks.

This trick is from the best article I've seen on the PowerShell behavior towards external executables: PowerShell and external commands done right.

Example:

$source = 'C:\hold\first test'
$destination = 'C:\hold\second test'
$robocopyOptions = @('/NJH', '/NJS')
$fileList = 'test.txt'

$CmdLine = @($source, $destination, $fileList) + $robocopyOptions
& 'robocopy.exe' $CmdLine

edited Jun 10 '19 at 21:46

answered Apr 10 '15 at 15:32

beatcracker

6,714
1
18
41

2

Original link in answer is dead ... Here is the updated link: [PowerShell and external commands done right](https://slai.github.io/posts/powershell-and-external-commands-done-right/) – Sharpenologist Jun 10 '19 at 17:33
@Sharpenologist Thanks, fixed! – beatcracker Jun 10 '19 at 21:46

score 6 · Answer 3 · answered Apr 10 '15 at 14:32

You can't use a string to pass options in that way because when you write

robocopy $source $destination $fileList $robocopyOptions

PowerShell will evaluate the last variable ($robocopyOptions) as a single string and it will quote it. This means robocopy will get "/NJH /NHS" (single string, quoted) on its command line. (Obviously not the intent.)

For details on how to work around these kinds of issues, see here:

http://windowsitpro.com/powershell/running-executables-powershell

The article includes the following function:

function Start-Executable {
  param(
    [String] $FilePath,
    [String[]] $ArgumentList
  )
  $OFS = " "
  $process = New-Object System.Diagnostics.Process
  $process.StartInfo.FileName = $FilePath
  $process.StartInfo.Arguments = $ArgumentList
  $process.StartInfo.UseShellExecute = $false
  $process.StartInfo.RedirectStandardOutput = $true
  if ( $process.Start() ) {
    $output = $process.StandardOutput.ReadToEnd() `
      -replace "\r\n$",""
    if ( $output ) {
      if ( $output.Contains("`r`n") ) {
        $output -split "`r`n"
      }
      elseif ( $output.Contains("`n") ) {
        $output -split "`n"
      }
      else {
        $output
      }
    }
    $process.WaitForExit()
    & "$Env:SystemRoot\system32\cmd.exe" `
      /c exit $process.ExitCode
  }
}

This function will let you run an executable in the current console window and also let you build an array of string parameters to pass to it.

So in your case you could use this function something like this:

Start-Executable robocopy.exe $source,$destination,$fileList,$robocopyOptions

score 1 · Answer 4 · answered Nov 25 '20 at 04:45

Putting the options in separate arguments worked for me. Using Robocopy for copying excluding any CSV files.

$roboCopyPath = $env:ROBOCOPY_PATH
$otherLogsPath = [System.IO.Path]::Combine($basePath, "Logs-Other")
$atrTestResults = [System.IO.Path]::Combine($Release, $BuildNumber)
$ResultsSummary = [System.IO.Path]::Combine($basePath, "Result")

$robocopyOptions = @("/log:$otherLogsPath\robocopy.log", '/xf', '*.csv')
$CmdLine = @($atrTestResults, $ResultsSummary) + $robocopyOptions 
&$roboCopyPath $CmdLine

Powershell with Robocopy and Arguments Passing

4 Answers4

Linked