Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 990
  • Last Modified:

PST Capture - Cant set destination mailbox on Office365

Hi

I have set up a PSTcapture agent and console on the same domain-joined 64bit Windows7 PC with Outlook 2010 64bit.

In tools \ settings i have successfully authenticated on our Office 365 server podXXXXX.outlook.com and got a green tick. I have also tried smtp.office365.com and outlook.Offcie365.com as per some suggestions on help threads.

The problem is that when i try to set the destination mailbox, i get the following message:

The central Service is retrieving the mailbox data, try again in a moment

The Office 365 account i am using is a tennant admin.
Any suggestions? should any particular firewall ports be open?

thanks

m
0
mk112233
Asked:
mk112233
  • 10
  • 6
1 Solution
 
mk112233Author Commented:
getting the following error in the PSTcapture logs

 |MSOnline365Helper   |5  |Error in CreateSession :
14:16:16.543|Error  |MSOnline365Helper   |5  |[ps.outlook.com] Connecting to remote server ps.outlook.com failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
14:16:16.902|Verbose|MSOnline365Helper   |5  |CheckSessionState  : recreateSession = True & MsOnline365Helper.O365Session.IsNull = True
14:16:16.918|Verbose|MSOnline365Helper   |5  |DisposeSession : Called
14:16:16.918|Verbose|MSOnline365Helper   |5  |CreateSession :  Called
14:16:16.918|Verbose|MSOnline365Helpe
0
 
Vasil Michev (MVP)Commented:
Can you manually connect to EO via PowerShell (http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx)? Do you have proxy configured in your network?
0
 
mk112233Author Commented:
Hi,

i get could not be found on your link, but if you are referring to this command:
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

i get the following output:

PS U:\> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/
 -Credential $LiveCred -Authentication Basic -AllowRedirection
New-PSSession : [ps.outlook.com] Connecting to remote server ps.outlook.com failed with the following error message :
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible
over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer.
By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local
subnet. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:12
+ $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ht ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
PS U:\>
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
Vasil Michev (MVP)Commented:
Yup, seems like a general connectivity issue. Make sure your company firewall is not blocking any EO related traffic (URLs and ports here: http://technet.microsoft.com/library/hh373144.aspx). If you are behind a proxy, configure powershell to use it with the following:

netsh winhttp set proxy proxy-server="http=myproxy;https=sproxy:88" bypass-list="*.foo.com"
0
 
mk112233Author Commented:
i am logged in as a domain users who is also the service user in PSTcapture. The user is a local admin, but has no special on-premise exchange permissions, since i am not dealing with on-premise exchange. the exercise is a proof of concept, to see if PSTcapture can help us import PSTs into our Office365 tennat.

We have a proxy. we recently changed to using a pac file proxy config (automatic script http://proxypac/proxy.pac). but im getting the same results with the old and new proxy settings. Are there any particular exceptions that should be set up on the proxy for this particular process? Office 365 outlook disciovery and functionality works fine with the pac file.

ps.outlook.com does not resolve on any of the 4 Internet connections i tested it on port 80, but in Google Chrome it redirects to https 443

Are there any external firewall rules i need to set up? this is a restricted environment so most things are disabled unless specifically enabled.

Thanks

m
0
 
mk112233Author Commented:
thanks, is there a variation of this command for the PAC file, as per my previous post?

netsh winhttp set proxy proxy-server="http=myproxy;https=sproxy:88" bypass-list="*.foo.com"
0
 
mk112233Author Commented:
getting the same error message after manually adding the proxy setting using http=myproxy;https=sproxy:88" bypass-list="*.foo.com
0
 
Vasil Michev (MVP)Commented:
I'm not really sure how to use PAC file directly with winhttp, although according to this article it should be possible: http://msdn.microsoft.com/en-us/library/aa384240.aspx

Just get the correct proxy settings that need to be used from the PAC file and set them up.
0
 
mk112233Author Commented:
The Pac file contains the same proxy settings as what i set up yesterday - it did not resolve the problem.

i.e the command was successful, but the followup session error was the same:

 -Credential $LiveCred -Authentication Basic -AllowRedirection
New-PSSession : [ps.outlook.com] Connecting to remote server ps.outlook.com failed with the following error message :
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible
over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer.
By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local
subnet. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:12
+ $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ht ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
0
 
mk112233Author Commented:
got a slightly different error message when not using https:

PS C:\Windows\system32> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ps.outlook.com
ershell -Credential $LiveCred -Authentication Basic -AllowRedirection
New-PSSession : Relative URIs are not supported in the creation of remote sessions.
At line:1 char:12
+ $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ps ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (ps.outlook.com/powershell:Uri) [New-PSSession], NotSupportedExceptio
    + FullyQualifiedErrorId : CreateRemoteRunspaceFailed,Microsoft.PowerShell.Commands.NewPSSessionCommand
0
 
mk112233Author Commented:
Ok, i can confirm my proxy is working in PowerShell. i'm able to import settings from IE
netsh winhttp import proxy source=ie

then successfully connect to office 365

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection


but this command still fails as above:
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ps.outlook.com/powershell -Credential $LiveCred -Authentication Basic –AllowRedirection
0
 
Vasil Michev (MVP)Commented:
You are using the old ConnectionURI, try with this one:

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Open in new window



http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx



Yup, this is the correct one, ignore the other one.
0
 
mk112233Author Commented:
Ok, i can now see the sist of mailboxes - THANK YOU!!

The import is extremely slow - i am importing a single 250mb pst file into a single o365 mailbox and its moving at 1-2 messages per minute, approx 3.5mb per minute. We need to move around 500 mailboxes over 1gb in size... is there anything that can be done to speed this up?
0
 
Vasil Michev (MVP)Commented:
Depends on many factors, including throttling on MS side. Overall, you will probably get better results during the night and over the weekend. You can however run the PST Capture tool on multiple machines to speed things up a bit :)

For general migration performance factors you can refer to this article: http://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
0
 
mk112233Author Commented:
Thanks! apart from running PSTcapture on multiple machines, are there any other practical tips you can give me? the article you sent me is quite theoretical
0
 
Vasil Michev (MVP)Commented:
The article is to set your expectations (0.5 GB per client per hour if you are lucky). PST migration is not really the best option, but at least it's fairly automated.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 10
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now