Hi ,

When we do pst migration via import pst it doesnt move the nk2 file. Is it suggested to copy & paste pst at the new specified Exchange Online address? 

Definately feeling a sense of accomplishment.. I have migrated 99.9% of my on premesis Exchnge 2007 users to their Cloud accounts.

I have taken down all Autodiscover A DNS records and replaced them with CNAME

I have a few questions

1 - The script that converts mailbox users to mail enabled users dies if the Legacy Exchange DN contains a comma... I cant believe no one has reported this before.  I'll have to change the Import-CSV portion of the 2nd script.

2 - We have SSIS packages, C# programs, SQL Mail etc.. that used to connect to our exchange servers to send mail via SMTP... How does that work now?

3 - We have an on premesis SharePoint 2007 site.. for the life of me I cannot get our Public Folders - Shared Contacts to copy into a SharePoint Contact list.  How do people do it? 

4 - When we have new people who need email accounts, do we still have to create for them local Exchange mailboxes while our Exchange servers are still online?  I tried to just create them in Active Directory, but could not get them to interop via email with rest of office

5 - Is there a Shared Calender, or should we divert to SharePoint for that?

6 - When some users were in their Exchange 2007 modes, some of them had their delivery options set to forward copies of emails to other people.. do these settings follow them?

We have recently enabled a hybrid deployment for our Exchange Organization utilizing Office365.  I used the Hybrid Deployment Wizard in Exchange 2010 sp2 and we are able to email back and forth between Office365 based users and on premise users (they all have the same smtp domain) but when I send from outside the organization to a cloud based mailbox, I get a no such user.

The MX records are pointed at our on premise mail servers.  

For example:

User A is on premise with address usera@domain.com

User B is on Office 365 with address userb@domain.com 

A can email B

B can email A

A can email external domains

B can email external domains

External domains can email A

External domains get a no such user when they email B

Any insight would appreciated!

Thanks!

Hi guys,

The wizard failed, I tried run it from different exchange servers and always the same issue.

Can anyone check the log below and tell me what can be the issue?

[2/15/2013 22:32:25] INFO:Opening runspace to http://xxxx/powershell?serializationLevel=Full

[2/15/2013 22:32:26] INFO:Successfully connected to On-Premises

[2/15/2013 22:32:26] INFO:Opening runspace to https://ps.outlook.com/powershell-liveid?serializationLevel=Full

[2/15/2013 22:32:29] INFO:Successfully connected to Tenant

[2/15/2013 22:32:29] INFO:Executing Task: Check Prerequisites

[2/15/2013 22:32:29] INFO:Check Prerequisites state

[2/15/2013 22:32:29] INFO:Running command: Get-AcceptedDomain

[2/15/2013 22:32:29] INFO:Cmdlet: Get-AcceptedDomain --Start Time: 2/15/2013 5:32:29 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --End Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --Processing Time: 921.8632.

[2/15/2013 22:32:30] INFO:Running command: Get-AcceptedDomain

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --Start Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --End Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --Processing Time: 78.124.

[2/15/2013 22:32:30] INFO:Running command: Get-AcceptedDomain

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --Start Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --End Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-AcceptedDomain --Processing Time: 78.124.

[2/15/2013 22:32:30] INFO:Running command: Get-OrganizationRelationship

[2/15/2013 22:32:30] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 31.2496.

[2/15/2013 22:32:30] INFO:Running command: Get-OrganizationRelationship

[2/15/2013 22:32:30] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 78.124.

[2/15/2013 22:32:30] INFO:Running command: Get-ExchangeServer -Identity 'xxx01'

[2/15/2013 22:32:30] INFO:Cmdlet: Get-ExchangeServer --Start Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-ExchangeServer --End Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:30] INFO:Cmdlet: Get-ExchangeServer --Processing Time: 62.4992.

[2/15/2013 22:32:30] INFO:Running command: Get-WebServicesVirtualDirectory -Server 'xxxx02'

[2/15/2013 22:32:30] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Start Time: 2/15/2013 5:32:30 PM.

