Exchange 2007 edb to Exchange 2013 - mailbox extraction and mounting

Hello everyone, here is my question:
I have a client who has Exchange 2007 running on a Domain Controller which is a Server 2008 and that is the only domain controller in his environment. That said, his domain controller crashed and all the AD data is now lost along with Exchange except the
EDB files. He wants to create a new domain controller with Server 2012 and wants to deploy Exchange Server 2013. Since the Domain Name will be the same, is it even possible to extract the mailbox information from Exchange 2007 EDB and attach it with new Exchange
Server 2013 and point them to newly created users on Exchange? If yes, how exactly will this work? Thanks in advance.

Excellent and factual responses from the others and the instructions/guidance should serve you well. If however you want to avoid building a new server etc you could use Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp to open the 2007 EDB on a 64 bit machine and then you could take 1 of 2 actions to resolve your issue.
1. You could then export all mailboxes to PST and then Import them into the 2013 environment
2. OR you could have DigiScope migrate/recover the data directly from the offline 2007 EDB into the Production 2013 server on the fly, i.e. no end user downtime is required.
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Similar Messages

  • Migration from Exchange 2007 SP3 to Exchange 2010

    Hello,
    We are planning a single server migration from Exchange 2007 SP3 to Exchange 2010.  I'll be building the 2010 server on a 2008 R2 box. My question is, can I make the jump directly to Exchange 2010 SP3, or do I need to install exchange 2010 SP1 first
    - migrate from 2007 SP3, and then install SP3 for exchange 2010 later? 
    Thanks,
    Eric

    @ Hasan
    Dimdik - TAT,
    That's not correct at all, you can migrate exchange server 2007 SP3 and RollUp Update 10 minimum to Exchange Server 2013 with minimum CU1.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • After Exchange 2007 Migration to Exchange 2010, OAB is erroring

    Hello all, 
    I migrated from single server Exchange 2007 to single Exchange 2010 2 months ago using a co-existence environment.  The 2007 server is still running, but it's not doing anything but SMTP relay, as I am waiting on Oracle admin to point their server at
    my new 2010  server.  Yesterday, I noticed a new mail enabled user we created was not showing up in the Address Book.  He is in the Global Address list when I check it from OWA.  And I can see him in my Address book if I search All Users,
    instead of the Global Address List.  Everytime I try to update the Offline Address Book, I get the following error
    OABGen encountered error 80004005 while cleaning the offline address list public folders under /o=2007Server/cn=addrlists/cn=oabs/cn=Default Offline Address Book.  Please make sure the public folder database is mounted and replicas exist of the offline
    address list folders.  No offline address lists have been generated.  Please check the event log for more information. 
    - \Default Offline Address Book 
    There was a Public Folder on the 2007 server, but I don't think anyone was using it.  All of our clients our 2007 or later.  Enable Web-based distribution is enabled and Generation server is my new 2010 server.  Enable public folder distribution
    not enabled.
    Any help would be greatly appreciated.  

    No, the Enable public folder check box is not ticked.  However, the link you provided has led me to other clues.  The author says "To locate the actual
    OAB distribution point on the Client Access Server, the Outlook client will use the autodiscover service."  I wonder if still having the CAS role on the old 2007 Exchange Server still installed is causing issues with Autodiscover.  Below
    are the results of the Test E-mail AutoConfiguration from Outlook.
    The Results tab of the Test E-mail AutoConfiguration:
    Autoconfiguration found the following settings:
    Display Name:  User1
    Redirect URL:  https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml
    Internal OWA URL: https://Exchange2010.Contoso.com/owa
    External OWA URL: https://Exchange2007.Contoso.com/owa
    Protocol: Exchange RPC
    Server: Exchange2010.Contoso.com
    Login Name:  user1
    Availability Service URL: https://Exchange2010.Contoso.com/EWS/Exchange.asmx
    OOF URL: https://Exchange2010.Contoso.com/EWS/Exchange.asmx
    OAB URL: https://Exchange2010.Contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/
    Unified Messaging Service URL: https://Exchange2010.Contoso.com/EWS/UM2007Legacy.asmx
    Auth Package: Unspecified
    Exchange Control Panel URL: https://Exchange2010.Contoso.com/ecp/
    ECP Sub URL: ?p=customize/voicemail.aspx&exsvurl=1
    ECP Sub URL: ?p=personalsettings/EmailSubscriptions.slab&exsvurl=1
    ECP Sub URL: PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=Is<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>
    ECP Sub URL: ?p=organize/retentionpolicytags.slab&exsvurl=1
    Protocol: Exchange HTTP
    Server: Exchange2010.Contoso.com
    Login Name: user1
    SSL: Yes
    Mutual Authentication: Yes
    Availability Service URL: https://Exchange2007.Contoso.com/ews/exchange.asmx
    OOF URL: https://Exchange2007.Contoso.com/ews/exchange.asmx
    OAB URL: https://Exchange2010.Contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6
    Unified Message Service URL: https://Exchange2007.Contoso.com/ews/UM2007Legacy.asmx
    Auth Package: Basic
    Certificate Principal Name: msstd:Exchange2010.Contoso.com
    Exchange Control Panel URL: https://Exchange2007.Contoso.com
    ECP Sub URL: ?p=customize/voicemail.aspx&exsvurl=1
    ECP Sub URL: ?p=personalsettings/EmailSubscriptions.slab&exsvurl=1
    ECP Sub URL: Personalsettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>
    ECP Sub URL: ?p=organize/retentionpolicytags.slab&exsvurl=1
    The Log tab of the Test E-mail AutoConfiguration:
    [email protected]
    Attempting URL https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.xml found through SCP
    Autodiscover to https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.sml starting
    GetLastError=0; httpStatus=401.
    GetLastError=0; httpStatus=302.
    Autodiscover to https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.xml Failed (0x800C8204)
    Autodiscover URL redirection to https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml
    Autodiscover to https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml starting
    GetLastError=0; httpsStatus=200
    Autodiscover to https://carus.Contoso.com/Autodiscover/Autodiscover.xml Succeeded (0x00000000)
    The XML tab of the Test E-mail AutoConfiguration:
    <?xml version="1.0" encoding="utf-8"?>
    <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
      <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
        <User>
          <DisplayName>Chad Wingo</DisplayName>
          <LegacyDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=cwingo</LegacyDN>
          <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
          <DeploymentId>c389bc85-adbe-4481-aa25-1fbc209a6fde</DeploymentId>
        </User>
        <Account>
          <AccountType>email</AccountType>
          <Action>settings</Action>
          <Protocol>
            <Type>EXCH</Type>
            <Server>Exchange2010.contoso.com</Server>
            <ServerDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2010</ServerDN>
            <ServerVersion>738280F7</ServerVersion>
            <MdbDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2010/cn=Microsoft Private MDB</MdbDN>
            <PublicFolderServer>Exchange2010.contoso.com</PublicFolderServer>
            <AD>DATA.domainskc.com</AD>
            <ASUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</ASUrl>
            <EwsUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</EwsUrl>
            <EcpUrl>https://Exchange2010.contoso.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <OOFUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</OOFUrl>
            <UMUrl>https://Exchange2010.contoso.com/EWS/UM2007Legacy.asmx</UMUrl>
            <OABUrl>http://Exchange2010.contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/</OABUrl>
          </Protocol>
          <Protocol>
            <Type>EXPR</Type>
            <Server>Exchange2010.contoso.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Basic</AuthPackage>
            <ASUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</EwsUrl>
            <EcpUrl>https://Exchange2007.contoso.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <OOFUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://Exchange2007.contoso.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://Exchange2010.contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/</OABUrl>
          </Protocol>
          <Protocol>
            <Type>WEB</Type>
            <Internal>
              <OWAUrl AuthenticationMethod="Basic, Fba">https://Exchange2010.contoso.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXCH</Type>
                <ASUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</ASUrl>
              </Protocol>
            </Internal>
            <External>
              <OWAUrl AuthenticationMethod="Fba">https://Exchange2007.contoso.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXPR</Type>
                <ASUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </External>
          </Protocol>
        </Account>
      </Response>
    </Autodiscover>
    Unified Messaging role has not been installed on 2010 Exchange Server yet and UM has been uninstalled on 2007 Exchange Server.  The URLs are just left in IIS I'm guessing.
    I have also noticed that this directory has not updated since the 11/12/2013 C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB.  While this directory continues to update C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB

  • Failing Exchange 2007 upgrade to Exchange 20113

    I have a failing Exchange 2007 SP 2 that I need to upgrade to Exchange 2013.  Yes, I do have consistent mail box backups to disk (Backup Exec 2014).
    I have several failed attempts on creating a VMWare 5 machine out of this EX 7 server.  We are out of hard drive space and unable to do the service pack 3.  The new server (EX 13) will have a 300 gig root directory and data drive of over 1 terabyte.
    I am looking for suggestions for the cleanest solutions to upgrading this server to 2013 since doing a migration with coexistence has been ruled out .  I work for a small company without funds to allow me to purchase some really good software to assist
    with this problem.  I cannot have the email server down for more than over night unless I do it over the weekend.
     

    Hi Praxis,
    Thank you for your question.
    If we could not recovery Exchange 2007 from Exec2014, we suggest you perform a disaster recovery for Exchange 2007 by the following link:
    https://technet.microsoft.com/en-us/library/aa998890(v=exchg.80).aspx
    Then, we could  follow ExchangeITPro’s advice to upgrade Exchange 2007 SP2 to Exchange 2007 SP3 CU10.
    Then we could start migration by the following link:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Exchange 2007 migrate to Exchange 2013

    Dear MS Support,
    I did migrate Exchange 2007 to Exchange 2013
    The install complete, the exchange 2007 and 2013 can work together successful
    DAG has created and work fine
    Below is capture on exchange group after migrate
    The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
    The cerificate enroll with
    Alternative Names: mail.biendongpoc.vn
    The autodiscover on exchange 2007:
    [PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
    Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
    Identity      AutoDiscoverServiceInternalUri
    BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
    I have created new certificate for Two exchange 2013
    The certificate enroll with
    Alternative Names: cas.biendongpoc.vn
    I have create cname cas point to dag  on DNS server
    I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
    I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
    connected to Exchange 2013 and working perfectly
    Our problem, the account exchange 2007 work not stable ,
    sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
    If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
    It is not stable for current exchange 2007
    Anyone who can help me ?
    Thanks

    Hi
    huynhtrongnhatminh,
    I suggest you please go through this article.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Please check this for step by step guide.
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Please point your autodiscover and commonname to Exchange2013 CAS
    Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
    You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally. 
    Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
    Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
    No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
    Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
    http://exchange.sembee.mobi/network/split-dns.asp
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Exchange 2007 migration to Exchange 2013

    Hello Exchange experts,
    I’m Planning an Exchange migration (EX07 to EX13) and despite to have read many many tutorials and technet opinions, I cannot see the correct path to migrate. I hope someone can help me.
    - Actual Infrastructure:
         1 Physical server (SERVER_08): DC + Exchange 2007. IP: 192.168.1.10
    - Future Infrastructure:
         1 Physical Server (SERVER_2012R2): DC, GC, FS. IP: 192.168.1.50
         1 Physical Server (EX2013): CAS,Mailbox. IP: 192.168.1.51
    My questions come once I’ve prepared the squema and I have to start with the Exchange Migration. As far as I know, I think the steps and infrastructure behavior will flow in this way:
    Initial State: Only one Exchange2007 installed and all the clients point to this server, and thus in this moment the value of SCP is the initial Exchange Server SERVER_08.
    In SERVER_08 there is one self-certificate with this names: SERVER_08.test.local and SERVER_08 and all the Outlook clients and Windows Phones use this certificate. This works perfectly.
     I install a secondary Exchange (EX2013) in a new server but in the same internal domain (test.local).
    Once the second Exchange server is installed, the SCP is automactly updated with the new SCP pointing to this Exchange 2013 (EX2013).
          So that the clients don’t give them
     a prompt message, the SCP must be changed with PowerShell to point the initial    Exchange Server (SERVER_08). (Right?)
     Create a A register (mail.test.local) pointing to the new Exchange 2013 (EX2013 - 192.168.1.51).
            At this point, I understand that the clients can coexist with both Exchange Servers (EX07/EX13) and no one will be prompted with new certificate issues. Right?
    Once the Mailbox Databases/Connectors are migrated to the new exchange 2013, I need to modify again through PowerShell the SCP value with the new EX2013
     (mail.test.local).
    When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
    everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime).
    I’ve been reading many tutorials and I want to make sure the steps until coexist both Exchange works fine, and obviously
     if the experts can suggest me something.
    Thanks in advance
    Best Regards
    Tecnico Superior de Sistemas

    There a few things missing in here like the legacy URL specifics, and Outlook client version requirements (do not overlook Outlook, or it will bite you).
    I'm curious about this bit "When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
    everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime).  "
    You should not be advocating the use of self signed certs, they are not supported for Outlook Anywhere.  Even if this is testing, install a Windows CA and use that to issue certs of
    get a cheap commercial one. 
    Training users it is OK to click here to see the dancing pigs never bodes well :)
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Issue removing Exchange 2007 after migration to 2013

    After migrating relatively successfully from Exchange 2007 to 2013, I am in the process of trying to decommission and uninstall 2007 from the servers. Through this process I have been following a guide found
    here. Our old 2007 servers have been off for over two weeks and it seems like a good time to remove them and reclaim some space. I removed the old OAB and Mailbox DB, however when I attempted to remove the Public Folders so I could take the PF DB out the
    following error appeared.
    Get-PublicFolder : There is no existing PublicFolder that matches the following Identity: '\'.
    I know that there are Public Folders existing as I can see them when I run Get-PublicFolderStatistics:
    I've been back and forth across the forums and web and haven't been able to find a solution to this. Ultimately we never have and are not interested in using public folders but they were originally configured when we had a contractor move us from 2003 >
    2007 several years ago. What I would like is to remove all traces of this garbage and just be able to uninstall/delete the old servers and move on with life.
    Any help is greatly appreciated. Thank you in advance.
    Jon Howard

    Hi,
    Have you tried to use Exfolders tool to remove PF?
    More details about exfolders tool refer to the following article:
    http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Remove Exchange 2007 from an Exchange 2013 coexistence.

    Hey everyone,
    I've just installed Exchange 2013 on a new server and all is working great.  It is currently in coexistence with our old Exchange 2007 server.  I've since shut the server down and Exchange 2013 has been working without issue.  However, I haven't
    been able to find any articles on this matter so I figured I would ask the question here.
    How do you remove Exchange 2007 from the coexistence.  Do I just uninstall Exchange 2007 from the old server and it will remove itself from the server and the domain?  Any help/link on this matter would be greatly appreciated.
    Thank you,
    Chris

    Hi Simon,
    I am about to do the same exercise as Chris,  I just would like some clarity.  
    1) When you say mailbox Database, do you mean make sure there are no more mailboxes that you want to move over, or are you actually meaning delete the physical DB on the exchange 2007 server.
    2) If there is no use of public folders does anything need to happen?
    Thanks,
    Terry

  • Address list service failed to respond error on Exchange 2007 (after adding first 2013 server)

    Hi,
    We just installed an Exchange 2013 server within an Exchange 2007 environment.
    The Exchange 2013 (CU6) server will be used to setup a hybrid connection with O365, and move mailboxes to O365.
    After installing the Exchange 2013 server it isn't possible anymore to create/enable mailboxes on the Exchange 2007 server.
    We end up with an error :
    Mig1 TestAccount
    Failed
    Error:
    The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
    Exchange Management Shell command attempted:
    Enable-Mailbox -Identity 'domain.be/customer/TEMP/Mig1 TestAccount' -Alias 'mig1' -Database 'Exchange2007\SG01\DB02'
    When executed via EMS we receive this error :
    The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error

    Hi Lyncer
    This error can be caused if the default Public Folder Database not being pointed to the exchange 2007 database which you are trying to create a new mailbox.
    Also it can happen if System Attendant service is not running.
    Troubleshooting steps:
    1) Restart the System Attendant Service 
    2) Point the affected database to the default public folder
    Follow the below steps to do that 
    Open EMC
    Go to Organization Configuration > Mailbox.
    Select the mailbox database that you want to change the default public folder database.
    Right click the database and select properties
    In <Mailbox Database Name> Properties, click the Client Settings tab.
    Next to the Default public folder database box, click Browse.
    In Select Public Folder Database, select the public folder database from the list of public folder databases, and then click OK.
    Cheers!!!
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Exchange 2007 rejecting e-mails from mailbox with a quote (') in the mailbox name.

    I have a HA Exchange 2007 Environment of 4 servers - two IS servers (primary/standby) and two Hub Transport servers (load balanced).  When I receive an e-mail from an e-mail address with a quote in the name, such as
    brian.o'[email protected], the email gets rejected with the error "550 Requested action not taken: mailbox unavailable(at FROM)".  Is there anything that I can do on my server to resolve this issue?
    telnet mail.domain.com 25
    Trying xxx.xxx.xxx.xxx...
    Connected to smtp.domain.com.
    Escape character is '^]'.
    220 mail.domain.com ESMTP (mx)
    ehlo me.com
    250-mx.domain.com Hello me.com [xxx.xxx.xxx.xxx], pleased to meet you
    250-PIPELINING
    250-AUTH LOGIN
    250-STARTTLS
    250 HELP
    mail from: brian.o'[email protected]
    250 Sender <brian.o'[email protected]> OK
    rcpt to: ***********@domain.com
    550 Requested action not taken: mailbox unavailable(at FROM)

    That transaction looks like you're sending to a non-Exchange server that is rejecting the quote character because that banner does not look like an Exchange response.  If so, that's a problem with that server, not yours.
    Consider removing the quote from your e-mail address.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Migrating Exchange 2007 SP1 to Exchange 2013

    Follow the Exchange Deployment Assistant to the letter and you will not have issues.http://technet.microsoft.com/en-ca/exdeploy2013/Checklist.aspxAnd my guide:You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option...

    This is a slightly daunting task I must admit. I am migrating an old exchange 2007 SP1 installation over to 2013 SP1 and looking for good advice and/or tips. I am finding the whole thing slightly unnerving as there seems to be about a million caveats give or take a few thousand. There seems to be about the same amount of tips, tricks and guides as well, but sadly they are not quite consistent and some are down right contradicting each other.I'm reading similar questions here on spiceworks, and it seems like I'm reading about one horrible episode after another. By now, I assume most have migrated already, so I though I might pick some brains and figure out the best way to do this ;)Might software like CodeTwo Exchange Migration or Dell Migration Manager be a good idea? Are there maybe similar tools available as well?Any feedback is very...
    This topic first appeared in the Spiceworks Community

  • Exchange 2013 mailbox rule and mail forwarding

    HI All,
    when user is forwarding messages from owa to same exchange organization (same smtp domain) or external domain is not working.
    please suggest.

    Hi,
    As ManU suggested, please take your time to post the error information for my further research.
    What's more, please verify if this user can send messages (not forwarding) directly to others.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • How to upgrade Exchange 2007 from Sp1 to SP3 RU13

    Hi everyone, I have a mail system Exchange 2007 SP1 CAS and HUB with 3 servers. 
    The mailboxes are on a Windows Server 2008 Failover Cluster. 
    Domain controllers are Windows Server 2003 SP2 
    I have to update the mail system with Service Pack 3 and RU13. 
    Does anyone can tell me the procedure? where I have to start by the CAS / HUB or cluster mailboxes? 
    How do I update the cluster of mailboxes, the resources on the active node and update it, or liability? 
    There's something I have to take intoaccount before upgrading? 
    I can upgrade directly to SP3? or I have to upgrade before SP2?  thank you very much
    Microsoft Certified IT Professional Server Administrator

    http://technet.microsoft.com/en-us/library/bb885043(v=exchg.80).aspx
    Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers
    and
    http://technet.microsoft.com/en-us/library/ee221147(v=exchg.80).aspx
    How to Install the Latest Service Pack or Update Rollup for Exchange 2007
    and, yes, you can go straight to SP3
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2007 CAS Unable To Display 2013 Mailbox Free/Busy to Clients

    Hi,
    I'm in the process of migrating to Exchange 2013 from an Exchange 2007 backend.  I have 2 2007 CAS servers in a Windows NLB named webmail.domain.com, and I'm having a problem with only a single one of those CAS servers being able to display the free/busy
    information of a mailbox residing on a 2013 mailbox server.  The other CAS works fine.
    Both CAS servers are Exchange 2007 SP3.  Both CAS servers have their virtual directories named webmail.domain.com/{vitual direction url}.  I built both servers from the ground up and configured them at the same exact time performing the same steps
    on each.  My 2013 CAS servers are in a Windows NLB for mail.domain.com, and they have all their virtual directories named for mail.domain.com.  These are separate entries in DNS.  Other autodiscover services are working fine.  I have most
    traffic flowing Exchange 2013 now as well.
    I've done compares on the virtual directories for each 2007 CAS, and they appear to be the same.  If I bypass the NLB and just go directly to the casname01/owa, I see free/busy no problem.  If I go to casname02/owa, then free/busy doesn't work
    ONLY for 2013 mailboxes.  It will display 2007 mailbox free/busy fine.  To complicate matters, I still have a 2010 CAS in the environment from a failed O365 pilot.
    Where can I look to begin to troubleshoot this?  Thanks.

    In the App log on the 2007 CAS, I'm seeing an Event ID 4002 from MSExchange Availability (below).  This made me check my 2013 CAS NLB.  It looks like it is one of the 2013 CAS servers in the mail.domain.com NLB that is causing this behavior.  I
    could still use guidance.  Thanks.
    Process 3576[w3wp.exe:/LM/W3SVC/1/ROOT/EWS-1-130366189751718750]: Proxy request IntraSite from Requester:S-1-5-21-2089814041-428609448-1854500012-56527 to https://mail.domain.com/EWS/Exchange.asmx failed. Caller SIDs: S-1-5-21-2089814041-428609448-1854500012-56527.
    The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: 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 10.128.13.38:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()
       at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult, Object& internalAsyncState, Stream& responseStream)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
       at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
       at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.CompleteRequest(). The request information is ProxyWebRequest type = IntraSite, url = https://mail.domain.com/EWS/Exchange.asmx
    Mailbox list = <NA-Bedford Adriatic Conference Room>SMTP:[email protected], Parameters: windowStart = 1/26/2014 12:00:00 AM, windowEnd = 3/9/2014 12:00:00 AM, MergedFBInterval = 30, RequestedView = MergedOnly
    .. Make sure that Active Directory site/forest containing the user mailbox has at least one local Exchange 2007 server running Exchange Availability service. Turn up logging for MSExchange Availability service and test basic network connectivity.

  • Exchange 2013 OWA server accessing mailboxes on Exchange 2007

    Hi All-
    I just completed the installation of Exchange 2013, co-existing with Exchange 2007.  I have 2013 CU1 and 2007 SP3 RU10.  The issue I have is that I cannot access mailboxes existing in the 2007 mailbox servers through my 2013 OWA server.  Is
    there some advanced configuration that I need to do, on either 2007 or 2013? The documentation I have read seems to indicated that I should be able to use OWA 2013 to access 2007 mailbox.
    TIA,
    Chris

    Just the HTTP 500 error through the website.  I found this in the HTTPProxy logs:
    2013-04-30T16:17:12.093Z,100f0d73-0d2c-4bee-aa7d-54ada2c4e050,15,0,620,16,,Owa,/owa,,FBA,True,Domain\username,,Sid~xxxxxx,Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0),10.1.200.21,servername,500,,ServerNotFound,GET,,,,,WindowsIdentity,,,,0,,,,2,0,,0,,0,,0,0,0,0,,-1,0,0,3,,,,2,,,OnBeginRequest=1;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
    Unable to find proper HTTP service. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: Unable to find proper HTTP service.    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetBestBackEndServiceForVersion[ServiceType](TopologyWithSites
    topology  ClientAccessType clientAccessType  Predicate`1 versionNumberCondition)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)   
    at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox  BackEndServer
    mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1 operationToTrack  Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon
    beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass2b.<OnCalculateTargetBackEndCompleted>b__2a()    --- End of inner exception stack trace ---;

Maybe you are looking for