M
Meg
Our issue at hand is with security warnings that appear when an add-in is
accessing Outlook data. e.g. A program is trying to access e-mail address
information . . .
Currently we are using the Outlook Security settings public folder on
Exchange and want to move to using Group Policy. We have set the gp settings
and have set the AdminSecurityMode to display 3: Use the security policy from
the GPO settings and the Addintrust is 0.
When testing the security settings in Group Policy, if there is an
Outlook add-in loaded, and the antivirus has been removed from the pc,
shouldn't the user get the security warning message since it doesn't meet the
criteria of : Antivirus software is installed and shares its status with
third-party software through the WSC?
We are wanting to use the group policy settings so that we can leverage our
antivirus in hopes to alleviate the Security Warning messages that users
receive with various add-ins.
Current environment: Exchange 2007 SP1, RU9, Outlook 2007 SP2, Sophos
antivirus
Articles used: kb926512 and msdn article 226709
Thanks
accessing Outlook data. e.g. A program is trying to access e-mail address
information . . .
Currently we are using the Outlook Security settings public folder on
Exchange and want to move to using Group Policy. We have set the gp settings
and have set the AdminSecurityMode to display 3: Use the security policy from
the GPO settings and the Addintrust is 0.
When testing the security settings in Group Policy, if there is an
Outlook add-in loaded, and the antivirus has been removed from the pc,
shouldn't the user get the security warning message since it doesn't meet the
criteria of : Antivirus software is installed and shares its status with
third-party software through the WSC?
We are wanting to use the group policy settings so that we can leverage our
antivirus in hopes to alleviate the Security Warning messages that users
receive with various add-ins.
Current environment: Exchange 2007 SP1, RU9, Outlook 2007 SP2, Sophos
antivirus
Articles used: kb926512 and msdn article 226709
Thanks