[2/15/2013 22:32:32] INFO:Cmdlet: Get-WebServicesVirtualDirectory --End Time: 2/15/2013 5:32:32 PM.

[2/15/2013 22:32:32] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Processing Time: 1734.3528.

[2/15/2013 22:32:32] INFO:Running command: Get-ExchangeCertificate -Server 'xxx03'

[2/15/2013 22:32:32] INFO:Cmdlet: Get-ExchangeCertificate --Start Time: 2/15/2013 5:32:32 PM.

[2/15/2013 22:32:33] INFO:Cmdlet: Get-ExchangeCertificate --End Time: 2/15/2013 5:32:33 PM.

[2/15/2013 22:32:33] INFO:Cmdlet: Get-ExchangeCertificate --Processing Time: 515.6184.

[2/15/2013 22:32:33] INFO:Running command: Get-ExchangeServer -Identity 'xxxxx'

[2/15/2013 22:32:33] INFO:Cmdlet: Get-ExchangeServer --Start Time: 2/15/2013 5:32:33 PM.

[2/15/2013 22:32:33] INFO:Cmdlet: Get-ExchangeServer --End Time: 2/15/2013 5:32:33 PM.

[2/15/2013 22:32:33] INFO:Cmdlet: Get-ExchangeServer --Processing Time: 62.4992.

[2/15/2013 22:32:33] INFO:Running command: Get-WebServicesVirtualDirectory -Server 'xxxxx'

[2/15/2013 22:32:33] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Start Time: 2/15/2013 5:32:33 PM.

[2/15/2013 22:32:33] INFO:Cmdlet: Get-WebServicesVirtualDirectory --End Time: 2/15/2013 5:32:33 PM.

[2/15/2013 22:32:33] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Processing Time: 343.7456.

[2/15/2013 22:32:33] INFO:Running command: Get-ExchangeCertificate -Server 'xxx'

[2/15/2013 22:32:33] INFO:Cmdlet: Get-ExchangeCertificate --Start Time: 2/15/2013 5:32:33 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeCertificate --End Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeCertificate --Processing Time: 1312.4832.

[2/15/2013 22:32:35] INFO:Running command: Get-ExchangeServer -Identity 'xxxx'

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeServer --Start Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeServer --End Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeServer --Processing Time: 62.4992.

[2/15/2013 22:32:35] INFO:Running command: Get-WebServicesVirtualDirectory -Server 'xxxxx'

[2/15/2013 22:32:35] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Start Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-WebServicesVirtualDirectory --End Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Processing Time: 453.1192.

[2/15/2013 22:32:35] INFO:Running command: Get-ExchangeCertificate -Server 'xxxxx'

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeCertificate --Start Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeCertificate --End Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeCertificate --Processing Time: 203.1224.

[2/15/2013 22:32:35] INFO:Needs Configuration state

[2/15/2013 22:32:35] INFO:Configuration not required

[2/15/2013 22:32:35] INFO:Executing Task: Configure Legacy Exchange Support

[2/15/2013 22:32:35] INFO:Check Prerequisites state

[2/15/2013 22:32:35] INFO:Needs Configuration state

[2/15/2013 22:32:35] INFO:Running command: Get-ExchangeServer

[2/15/2013 22:32:35] INFO:Cmdlet: Get-ExchangeServer --Start Time: 2/15/2013 5:32:35 PM.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-ExchangeServer --End Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-ExchangeServer --Processing Time: 140.6232.

[2/15/2013 22:32:36] INFO:Running command: Get-PublicFolderDatabase -Server 'A11OWA01'

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] ERROR:System.Management.Automation.RemoteException: 'xxxxx' does not have the right Exchange Server version or role required to support this operation.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 93.7488.

[2/15/2013 22:32:36] INFO:Running command: Get-PublicFolderDatabase -Server 'xxxx'

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] ERROR:System.Management.Automation.RemoteException: 'xxxxx' does not have the right Exchange Server version or role required to support this operation.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 46.8744.

