I am performing a migration using the built-in Office 365 IMAP migration tool.

I have noticed that if the source IMAP mailbox contains a manually created folder called 'Notes' that contains email items this folder is not migrated to Office 365. I presume this is because the name 'Notes' conflicts with the default folder of the same name in Office 365 that contains non-email items.

Is this assumption correct?

The CSV report produced at the end of the IMAP migration is not included in the 'Skipped Items' section of the report, so it seems that there are some folders that are excluded from migration by default. I'm basically looking to find out what these are.

Thanks

Hi Everyone,

I recently completed the hybrid configuration between our on-premise Exchange 2010 organization and Office 365 (Education). In our on-premise organization, we use the SMTP addresses user@domain.org and user@students.domain.org. These SMTP addresses match user's UPNs in AD. 

In Office 365 I have our main domain.onmicrosoft.com domain as well as two mention above, both of which are verified. SSO is also enabled for both. On the domain settings page this is confirmed. 

If I create a new user in AD and set their UPN to students.domain.org and put in their AD profile the email address, I can go into O365 admin portal after an AD sync and active the user. The primary email address becomes username@students.domain.org as it should. Mail is sent from this address, etc. But here's the issue: when I send an email from this student user to another internal (on-premise) user and the on-premise user attempts to reply, they get an error that the email address for username@students.domain.org is invalid. 

Checking the account with ADSI Edit reveals that no proxyAddress is being set. Manually setting SMTP:username@students.domain.org doesn't seem to fix this issue. 

If I create a brand new user through the "New Remote Mailbox" option in the Exchange console, and specify the UPN of students.domain.org, the user is given a primary SMTP address of username@domain.org. This also seems wrong to me. Does Office 365 not use the UPN to set the SMTP address? 

Thanks!

 I tried to create an additional cloud email address for the onmicrosoft cloud but it threw an error as we are in Hybrid mode and told me to add the email address in the local AD, not the Office 365 portal (makes sense). I have done that but it is not replcating up to the 365 mailbox, so I cannot use this email address until it does. I have waited all weekend for changes to replcate including a manual rebuild of the offline GAL on our local 2003 Exchange Server. Why is the onmicrosoft email address I created NOT being replicated up to the account on 365 where I want the additional email address?

Hi,

We are migrating to office 365 and have converted our domain to federated.

We are having problems connecing with outlook. When configuring a profile we cant get pass the authentication windows. It just keeps asking for credentials.

We have configured one adfs server (on one of our DCs) and a adfs proxy on a new server.

The adfs proxy is using a 3d party certificate and we are not getting any certificate warnings when we connect to the site.

The certificate provider is Starfield Technologies.

We can authenticate and logon to OWA and the portal but outlook just wont work... We have tried installing all the recommendet patches but this made no difference. When testing outlook over http/rpc using www.testexchangeconnectivity.com we get this error:

"RPC Proxy can't be pinged."

"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)."

We have tried to configure outlook manually as well but that has made no difference.

Any help is appreciated.

Hola a todos, mi nombre es Christopher y esta es primera vez que me veo en la obligación de pedir ayuda :/.

Actualmente soy ingeniero de plataforma y me encuentro implementando Office 365 bajo el método de coexistencia. La infraestructura que manejan donde me encuentro habilitando el servicio es de un Exchange 2003 migrado a Exchange 2010, aun no se da de baja totalmente el Exchange 2003 pero ya todas sus carpetas publicas se encuentran replicadas hacia 2010 y sus Address Policy que pueden ya ser modificadas en Exchange 2010.

El ADFS funciona sin problemas, DirSync también, se creo la foresta nueva dentro de Exchange 2010 para Office 365 pero al momento de configurar el Wizard Híbrido me arroja un error el cual no logro entender:

Error:
Updating hybrid configuration failed with error 'Subtask ValidateConfiguration execution failed: Configure Legacy Exchange Support

Las proof se encuentran activas, lo comento porque es lo que siempre preguntan para este tipo de configuraciones, ahora el tema es que realmente esta sucediendo, me he dado mil vueltas, el usuario del On-Premise tiene casilla, pertenece a los 3 grupos principales ( Enterprise, Schema y Domain), no me quedan mas cartas bajo la manga, por ello quise acceder a este foro para ver si pueden orientarme y ver si algo se me esta pasando en alto.

Agradecería su ayuda.

Saludos.

Hi,

We are about to migrate from an on-premise Exchange 2003 setup to Office 365. Currently we are running all the DCs on Server 2003.

We plan to upgrade all the DCs to Server 2008 in a few months.

Will it be possible to migrate all the users to Office 365 now with only Dir Sync configured in Server 2003 and later once we migrate the DCs to Server 2008 will I be able to sync the passwords after I configure ADFS?

(Basically I just want to know if I can configure ADFS to sync passwords with Office 365 after the migration is complete and after the users have started using Office 365)

