Skip to content
Go to k12panel.com
  • There are no suggestions because the search field is empty.

Running a Modifier Now

You don't have to wait for a computer's next regular check-in to see what a modifier does. From an asset's detail page, you can tell the computer to check in right away and run one modifier, and nothing else. It's a quick way to try a new or changed modifier on a single computer, or to retry a modifier after you fix what was blocking it.

What you need

  • Role: Manager or higher. To read the results on the Modifier Reports tab, you need Modifier or higher.
  • License: an organization licensed for Core+Deploy.
  • Computer: a Windows computer with the Panel Service Agent installed that can receive Quick Commands. If the asset page shows a Command button, the computer can receive them.
  • Asset state: Active or Inactive.

Run a modifier now

  1. Open the asset's detail page.
  2. Scroll to Asset-Scoped Modifiers in order of Execution at the bottom of the page. You can also click Modifier Execution Order under On this page.
  3. Click the play button next to the modifier you want to run.
  4. Read the confirmation, then click Run Now.

K12Panel confirms that the run is queued and returns you to the modifier list. A Force Poll command appears in the asset's Quick Commands list while it waits for the computer.

What happens on the computer

The computer receives a Force Poll that carries only the modifier you chose. It then runs that modifier just as it would during a normal check-in:

  1. The modifier's validator runs first to check whether any work is needed.
  2. If work is needed, the computer downloads any payload and runs the worker.
  3. The validator runs again to confirm the result.

If the validator reports that nothing needs to be done, the worker doesn't run and nothing is downloaded.

During that one check-in, every other modifier is skipped, and so are K12Panel's own background tasks, such as hardware and software inventory. They all run again at the computer's next regular check-in.

Note: A Force Poll command expires after 10 minutes. If the computer is off or offline during that time, nothing runs, and K12Panel doesn't try again later.

Results

A forced run is reported just like a regular one. Open the asset's Modifier Reports tab to see the validator results and the worker's report. The run also counts toward the modifier's history on that asset.

Suspended modifiers

A modifier is suspended on an asset after it fails five times in a row, and then it stops running at regular check-ins. Running a modifier now runs it even if it's suspended. This lets you check whether you've fixed the problem before you clear the suspension.

  • Running a suspended modifier doesn't clear the suspension. Clear it from the asset's Modifier Reports tab, or from the Modifiers page, once the modifier succeeds.
  • A failed forced run counts toward the modifier's failures in a row, just like a regular run.

The confirmation dialog tells you when the modifier is suspended on that asset.

Inactive assets

Modifiers don't run on Inactive assets at regular check-ins. Running a modifier now does run it on an Inactive asset, as long as the computer is on and can receive commands. This is useful for testing a modifier on a spare or test computer without making it Active.

When the play button doesn't appear

  • Person modifiers: modifiers that run for the signed-in user don't have a play button. Only asset modifiers can be run this way.
  • The computer can't receive commands: the agent isn't installed, hasn't checked in yet, or is too old. The Command button is missing from the asset page too.
  • The asset is Archived or in the Trashcan.
  • Your organization isn't licensed for Core+Deploy.
  • Your role is below Manager.

Common Questions

Does running a modifier now change the modifier or its asset groups? No. It's a one-time run on one computer. The modifier, its properties, and its asset groups don't change.

Does it download the payload every time? No. The payload is downloaded only when the validator reports that work is needed and the worker is going to run.

Why didn't my other modifiers run at the same time? A forced check-in carries only the modifier you chose. Everything else runs at the computer's next regular check-in, usually within a few minutes.

The Force Poll command shows as Expired. What happened? The computer didn't pick up the command within 10 minutes, usually because it was off or offline. Turn the computer on, make sure it's connected, and click the play button again.

Can I run a modifier on many computers at once this way? No. The play button runs a modifier on one asset. To run a modifier on many computers, add it to an asset group. It runs on each computer at its next check-in.

I don't see any results on Modifier Reports. Give the computer a minute to finish the run, then reload the page. The Modifier Reports tab appears for Modifiers and above once the asset has at least one report. If the Force Poll command expired, the modifier didn't run.

Who can use it? Managers and above, in organizations licensed for Core+Deploy.