Functionally, they are identical. The button is actually a link to the folder, which is in turn a link to the Netmail Search portalwebpage.
The button will always be visible if the Add-in is successfully loaded, however the folder may be hidden by the administrator. The option to do this is in C:\IISext\webcontent\config.xml on the Exchange server(s). Bear in mind that changing it on Exchange within that file will apply it to the whole organization, not just a workstationsingle user.
The recommended practice is to hide the folder and leave the button as the only method of to access to the archives within the Outlook client. The motivations for this are two-fold:
- Microsoft has acknowledged that there is a bug in Outlook which may cause the Netmail folder not to not display. This problem is exacerbated by accounts which already have a large number of folders. Restarting Outlook will eventually solve the problem, but this is not a pleasant user experience.
- Users may believe that the Netmail folder is a mechanism by which they can archive their items. Unfortunately items dragged into the folder will not be archived; in fact they will be destroyed along actually be destroyed (together with the folder) when Outlook exits and the Add-in is unloaded and Outlook is shutdown. Again, this is not a pleasant user experience.
After install, the first time the Add-in is loaded it will prompt for credentials. This are the same credentials used to log-in to Netmail Search (ieeg. the domain credentials). Once entered, the credentials are cached in the registry at HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook\Messaging Architects.
When the button/folder are clicked, the Add-in will contact the Remote Provider (aka. Netmail Search) and provide the credentials from the registry cache. If they are accepted, the archives for the user are displayed. If the credentials are rejected then the Add-in will return to prompt the user for new credentials to try.
How to deploy in Office 365 environments?
Within an Office 365 environment the The main obstacle is serving up the config.xml from a web server. Normally this is achieved using the With Exchange on-prem deployments this file is served by IIS on the Exchange serverservers, but since this may not exist in a hosted an Office 365 environment, another solution must be found. Any web server in the environment may be a substitute, and the corresponding URL can be provided to the Add-in at install-time. Entering that URL into a browser should return the config.xml file.
For example, assume an Apache server at 10.20.30.40 and the config.xml file in a folder \netmail. If http://10.20.30.40/netmail/config.xml opens the file in the browser, then this is also a valid URL for the Add-in installer. In In most cases, the Netmail Search server itself can be used to serve up this file. Just place the config.xml in ..\RemoteProvider\WebContent\ and point the Add-ins to http://NetmailSearchIP:8888/