[2/15/2013 22:32:36] INFO:Running command: Get-PublicFolderDatabase -Server 'xxxx'

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] ERROR:System.Management.Automation.RemoteException: 'xxxx' does not have the right Exchange Server version or role required to support this operation.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 31.2496.

[2/15/2013 22:32:36] INFO:Running command: Get-PublicFolderDatabase -Server 'xxxx'

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 78.124.

[2/15/2013 22:32:36] INFO:Running command: Get-PublicFolder -Identity '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' -Server 'xxxx' -Recurse ''

[2/15/2013 22:32:36] INFO:Cmdlet: Get-PublicFolder --Start Time: 2/15/2013 5:32:36 PM.

[2/15/2013 22:32:37] INFO:Cmdlet: Get-PublicFolder --End Time: 2/15/2013 5:32:37 PM.

[2/15/2013 22:32:37] INFO:Cmdlet: Get-PublicFolder --Processing Time: 828.1144.

[2/15/2013 22:32:37] INFO:Configuration state

[2/15/2013 22:32:37] INFO:Calling Install-FreeBusyFolder

[2/15/2013 22:32:37] INFO:Install-FreeBusyFolder completed

[2/15/2013 22:32:37] INFO:Verify Configuration state

[2/15/2013 22:32:37] INFO:Running command: Get-ExchangeServer

[2/15/2013 22:32:37] INFO:Cmdlet: Get-ExchangeServer --Start Time: 2/15/2013 5:32:37 PM.

[2/15/2013 22:32:37] INFO:Cmdlet: Get-ExchangeServer --End Time: 2/15/2013 5:32:37 PM.

[2/15/2013 22:32:37] INFO:Cmdlet: Get-ExchangeServer --Processing Time: 109.3736.

[2/15/2013 22:32:37] INFO:Running command: Get-PublicFolderDatabase -Server 'xxxx'

[2/15/2013 22:32:37] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:37 PM.

[2/15/2013 22:32:37] ERROR:System.Management.Automation.RemoteException: 'xxxx' does not have the right Exchange Server version or role required to support this operation.

[2/15/2013 22:32:37] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:37 PM.

[2/15/2013 22:32:37] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 46.8744.

[2/15/2013 22:32:37] INFO:Running command: Get-PublicFolderDatabase -Server 'xxxx'

[2/15/2013 22:32:37] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:37 PM.

[2/15/2013 22:32:38] ERROR:System.Management.Automation.RemoteException: 'xxxx' does not have the right Exchange Server version or role required to support this operation.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 31.2496.

[2/15/2013 22:32:38] INFO:Running command: Get-PublicFolderDatabase -Server 'xxxxx'

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] ERROR:System.Management.Automation.RemoteException: 'xxxxx' does not have the right Exchange Server version or role required to support this operation.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 46.8744.

[2/15/2013 22:32:38] INFO:Running command: Get-PublicFolderDatabase -Server 'xxxx'

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 78.124.

[2/15/2013 22:32:38] INFO:Running command: Get-PublicFolder -Identity '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' -Server 'xxx' -Recurse ''

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolder --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolder --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolder --Processing Time: 265.6216.

[2/15/2013 22:32:38] INFO:Running command: Get-PublicFolderDatabase -Server 'xxx'

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 46.8744.

[2/15/2013 22:32:38] INFO:Executing Task: Configure Recipient Settings

[2/15/2013 22:32:38] INFO:Check Prerequisites state

[2/15/2013 22:32:38] INFO:Needs Configuration state

[2/15/2013 22:32:38] INFO:Running command: Get-RemoteDomain

[2/15/2013 22:32:38] INFO:Cmdlet: Get-RemoteDomain --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-RemoteDomain --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-RemoteDomain --Processing Time: 31.2496.

[2/15/2013 22:32:38] INFO:Running command: Get-EmailAddressPolicy

[2/15/2013 22:32:38] INFO:Cmdlet: Get-EmailAddressPolicy --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-EmailAddressPolicy --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Get-EmailAddressPolicy --Processing Time: 124.9984.

