Migrating mailbox to 365 re-authenticate

When I migrate user joe bloggs to 365 user dave smith who has joe bloggs calendar added to outlook gets prompted to re-start outlook and to enter their username and password.
I thought it would only prompt for mailboxes added to accounts not calendars as i thought they connected via EWS for availibility...
***Don't forget to mark helpful or answer***

Hi,
Did this user get prompt to re-start Outlook every time the user log in mailbox using Outlook?
Did other users who have this shared calendar get this issue?
Based on my knowledge, if you want to share calendar between Office 365 and Exchange 2013, you need to use organization relationships. You can look at the following articles for more details.
Cross Premise Calendar Sharing with Office 365
http://blogs.technet.com/b/matabra/archive/2013/05/07/cross-premise-calendar-sharing-with-office-365.aspx
Sharing
http://technet.microsoft.com/en-GB/library/dd638083(v=exchg.150).aspx#scenarios
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

  • Disabling AD Autodiscover while migrating to Office 365

    I'm in the middle of migrating from Exchange 2007 to Office 365.  I can autodiscover to the Office 365 service successfully in every instance except when I'm on a PC joined to the AD domain and the domain is accessible.  I have added a registry
    key on my test PC that keeps it from using the AD SCP to autodiscover but it still gets my Exchange server mailbox instead of the Office 365 mailbox even without using SCP.
    If I remove the PC from the domain, it works both locally and remotely so I know all my other settings are okay, it's only giving me this issue when it's a domain member and is running local to the AD domain.  Tried a laptop, joined it to the domain,
    took it home and let it autoconfigure, worked great.  Same laptop, when local to the domain, tries to autoconfigure using the local Exchange server settings.
    I'd like to give my users back their Outlook (rather than OWA) after I migrate them.  How do I prevent my locally deployed, AD-joined computers from getting autodiscover info from my local Exchange CAS server while I complete my migration to Office
    365?

    Hi,
    I ran into the same problem. I came up with a work around but I’m not sure this is the correct approach.
    First, with Outlook 2010 already installed I had to run the Set up and configure your Office desktop apps from Office 365. I’m not sure of all the configuration changes this makes but I know after you install it that it will allow
    you to change the username field when trying to authenticate to Office 365 (will get back to that in a minute)
    Second, from my domain joined computer where outlook was connected to my on premise exchange 2007 server mailbox, I setup a new outlook account, either from the control panel mail icon, or from within outlook (both worked) Note; doing from within your already
    existing configured outlook allowed me to migrate my email from on-premise to office 365.
    From Control Panel/Mail , I created profile name “Office 365”
    In the next window it then auto discovered my on premise exchange mailbox email address
    [email protected] (which in my case is the same as the office 365 email address
    [email protected] )
    I replaced the email address with the secondary domain email address that Microsoft office 365 created
    [email protected]. I did not put in password at this point and clicked next. It then searched for mailbox, a windows security mail application windows will pop up.
    This is where I then replace username
    [email protected] with
    [email protected] and put in my office 365 account password.
    As mentioned above when I said I would get back to that in a minute, if you don’t run the
    Set up and configure your Office desktop apps from Office 365. You will not have the option to replace the username from the windows security mail application windows.
    It finishes configuration and you’re now connected.
    Worth mentioning though that I’m still having some funky mail delivery issues with on-premise users with my imported “contacts” in outlook. The contacts work from office 365 web apps, but not from outlook. If I type the address everything
    is fine, but using contacts or replying to on-premise users is giving me some grief. It’s a contact issue but I’m still unable to resolve it.

  • Migrating to Office 365, keeping Lync Server 2010 on Premise

    Hi,
    I have a Lync Server 2010 on Premises implemented, it is use a UM Sever to connect with  Exchange Server 2010.
     I migrate to Office 365 Exchange Online and keep all the Lync Server On Premise current functionalities, including "Conversations history", total connection between Lync Server and mailboxes (on O365) for conference calls and Web conferences?
    Thank you,
    Nerio

    Hi,
    If you want to integration Lync 2010 integration with Exchange online, you must configure Edge server in your on-premises Lync Server 2010 deployment by completing the following tasks:
    Configure a shared SIP address space
    Configure a hosting provider on the Edge Server
    Create a DNS Record for Integration with Hosted Exchange
    Verify replication of the updated Central Management store
    More details:
    http://technet.microsoft.com/en-us/library/hh533880.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Public Folder Migration to Office 365

    I am performing a Public Folder Migration to Office 365 according to the steps at http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx#Scripts. I made it down to Step 5, substep 5 where we are supposed to start the migration with a
    New-PublicFolderMigrationRequest. The script fails with the following error message:
    Starting a command on remote server failed with the following error message : [ClientAccessServer=BN1PR07CA0067,BackEndServer=co1pr07mb395.namprd07.prod.outlook.com,RequestId
    =0f9fb78e-1c50-4371-9add-414cbbfc9f69,TimeStamp=10/30/2014 3:24:26 PM] [FailureCategory=Cafe-HttpProxyException] Cannot replay request as bufferedRegionStream cannot be reset
    . For more information, see the about_Remote_Troubleshooting Help topic.
        + CategoryInfo          : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRemotingTransportException
        + FullyQualifiedErrorId : JobFailure
    Any help or guidance is very much appreciated.
    Randy Goodson

    So...I double-checked the authentication setting on Outlook Anywhere...it says Basic. But, when I changed to NTLM in the command line, it seems like it is working. However, now I get the following error:
    The specified mailbox "Mailbox1" doesn't exist.
        + CategoryInfo          : NotSpecified: (:) [New-PublicFolderMigrationRequest], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : [Server=CO1PR07MB395,RequestId=e9e9e242-9b1c-46ad-8f0f-375eeb0d5527,TimeStamp=10/31/2014 1:47:31 PM] [FailureCategory=Cmdlet-ManagementObjectNo
       tFoundException] 933A0896,Microsoft.Exchange.Management.RecipientTasks.NewPublicFolderMigrationRequest
    Any assistance would be greatly appreciated.
    Thanks,
    Randy
    Randy Goodson

  • Best way to migrate Mailboxes with all permissions Exchange 2010 to Exchange 2010--cross forest

    Hi,
    Due to some Exchange and Active Directory issues (with remnants of old Ex 2003 server), we are going to migrate Exchange 2010 Mailboxes and public folders to a new Exchange 2010 Sp3 server, which is created in a new AD forest.
    I would really appreciate if someone can direct us to the best way to migrate mailboxes and PFs with their permissions, to new Ex 2010 SP3 server. We have around 30 mailboxes, and 300 GB of mailboxes data, and 200 GB of PFdata.
    Thanks in anticipation.
    Regards, David Johnson

    Hello,
    Firstly, you need to creat forest trust between two forests.
    If you want to move AD user account and mailboxes, please use ADMT and PrepareMoveRequest script.
    If you want to migrate public folder, please export data to PST file and then import pst file to new server. 
    Additional article for your reference.
    http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
    Cara Chen
    TechNet Community Support

  • Migrating mailboxes from 2010 to 2013

    I have tried to migrate a mailbox between forest from Exchange 2010 to Exchange 2013 but when I run the new-moverequest on Exchange 2013 I get the following error
    RemoteLegacy moves must involve Exchange 2010 or lower versions only.
    Remote Moverequest dosn't work (The call to ‘https://mail.com/EWS/mrsproxy.svc’ failed. Error details: Could not establish trust relationship for the SSL/TLS secure channel with authority ‘mail.com’. –>
    The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. –> The remote certificate is invalid according to the validation procedure.)
    Can i use RemoteLegacy moves, or only Remote?
    Thanks.

    When migrating mailboxes from Exchange 2010 to Exchange 2013, a Remote Moverequest must
    be used.
    Example: 
    $Cred = Get-Credential (source\account)
    New-MoveRequest -Identity [email protected] -Remote
    -RemoteHostName mail.sourcedomain.com -RemoteCredential $Cred -TargetDeliveryDomain targetdomain.com
    So with the above example, the certificate installed on the source server must include the name mail.sourcedomain.com and target server must trust the certificate.
    Martina Miskovic

  • Downsize Public Folders for Migration to Office 365

    To migrate public folders, I have been following this link: http://technet.microsoft.com/en-us/library/jj983799%28v=exchg.150%29.aspx
    However, this customer's public folders are exceeding well over 50GB. There are contacts and a calendar. I am looking for assistance/advice on downsizing public folders for migrating to Office 365.
    Exchange 2007
    Server: Windows Server 2008 Standard

    Hi,
    To reduce the public folder's size prior to the migration, you can try to delete the old content or split it into multiple smaller public folders.
    Here is a related article for your reference.
    Public Folders and Exchange Online
    http://blogs.technet.com/b/exchange/archive/2013/05/02/public-folders-and-exchange-online.aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Mailflow Problem After Migrating Mailbox From 2007 to 2013

    I thought I was at the point of migrating our mailboxes from 2007 to 2013.  I had created a new test mailbox on the 2013 server and changed all the DNS and virtual directories for the legacy on the 2007 server and was able to successfully send mail
    to the test mailbox out and in both internally and externally.  Then I migrated my first mailbox from 2007 to 2013 and things went south.
    I CAN NOT:
    Send e-mail from a mailbox on the 2007 server to the migrated mailbox on the 2013 server.
    Send e-mail from migrated mailbox to external e-mail address.
    I CAN:
    Send e-mail from the migrated mailbox to a 2007 mailbox and the test mailbox on the 2013 server.
    Send e-mail from the internet to the migrated mailbox and the 2013 test mailbox.
    I unfortunately am running Exchange 2013 with CU6 (I am already aware of the activesync issue and delegation crash issue but saw the info too late).
    Suggestions please!!

    Hi,
    Before going further, I'd like to ask the following questions to troubleshoot the issue:
    1. Could you send email from 2007 mailbox to the test mailbox on 2013 server? 
    2. Did you get any NDR message when sending email to the migrated mailbox failed?
    In addition, I recommend you try the following methods to find out the root cause:
    1. Try to use message tracking tool in exchange 2007 server ,it will help us to find the email which was sent to the migrated mailbox .
    2. Run the following command to check the permission groups of the receive connector:
    Get-Receiveconnector |fl Name,PermissionGroups,Exchangeversion
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Migrate mailboxes from Exchange 2013 to Exchange 2010

    Hello,
    We have a merger and would like to know if it is possible to migrate mailboxes from Exchange 2013 to Exchange 2010 in a cross-forest scenario.
    Or should we first upgrade destination Exchange 2010 to 2013?
    Peteris

    Hi Peteris,
    Based on my tests, we can move mailboxes from Exchange Server 2013 to Exchange server 2010. You can use the Prepare-MoveRequest.ps1 script in the EMS to prepare mailboxes for cross forest moves.
    For more information about it, here is a helpful article for your reference.
    Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
    http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
    Hope my clarification can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Migrating mailboxes to another forest Exchange organisation

    Hello,
    We are looking to achieve 2 migration tasks: one is to upgrade one Exchange organisation from 2010 to 2013 and the second is to migrate mailboxes from the second organisation to the new 2013 server. 
    To explain the scenario in a bit more detail:
    Forest A – 1  AD domain with a single Exchange 2010 server
    Forest B – 1 AD domain with a single Exchange 2010 sever
    Stage 1 – Migrate Forest A to Exchange 2013
    Stage 2 – Migrate mailboxes from forest B to forest A but still keep forest B as its own AD domain. Or to put it another way; we want the users in forest B to have their mailboxes migrated to forest A (linked mailboxes?) but still keep use forest B to login
    etc, essentially making forest A a resource forest for users in forest B
    I hope that makes sense! One of my main concerns is I am assuming it is possible to perform a cross forest migration from forest B which will be at 2010 to forest A which will be 2013. Would it be better to perform the cross forest migrations before hand?
    If someone is able to let me know if what I am proposing is possible I would be extremely grateful. 

    Hi
    There is no problem with any of those ideas.  You can migrate cross-forest between to either 2010 or 2013 irrespective of the source Exchange version, using the native tools.
    http://technet.microsoft.com/en-us/library/ee633491(v=exchg.150).aspx
    If you want to have them as linked mailboxes you just specify the -linkedmailuser switch when you run the preparemoverequest.ps1 script, you then perform the remote move as described in the link above.
    Steve

  • Pre-Requirement for Stage Migration in Office 365

    Hi,
    Please help to find the prerequisites or Hardware and software requirement for performing an Stage Migration on office 365.
    Regards,
    Shabu.B

    Hi,
    This forum is to discuss problems of Office development such as VBA, VSTO, Apps for Office .etc.
    Since your issue is more related to the feature of Office 365, as @AK-Azure said, I suggest you posting in
    OFFICE 365 FORUMS for more effective responses.
    Thanks for your understanding.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Microsoft Office 2013 (Word,excel) Still appear as "Standard" after migrate in ProPlus 365

    Hi,
    I'm planning a mass deployment of Microsoft Office 365 ProPlus with SCCM 2012.
    I made my application, and added a supersedence of Microsoft Office 2013.
    So when I deploy ProPlus, It first uninstall Office 2013, then reboot, then install Office ProPlus 365
    My problem is that when it install Office ProPlus product that I had on Office 2013 and I go in Account tab, I still see "Microsoft Office Standard 2013"
    When I see the others product, I see Microsoft Office ProPlus.
    I'm sure that Standard is uninstalled first, I can also see in Add/Remove programs that there is no Standard version.
    Is that just a bug, or some of my product hasn't migrate on Office 365 Proplus ?
    Thanks ! :)

    @Don, I reboot the client computer after uninstalling Office 2013. Nothing have changed.
    @Aravindhan, I'm lauching Office from the start menu. I already tried to just uninstall Office and see what's happen. Office uninstalling correctly. But When I install ProPlus, I can see "Office Standard" in account tab.. (and Standard doesn't
    appear in Add/remove programs)
    Maybe check c:\windows\temp\SetupExe(YYYYMMDDHHMMxxxxx).log
    This is the Office (MSI) setup logfile, to see if there were any uninstallation errors?
    Are there any standalone Office products installed previously, e.g. SharePointDesigner or similar ?
    It might be necessary to use OFFSCRUB.VBS (from the Office removal Fixit) to clean that up?
    http://blogs.technet.com/b/odsupport/archive/2011/04/08/how-to-obtain-and-use-offscrub-to-automate-the-uninstallation-of-office-products.aspx
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Migrating mailboxes Exchange 2010 to 365, e-mail delivery failed

    We are currently in a hybrid configuration with 2010 and 365. I have migrated one mail box to test, but now when I try to e-mail from that box to internal and external users I get this undeliverable message:
    Generating server: BY2PR05MB630.namprd05.prod.outlook.com
    [email protected]
    Remote Server returned '< #5.7.0 smtp;550 5.7.0 Proxy session setup failed on Frontend with '554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain'>'
    [email protected]
    Remote Server returned '< #5.7.0 smtp;550 5.7.0 Proxy session setup failed on Frontend with '554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain'>'
    Original message headers:
    Received: from BY2PR05MB631.namprd05.prod.outlook.com (10.141.218.20) by
     BY2PR05MB630.namprd05.prod.outlook.com (10.141.218.13) with Microsoft SMTP
     Server (TLS) id 15.0.921.12; Tue, 22 Apr 2014 17:46:14 +0000
    Received: from BY2PR05MB631.namprd05.prod.outlook.com ([127.0.0.1]) by
     BY2PR05MB631.namprd05.prod.outlook.com ([10.141.218.20]) with Microsoft SMTP
     Server id 15.00.0921.000; Tue, 22 Apr 2014 17:46:13 +0000
    Content-Type: multipart/mixed;
                boundary="_000_10047ccea0ec4ac6b152ab717cee271fBY2PR05MB631namprd05pro_"
    From: User <[email protected]
    >
    To: user <[email protected]>
    Subject: FW: SRX614042290246126ID -
    Thread-Topic: SRX614042290246126ID -
    Thread-Index: Ac9eUriGOe4zLpjESEeTsp1IfSBH8AAAAict
    Date: Tue, 22 Apr 2014 17:46:13 +0000
    Message-ID: <[email protected]ok.com>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    X-MS-Has-Attach:
    X-MS-Exchange-Inbox-Rules-Loop: [email protected]
    X-MS-TNEF-Correlator: <[email protected]ok.com>
    x-ms-exchange-parent-message-id: <[email protected]>
    auto-submitted: auto-generated
    x-ms-exchange-generated-message-source: Mailbox Rules Agent
    x-forefront-antispam-report: SFV:SKI;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:BY2PR05MB630;H:BY2PR05MB631.namprd05.prod.outlook.com;FPR:;LANG:en;
    MIME-Version: 1.0
    X-Auto-Response-Suppress: DR, OOF, AutoReply
    X-OriginatorOrg: achievesd.org
    X-OrganizationHeadersPreserved: BY2PR05MB630.namprd05.prod.outlook.com

    Also, since you have tried that for your test environment, how you are proceeding the hybrid migration ?
    You can get better help by using
    exchange server deployment assistant for hybrid deployment migration which auto configure the all setup according to our exchange environment.
    Moreover, here is another appreciable
    resource which can be a good approach to proceed migration from exchange 2010 to office 365.

  • Summary Report after migrating to Office 365

    Hi all,
    I just successfully performed a cutover migration off a SBS 2011 Server.
    Admins are missing the Daily/Weekly Status report email generated by SBS.  The report still goes to the on-premises mailbox.  I also unticked the users from the list and created new emails as "external" recipients but did not work.
    The DNS is authoritative for contoso.local. I don't know how to create a MX record for contoso.com within that zone.
    I think it may be an attribute in AD that needs to be changed. 
    Could you guys provide help with this?
    Regards,
    Frank

    Hi Frank,
    On current situation, please refer to following thread and check if can help you.
    Change
    email address of SBSMonAcct on SBS 2011
    Meanwhile, please refer to the “Completion of the Migration”
    section in following article.
    Step-By-Step:
    Migrating from Exchange 2007 to Office 365
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Migrate mailbox in Hybrid environment with MDM

    Hi,
    Just a question. What if i push an active-sync email profile with Intune to my mobile devices and i migrate someones mailbox from on-premises to Office 365? Will active-sync use auto-discovery to find the mailbox again? Or do i have to push a new email profile
    to the migrated user?
    Does anyone have experience with this?
    Thx.
    Davy

    https://technet.microsoft.com/en-us/library/dn800672.aspx
    If you have deployed an email profile and then wish to change the values for
    Exchange ActiveSync host or Email address, you must delete the existing email profile and create a new one with the required values.
    Paul Goodson
    This posting is provided "AS IS" with no warranties and confers no rights.

Maybe you are looking for