ITAA - Incompatibility with Standard Enterprise GPO Security Policies

Greetings,

The root cause of this issue has been identified as an architectural dependency on a third-party component used internally by ITAA, which enforces specific Windows GPO requirements. These requirements conflict with standard enterprise security baselines, making ITAA's web encapsulated remote access unusable in hardened server environments without relaxing security policies.

As a product enhancement, we request that the AVEVA team evaluate the following approaches:

1. Replace or abstract the third-party dependency so that ITAA's web client no longer enforces GPO requirements that conflict with common enterprise security standards.

2. Provide granular documentation identifying exactly which local security policies are affected, so that customers and administrators can make informed, targeted adjustments rather than broad policy relaxations.

3. Introduce a compatibility validation tool or checklist that can be run preinstallation to detect conflicting GPO settings and suggest the minimum required changes.

The ability to run ITAA in environments with standard enterprise security hardening is a baseline expectation for enterprise deployments. Addressing this dependency would directly improve the platform's viability in regulated or security-conscious environments, which represent a significant portion of the industrial automation market.

Kind Regards,