[2/15/2013 22:32:38] INFO:Configuration state

[2/15/2013 22:32:38] INFO:Running command: New-RemoteDomain -Name 'Hybrid Domain - xxxxxx.mail.onmicrosoft.com' -DomainName xxxxxmail.onmicrosoft.com'

[2/15/2013 22:32:38] INFO:Cmdlet: New-RemoteDomain --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: New-RemoteDomain --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: New-RemoteDomain --Processing Time: 93.7488.

[2/15/2013 22:32:38] INFO:Running command: Set-RemoteDomain -Identity 'Hybrid Domain - xxxxxx.mail.onmicrosoft.com' -TargetDeliveryDomain 'True'

[2/15/2013 22:32:38] INFO:Cmdlet: Set-RemoteDomain --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Set-RemoteDomain --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: Set-RemoteDomain --Processing Time: 109.3736.

[2/15/2013 22:32:38] INFO:Running command: New-AcceptedDomain -DomainName 'xxxx.mail.onmicrosoft.com' -Name 'xxxxxx.mail.onmicrosoft.com'

[2/15/2013 22:32:38] INFO:Cmdlet: New-AcceptedDomain --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: New-AcceptedDomain --End Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:38] INFO:Cmdlet: New-AcceptedDomain --Processing Time: 124.9984.

[2/15/2013 22:32:38] INFO:Running command: Get-AcceptedDomain

[2/15/2013 22:32:38] INFO:Cmdlet: Get-AcceptedDomain --Start Time: 2/15/2013 5:32:38 PM.

[2/15/2013 22:32:39] INFO:Cmdlet: Get-AcceptedDomain --End Time: 2/15/2013 5:32:39 PM.

[2/15/2013 22:32:39] INFO:Cmdlet: Get-AcceptedDomain --Processing Time: 46.8744.

[2/15/2013 22:32:39] INFO:Running command: Set-EmailAddressPolicy -Identity 'CN=xxxxxx-EnabledEmailAddressTemplates 'Microsoft.Exchange.Data.ProxyAddressTemplateCollection' -ForceUpgrade 'True'

[2/15/2013 22:32:39] INFO:Cmdlet: Set-EmailAddressPolicy --Start Time: 2/15/2013 5:32:39 PM.

[2/15/2013 22:32:39] INFO:Cmdlet: Set-EmailAddressPolicy --End Time: 2/15/2013 5:32:39 PM.

[2/15/2013 22:32:39] INFO:Cmdlet: Set-EmailAddressPolicy --Processing Time: 249.9968.

[2/15/2013 22:32:39] INFO:Running command: Update-EmailAddressPolicy -Identity 'CN=xxxxx

[2/15/2013 22:32:39] INFO:Cmdlet: Update-EmailAddressPolicy --Start Time: 2/15/2013 5:32:39 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Update-EmailAddressPolicy --End Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Update-EmailAddressPolicy --Processing Time: 9874.8736.

[2/15/2013 22:32:49] INFO:Verify Configuration state

[2/15/2013 22:32:49] INFO:Running command: Get-RemoteDomain

[2/15/2013 22:32:49] INFO:Cmdlet: Get-RemoteDomain --Start Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-RemoteDomain --End Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-RemoteDomain --Processing Time: 31.2496.

[2/15/2013 22:32:49] INFO:Running command: Get-EmailAddressPolicy

[2/15/2013 22:32:49] INFO:Cmdlet: Get-EmailAddressPolicy --Start Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-EmailAddressPolicy --End Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-EmailAddressPolicy --Processing Time: 31.2496.

[2/15/2013 22:32:49] INFO:Executing Task: Creating Organization Relationships.

[2/15/2013 22:32:49] INFO:Check Prerequisites state

[2/15/2013 22:32:49] INFO:Running command: Get-OrganizationalUnit -SingleNodeOnly 'True'

[2/15/2013 22:32:49] INFO:Cmdlet: Get-OrganizationalUnit --Start Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-OrganizationalUnit --End Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-OrganizationalUnit --Processing Time: 140.6232.

