Exchange 2007 to Exchange 2010 Transition

I am in the process of transitioning a client from Exchange 2007 to 2010(clients are XP/Win 7 with Outlook 2007/Outlook 2010). I know if have to extend the schema for Exchange 2010 and there will be co-existence throughout the process. At this point, Outlook
profile on users are point to either IP or netbios name of the server and their credentials. When I move their mailbox(in Exchange 2010 migration wizard), do I have to go to each Outlook and repoint their profile to the new netbios name of the Exchange 2010? 

Outlook 2007 and newer will use a combination of AutoDiscover and redirection to update the client profile from the existing settings to the new server supporting their mailbox.  Just make sure you have DNS resolution for autodiscover and the new
server names.
Gary A. Cooper | Senior Systems Architect | MCA:Exchange 2003/2007/2010 | MCM:Exchange 2003/2007/2010 | Horizons Consulting, Inc. If you have found my answer helpful, please vote as such.

Similar Messages

  • Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

    I'm trying to remove Exchange 2007 from an SBS 2008 server
    (Server 2008 Standard FE).  My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
    We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
    I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers.  We have two full blown DC's in the environment.
    I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server.  I can NOT seem to find a TechNet article that shows me how
    to proceed in this kind of scenario.  I am trying to use the TechNet article:
    http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
    This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard. 
    When I go to Disable Mailboxes I get the following error:
    Microsoft Exchange Error
    Action 'Disable' could not be performed on object 'Username (edited)'.
    Username (edited)
    Failed
    Error:
    Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
    OK
    I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010.  I just want
    to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
    Can someone point me in the right direction?
    Thanks!

    Hi,
    Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
    2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
    On current situation, please refer to following articles and check if can help you.
    Transition
    from Small Business Server to Standard Windows Server
    Removing SBS 2008 –
    Step 1: Exchange 2007
    Removing SBS 2008 – Step 2:
    ADCS
    Removing
    SBS 2008 – Step 3: remove from domain / DCPROMO
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
    does not guarantee the accuracy of this information.
    Hope this helps.
    Best regards,
    Justin Gu

  • OUTLOOK 2013 permission shared calendar Free/Busy doesn't work for some the users Exchange 2010 and Exchange 2003 that use outlook 2007/2010

    Hello,
    We are in coexitence organisation (transition Migration) Exchange 2003 sp2 and Exchange 2010 sp1.
    Users in Exchange 2003 use outlook 2007 and outlook 2010
    Users in Exchange 2010 use outlook 2007, outlook 2010 and outlook 2013.
    Issue: users in Exchange 2003 can't open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
    User in Exchange 2010 with outlook 2007 can't also open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
    Is it normal ? or exist some configurations to do in order to coexist all thoses clients and servers ?
    Thanks in advance

    Hi,
    Does this issue occur on Outlook only or both Outlook and OWA?
    Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
    If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
    I suggest run Outlook under safe mode to avoid some AVs and add-ins.
    I suggest re-create profile to refresh the caches.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Public Folders no longer visible in Outlook 2007 with Exchange 2010

    Hi all,
    This is a perplexing problem because I though I had done everything right
    About 1 year ago, I migrated my Exch2007 to Exch2010.  The 2007 hardware was showing signs of quitting but it hung in there long enough to complete the migration.
    All the user mailboxes, OWA, all other functions moved to the new server.
    We use legacy Pub Folders and I manually created a Pub folder database and set up all the Pub folders to replicate from 2007 to the 2010.  Once replication has taken place, I removed the 2007 replication partner on all the Pub and System folders in
    prep for removing the 2007.  But then I got busy and never finished removal.
    Flash forward to a few weeks ago and the Exch 2007 box goes down hard, RAID containers gone, totally lost.  I did not immediately worry since all was still fine with Outlook and Pub Folder Access.
    I got around to cleaning things up and after verifying that there was nothing pointing to the old server including the OAB and any PF, I used ADSIedit to remove the reference to the old server in the Exchange Organization.  Since then, although I still
    see the PF object in the Mgmt Tool, Outlook does not see their existence.  OWA cannot see them either.
    I have read that GAL problems can cause this so I have recreated this object to see if will help.
    Has anyone else faced this situation?  I really need to get PF access back...

    Here is an update:
    When attempting to "Update" the Default Offline Address List, I get the following error:
    Microsoft Exchange Error
    Action 'Update' could not be performed on object 'Default Offline Address List'.
    Default Offline Address List
    Failed
    Error:
    Couldn't find database "Acteon.local/Configuration/Deleted Objects/Public Folder Database
    DEL:9f2e6205-6d06-4cc8-91be-423df4248a4c". Make sure you have typed it correctly.
    OK

  • 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.

  • Problems with a shared calendar using Outlook 2007 and Exchange 2010

    Hello all,
    We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
    I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
    who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
    One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
    of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
    I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
    am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
    I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
    able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
    So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
    one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
    I realize this is a big mess, and your help would be greatly appreciated.

    Hi Nigel,
    How is the impact, just one user or all users, Outlook or OWA?
    If just one user, it seems like an issue on the Outlook Client side.
    Please trying to re-create new profile to fresh the caches.
    Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
    Found a similar thread for your reference:
    Calendar Sharing not available error message
    http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • I need help with a migration from Exchange 2010 to 2007

    Hi All,
    I need help migrating mailboxes from a separate forest / domain using exchange 2010 to our Exchange 2007 SP3 servers..  I am following this procedure:
    1. On source server, create a mailbox user, test01.
    2. On target server, run the following command to move the AD account:
    Prepare-MoveRequest.Ps1 -Identity [email protected] -RemoteForestDomainController FQDN.source.com -RemoteForestCredential $Remote -LocalForestDomainController FQDN.target.com -LocalForestCredential $Local -UseLocalObject -Verbose"
    3. Run the ADMT to migrate the password and SID history.
    4. Run the following command to move the mailbox:
    New-MoveRequest -Identity '[email protected]' -RemoteLegacy -RemoteTargetDatabase DB03 -RemoteGlobalCatalog 'GC01.humongousinsurance.com' -RemoteCredential $Cred -TargetDeliveryDomain 'mail.contoso.com'
    (Changed all the details obviously)
    It gets to 95% and shows this error
    01/12/2014 12:47:24 [EX2K10] Fatal error UpdateMovedMailboxPermanentException has occurred.
    Error details: An error occurred while updating a user object after the move operation. --> Active Directory operation failed on DC.DC.COM . This error is not retriable. Additional information: The parameter is incorrect.
    Active directory response: 00000057: LdapErr: DSID-0C090A85, comment: Error in attribute conversion operation, data 0, vece --> The requested attribute does not exist.
       at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox(UpdateMovedMailboxOperation op, ADUser remoteRecipientData, String domainController, ReportEntry[]& entries,
    Guid newDatabaseGuid, Guid newArchiveDatabaseGuid, String archiveDomain, ArchiveStatusFlags archiveStatus)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass3c.<Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox>b__3b()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.UpdateMovedMailbox(UpdateMovedMailboxOperation op, ADUser remoteRecipientData, String domainController, ReportEntry[]& entries,
    Guid newDatabaseGuid, Guid newArchiveDatabaseGuid, String archiveDomain, ArchiveStatusFlags archiveStatus)
       at Microsoft.Exchange.MailboxReplicationService.RemoteMoveJob.UpdateMovedMailbox()
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.UpdateAD(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: IMailbox.UpdateMovedMailbox
    OperationSide: Target
    Primary (b5373e49-6a06-41f4-990e-27807c7a57f3)
    01/12/2014 12:47:24 [EX2K10] Relinquishing job.
    Any ideas what i can do about this? 

    Hi,
    From your description, I recommend you follow the steps below for troubleshooting:
    Open the problematic user in AD and check the Email Address. Verify if you can open or edit the x400 address. If no, remove the x400 address and recreate it. If yes, ensure that the name is spelt correctly. After that, continue to move the mailbox and check
    the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2007 to Exchange 2010 Cross Forest

    Hi
    We have a scenario where we have an Exchange 2007 organization (Org A - Source) and a separate Exchange 2010 organization (Org B - Target). Both the organizations (AD Forests) have two way trusts between them.
    We want to have our Exchange 2007 users have their mailboxes hosted on Exchange 2010 organization. Meaning that the user (AD) accounts of Org A will remain in Forest A but there mailboxes will be available on Exchange 2010 servers in Org B. So we don’t need
    a user / group migration stuff here and mailbox data on Exchange 2007 servers is also not critical (not required to be migrated) so we will be creating new disabled accounts and mailboxes in Org B for each user in Org A and connect the mailboxes. There will
    be a brief period of co-existence between two Orgs (to enable mail-flow) until all the users have their mailboxes active in Org B. Need to figure out a way to achieve this.
    We are planning to follow the steps below:
    Setup name resolution between the forests (although basic connectivity is there and we can ping servers in one forest using IP Addresses from other forest) –
    Please suggest if this is necessary or we can get away with it?
    Setup SMTP namespace sharing for Exchange 2007 SMTP Domain name
    Add Exchange 2007 SMTP domain as authoritative domain to E2K10
    Create EAP for new SMTP Domain
     SMTP Connector Creation for Direct E-mail Routing (Co-exist) Between Forests
    Create disabled Mail Enabled (not Mailbox Enabled) User or Mail Enabled Contact in Org B.
    Can we use Prepare-MoveRequest.ps1 script to create these?
    Once a mail enabled user / contact is created in Org B for all the users, change incoming traffic from Internet for Org A SMTP domain to hit HT server in Org B
    Make changes to Exchange 2010 certificate and install new certificate
    Select a batch of users every day, create new mailbox for them using scripts in Org B and delete the corresponding contact in Org B
    Can someone please confirm if this is correct and point out something I am missing?
    Is there any other way to achieve the same goal?
    Thanks
    Taranjeet Singh
    zamn

    Hi Everyone
    Thanks for the inputs so far. I need to confirm some steps to establish direct email flow unless all the mailboxes are created in target organization, can somebody have a look at the steps below and confirm if they are correct or add something that
    I missed here:
    Setup source Exchange organization:
    a) Add unique SMTP domain for source organization, like @source.local. This domain will be added to all mail enabled objects in this organization and will be used for internal routing only
         i) Add to Accepted Domains list
         ii) Create EAP to add domain to existing objects
    b) Use manual means to stamp SMTP domain to objects in source organization on objects that don’t have EmailAddressPolicyEnabled set to False
    c) Create Send Connector to target forest. The target domain should also have a unique e-mail address, like @target.company.com (in our case 19 SMTP domains including JUBL.COM)
         i) Include the valid SMTP domains and the unique one for internal routing
             (source.local)
         ii) Point to a smart host in the target forest
    d) Set existing SMTP domain (JubilantRetail.com) as “Internal Relay Domain”. The target Exchange org will be authoritative for this domain
    Setup target Exchange organization
    a) Create Send Connector to unique SMTP domain in source forest. Includes shared name space (source.local) and @JubilantRetail.com
    b) Set Default receiver connector, being used by source forest, to allow anonymous connections
    c) Add shared SMTP domain (source.local) to Accepted Domains list as authoritative
    d) Create EAPs to replicate the SMTP domains (e:g JubilantRetail.com and source.local) in the source environment
    Thanks
    Taranjeet Singh
    zamn

  • Configuring Message Clasifications Exchange 2010 - Outlook 2007/2010/2013

    Hi
    I created Message Classification as described in:
    http://technet.microsoft.com/en-us/library/bb123498(v=exchg.141).aspx
    New-MessageClassification ....
    New MessageClassification is visible in OWA.
    I stared deploy Message Classifications for Outlook 2007 using this
    http://technet.microsoft.com/en-us/library/aa998271(v=exchg.141).aspx
    Of course there is small bug: "AdminClassificationPath"="c:\\Classifications.xml" but is should be
    "AdminClassificationPath"="c:\Classifications.xml"
    After set up it doesn't work. The same for Outlook 2010 and 2013?
    Does anybody deploy Message Classifications for Outlook 2007 or 2010 or 2013 with success?
    I use Exchange 2010 SP3 with all RU and Outlook 2007, 2010, 2013 with all updates.
    Kind Regards Tomasz

    Hi,
    How do you know this is an old reoccurring message? Based on the content or time?
    Since the MailboxAutoReplyConfiguration is correct, I suspect the issue can occur by certain client machine. At this stage, I suggest you disable OOF and re-enable
    OOF on the problematic machine. If the issue persists, please refer to the following article to clean the problematic client’s Outlook rules. (run Outlook.exe /cleanrules in Run console.)
    http://www.tech-recipes.com/rx/2161/outlook_2007_clean_up_command_line_switches/
    Thanks.
    Novak Wu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    [email protected]  
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • 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

  • TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

    When customer configures the ActiveSync account on Apple Mail (using Exchange Server 2010 CAS array name) for the user whose mailbox is on Exchange Server 2007, they are not able to get any mail and account displays offline. It shows the mailbox empty as well, even though mailbox has the email items in it.
    But when same account is configured using ActiveSync (using Exchange 2007 CAS Server name) it works fine.
    ActiveSync & Web Services URLs for Exchange 2010 and Exchange 2007 are given as below:
    S#
    Virtual Directory
    URL
    Exchange Server 2010
    Exchange Server 2007
    1
    Web Services Virtual Directory
    Internal URL
    https://email2.domain.ae/EWS/Exchange.asmx
    https://email.domain.ae/EWS/Exchange.asmx
    2
    Web Services Virtual Directory
    External URL
    https://email2.domain.ae/EWS/Exchange.asmx
    https://email.domain.ae/EWS/Exchange.asmx
    3
    ActiveSync Virtual Directory
    Internal URL
    https://email2.domain.ae/Microsoft-Server-ActiveSync
    https://email.domain.ae/Microsoft-Server-ActiveSync
    4
    ActiveSync Virtual Directory
    External URL
    https://email2.domain.ae/Microsoft-Server-ActiveSync
    https://email.domain.ae/Microsoft-Server-ActiveSync
    Following error is logged on Console on Mac when this issue happens:
    30/10/12 3:27:28.398 AM
    Mail
    *** Assertion failure in -[EWSConnection _fetchRootFolderId:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSConnection.m:202
    EWS fetchRootFolderId: expected one folder in response, received: 0
    0   Message                             0x00007fff8cdeeef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
    1   Message                             0x00007fff8cdef08e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
    2   Message                             0x00007fff8cd1c8db -[EWSConnection _fetchRootFolderId:] + 768
    3   Message                             0x00007fff8cd1deba -[EWSConnection _connectAndAuthenticateUsingAccount:] + 650
    4   Message                             0x00007fff8cd1c42d -[EWSConnection connectUsingAccount:] + 462
    5   Message                             0x00007fff8cd1996a -[EWSAccount authenticatedConnection] + 437
    6   Message                             0x00007fff8cd2c00e -[EWSGateway connection] + 55
    7   Message                             0x00007fff8cd2dddf -[EWSGateway sendMessage:forRequest:] + 43
    8   Message                             0x00007fff8cd3e54c -[EWSRequestOperation executeOperation] + 108
    9   Message                             0x00007fff8ce0f97f -[MonitoredOperation main] + 228
    10  Foundation                          0x00007fff94aae6b4 -[__NSOperationInternal start] + 705
    11  Foundation                          0x00007fff94ac1912 ____NSOQSchedule_block_invoke_2 + 124
    12  libdispatch.dylib                   0x00007fff8adc8a86 _dispatch_call_block_and_release + 18
    13  libdispatch.dylib                   0x00007fff8adc9965 _dispatch_worker_thread2 + 255
    14  libsystem_c.dylib                   0x00007fff8a32c3da _pthread_wqthread + 316
    15  libsystem_c.dylib                   0x00007fff8a32db85 start_wqthread + 13

    Hi Akebono,
    Let's check a few things in your server:
    1. From the Organization Configuration - Client Access - Exchange Activesync policies - Default: Verify if the option "Allow non-provisionable devices" is ON.
    2. From Server Configuration - pointing <YourExchange2010> - Certificates: Verify if your SSL certificate is assigned to IIS. (You should also be able to see this certificate from OWA https session)
    3. The problem may also reside in iPhone outdated software, try to test activesync connection from iPhone with the latest OS version.
    4. Take a look at logs in C:\inetpub\logs\LogFiles\W3SVC1\ of Exchange 2010, those might give some more details on connectivity problems.
    5. If you still experience such problems - post the ExRCA error report here.
    ▲ Vote if Helpful / Mark if Answer
    MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
    MaximumExchange.ru

  • Outlook 2007 Clients Cannot Access Free/Busy Calendar info. for Exchange 2010 Mailbox

    Hi:
    I have Outlook 2007 clients that cannot access Free/Busy Calendar info. for Exchange 2010 mailboxes.  They receive error like "...you do not have appropriate permissions..."
    If those same users logon to a machine running Outlook 2010 then they can view the free/busy info. of the other user's mailbox, so I believe the permissions are set correctly on the mailbox to allow the viewing.
    Any insights are greatly appreciated!
    Thank you!
    Bob Herman IT Tropolis

    Hi Herman,
    As you said, it seems users have proper permissions on mailbox.
    Please make sure users has Reviewer permission on Outlook 2007.
    Please try to run Outlook 2007 under safe mode or re-create profile.
    Also try to turn Outlook 2007 to Exchange Online mode from Cached mode.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Does MS outlook 2007 in client machine is recommended in Exchange 2010

    Hi All,
    We have a users who uses an outlook via citrix. The outlook clinet on citrix servers is 2007 SP1 and recently there is an upgrade at Exchange server from 2007 to 2010 and all users mail boxes are upgraded to Exchange 2010. After upgrading users mail box to
    2010, there are many issue like
    1. Outlook takes more time to load for few users.
    2. Gets a pop-up "trying to connect to Exchange server".
    3. Due to this, performance of citrix becomes very slow. Citrix works fine once outlook closes.
    4. Another strange thing.....there are 2 mailboxes under Exchange 2007, when we send an email from these mail box the mail shows in Outbox but mail got delivered recipients and will not show up in Sent mails.. :(
    Could you please give me some suggestions.

    For 1-3 problem, you may try to run Outlook in safe mode ("Outlook.exe /safe") without Anti-virus running and check whether the performance of Outlook against Exchange in Citrix platform is fine. If the problem is not caused by client, I think there might
    be something configuration problem on Citrix or Windows Server site.
    Here is a discussion thread with the same topic from Citrix forum
    http://discussions.citrix.com/topic/310220-poor-performance-on-new-xenapp-farm/
    For the Question 4, please check the following Outlook option to check the result.
    File > Options > Mail tab > Save messages section > tick the option "Save copies of message in the Sent Items folder"
    Tony Chen
    TechNet Community Support

  • Exchange 2007 and exchange 2010 Federation

    Hi all I am trying to federate between Three organisations
    org A exchange 2007 with exchange 2010 cas
    org B exchange 2010.
    org C exchange 2010.
    I cannot share my calendar from org A to Org B
    I can share Org B to Org A and Org B to Org C.
    when I try from Org A to Org B or Org C
    When I try to share free/busy fro the exchange 2007 with exchange 2010 cas. The user gets an error
    "calendar sharing is not available with the following entries because of permission settings on your network."
    -availabilityaddressspace. Autodiscover works TXT works. I have added a user from Org B as a contact in exchange.
    The exchange 2010 server is not the CAS server for the exchange environment and I is not a proxy for exchange 2007. Is this where I am failing ?
    Heeeelp

    Hi Nigel,
    How is the impact, just one user or all users, Outlook or OWA?
    If just one user, it seems like an issue on the Outlook Client side.
    Please trying to re-create new profile to fresh the caches.
    Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
    Found a similar thread for your reference:
    Calendar Sharing not available error message
    http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 - Decommissioning Exchange 2007 Coexistence and Removal of Public Folders

    We are about to decommission exchange 2007, currently in coexistence with Exchange 2010.
    We do not want to use ANY public folders in exchange 2010 going forward. Will do this after decom of 2007:
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
    I see this in the outlook connection status in outlook:
    I have changed all Exchange 2010 mailbox databases to use a temporary 2010 public folders db named "public1" so that it is not communicating with the 2007 mailbox virtual server. However, the exact same connection status appears after I changed
    the 2010 mailbox DBs to use a 2010 public folder db instead of the old 2007.
    Question is, is it safe to decom the 2007 environment now? Is it normal to still have a connection to 2007  in "connection status" in outlook when the users mailbox is on a 2010 mailbox db? Is this connection related to public folders or something
    else that needs modified before decom?
    Thanks,
    Josh

    So, that wasn't the answer. I switched the Public folder DB on each mailbox database to a exchange 2010 server, PF DB, but hadn't actually moved any data from 2007 to 2010. 
    I didnt realize this is needed when we don't use public folders except for free-busy, default, etc.
    What is the correct way to move the default public folders to a 2010 public folder?
    I'm using the below URL as a template to migrate this info to a 2010 PF db.
    https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
    "The user Public Folders then need to be replicated to the Exchange 2010 Public Folder database as well. It is possible to manually configure
    all Public Folders with a new replication partner, but it’s better to use PowerShell scripts that Microsoft delivers with Exchange Server 2010. Open the Exchange Management Shell and navigate to the Scripts directory
    by entering the CD $ExScripts command,
    and execute the following script:
    AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\" 
    -ServerToAdd 2010MBX"
    My question is, do I have to do this "3rd step" since I don't think i have any custom "user public folders". Is this the user's free busy that I have to migrate, or is this author referring to custom PF db info?
    Do I have to have public folders for free-busy and default exchange services at all in 2010?

Maybe you are looking for