Hi,

I've done the domain verification and now I have to change the DNS settings in Parallel Plesk Panel 10.3.1. Just to make sure all the value is properly populated, I need your help to clarify which value should be placed in which field for each MX and CNAME.

Below is the value given by MS for the DNS setup

Type: MX

Priority: 0

Hostname: @

Points to address: mydomain-com.mail.eo.outlook.com

TTL: 1 hour

Type: CNAME

Priority: -

Hostname: autodiscover

Points to address: autodiscover.outlook.com

TTL: 1 hour

Below is the screenshot for both MX and CNAME provided in Plesk Panel.

Helo

I have problem with migrating user mailbox from on-premise Exchange 2010 SP2 to Exchange Online Office 365.

When I start new remote move request migration failed:

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:06

Failed

Error:
The call to 'net.tcp://db3prd0510ca018.eurprd05.prod.outlook.com/Microsoft.Exchange.MailboxReplicationService DB3PRD0510CA018.eurprd05.prod.outlook.com (14.16.190.8 caps:07)' failed. Error details: Object reference not set to an instance of an object..

Exchange Management Shell command attempted:
'281cb9c0-ff72-4299-96a6-4742e7810968' | New-MoveRequest -Remote -RemoteHostName 'myonpremisedomain' -TargetDeliveryDomain 'service.myonpremisedomain'

Elapsed Time: 00:00:06

What to do?

Client is able to migrate to the cloud just fine.  But when attempting to move mailbox back to on-prem 2007 server getting an error about ArchiveDomain even thou the mailbox does not have archiving enabled.

Error: An error occurred while updating a user object after the move operation. --> Property ArchiveDomain can't be set on this object because it requires the object to have version 0.10 (14.0.100.0) or later. The object's current version is 0.1 (8.0.535.0).

We change the MSExchangeVerison attribute to match but still run into error.

Thinking this is an error due to moving back to a 2007 mailbox server.

Hello,

I was wondering if it was possible to host Public Folders using on-premise Exchange 2010 servers in Hybrid mode and whether the user would be able to access these using outlook while also connected to Exchange Online using Outlook?

We eventually want to decommission the Public Folders however migrating all the content will take some time and we were hoping we could keep the same user experience once the users are migrated to Office 365.

Kind regards,

Rahim Hasham

I am wondering if\how the situation below would be possible.

Company.com has an existing Exchange 2003 on premise environment with external access via owa.company.com etc.

Company.com deploys a new Hybrid Echange 2010 SP2 RU3 server.  This server is pubished with different url's, such as hybrid.company.com etc.

Can co-existence features (minus of course URL re-direction for Office 365) exist in this fashion?  We do not want to alter the existing production mail flow while building and migrating users.

I've tried over 20 times at this point to migrate ONE user's mailbox from Google Apps to Office 365 using IMAP migration. No matter how many times I re-check, re-make, and re-upload the CSV file, I'm always met with the following error:

We had trouble signing in to this
account. Please confirm that you're using the correct user name and
password.

My CSV file looks like the following when opened up in notepad:

EmailAddress,UserName,Password
myuser@mydomain.com,myuser@mydomain.com,mygmailpassword

Obviously I've changed the e-mails and my google password in the above example. However, I'm 100% SURE that the user/pass is correct with regard to the google login information. There's no 2 factor authentication enabled, IMAP and POP are fully enabled in the settings, everything really is properly set on Google's end.

I'm beginning to arrive at my wit's end here with this issue. Any ideas?

I've started a cutover migration and there are a few source mailboxes that are normal user mailboxes that need to be shared mailboxes in Office 365 so that they don't consume a license.

