Using Software Delivery › Delivery and Staging of Software › Orders Sent from the Domain Manager › Empty Jobs and Job Containers

Empty Jobs and Job Containers

There are a number of situations that a job is set up but there are no target computers to receive that job. Or, a job was set up for a group that has no Execute permissions. This resulted, in the first case, in an empty job which was marked OK, or, in the second case, in a job container with no jobs.

The software delivery system behavior is as follows:

• If it can be determined when the job is set up that there are no target computers, an error is returned immediately.
• If no jobs could be set up, the job container is deleted.
• If the background evaluation of a job container results in no targets for the job, the job is marked by a warning symbol. This can happen under the following circumstances:
  • A job container with ACTIVATE, CONFIGURE, or UNINSTALL procedures has been set up with target computer groups or computers as targets. When the container is evaluated, it is found that none of the target computers has an installation of the item to which the item procedure belongs.
  • A job container has been set up using any procedure, with target computer groups as targets. When the container is evaluated, it is found out that the software delivery agent is not installed at all on the machine (for example, the asset management agent only has been installed on the target computers.)

In these cases, a new job message states why no targets were found, for example, "No target computers found in evaluation step" or "No target installations found in evaluation step".