Deploy software using Distribution or Scripting?

In our environment we are rolling out Windows 10 using SCCM.  Since we are a company that has a large portion of our workforce remotely we have decided to install Direct Access so our remote users can receive the Win10 upgrade.

To deploy Direct Access we have attempted to use software distribution via Kace but found a crazy error that we cannot quite figure out.

DA (direct access) has an MSI install that needs run as well as several Reg keys that need to be installed for our specific network information.  We packaged them all up and created a install.bat file.  The install instructions have the files load up and then run the bat file.  Kace will prompt in the lower right hand corner with the only Option being Finish.  Once the user presses the Finish button this will execute the batch file to run.

We have several instances where the batch file runs and the software will install and report back to Kace that the software has installed successfully but there are other instances where the batch file will run, install the software, reboot and then prompt the user again to install the software moments after the computer reboots.

What is the trigger that indicates a software push was successful?  

We want the users to be informed of the software install because it requires a reboot for completion and we also want it to report back to Kace as a successful install. Looking for help to make this work.  Thank you.

3 Comments   [ + ] Show comments
  • If you are having a problem with a managed install kicking off more than once...
    Make sure you have the software package associated with the proper software inventory Item.
    Check the computer inventory for a PC that you have already installed the software on. Go to Installed Software under that computer in KACE, Select the software entry, and check to see if this is where you added the files. - Desktop Jockey 4 years ago
  • Does the program actually install on the computers with the error? If so, maybe the label is sometimes not removed from the computer so it thinks it has to run the job again? - JasonEgg 4 years ago
  • The software does install, it actually applied a Microsoft KB. Once the computer reboots it then prompts for the software to install again. The behavior acts like there is no finish "command" send to Kace after the reboot starts. - easyname001 4 years ago

Answers (1)

Posted by: anonymous_9363 4 years ago
Red Belt
As it's MSI-based, you can get a log of the installation. In fact, if any installer has a logging option, you should use it. Otherwise, you get into scenarios like this - stuff happens and you have no clue why. Use the 'verbose' option. The resulting log will tell you why the reboot is required.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