Scheduling Page
Connections defined on your inventory beacon are also scheduled on the same beacon.
When the inventory beacon is co-installed on your central batch server (or whichever server hosts that functionality), the schedules created on this page are available only for Active Directory imports. All other connections coming from the batch server are scheduled by the Windows Task Scheduler on that server, and cannot be controlled through the inventory beacon interface. However, on all other (free-standing) inventory beacons, all the following comments apply for scheduling connections of all types.
All schedules for activities on the inventory beacon are interpreted as local time on each inventory beacon.
- A list of all the schedules that have so far been configured for connections managed from this inventory beacon.
- A single row for collecting activities that have not yet been scheduled. Use the
(+) expander on the left of the row to display those
connections that have not yet been linked to a schedule.Tip: You can temporarily disable any data-gathering connection from its own page by selecting the Not scheduled setting for its schedule.Note: For a beacon co-installed on your central batch server, all connections (other than to Active Directory) always show as Not scheduled by the internal inventory beacon scheduling engine. This is because, on the batch server, all connections are triggered by Windows Task Scheduler, and must be managed through that system interface.
- Create an additional schedule (see Creating a Data Gathering Schedule)
- Edit an existing schedule to modify its timing
- Delete a schedule so that it is no longer available on this inventory beaconTip: Activities linked to a deleted schedule automatically move to the Not scheduled collection.
- Trigger a schedule immediately, so that all its associated activities run
nowTip: Individual connections can be triggered for immediate execution from their respective pages.
From this page, you cannot link a schedule to a particular data-gathering connection. Do that from the appropriate page for the connection type.
These columns are available for each schedule:
Column | Notes |
---|---|
+ | An expander. Click to reveal a separate list of the connections (activities) that are already linked to this schedule. |
Name | The distinguishing name given to this schedule as it was created. The name remains editable after the schedule is in use. |
Summary | A system-generated (non-editable) text summary of the settings recorded for this schedule. |
Next run at | The next scheduled trigger time for this schedule (plus a small randomization window, typically one minute). |
Last run at | The time stamp for when this schedule most recently triggered data collection. Remains blank for schedules that have not yet executed any attached activities. |
When you click an expander, a sub-list is revealed of the connections (or activities) that are attached to this schedule. Each sub-list contains these columns:
Column | Notes |
---|---|
Connection name | The name given to this connection when it was created. |
Type | The kind of connection, including inventory imports (from non-FlexNet systems), business data imports, and so on, covering all types of connection that this inventory beacon can manage. |
Last run at | The time stamp for when this connector was most recently exercised. Remains blank for connectors that have not yet been executed. The value often matches the same column in the parent schedule; but this separate entry allows you to track connectors recently attached to a different schedule, triggered with a Run now button for an unscheduled execution, and so on. |
FlexNet Manager Suite (On-Premises)
2020 R2