[2/15/2013 22:32:49] INFO:Running command: Get-FederationTrust

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederationTrust --Start Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederationTrust --End Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederationTrust --Processing Time: 31.2496.

[2/15/2013 22:32:49] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 31.2496.

[2/15/2013 22:32:49] INFO:Getting Value 'DefaultDomain' from '' with 'Get-FederatedOrganizationIdentifier'

[2/15/2013 22:32:49] INFO:Running command: Get-FederatedOrganizationIdentifier

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:32:49] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 343.7456.

[2/15/2013 22:32:49] INFO:Needs Configuration state

[2/15/2013 22:32:49] INFO:Configuration state

[2/15/2013 22:32:49] INFO:Running command: Enable-OrganizationCustomization

[2/15/2013 22:32:49] INFO:Cmdlet: Enable-OrganizationCustomization --Start Time: 2/15/2013 5:32:49 PM.

[2/15/2013 22:34:27] INFO:Cmdlet: Enable-OrganizationCustomization --End Time: 2/15/2013 5:34:27 PM.

[2/15/2013 22:34:27] INFO:Cmdlet: Enable-OrganizationCustomization --Processing Time: 97858.1224.

[2/15/2013 22:34:27] INFO:Running command: Set-Federationtrust -RefreshMetadata '' -Identity 'Microsoft Federation Gateway'

[2/15/2013 22:34:27] INFO:Cmdlet: Set-Federationtrust --Start Time: 2/15/2013 5:34:27 PM.

[2/15/2013 22:34:27] INFO:Cmdlet: Set-Federationtrust --End Time: 2/15/2013 5:34:27 PM.

[2/15/2013 22:34:27] INFO:Cmdlet: Set-Federationtrust --Processing Time: 109.3736.

[2/15/2013 22:34:27] INFO:Running command: Set-FederatedOrganizationIdentifier -DelegationFederationTrust 'Microsoft Federation Gateway' -AccountNamespace xxxxx -Enabled 'True'

[2/15/2013 22:34:27] INFO:Cmdlet: Set-FederatedOrganizationIdentifier --Start Time: 2/15/2013 5:34:27 PM.

[2/15/2013 22:34:38] INFO:Cmdlet: Set-FederatedOrganizationIdentifier --End Time: 2/15/2013 5:34:38 PM.

[2/15/2013 22:34:38] INFO:Cmdlet: Set-FederatedOrganizationIdentifier --Processing Time: 11015.484.

[2/15/2013 22:34:38] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''

[2/15/2013 22:34:38] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 2/15/2013 5:34:38 PM.

[2/15/2013 22:34:38] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 2/15/2013 5:34:38 PM.

[2/15/2013 22:34:38] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 31.2496.

[2/15/2013 22:34:38] INFO:Running command: Get-FederationTrust -Identity 'Microsoft Federation Gateway'

[2/15/2013 22:34:38] INFO:Cmdlet: Get-FederationTrust --Start Time: 2/15/2013 5:34:38 PM.

[2/15/2013 22:34:38] INFO:Cmdlet: Get-FederationTrust --End Time: 2/15/2013 5:34:38 PM.

[2/15/2013 22:34:38] INFO:Cmdlet: Get-FederationTrust --Processing Time: 31.2496.

[2/15/2013 22:34:38] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''

[2/15/2013 22:34:38] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 2/15/2013 5:34:38 PM.

[2/15/2013 22:34:39] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 2/15/2013 5:34:39 PM.

[2/15/2013 22:34:39] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 124.9984.

[2/15/2013 22:34:39] INFO:Running command: Get-FederationTrust -Identity 'MicrosoftOnline'

[2/15/2013 22:34:39] INFO:Cmdlet: Get-FederationTrust --Start Time: 2/15/2013 5:34:39 PM.

[2/15/2013 22:34:39] INFO:Cmdlet: Get-FederationTrust --End Time: 2/15/2013 5:34:39 PM.