Even though we're still in the sychronisation phase I've changed the Office 365 mailboxes to type 'shared' and limited them to 5GB quotas (they're all less than that).  Unfortunately they are still listed in the custom view “Users with Exchange mailboxes or archives and no licenses” which suggests they require a license.

I've created a new test shared mailbox in Office 365 and it doesn't show up in this view.

What will happen after the migration is complete?  I'm worried that these mailboxes will be deleted at the end of the grace period as there are no licenses available for them.  As far as I can tell they meet the criteria for unlicensed shared mailboxes.  Is it just new shared mailboxes that are created in Office 365 (not migrated) that fulfil the criteria?  How do other people deal with this?

Where's the documentation for this?  I'm starting to get annoyed at the lack of detail in the Office 365 documentation...

I have an on premise Exchange 2010 SP2 environment, running in rich co-existance. We're running SSO and Dirsync. All is working flawlessly except for one thing.

If I create a new user in AD, run dirsync up to the cloud, and then enable the mailbox in the cloud, Autodiscover does not work for that user. The mailbox is fine, as access through OWA is okay.

If I create a new user in AD, create the mailbox on premise, and MOVE the mailbox to the cloud, Autodiscover works like a charm.

Microsoft has told me this is by design, and the move request stamps something that allows Autodiscover to work. This does not make much sense, in fact, it seems a bit backwards to me.

Can someone confirm this is by design, or is something missing? All Autodiscover entries on Public and Internal DNS are set accoring to Microsofts guidelines.

I created 2 mail boxes on Exchange Online, one a user mailbox type, the second a shared mailbox, added the full access permitions to the shared mailbox.

When I addedd the 1st account to Outlook I had no problems, the issue is the 2nd one, the Shared mailbox, I let's me add the account, but when I restart Outlook it prompts me to give the password, I enter the correct one, but apparently it is not the correct one. As a note, I can access the shared mailbox with the password I entered without problems, but I cannot open that shared mailbox on Outlook.

I need this because I want to migrate our exchange public folder to the online service.
Can you help me on this issue?After this, the account is not added and does not open the mailbox and I cannot migrate the public folder.

Can someone help me on this?

Thanks

We are in the process of performing a staged migrating from SBS 2008 with Exchange 2007 to office 365. Currently our External DNS has a cname for autodiscover record that points to our exchange 2007 and working well.  

I have verified our domain and as a test I changed the autodiscover cname to point to the office 365, now a number of my mac office 2011 clients are failing and asking to redirect to the office365 url.  I redirected the autodiscover back to our exchange 2007, and that fixed the mac issue.

Our goal is to configure secondary outlook profiles for users to office 365 prior to moving their mailboxes, but it seems that i may not be able to complete this task, unless we move our cname autodiscover record from our onsite exchange 2007 to office 365. 

Any guidance on this would be greatly appreciated.

best regards,

DC

Hi, I've an Active Directory forest with several thousand of users synced with Office 365 through DirSync and integrated with a SSO ADFS solutions. Right now I've another Exchange organization on another forest with over 1000 users and about 400 Shared Mailbox that need to be migrated on the previous Office 365 account.

My answer is: is possible to manage the transition with Exchange migration path or is necessary to use other transition path (for example IMPA Migration)?

Thanks

Hi,

Has anybody seen an issue when moving a mailbox via the hybrid console from on-premise to o365 that the on-premise exchange database grows drastically i.e. for no known reason grows by a couple of gigs on every mailbox move.

Note: on-premise mailbox is part of a dag

I have been trying for a week to connect Outlook 2010 to my new Office 365 account. All of my coworkers have been able to connect, but I have not been able to for some reason. I have tried autodiscover and the manual setup and neither work. I have tried the Remote Connectivity Analyzer and that failed. Here is what I received:

Attempting the Autodiscover and Exchange ActiveSync test (if requested).

Testing of Autodiscover for Exchange ActiveSync failed.

Test Steps

Attempting each method of contacting the Autodiscover service.

The Autodiscover service couldn't be contacted successfully by any method.

Test Steps

Attempting to test potential Autodiscover URL https://bitnercollingscpa.com/AutoDiscover/AutoDiscover.xml

Testing of this potential Autodiscover URL failed.

Test Steps

Attempting to resolve the host name bitnercollingscpa.com in DNS.

The host name couldn't be resolved.

Tell me more about this issue and how to resolve it

Additional Details

Host bitnercollingscpa.com couldn't be resolved in DNS InfoNoRecords.

Attempting to test potential Autodiscover URL https://autodiscover.bitnercollingscpa.com/AutoDiscover/AutoDiscover.xml

Testing of this potential Autodiscover URL failed.

Test Steps

Attempting to resolve the host name autodiscover.bitnercollingscpa.com in DNS.

The host name resolved successfully.

Additional Details

IP addresses returned: 157.56.240.137, 157.56.236.89, 157.56.244.217, 157.56.234.137

Testing TCP port 443 on host autodiscover.bitnercollingscpa.com to ensure it's listening and open.

The specified port is either blocked, not listening, or not producing the expected response.

Tell me more about this issue and how to resolve it

Additional Details

A network error occurred while communicating with the remote host.

Attempting to contact the Autodiscover service using the HTTP redirect method.

The attempt to contact Autodiscover using the HTTP Redirect method failed.

Test Steps

Attempting to resolve the host name autodiscover.bitnercollingscpa.com in DNS.

The host name resolved successfully.

Additional Details

IP addresses returned: 157.56.236.89, 157.56.244.217, 157.56.234.137, 157.56.240.137

Testing TCP port 80 on host autodiscover.bitnercollingscpa.com to ensure it's listening and open.

The port was opened successfully.

ExRCA is checking the host autodiscover.bitnercollingscpa.com for an HTTP redirect to the Autodiscover service.

The redirect (HTTP 301/302) response was received successfully.

Additional Details

Redirect URL: https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml

Attempting to test potential Autodiscover URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml

Testing of this potential Autodiscover URL failed.

Test Steps

Attempting to resolve the host name autodiscover-s.outlook.com in DNS.

The host name resolved successfully.

Additional Details

IP addresses returned: 157.56.234.86, 157.56.234.118, 157.56.234.134, 157.56.240.86, 157.56.236.102, 157.56.244.230, 157.56.234.150, 157.56.240.102, 157.56.240.118, 157.56.240.134, 157.56.236.86, 157.56.236.118, 157.56.236.134, 157.56.244.182, 157.56.244.214, 157.56.245.6

Testing TCP port 443 on host autodiscover-s.outlook.com to ensure it's listening and open.

The port was opened successfully.

Testing the SSL certificate to make sure it's valid.

The certificate passed all validation requirements.

Test Steps

ExRCA is attempting to obtain the SSL certificate from remote server autodiscover-s.outlook.com on port 443.

ExRCA successfully obtained the remote SSL certificate.

Additional Details

Remote Certificate Subject: CN=outlook.com, OU=Exchange, O=Microsoft Corporation, L=Redmond, S=Washington, C=US, Issuer: CN=Microsoft Secure Server Authority, DC=redmond, DC=corp, DC=microsoft, DC=com.

Validating the certificate name.

The certificate name was validated successfully.

Additional Details

Host name autodiscover-s.outlook.com was found in the Certificate Subject Alternative Name entry.

Certificate trust is being validated.

The certificate is trusted and all certificates are present in the chain.

 
Test Steps

ExRCA is attempting to build certificate chains for certificate CN=outlook.com, OU=Exchange, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.

One or more certificate chains were constructed successfully.

Additional Details

A total of 1 chains were built. The highest quality chain ends in root certificate CN=GTE CyberTrust Global Root, OU="GTE CyberTrust Solutions, Inc.", O=GTE Corporation, C=US.

Analyzing the certificate chains for compatibility problems with versions of Windows.

No Windows compatibility problems were identified.

Additional Details

The certificate chain has been validated up to a trusted root. Root = CN=GTE CyberTrust Global Root, OU="GTE CyberTrust Solutions, Inc.", O=GTE Corporation, C=US.

Testing the certificate date to confirm the certificate is valid.

Date validation passed. The certificate hasn't expired.

Additional Details

The certificate is valid. NotBefore = 4/17/2012 9:26:21 PM, NotAfter = 4/17/2014 9:26:21 PM

Checking the IIS configuration for client certificate authentication.

Client certificate authentication wasn't detected.

Additional Details

Accept/Require Client Certificates isn't configured.

Attempting to send an Autodiscover POST request to potential Autodiscover URLs.

Autodiscover settings weren't obtained when the Autodiscover POST request was sent.

Test Steps

ExRCA is attempting to retrieve an XML Autodiscover response from URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user paul@bitnercollingscpa.com.

The Autodiscover XML response was successfully retrieved.

Additional Details

An HTTPS redirect was received in response to the Autodiscover request. The redirect URL is https://pod51009.outlook.com/Autodiscover/Autodiscover.xml.

Attempting to test potential Autodiscover URL https://pod51009.outlook.com/Autodiscover/Autodiscover.xml

Testing of this potential Autodiscover URL failed.

 
Test Steps

Attempting to resolve the host name pod51009.outlook.com in DNS.

The host name resolved successfully.

Additional Details

IP addresses returned: 157.56.236.86, 157.56.234.86, 157.56.244.182, 157.56.240.86

Testing TCP port 443 on host pod51009.outlook.com to ensure it's listening and open.

The port was opened successfully.

Testing the SSL certificate to make sure it's valid.

The certificate passed all validation requirements.

Test Steps

ExRCA is attempting to obtain the SSL certificate from remote server pod51009.outlook.com on port 443.

ExRCA successfully obtained the remote SSL certificate.

Additional Details

Remote Certificate Subject: CN=outlook.com, OU=Exchange, O=Microsoft Corporation, L=Redmond, S=Washington, C=US, Issuer: CN=Microsoft Secure Server Authority, DC=redmond, DC=corp, DC=microsoft, DC=com.

Validating the certificate name.

The certificate name was validated successfully.

Additional Details

Host name pod51009.outlook.com was found in the Certificate Subject Alternative Name entry.

Certificate trust is being validated.

The certificate is trusted and all certificates are present in the chain.

Test Steps

ExRCA is attempting to build certificate chains for certificate CN=outlook.com, OU=Exchange, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.

One or more certificate chains were constructed successfully.

Additional Details

A total of 1 chains were built. The highest quality chain ends in root certificate CN=GTE CyberTrust Global Root, OU="GTE CyberTrust Solutions, Inc.", O=GTE Corporation, C=US.

Analyzing the certificate chains for compatibility problems with versions of Windows.

No Windows compatibility problems were identified.

Additional Details

The certificate chain has been validated up to a trusted root. Root = CN=GTE CyberTrust Global Root, OU="GTE CyberTrust Solutions, Inc.", O=GTE Corporation, C=US.

Testing the certificate date to confirm the certificate is valid.

Date validation passed. The certificate hasn't expired.

Additional Details

The certificate is valid. NotBefore = 4/17/2012 9:26:21 PM, NotAfter = 4/17/2014 9:26:21 PM

Checking the IIS configuration for client certificate authentication.

Client certificate authentication wasn't detected.

Additional Details

Accept/Require Client Certificates isn't configured.

Attempting to send an Autodiscover POST request to potential Autodiscover URLs.

Autodiscover settings weren't obtained when the Autodiscover POST request was sent.

Test Steps

ExRCA is attempting to retrieve an XML Autodiscover response from URL https://pod51009.outlook.com/Autodiscover/Autodiscover.xml for user paul@bitnercollingscpa.com.

ExRCA failed to obtain an Autodiscover XML response.

Additional Details

An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).

