Discovery and Inventory Group

Does a custom schedule have an End Date that’s passed?

By default Inventory Policies have no end date to their schedules. If using the default schedules (listed on the policy as Daily, Weekly, and Monthly) no end date will ever be applied. If using a Custom schedule, the end date is not checked by default, however a user can check the end date. Use the following process to determine if an end date is being used, and if so, to correct it. Note that these steps can also be conducted at the same time as the Run Once issue.

1. 1. For each applicable Inventory Policy that is not being run, browse in the Symantec Management Console under Manage > Policies and browse in the left-hand tree under Discovery and Inventory > Inventory > and select the policy.
   2. Click on the Custom schedule hyperlink. If one of the default schedules are being used, this is not the cause of the issue.
   3. Click the Advanced button.
   4. Ensure the End checkbox is not checked. If it is checked, uncheck it. If an end date is required in the future, adjust the end date so it is not past.
       
2. 5. Click OK, and OK, and save the Policy to apply the changes.
   6. Repeat these steps for each policy that is not running.

Does the schedule only run once?

When a schedule is created, a date is not specified unless you go into the advanced settings. Also schedules do not repeat unless a repeat is added. If Inventory is not running as expected, it could be that the schedule applied to the policy only runs once. The following process walks through checking and adjusting the schedule as needed. Note that these steps can also be conducted at the same time as the End Date issue.

1. 1. For each applicable Inventory Policy that is not being run, browse in the Symantec Management Console under Manage > Policies and browse in the left-hand tree under Discovery and Inventory > Inventory > and select the policy.
   2. Click on the Custom schedule hyperlink. If one of the default schedules are being used, this is not the cause of the issue.
   3. Click the Advanced button.
   4. The schedule should have the repeating data included. The below screenshot shows a schedule with repeating executions, and one that will only run once.
       
2. 5. Add a repeating schedule to at least one of the schedules shown to ensure systems run it regularly to keep Inventory up to date.
   6. Keep the run once since this will act as a "If I've never run this before, run it immediately". That functionality does not apply to a repeating schedule since it will simply wait until the next repeat of the schedule. To ensure each policy runs immediately when it is first received, especially the Full Inventory Policies, keep the run once schedule as shown. This will cause the agent to recognize that the time for the schedule as passed and it will run the policy immediately.
   7. Repeat these steps for all policies.

Lastly, check to ensure the licenses are not maxed. This can cause inventory to be thrown out and may make it appear that inventory is not running when it is the server rejecting a client's inventory because it has no valid license. The error logs will show an error when this occurs.