Forgive me if this is already answered… my google fu is off lately.
I have a single custom action that runs an ActionScript against all of my servers and it applies various settings. I’d like this action to run against all of the servers on a weekly basis, but I can’t seem to figure out how. It runs once, but then never again. The idea is that if a server is moved from one group to another, the settings would be updated accordingly but this doesnt happen as apparently once the action runs, it is no longer relevant to that server. I’ve got my action setup as:
Messages
No user interface will be shown before running this action.
No message will be shown while running this action.
Users
This action will run independently of user presence.
User interface will be shown to all users.
Execution
This action will never expire.
It will run at any time of day, on any day of the week.
If the action becomes relevant after it has successfully executed, the action will be reapplied as a policy an unlimited number of times.
If the action fails, it will be retried up to 3 times, waiting until the computer is rebooted between attempts.
Post-Action
No operations will occur after the action completes.
Wouldn’t this work for you?
If it is showing as no longer relevant, then you need to fix the content to become relevant again, or remove relevance that causes it to become non-relevant.
If it is just a task to run weekly, remove the relevance and have it apply to all systems, or add relevance to apply to just windows systems. Whatever floats your boat.
Based on this, it’s clear the issue isn’t with the action execution settings, it’s likely due to the detection (relevance) logic.
In such scenarios, where you expect the action to become relevant again after a change, you should directly test your relevance statement on a device where the action is no longer relevant. This helps identify whether the logic is truly dynamic and correctly reflects the new conditions.
The “If the action becomes relevant after it has successfully executed, the action will be reapplied as a policy an unlimited number of times.” - means that the “Relevance” statement of the content should be Dynamic - When relevant it will return TRUE and after completing successfully it will return FALSE.
When you create content by default, the Relevant statement is TRUE - because of that the previous configuration won’t work.
If you want to leave the TRUE relevance statement - you can use what @D.Dean suggested
