How do a silent install with a "Setup Bootstrap for Visual Basic Setup Toolkit" setup.exe

Comments

7 comments

  • TonsOFun

    Hi Lodola, 

     

    Did you make sure that "Include Entire Directory" is checked in the deployment package? 

    What errors are you getting? 

    0
    Comment actions Permalink
  • Lodola

    Hi TonsOFun,

    I just try all the possibilities and to check the "include directory" too.

    Are not errors, because the deployment run and run... more time and do not get errors. Always I abort the deploy because is it not possible too wait more than 30 minutes..

    0
    Comment actions Permalink
  • TonsOFun

    might be easier if you took screenshots of the package. 

    It's still a little vague at the moment. 

    You're using full UNC path for the install file correct? not a drive letter? 

    If it's working under the command prompt but not working in the deploy package, it's usually just a syntax error. (most of the time)

    0
    Comment actions Permalink
  • Lodola

    Hi TonsOFun,

    I try another times to install the sw but I have no results. I send you the image of the command line in dos "setup.exe /sc:\setup.log" thats run, and the package that I try to install with the same command. In this case is not checked the flag "include entire directory" but in another test I just tried too, but not work.

    0
    Comment actions Permalink
  • TonsOFun

    Hmm... was doing some research and maybe admins can share some light into this as i'm not sure how temp environment variables are handled with PDQ. 

    Source: http://support.microsoft.com/kb/182470

    Although the version might be different, the rule may still apply? 

    -------------Copy and paste of KB-----------

    NOTE: Installing an application using the NT Schedule service with the silent or SMS parameter will not work and is not supported. The Schedule service does not create a complete copy of the environment when it starts the Setup. When Setup tries to check for free disk space, the test fails because the TMP and TEMP environment variables are not present. Trying to work around the problem by setting the variables in a batch file, such as the following example, also fails:

       Set TMP=C:\TEMP
       Set TEMP=C:\TMP
       Setup -q MyLog.txt


    0
    Comment actions Permalink
  • Shane Corellian

    If there are additional files required for the installation then you will definitely need to check the Include Entire Directory. If you don't do this then setup.exe will be executed but will not be able to access the other install files.

    For the sake of troubleshooting, go to the Options tab for Step 1 and select Run as Logged On User. Log on to the target computer with an admin account. Deploy the package. This way any error windows that are encountered will be displayed on the target computer. This should help you nail down the problem.

    **UPDATE** To answer TonsOfFun's question: PDQ Deploy passes the unexpanded variables to CMD in a command step. For an Install Step PDQ Deploy attempts to expand any variable in the parameters field and passes the expanded value to the Install File.

     

    0
    Comment actions Permalink
  • BigChuck75

    I'm running into the same issue, I can run it from the command line with the silent install setup.exe /sc:\setup.log and I include the entire directory but it just hangs when using PDQ deploy.  I changed the user to the logged in user, nothing shows up on the screen during deployment and that step just hangs.

    0
    Comment actions Permalink

Please sign in to leave a comment.