Dynamic Groups, Scheduled Tasks, Group Families, Automation Workflows, and/or pending Temporal Group Management operations are not functioning after an Active Roles upgrade (4336484)

Dynamic Groups have their Service to evaluate and apply rule changes set to unknown after an upgrade. This causes some Dynamic Group functionality to not operate as expected.

Scheduled Tasks have their Execute On cleared after an upgrade. This causes Scheduled Tasks to not function as expected.

Group Families have their Run on this server cleared after an upgrade.

Scheduled Automation Workflows do not execute as scheduled.

Pending Temporal Group operations are not performed as expected.

STATUS

For Dynamic Groups, Scheduled Tasks, and Group Family Groups, this issue has been resolved as of Active Roles 7.4.3. For previous versions, please follow the workarounds as noted below.

To resolve this issue with Temporal Group operations, please follow Workaround 1 below.

NOTE: Although this issue should be resolved by following the prompts in the Active Roles Configuration Wizard in Active Roles 7.4.3 and later, the UpdateServicesToExecute script module created by one of these prompts does not execute as expected. Because of this, please either continue to leverage one of the workarounds below or in the linked solution. It is only necessary to following one of these workarounds.
 

WORKAROUND 1

1. Right-click the container to create a new Script Module named UpdateServiceName.
2. Leave Script Language as PowerShell, and select Next.
3. Under Script Type select Policy script, and select Next.
4. Select Next on Event handler functions: screen.
5. Select Finished.
6. Copy the PowerShell Policy script contents from notepad and paste the contents into the new Script Module, and Save the changes.
7. Create an Automation Workflow and drag the Script basic activity into the workflow.
8. Double-click the Script basic activity, and select the Browse... button on the Script to use: field.
9. The Function to Run should be set to the updateServiceName function.
10. Select the script created, and select OK to confirm and OK to close Script Activity.
11. Select Save Changes on the workflow window to commit the changes.
12. Execute this Workflow by clicking the Run Workflow button  

NOTE: In medium-to-large environments, it may be necessary to increase the default Automation Workflow timeout beyond the default of five minutes in order for this script to complete successfully. This script only needs to be executed once to update the Execute On field for the Scheduled Tasks.

In the Automation Workflow, expand Workflow options and start conditions and click on Configure.

Click on Additional Settings and set the Terminate the workflow if it runs longer than: option to 2 hours (or another appropriate value, if desired).
 

WORKAROUND 2

1. In the Active Roles Console, navigate to Configuration/Policies/Workflow/Builtin
2. Enable the Workflow named Update Services To Execute On by right-clicking on it and choosing Enable Workflow
3. Reconnect in the Active Roles Console by right-clicking on the root node and choosing Reconnect
4. Navigate to Configuration/Policies/Workflow/Builtin and select the Update Services To Execute On Workflow 
5. Execute it by clicking the Run Workflow button  

WORKAROUND 3 -  For Active Roles Automation Workflows

1. Open each affected Automation Workflow in the Active Roles Console.
2. Expand Workflow options and start conditions and click Configure.
3. Set a value in the Run the workflow on the dropdown.