Problem:
Issues arise in the instal software section of the provisioning process if the scheduler tasks in the agent are permitted to run as designed. A full description of the cause and consequences of these issues can be found in the following document;
http://community.landesk.com/support/docs/DOC-9526
The resolution in the above document has you create a provisioning agent that resolves the issues referenced, but requires the installation of the "desired" agent at the end of the provisioning process to restore the scheduler tasks for normal agent behavior. This can add 15+ minutes to the template to get the "desired" agent installed.
Resolution:
Instead of installing a second agent at the end of the provisioning template, you can simply restore the local scheduler tasks with a script in the provisioning template. This adds seconds to the template process and accomplishes the same thing.
In order to accomplish this and have it work properly, the name of the agent has to start out having the name of the agent you want it to end with. We change the "desired" or "default" agent, create a self contained exe, then change the agent back to the "desired" state.
This is accomplished by the following steps;
1. Go to your "desired" or "default" agent. The one you want to end up on the client machines. Right click > Properties to edit it's settings. We are going to make 4 simple changes.
2. We want to change each one of the schedules in the agent to run at a future time;
a. first, the inventory scanner;
Uncheck the mini scan option,
Select the change settings button, then;
Change the start date to the year 3000.
b. Now the same with the policy scanner;
Select the change settings button, then;
Change the start date to the year 3000.
c. and the last to change is the patch and compliance scanner;
Select the change settings button, then;
Change the start date to the year 3000.
3. Save the agent. Do not change the name of the agent.
4. Right-click on the agent and select "Create self-contained client..."
5. Now that you have a "self-contained" of your "Desired" agent install in a "Provisioning Agent" form, you want to go back into the agent and resore the date of the schedules in back to the way you had them. Repeat steps 2a through 2c, only change the year back to the current year.
6. Use the self contained agent instal in your provisioning template at the place you would install the provisioning agent.
7. Download this bat file. It will add each of the schedules back.
8. You must edit the bat file to change the word "CoreName" with your core server's name. It may or may not require the Core's FQDN depending on your environment. You can modify the script to remove one or more line if you do not want all of the schedules active in your environment, or to change the schedules they are set to run. As it is set, it will resore;
a. the mini scan option (once every 10 minutes)
b. the Inventory scan (once a day with an auto delay of up to an hour)
c. the policysync scan (once every 8 hours no delay)
d. the vulnerability scan (once every 2 days with an auto delay of up to an hour)
9. If you have a drive mapped to the core, you can place the bat script there. (This example shows drive P: mapped)
10. At the end of the provisioning template, right before the reboot or shutdown, run the script to add back the local scheduler tasks to the agent.
a. Use an execute file action to kick off the bat script as shown below;
