1 Reply Latest reply on Jun 15, 2009 11:59 AM by Watticus

    Setting Registry Entry with Provisioning


      I am trying to use provisioning to deploy a set of executables.  I need a registry entry added, a setup.exe to be run with a set of command line parameters, reboot the target machine and install the second file, setup2.exe and one second and final reboot.  I created 4 templates for these actions with one fifth and final template to contain the other 4.  Arranging the four templates in sequence and scheduling it for deployment goes well.  I can run the job for the test machine, and it will show that it is being provisioned, but it won't actually be run.  No registry entries get created, my setup files are not run.  I do not know where to check for a log file to try to find an error for provisioning.  Please let me know what information you may need that I can provide.

        • 1. Re: Setting Registry Entry with Provisioning

          First, what version of LANDesk are you running?  I ask this becasue between 8.7 and 8.8 the location of the log files on the core server changed.  In 8.7 the logs are located in ldlogon\provisioning.  In 8.8, the logs are located in ldmain\log\provisioning.  Additionally, the provisioning product is much more stable and reliable in the 8.8 branch of code.  If you are not already on 8.8 SP 2 or SP3, I would highly recommend upgrading as many issues have been resolved with fixes in these versions.


          Having said that, there are a few things to check in the process:


          1. In which section are the actions added in the template?

          2. How is the template being started, from the core or on the client side?

          3. Does the target machine have a LANDesk agent installed?

          4. Are you using distribute software actions or file execute actions?

          5. If you right-click on the target machine in the task window, choose "View Provisioning Histroy".  Are any of the actions executing?


          This information will be helpful in figuring out what is going on.