Some customers might be tempted to leverage Active Roles in order to organize and execute custom script modules which execute 3rd party utilities or perform advanced operations against Active Directory.
For example, an Active Directory replication status check.
This is not a supported or recommended practice, and could compromise the integrity and reliability of the Active Roles solution.
The Active Roles process encapsulates a PowerShell runspace, and executing large or complicated external applications within as scheduled tasks causes Active Roles to share internal process resources which are better suited for managing Active Directory.
External applications should be triggered as Windows Scheduled Tasks. In this way, they will get their own PowerShell runspace, separate from Active Roles.