If a dedicated Proxy server is being used in the environment there are some configuration changes that may have to be made.
To get the application to connect to Office 365, the netsh command should be used to set the proxy. For example if the proxy settings are configured in Internet Explorer you would run the following command in PowerShell to have it use the same proxy:
netsh winhttp import proxy source=ie
If you are running a 64 Bit Operating System
If you are running a 64 bit operating system, then you need to make sure you run the netsh command in the 32 bit version of PowerShell as that is what the Migrator uses to connect to remote powershell.
To do that, start the 32 bit version of powershell using C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe or there should be a shortcut for Powershell (x86) in Accessories\Windows Powershell and run the same netsh command.
netsh winhttp import proxy source=ie
Advanced Proxy Configuration
In most cases setting the proxy value with netsh should work, but if it doesn’t you can modify the application configuration files as described below.
In the C:\Program Files\MessageOps\MessageOps Exchange Migrator directory there should be a file called MOExMigrator.exe.config
If you open this file you should be able to add setting that tell the application to use the default proxy.
<configuration>
<system.net>
<defaultProxy>
<proxy bypassonlocal=”false” usesystemdefault=”true” />
</defaultProxy>
</system.net>
</configuration>
If that doesn’t work you can also try specifying the proxy to use
<configuration>
<system.net>
<defaultProxy enabled=”true”>
<proxy proxyaddress=”http://proxyserver:8080″/>
</defaultProxy>
</system.net>
</configuration>
Updated: April 16, 2016