Installer requires full path for output log

Comments

3 comments

  • Official comment
    Dakota Clark

    Try using  /l=.\output.log as some installer technologies will interpret . as the current directory. If that doesn't work try setting just the file name like so /l=output.log as that can also be taken to use the current directory.

    Comment actions Permalink
  • Colby Bouma

    Strange, I would have expected /l="%cd%\output.log" to work. The absolute path starts here: C:\Windows\AdminArsenal\PDQDeployRunner\service-1\exec

    As long as you only have 1 instance of Deploy in your network, it shouldn't go above service-1. However, there are situations such as stuck deployments that can cause it to increment. If the absolute path works, I recommend that you keep trying to get something like /l="%cd%\output.log" to work.

    1
    Comment actions Permalink
  • Stefan Rado

    It seems like this environment variable is not expanded when calling the installer file.

    The installer unpacks another exe to a temporary directory and executes it. I checked the command line of the child process and the argument passed to the child still contains the /l="%cd%\output.log" part. But even if the child process expands the variable before creating the log file, it will no longer point to the PDQDeployRunner directory, because the working directory of the child process is a temporary folder.

    1
    Comment actions Permalink

Please sign in to leave a comment.