Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Behaviour of the "Immediate" task schedule

Status
Not open for further replies.

simonjcook

IS-IT--Management
Mar 2, 2004
94
GB
As I recall, under ePO 1.1 the immediate task schedule would execute the task on every ASCI (Agent to Server Connection Interval).

Under ePO 2.5.1 I have observed that the immediate task only seems to execute once. In much the same manner as the "Once" task schedule.

Can anyone confirm this behaviour and whether it is present in ePO 3.x?

Background information:
An immediate AutoUpgrade task was set-up to point to a share which would hold the latest SuperExtraDat (renamed setup.exe) along with the pkgdesc.ini and setup.iss.
The task is disabled by default. In the event of an Extra dat release we would replace the setup.exe with the current superextradat, enable the task and send an agent wake-up call to all the nodes. Once the majority had applied the extra dat, the task would be disabled.
 
Immediate will run once at the next ASCI. Once will run whenever the schedule says it will (w/ random and all that stuff).

I have my daily DAT Update task that I don't change. If a DAT comes out for a medium virus I add a task to update DATs immediately. Once the PCs have refreshed their policy I deleted the immediate task.
 
Have you tried disabling and re-enabling it at a later date?

It is my belief that you can't reuse a task set up on an immediate schedule, is that your experience?

 
Haven't tried disabling / re-enabling.

Your belief and my experience are the same. Once a immediate task is run it will not run again.

I have just found it easier to make another task for unscheduled updates.

I might be dumb and doing it the hard way but that is the best way I have found so far.
 
Ok, we have established between us that this is how the immediate task schedule behaves. The next point is, do you believe it should behave in that manner?

It does not seem to be a logical behaviour.

We have 3 ePO servers running at least 2 products each. That means that 6 immediate tasks have to be set-up every time we want to push the extra dat.

It would be far simpler to disable the tasks until they are needed again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top