1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

File Copy mode help

Avatar
Richard Hagen

Hi,

I've been having some weirdness with the "File Copy" step. Basically, setups that I've been using fine for awhile have stopped working as of a few days ago.. PDQdeploy goes through the motions and reports a "successful", but when I check a machine it deployed to.. it didn't copy at all.

Looking at the results, I do find a log file which says this:

C:\windows\AdminArsenal\PDQDeployRunner\service-1\exec>robocopy . "C:\Program Files\Pixologic" /COPY:DT /E /XX /R:0 /W:0 /NP /XF RunFileCopy.cmd /IS /IT   'robocopy' is not recognized as an internal or external command, operable program or batch file.

I'm running 17.1.0.0 PDQDeploy.

Looking at some online instances of this happening, some people said to check the PATH variables.. but they seem to be fine, with c:\windows\system32 being present in the path. I don't know what else to troubleshoot or why PDQDeploy reports this as a "success" since I have errors set to "stop deployment".

I can include the exported .xml for the script if needed.

0

Comments

6 comments
Date Votes
  • Avatar
    Richard Hagen

    A screenshot of the "success" status and the log file saying that it can't find robocopy

    A screenshot of the "success" status and the log file saying that it can't find robocopy

    I also tried not copying a folder but rather just one file and I get the same status, just that the robocopy command comes out differently

    C:\windows\AdminArsenal\PDQDeployRunner\service-1\exec>robocopy . "C:\Program Files\Pixologic\ZBrush 2019 FL\ZData\ZPlugs64\RLM\\" /COPY:DT /E /XX /R:0 /W:0 /NP /XF RunFileCopy.cmd /IS /IT   robocopy' is not recognized as an internal or external command, operable program or batch file.
    0
  • Avatar
    Wei

    Does "robocopy" exist on the target ? If robocopy was working few days ago, check to see if there is any change made to the target recently like "Environment Variable".

    0
  • Avatar
    Richard Hagen

    Hi Wei,

    Yup - Robocopy exists at the targets and no environment variables were changed - the PATH variable still contains c:\windows\system32

    0
  • Avatar
    Wei

    The next thing I would try is creating a new testing package with a copy step to see if there is something wrong with your package. Also if you are running 64bit OS, you may want to include C:\Windows\SysWOW64 in the path variable.

    0
  • Avatar
    Colby Bouma
    1. Does the command where robocopy return a path or "INFO: Could not find files for the given pattern(s)." on the affected targets when you run it as the Deploy User?
    2. What does the same command return when you run it as a different user?
    3. Run $env:Path -split ";" in PowerShell and look for anything weird. I think $env:Path -split ";" | Select-String "C:\\.*C:" will identify malformed entries, but I'm not 100% certain.

    I was able to reproduce the symptoms you described by renaming robocopy. I will create an internal ticket about the File Copy step handling this error incorrectly. I still want to know what happened to these machines though 😃

    0
  • Avatar
    Richard Hagen

    Hi everyone - thanks for the input! I managed to get it fixed with your help!

    So trying the command "where robocopy", I was getting the "not recognized as an internal command.." error as well. The Powershell script said that I had c:\windows\system32 in the path no problem.

    However, Wei said something about SysWOW64 needing to be in there too... which apparently now my machines want now (??)

    Thanks for the troubleshooting help!

    0