[2/15/2013 22:34:39] INFO:Cmdlet: Get-FederationTrust --Processing Time: 531.2432.

[2/15/2013 22:34:39] INFO:Disconnected from On-Premises session

[2/15/2013 22:34:39] INFO:Disconnected from Tenant session

[2/15/2013 22:34:39] ERROR:Updating hybrid configuration failed with error 'Subtask Configure execution failed: Creating Organization Relationships.

Any one saw the issue before?

Thanks

One of my client is using google apps and we are migrating mailboxes from google apps to office 365. we did all things according method described on microsoft communities. first we created dual delivery to get mails in each mail box every time.

1. We uses Imap migration process with CSV file . everything goes fine but second day i saw in report that most of the mailboxes have problem with skipped items.

2. It is taking too long time to migrate.

3. some users have problem of duplicate mails.

Pls provide proper method and steps to do migration.

Hello all.

We have problem on moving Exchange 2010 to office 365.

We have created new  office365 account and we do not using DIRSync.

when trying to cutover  migration only one administrator mailbox synced. And also External contacts+ Distribution Groups Synced. All other mailboxes not sync.

We´ve checked that administrator account that we provided for migration is set full access to all mailbox.

Here is the error msg:

"firstname.lastname@domainname.com","Windows Live Domain Services returned an access error: 'System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 157.56.58.46:443

Hi,

I was wondering if anyone could offer some advice, we’re using a third party tool to migrate our Groupwise mail to Office 365.

When we have been migrating historic calendar entries we are having issues with outlook warning that these appointments are overdue. In some cases users are having to dismiss hundreds of old calendar entries.

Is there any way we can control this or set the calendar entries in a state where they are automatically treated as dismissed?

I've logged this with the support team from the migration tools but want to know if their is anything we can do from Exchange Online or via OWA / Outlook client. As it stands we are having OWA crash with script errors when it asks if a user wants to dismiss hundreds of appointments at once.

Thanks,

Stuart

Hi,

The migration is nearly over and everything went pretty well, and the help we got was great.  I noticed a couple of posts about people having to convert their AD users into Mail Enabled Users in preparation for getting rid of their in-house Exchange Servers (but obviously keeping the AD).

We're in the same boat, we want rid of on-premises Exchange, but will be keeping our Active Directory, which is where we will configure any Exchange Online stuff.

The problem that I'm faced with is that the scripts to list and covert users to MEU's references a CSV file which was supposedly used in the staged migration (which is what I thought we did), but we didnt need one.  I'll explain what we did so hopefuly you can tell us whether we STILL NEED to convert to MEU's.

We have Exchange 2007 on-premises, we following the Exchange Migration Wizard, we installed Exchange 2010 SP1 so we could connect to both on-premises and cloud resources.  We route ALL mail through O365, all of the mailboxes were migrated to the cloud using Exchange 2010's Remote Mailbox Move Request, as its Client Access role is exposed through hybrid.domain.com.  All Outlook clients now point to Office 365 directly and are working perfectly, and the DirectorySync and ADFS farm are operating as expected.

My fear is we turn the old Exchange server off and things stop working.  Can you tell me whether I can do this, whether the users need to be converted to MEU's?

Thanks,

Ross

Hi,

we have a hybrid coexistence enverionment with Exchange 2010 sp2 and Office365. Some mailboxes were moved to Exchange Online via Exchange Management Console without a problem - we would like to move some mailboxes back. The GUI reports an error:

If we run the move requests via the shell we get this:

(New-MoveRequest -Identity username -Remote -RemoteHostName exurl -TargetDeliveryDomain domain -RemoteCredential $cred -Verbose)

regards,

Mark

Hi,

We are currently evaluating Exchange Online (W14) and would like to move about 60 Accounts.

I couldn't find any information about how to migrate from an on-premise Exchange 2013 to Exchange Online other than hybrid deployments which only work with the new tenant (unfortunately our Exchange Online account is W14).

Is cutover migration supported in the scenario?

Would it make sense to first sync active directory to import GAL et.c.?

