Configuring access to Office 365 through a proxy server
If the migration environment needs to use a web proxy to access HTTP or HTTPS sites on the internet, then the Office 365 module needs to be configured to also route traffic that way.
1.Log in to the server or workstation where the Office 365 Module is currently deployed using the account that is used to run the Archive ShuttleOffice 365 Service.
2.Browse to the folder where the module is installed, and locate the file ArchiveShuttle.Module.Office365.exe.config and open it in a text edit.
You can choose set the proxy configuration for the Offfice 365 Module by inheriting the config from either IEConfig, AutoDetect, WinHTTP or by specifying a web proxy URI in the config file.
a. By inheriting the config from either IEConfig, AutoDetect, WinHTTP
3.Remove the <!-- from the beginning of the line containing the <add key="ProxyAccessType" value="None"/> and remove the --> from the end of the line:
<!-- ProxyAccessType needs to be set occasionally. Following are valid options:
None (default), IEConfig, AutoDetect, WinHttpConfig, NoProxyServer -->
<!--<add key="ProxyAccessType" value="None"/> -->
4.Set the ProxyAccessType value to be one of:
·IEConfig
·AutoDetect
·WinHttpConfig
·NoProxyServer
See this Microsoft article for correct usage.
5. Save and close ArchiveShuttle.Module.Office365.exe.config file.
6. Restart the Office 365 Module service.
b. Specifying web proxy URI
3. Remove the <!-- from the beginning of the line containing the defaultProxy and remove the --> from the end of the line:
<system.net>
<defaultProxy enabled="true" useDefaultCredentials="true">
<proxy bypassonlocal="True" usesystemdefault="True"/>
</defaultProxy>
<connectionManagement>
<add address="*" maxconnection="500"/>
</connectionManagement>
<!--<defaultProxy useDefaultCredentials="true">
<proxy bypassonlocal="true" usesystemdefault="true" proxyaddress=http://192.168.1.20:8080 />
</defaultProxy>-->
</system.net>
4.Update the required proxyaddress URI to use. Then, save and close ArchiveShuttle.Module.Office365.exe.config file.
5.Restart the Office 365 Module service.
See this Microsoft article for correct usage.
Force configuration of proxy settings
In some environments, even when a proxy server is configured in the Archive Shuttle installer, there are still problems with connectivity. These problems are either between the module and the Core, or the module and a cloud service (e.g. Office 365).
It is possible in some situations to force all traffic through a proxy configuration. The first step is to ensure that Microsoft Edge works as expected.
From Microsoft Edge configuration, we can verify if the Proxy setting are configured. Go to Start > Control Panel > search 'Internet options' > Connections (Tab) > LAN settings > Proxy server:
To check the proxy setting, issue following command:
netsh winhttp show proxy
Then, issue the following command:
netsh winhttp import proxy source=ie
If you are installing the Archive Shuttle modules where communication to the Core is via a proxy, review this page for more details. This will help in situations where:
1. Using a proxy on a bridgehead server
When PowerShell tries to connect to Office 365 or Azure, it may not be able to connect. It does not follow the Microsoft Edge proxy settings.
2. If a proxy PAC script is used in Microsoft Edge
In this case, the installation of Archive Shuttle modules will likely fail.
Enterprise Vault installation scenarios
The following topics give some example installations showing which components are installed on which servers.
Enterprise Vault to Enterprise Vault - cross site
The following diagram shows one possibility of where the Archive Shuttle modules can be installed in order to support the migration of Enterprise Vault archives between Enterprise Vault sites. This scenario can also be used to migrate archived data between Enterprise Vault servers and Vault Stores in the same Enterprise Vault site.
The migration configuration shown will also support migration between different versions of Enterprise Vault. This is possible because the EV Export Module is installed on a source EV server, and the EV Import Module is installed on a target EV server.
