Archive Assistant not working with %APPDATA% being redirected via GPO to a network share

Versions / Builds Affected

Any

Status

Open

Problem Summary

Archive Assistant not working with %APPDATA% being redirected via GPO to a network share

TT / JIRAID

1702

How to Identify

The Archive Assistant appears to not register / work at all if the user's %APPDATA% directory is redirected (via GPO) to a network share. Symptoms: 1. A user installs the AA and the installation completes without errors 2. When the user opens Outlook the AA's buttons do not appear in Outlook nor does it show under the Addins list in Outlook To check if %appdata% is redirected run "SET APPDATA" while logged into the affected machine with the affected user. It will show the variable set to a UNC path / a network share rather than a local path. You can also check the GPO itself.

Workaround / Fix Details

The Archive Assistant can also be registered manually. This can be tied together in logon scripts for automation in general. If a customer uses this procedure to roll out the Archive Assistant to multiple users it will have a negative impact on topics like maintainance, upgradability and troubleshooting. This should not be performed unless the full impact is clear to everyone involved. If considered please discuss the situation with a Product Specialist before implementation. Article 7745 option 2 explains how what needs to be done.

Required Actions

Development confirmed this as a limitation of the Archive Assistant and this situation is currently handled as a feature request. If a customer opens a case with this topic stress to him that this is a limitation and handled as a feature request. Unless a customer pushes for a solution, I suggest not to even mention the possibility of manually registering the Archive Assistant.