Appreciate any response. Thanks!

Regards,

Thilina

Hi,

this is a long question, so bear with  me; please consider the following: I have ~30 user accounts in domain @somedomain.com, that have mailboxes with my domain/hosting provider. These are plain mailboxes, accessed by IMAP.

Now, I purchased ~10 Exchange Online licenses, as I want to give selected users the Exchange capabilities. I do not intend to migrate all users to exchange online.

So, I:

1) verified the domain @somedomain.com with exchange online (NOT changing the MX records, only adding the TXT record to prove ownership). I created user accounts (with username@somedomain.com login) for those lucky users and assigned licenses in Exchange Online. I also set the @somedomain.com domain as "Shared".

2) Then, I set up email forwarding with my hosting provider to forward all emails for the specific user (username@somedomain.com) to default alias (username@somedomain.onmicrosoft.com). It works - the exchange online user receives the email, and is able to send email from @somedomain.com address.

The only (and serious) issue is that Excahnge online users are not able to send emails to other @somedomain.com mailboxes, that are not on Exchange online.

Any kind suggestions? Thanks for your patience.

I have a 365 account

I use a mydomain .eu which was properly exported to Australia???

I have created my associated @ mydomain.eu emails

I would like to continue using Livemail2009 as my tool to manage my emails but I can't get my emails to work

Ive configured the accounts with the proper protocol settings but the SMTP encryption method (TLS)  does not appear in the LiveMail wizard?????

And

When I created the emails on 365 I was not asked to create a password for these email accounts but when I create them in Live mail I am asked for a password. I tried my main 365 password but this does not seem to work.

HELP?!!§?

hi there,

I am in the middle of a migration from sbs2003 to office365. I have kicked off an migration in the portal.

I have done this in the past and it has uploaded email without disrupting the source exchange server.

This time however it is automatically redirecting all email to office365. i.e. if I send an email to the customer it goes to their email server and is then forwarded to office365. No copy is left on the original exchange server.

I am a little confused as to how this is happening. I wasn't planning on moving users to office365 until next week but they can't now access their emails via the old server.

Can anyone advise what has happened here?

Cheers,

Al

I have been bashing my head against a wall for a week now and would appreciate some help or suggestions.

I have an internal existing exchange 2010 organization which I want to coexist with office365.

I have configured federation and am able to log on with my local domain credentials which leads me to believe that the federation is working correctly.

When I try to complete the Hybrid configuration wizard I get the error :

Execution of the Get-FederationInformation cmdlet had thrown an exception. This may indicate invalid parameters in your Hybrid Configuration settings. 


Federation information could not be received from the external organization.

When I perform a Get-FederationInformation from both the on premise powershell and the tenant 365 powershell this command executes correctly with no errors.

If I do a Get-AcceptedDomain | fl DomainName,isCoexistenceDomain my domain is listed as false, and presumably this is because the hybrid configuration wizard is failing?

I have DirSync enabled with no obvious errors also.

If I try to perform a RemoteMailbox move I get the error that the user already has a primary mailbox - presumably because the conexistence for that domain is set to false.

I believe autodiscover is working correctly, however am unable to check 100% - the exRCA tool fails due to an SSL certificate error, but it does not tell me what this error is. I am using trusted wildcard certificate for our domain and this is currently working for our activesync users, so I have no reason to believe it shouldnt work also for autodiscover.

I am not using Forefront.

Any help or suggestions would be much appreciated as I am currently unable to see a way to get this fixed!

Thanks.

Taking a look at these posts, I can assume that calendars could be shared at AvailabilityOnly and LimitedDetails levels for users between on-premises and o365, and higher permission such as Reviewer, Editor is not included in cross premises calendar sharing feature.

We are doing a cutover migration, with 24 of 41 mailboxes already migrated.

We missed the fact that one user has an extremely  huge mailbox, with over 100,000 items taking up 28GB of disk space on the current Exchange 2007 server. I know we should have caught it before ...

About 17,000 items of this mailbox has been migrated so far.

Is there a recommend way that we can pause the migration, and select to skip migrating this user for now, allow the rest of the users to be migrated, and then migrate this user once we have exported off a lot of her old emails to a PST file?

Thanks.

We are in the middle of a staged migration.

Some of our users who have already been moved over to Office 365 are finding emails from senders who are still on the on-premise server in their Junk E-mail folder.

When they go to add the sender to the Safe Senders list, they got a error message indicating that the sender can't be added to the Safe Senders and Recipients list .

Hello,

I have read the instructions for the "Simple Domain Sharing" solution and wanted to ask if the following was an option.  These instructions kinda lend to the fact that the user is not fully migrated until the MX record is configured from my current provider to Office 365.

However, can we just ADD an additional MX record to our DNS settings.  Basically, it would look like this with the additions being in red:

mydomain.com.       3600    IN      MX      30 mydomain-com.mail.eo.outlook.com
mydomain.com.       86400   IN      MX      20 mx2.emailsrvr.com.
mydomain.com.       86400   IN      MX      10 mx1.emailsrvr.com.

mydomain.com.       3600    IN      TXT     "v=spf1 ip4:209.23.116.0/22 include:outlook.com ~all"

Further more, can we have multiple autodiscovery records?  Again, the additions being in red:

autodiscover.mydomain.com. 86400 IN CNAME   autodiscover.emailsrvr.com.

DirSync currently pushes up extended attributes into Office 365, that prohibits Office 365 from  creating a mailbox if a mailbox is present in the on premises exchange server.  This appears to be controlled by the extended attributes in the MS Online Dirsync client.

To access the DirSync gui, you need to load the MIISclient.  This client is located in the Program Files\Microsoft Online Directory Sync\SYNCBUS\Synchronization Service\UIShell\miisclient.exe.  If you run this  tool, and  look at the management agent properties,  for Source AD, you have the ability to disable certain exchange parameters form being sync.

It appears that if you disable the “msExchMailboxGuid” in the sourceAD (properties), this will enable Office 365 to create the  Office365 mailbox when a license is assigned.

Question:  What are the other extended extended exchange attributes that need to be blocked in dirsycn that will allow a mailbox creation in Office 365, when a license is assigned to an office 365 account?

Hi All,

Hoping someone can offer some advice on this strange issue.

1 - Prior to migration of a mailbox I add SMTP address mailbox@XXX.mail.onmicrosoft.com to the users mailbox.

2 - Once Dir Sync updates Office 365 I start to get NDR's indicating a mail loop.

mailbox@XXX.mail.onmicrosoft.com
VA3EHSMHS009.bigfish.com #554 5.4.6 Hop count exceeded - possible mail loop ##rfc822;mailbox@XXX.mail.onmicrosoft.com

3 - I look at the Office 365 contact details for the mailbox using Exchange Management tools on the Hybrid server, I see the external e-mail address has been set for the mailbox as XXX.mail.onmicrosoft.com rather than mailbox@mydomainname.com.au

this service delivery domain is obviously incorrect as the mailbox is not yet migrated.  Users sending mail from Office 365 to the on-prem mailbox will get NDR's.

Could someone offer any advice on whey the Dir Sync is causing this to happen?

thanks

Hi,

 I got a problem with my corporate hybrid configuration for Office365, i got this error:

An error occurred while attempting to provision Exchange to the Partner STS.  Detailed Information "An unexpected result was received from Windows Live.  Detailed information: "InvalidUri InvalidUri: Passed URI is not valid.".".

 I have opened a ticket on Microsoft Support but no solution was found at this time. I have see that could be caused by an unauthorised word in my domain name but i can't verify it.

 How can i do to verify it ?

I searched and found this but no resolution:  Office 365 forum post

Problem:  I migrated a user last night to the cloud and she received this error today in her Inbox:

Synchronization with your SAMSUNGSGHT959V failed for 1 items.

The following items couldn't be sent to your mobile phone. They haven't been deleted. You should be able to access them using either Outlook or Outlook Web App.

Known information: 

• The person that received this error message (user A) is a delegate of another person's calendar (user B) and has the rights to accept meeting requests on their behalf.

• I was able to duplicate this by sending an appointment to user B.  By design this will automatically get forwarded to user A and it did but also resulted in the same error.

• user A is in the cloud, user B is not (staged, hybrid migration)

Since I've already duplicated this I'm willing to guess that this issue is caused by one person being in the cloud and the other being on-premise.  I'm hoping this goes away after the second person is migrated to Office 365 and will certainly update this post.  If anyone else can chime in on this that would be much appreciated.  I'm also posting this so that this can help others with the same issue.

Problem:  After migrating mailboxes a set number of mailboxes last night to the cloud, some of them are getting security prompts after launching Outlook on their local machines

Background info:  Staged, hybrid migration.  Some users on XP running Office 2007 and others on Win 7 running Office 2010.

XP users get this:

For now they can enter their full email address as the Username and their password and it will allow them to work in Outlook but this keeps popping up every time they open Outlook.

Windows 7 users get this:

They can click on Cancel and it will allow them bypass and use Outlook but they are prompted every time Outlook opens.

For both messages I have tried entering their full email address as the username and their Office 365 password but these messages will not go away.

Any thoughts or help would be much appreciated

I'm part way through a cutover migration from SBS (Exchange 2007) to Office 365.  The initial sync was successful and all the mailboxes were copied however during the every-24-hour maintenance sync one of the mailboxes is failing and stopping the migration.  This is the error I receive:

After a bit of further investigation it turns out the user did a major reorganisation of their mailbox and shuffled all their folders/messages around.  It's too different for me to be able to manually change the destination mailbox and even after moving a few folders around in it the exact same error message appears.

Can I just delete her destination mailbox and will the migration batch job re-migrate it again?