Attempting to contact the Autodiscover service using the DNS SRV redirect method.

ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method.

Test Steps

Attempting to locate SRV record _autodiscover._tcp.bitnercollingscpa.com in DNS.

The Autodiscover SRV record wasn't found in DNS.

Tell me more about this issue and how to resolve it

Please help me with this issue. Thanks.

During the mailbox batch migration for a cutover migration I get the following error on a couple of users who are on the list of email addresses to migrate.

"Unable to provision jobs from the current recipient. The owner recipient isn't a valid user. "

How do I fix this?

I ran an IMAP-migration from my Google Apps account and got such a large reported Mailbox size that I suspected that I got a lot of duplicates over as a result of all my gmail labels/tags.

I have only set up a 1 user Office 365 E3 account, using myself as a guinea pig before migrating the organisation over to another 365 account. Thus I can't simply delete the mailbox and start over because I am the only admin in the system.

 To remove all the messages and rerun the migration I deleted all the existing mail using PowerShell Search-Mailbox -DeleteContent.

I then created a new migration and ran it and got not a single message over. It seems to me that there is a system in place to prevent duplicates that has not realized that the mailbox is empty.

The migration report proudly states that it has transferred 208k items and skipped 0. Can anyone tell me what is going on here?

/Magnus

  I just finished setting up a new Exchange 2010 hybrid server. I am trying to move mailboxes from on premises Exchange 2003 server to the Exchange online service. When I create a new remote mailbox move I get an error

Error:
Exception has been thrown by the target of an invocation.


Exchange Management Shell command attempted:
'c8b41149-2430-46f5-a744-51b3f9391c09' | New-MoveRequest -Remote -RemoteHostName 'msg02.ism.ws' -RemoteCredential 'System.Management.Automation.PSCredential' -TargetDeliveryDomain 'napmsso.mail.onmicrosoft.com'


Elapsed Time: 00:00:05

Hi

I'm testing migrating mail from a webcentral hosted exchange 2003 to office 365.

I created a csv file with the UserName as