Custom variable for log location resolving for PSADT logs but not MSI logs

//Custom variable for log location resolving for PSADT logs but not MSI logs
Custom variable for log location resolving for PSADT logs but not MSI logs 2017-09-29T22:51:33+00:00

The Toolkit Forums General Custom variable for log location resolving for PSADT logs but not MSI logs

  • Author
    Posts
  • Holly
    Participant
    Post count: 5
    #2325 |

    I added this custom variable to AppDeployToolkitExtensions.ps1:
    [string]$dirWSSource = ‘c:\sccmsupport’

    Then I changed the log locations in AppDeployToolkitConfig.xml:
    <Toolkit_LogPath>$dirWSSource\PSADTLogs</Toolkit_LogPath>
    <MSI_LogPath>$dirWSSource\PSADTLogs</MSI_LogPath>

    It’s working perfectly for the PSADT logs. I know this, because there is a log where I expect it to be. But it’s passing through incorrectly to the MSI Log:

    <![LOG[[Installation] :: Executing [C:\WINDOWS\system32\msiexec.exe /i “L:\Windows10Deploy\AppSource-Executing [C:\WINDOWS\system32\msiexec.exe /i “L:\Windows10Deploy\AppSource-PSDeploy\AdobeFlashPlayer\Files\install_flash_player_27_active_x.msi” TRANSFORMS=”L:\Windows10Deploy\AppSource-PSDeploy\AdobeFlashPlayer\Files\install_flash_player_27_active_x.mst” TRANSFORMSSECURE=1 REBOOT=ReallySuppress /QB-! /L*v “\PSADTLog\install_flash_player_27_active_x_Install.log”]

    Note the bad log path: “\PSADTLog\

    Any suggestions for getting this to pass through correctly?

  • Francois
    Participant
    Post count: 101

    HI,

    Did you configure the XML correctly?

  • Jim
    Participant
    Post count: 43

    Are you using $dirWSSource for anything else? Why not just put c:\sccmsupport in the XML file?

    <Toolkit_LogPath>c:\sccmsupport\</Toolkit_LogPath>
    <MSI_LogPath>c:\sccmsupport</MSI_LogPath>

You must be logged in to reply to this topic.