Thank you!

Should I expect any delay in service after completing step 5 "Complete the process" ? I need to know that there will be no lost emails, even if this process only takes seconds.

Also, do I have any guarantee that there will be no hiccups in that transition?

Do I need to have kept the TXT Record that I created for verification purposes on my original host? I ask this because after the verification I deleted the record.

Thanks,

Rob

Hi All

We have completed the migration of all mailboxes to Exchange Online and they are now synching every 24hours keeping up to date.

I wanted to connect one of the Outlook clients to the Online Exchange but it seems our internal server always gets in the way of the auto setup working and sets itself up as the mail server continuously.

We tried doing the settings manually choosing Outlook.com as the mail setup type but we do not know what the server address to use is.

We have tried the address in the address bar when we login to the web interface for exchange online. with /owa and without.

tried db3prd0210.outlook.com/owa/

and db3prd0210.outlook.com

I forget where I dug up the info for my phone but that server address is pod51007.outlook.com and my phone ActiveSync is working perfectly. even tried that address in the setup but still no joy.

Any advice welcomed :)

Hi.

I am responsible for the UK subsidiary of a company in Hong Kong. The HK company uses hosting services from 188 Web.

I would like to use Exchange Online so that I can share calendar information and contacts with other UK colleagues, but the parent company in HK is happy with its current arrangements.

So I want to set-up Exchange Online just for the UK personnel, but share the domain name used by the parent company.

