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.

Quick Batch File Compiler + Office and Run times

Avatar
Charsmith

We create a custom .exe using quick batch. The custom.exe does the following

1. Has an Install.cmd file that references a restricted file share that contains our install files, and it just points to the setup.exe file of the program

2. Has a VBS script that looks to see if the computer has been added to an AD group. If it has not the setup will not run. This is how we control access to some of our software. The custom .exe is put on a non-locked down share. 

3. psexec.exe 

In my pdq deploy package I just have to point the the custom .exe file and have not needed to do anything else. However, when I deploy office 2007 or 2010 products about half the time the installer will run until the end of the timeout settings even though it finishes correctly. The installs are not completely silent but do not require user interaction (this is on purpose). 

Any idea of something I can do differently that will stop it from running until time out. The same package will report Successful with run times anywhere between 5mins and up to the time out of an hour. Even though the install was really finished between 5-20mins. Then others it will never report Successful as it times out after 60mins, but the install was successful after 5-20mins. 

I have not tried any parameters on my packages but given the inconsistent behavior I wanted to ask for advice before changing anything. 

 

0

Comments

1 comment
Date Votes
  • Avatar
    Shane Corellian

    Interesting on the Office 2007 and 2010 timing out half the time. What is your timeout set to? This is normally caused by the Completion Notice checkbox being enabled in the Office Customization Tool. This could still be the issue if the deployments which timed out had someone logged on. Open your MSP file (that you use to deploy Office) and under the Licensing and user interface section verify that Display level is set to None and that the Completion Notice is unchecked.

    0