Environment
- App Control: All Supported Versions
- Microsoft Windows: All Supported Versions
Symptoms
- Blocks of login scripts where AD groups are selected as the applicable target
- Blocks of software that loads very early in the boot process
Cause
There is a brief delay after a user logs in before group membership is established and group-based rules become effective. This delay may be longer if you have a large number of rules
Resolution
If a rule must be effective as soon as possible after a user logs on, do not specify a user group in the rule. Rules that specify a username or SID are always active and won't be affected by this delay
Additional Notes
Further information on creating custom rules can be found in the User Guides
here
Related Content