Windows intune temp software installation path for deployed software?

Отвечено Windows intune temp software installation path for deployed software?

  • Friday, March 01, 2013 9:36 AM
     
     

    Hi All,

    Does somebody know where the tempfiles for intune managed deployed software are being created or saved?

    I want to create a package for PDFcreator with a settings ini file. That ini file is used to have a configured base installation.

    The command line is : PDFCreator-1_6_2_setup.exe /SP /VERYSILENT /NORESTART /LOADINF="C:\pdf.inf"

    However, I need to define the /LOADINF="C:\pdf.inf", but since this is not directly installed on c:\ I need to know the 'temp save' location of the packages deployed with Intune. Using a networkpath to load the ini file can't be done...

    Thanks

All Replies

  • Friday, March 01, 2013 3:22 PM
    Moderator
     
     Answered

    Hi Andy,

    Intune uses a random guid for your package folder and it drops the files under your install folder usually at c:\program files\microsoft\onlinemanagement\updates\download

    However it may be possible to include the pdf.inf in your package by using the "include all files in the folder" option in the Software Publisher and then just using the switch /loadinf="pdf.inf" which would pull the file from the directly the PDFcreator.exe is running from.

    Have you tried that?

    Thanks,

    Jon L. - MSFT

    • Marked As Answer by Andy VC Monday, March 04, 2013 10:04 AM
    •  
  • Monday, March 04, 2013 10:05 AM
     
     

    Hi Andy,

    Intune uses a random guid for your package folder and it drops the files under your install folder usually at c:\program files\microsoft\onlinemanagement\updates\download

    However it may be possible to include the pdf.inf in your package by using the "include all files in the folder" option in the Software Publisher and then just using the switch /loadinf="pdf.inf" which would pull the file from the directly the PDFcreator.exe is running from.

    Have you tried that?

    Thanks,

    Jon L. - MSFT

    Hi Jon,

    Thats correct... I tried some options and leaving out the %installpath% did the trick. Thanks!