So far, I have created an Office 365 trial account, and 188 Web created a TXT record in our domain DNS to enable me to verify our domain ownership (which I've done).

How can I now configure Office 365/ Exchange Online to achieve my desired outcome?

Thanks in anticipation of your help!

Richard

I've waded my way through almost all the steps to get our hybrid exchange 2010 / office 365 configuration up and running. The directory is synchronized, I've created a new remote mailbox user that can send internet email, but I'm having problems with mail flow between on-premises exchange and online exchange mailboxes (both directions).

The online FOPE tracking logs show a delivery result for all emails sent from my cloud mailbox to an on-premises mailbox:

• In Deferral: 451 4.4.0 Primary target IP address responded with: "451 5.7.3 Must issue a STARTTLS command first." Attempted failover to alternate host, but that did not succeed. Either there are no al

The on-premises exchange queue viewer shows this error:

"451 4.4.0 Primary target IP address responded with: ""451 5.7.3 Must issue a STARTTLS command first."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts."

One possibly related issue is that when I went to the domain list, selected "change domain purpose" and ticked the "I plan to set up on-premises mailboxes to work with Office 365 or make sure they’re protected with Exchange Online Protection." option, the wizard responds with an error about the connectors - "Sorry, it looks like your outbound connectors aren’t set up correctly." - but doesn't give any further information and the connectors look fine in FOPE administrator.

Any help very much appreciated.

We are currently in hybrid mode with an on-premise 2010 CAS server.  Our autodiscover record is pointed to the hybrid server, hybrid.domain.com.  75% of our people have been migrated to online.  We are constantly having a problem with password popup messages for Outlook and Link.  We also have popup messages for our online SharePoint site that is attached to our Outlook, (basically we have a contact list that was added to Outlook from online SharePoint).  We are getting popups with on-premise and online people.

We have rebuilt profiles, deleted everything in credential manager and tried all the other myriad of suggestions on the forums and they still keep coming back.  I have also seen where our autodiscover record should be pointed to outlook.com.  Well, when setting up our hybrid server, Microsoft's directions were to point autodiscover to the hybrid server.  I would like to point it to outlook.com but don't want to impact all the remaining people on-premise.  When they are migrated to online I will point it there. 

This is a real pain in the butt going around and deleting everyones credential manager on a daily basis.  Why is this happening and how do we stop it?  I have scoured the forums and tried most everything I've seen there so please don't lead me down that road.  Is it the autodiscover record causing this?  If so, then why does Microsoft recommend setting it to the hybrid server?

We are a small company  (10 people) in the process of jumping over from a pop server to exchange online. I am at step 5 of the process where I need to change over the name server to move the DNS ownership over to Microsoft.

Because of the unpredictable delay, of as much as 72 hours, for this to process to complete, I am attempting to realize the best way to make sure our employees stay connected immediately following the change over.

The best thing I can think to do is to add each user's account to their local machine, and just let it keep attempting to grab (and error out) until it inevitably does work.

My question is 2 fold:

1. Is this the best course of action?
2. Will the exchange server address (BL2D7D0611.mailbox.outlook.com) change to something else once the DNS/Name Server process is complete?

If the answer to Question 2 is "Yes" then I suppose this invalidates this plan completely, and I will be looking for suggestions on alternate courses of action.

Regards,

Rob

I have my own domain, with several e-mail accounts. Just three of these accounts are office365 accounts, with names like xxx@mydomain.onmicrosoft.com.

I want the three online accounts change tot our own account name (xxx@mydomain.nl), but the other accounts must stay the way they are now.

When I bring my domain tot office365, all accounts are only reachable via office365. Am I right?

An I don't want them all bring in in office365. Is there a solution?

I am trying to use a staged migration to migrate approximately 110 mailboxes from an Exchange 2010 server (SP1 is not installed) to O365, but am having problems running the first test migration. I am able to create the migration batch, so this proves the connectivity to the server is OK and the email address used in the CSV file can be found in the O365 directory. I start the migration, but it never progresses beyond ProvisioningUpdatePending, and after about 30-45 minutes, it fails with the error:

Failed to update the on-premises mailbox with the target address….

The AD account I am using for the migration has Enterprise Admin, Domain Admin and Exchange Organisation permissions, as well as Receive-As permission to the Database and Full Access permissions to the individual mailbox.

There is an added complexity to this scenario as well. This Exchange 2010 server is not part of the company’s main AD forest – it is running independently in a separate AD forest and there is no trust or physical connectivity between the two forests.

Our main company, let’s just call it CompanyA, has approximately 3000 users on O365. We have DirSync and ADFS configured. We do not have a Hybrid installation, as we have no mailboxes hosted on-premise. CompanyA is not having any problems.

CompanyB is what we are trying to migrate, and they have their own separate AD that is not linked with O365.

In the CompanyA AD, MailUser accounts have been setup for each of the users from CompanyB with primary and external email addresses setup that match their current email address. These accounts have all sync’d successfully to O365 and show in the GAL. The domain name used by CompanyB has been added to our tenant and verified, but is currently set as a Shared domain so that mail will flow from our O365 users to the CompanyB server.

We have used this scenario a number of times previously when integrating other parts of our business and have not had this problem before. The only difference is that this is the first time we have tried to migrate from Exchange 2010. We have been successful with migrations in separate AD forests with Exchange 2003 and Exchange 2007, as well as running IMAP migrations from Gmail.

I can see in the documentation that it says you can’t use a staged migration to migrate from Exchange 2010 to O365, but it doesn’t say why. I have also seen in these forums a comment that says it does work, but it’s not supported/recommended.

For Exchange 2010 migrations, the documentation says to use a cutover migration, but to do that you can’t have DirSync running. We have DirSync running with the CompanyA AD, but not CompanyB, but all CompanyB users have accounts already in O365. This means we cannot do a cutover migration as all the users accounts and email addresses already exist within O365 so will conflict if we tried this.

The business needs to do this migration in a staged approach as most of the places where the users are physically located have dodgy or unreliable internet connections, so in order to minimise impact to the users and the business during the migration process, we need to migrate users in batches of approx 5 at a time.

I have done a considerable amount of searching on the Internet for this error, but each time I find it, the questions generally remain unanswered, or the reply is that it just started working, so I am no closer to finding a resolution.

Would anyone be able to suggest where I might be going wrong with the migration, if there is something on the Exchange 2010 server that might not be correct, or alternatively, what my options are for migrating these users in a staged approach if I absolutely can't do a staged migration from Exchange 2010?

Thanks.