Moving mailbox from exchange 2013 back to exchange 2007 ..

Hi Guys,
I recently configured configured co-existence between exchange 2007 and exchange 2013. I moved a pilot user from exchange 2007 to exchange 2013 and now the user has issues receiving mails.
I am trying to move the user back to 2007 pending the resolution of the issue. The move status says completed but the mailbox remains in the exchange 2013 environment.
I need to return the user to an exchange 2007 mailbox database ..any ideas on what I am missing.
 Thanx guys ..
~Richard
..forever is just a minute away*

Hi Richard,
Please move your mailbox from Exchange 2013 to 2007 from the Exchange 2013 admin center (EAC) and the Exchange Management Shell instead of EMC in Exchange 2007.
Then check whether the issue persists. If possible, please provide more error logs for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

  • OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

    Anyone come across this?
    Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
    outlook client knows the mailbox has moved as it connects to the new server
    Not happening to every mailbox
    thak=nks

    Hi,
    After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
    Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
    I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
    If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Recreation of user mailbox from exchange 2007 to Exchange 2013

    In my domain I was using Exchange 2007 earlier. I have installed Exchange 2013 successfully and running perfectly. I have one Issue:
    1. A user's mailbox in Exchange 2007 was disabled from Exchange 2007 and recreated on Exchange 2013.
    When a user try to send mail from outlook be it old one(2007) or new exchange(2013), gets NDR
    If user send via owa it get delivered.
    2. External mails are coming and user can send also like gmail or yahoo.
    This is not an issue of cached address (outlook) I have checked this possibility.
    Any luck
    Deepak Vashistha
    Deepak Vashistha Network Admin. Mayo College Ajmer

    Hi,
    From your description, OWA works well, the issue is related to Outlook side. In your case, I recommend you update the Address Book manually on Outlook and check the result. If the issue persists, you need to re-create the profile.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

    Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
    I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
    "Could not find a valid mailbox migration for this organization"
    Do you know that you can be?
    regards
    Microsoft Certified IT Professional Server Administrator

    Hi,
    From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
    Migration.8f3e7716-2011-43e4-96b1-aba62d229136
    If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
    Hope this can be helpful to you.
    Best regards,
    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]
    Amy Wang
    TechNet Community Support

  • Move Mailbox from Exchange 2007 to 2013 creates additional Contacts and Junk E-mail folders in Outlook Clients

    I have moved a handful of mailboxes from my Exchange 2007 server to my new Exchange 2013 server.  When the users logon to Outlook, usually Outlook 2007 Pro, they have a new default Contacts folder and Junk Email folder that are empty.  I
    have to copy all the user's contacts into the new default folder and delete the old one.  Not sure why this is happening.  Any information would be appreciated.  Thanks.

    Are you sure your Outlook 2007 is compatible with Exchange 2013?
    http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    http://support.microsoft.com/default.aspx?kbid=2687404
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

    Hi,
    I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
    Configuration server Exchange 2007 SP3 :
    Domain : test.com
    OS : Windows 2008 server SP2 (not R2)
    Firewall : OFF
    Exchange roles are on separate three  servers : CAS - MAILBOX - HUB.
    Configuration Server Exchange 2013 :
    Domain : new.com
    OS: Windows 2012 R2
    Firewall : OFF
    This environment is on a closed network unable to reach internet.
    I have try to restart the Replication service, but it didn't worked.
    I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
    Anyone ever had this issue?
    Thanks you and have a nice day.

    Hi ,
    Based on my knowledge below things need to checked.
    1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
    2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
    DataMoveReplicationConstraint : None
    Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
    3.Restart the Microsoft exchange mailbox replication service and check the results.
    4. Have you tried moving the same mailboxes to the different databases.
    5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
    Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
    Please feel free to reply me if you have any queries.
    Thanks & Regards S.Nithyanandham

  • Cannot move more than 2 mailboxes from exchange 2007 to Exchange 2013

    I have been trying to move mailboxes from ex2007 to ex2013with the new-migrationbatch and the new-moverequest command.
    I have a DAG-cluster with two servers with all roles.
    What happens is that I cannot get more than two concurrent mailbox moves.  If I restart the MRS-service nothing happens. I have changed the config-file for the mailbox replication service and currently have these settings:
    MaxMoveHistoryLength="5"
    MaxActiveMovesPerSourceMDB="20"
    MaxActiveMovesPerTargetMDB="20"
    MaxActiveMovesPerSourceServer="100"
    MaxActiveMovesPerTargetServer="100"
    MaxTotalRequestsPerMRS="100"
    What is funny is that when I start a new batch with autocomplete off, only two mailboxes goes to 95% and the rest of them is not even started. 
    The command I use is  New-Migrationbatch -local -Name TestNew -csvdata ([System.IO.File]::ReadAllBytes("c:\temp\exchange\migration\testmigration.txt")) -targetdatabases mdb001,mdb002 -autostart
    Here is the output of Get-MigrationConfig | fl
    RunspaceId : d382f8a7-924a-4f0e-812e-f18970b632e2
    Identity :
    MaxNumberOfBatches : 100
    MaxConcurrentMigrations : Unlimited
    Features : MultiBatch
    CanSubmitNewBatch : True
    SupportsCutover : False
    I have off course restarted both servers and services.

    Just out of curiosity, on which server you made these changes? Mailbox or CAS? And on Target or Source Server? 
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://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.

  • Cannot transfer mailbox from Exchange 2007 to Exchange 2013

    Error message I get is below:
    Any one got the same issue?
    It was working fine a few days ago,suddenly cannot move mailboxes.
    -Tried to create another database in case it has a limit: same issue
    -tried to move from GUI and shell same issue.
    MigrationTransientException: The call to ‎'net.tcp://domain.local/Microsoft.Exchange.MailboxReplicationService.ProxyService domain.local ‎(15.0.995.28 caps:017FFFFFCB07FFFF)‎‎' timed out.
    Error details: This request operation sent to net.tcp://domain.local/Microsoft.Exchange.MailboxReplicationService.ProxyService did not receive a reply within the configured timeout ‎(00:00:50)‎.
    The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message.
    Please consider increasing the operation timeout ‎(by casting the channel/proxy to IContextChannel and setting the OperationTimeout property)‎ and ensure that the service is able to connect to the client. -->
    The call to ‎'net.tcp://lnp-exch2013.loopartners.local/Microsoft.Exchange.MailboxReplicationService.ProxyService domain.local ‎(15.0.995.28 caps:017FFFFFCB07FFFF)‎‎' timed out. Error details:

    Hi,
    I recommend you refer to the following article:
    http://blogs.technet.com/b/asiasupp/archive/2011/06/23/when-you-attempt-to-move-mailbox-from-to-exchange-online-you-receive-the-error-quot-the-call-to-microsoft-exchange-mailboxreplicationservice-timed-out-quot.aspx
    Cause:
    The DataImportTimeout property may be set too low.
    Resolution:
    To isolate the issue, you may check how it works if you increase the timeout with the following steps:
    On the Client Access server, open the following file with a text editor such as Notepad:
    \ExchWeb\EWS\web.config
    Locate the following section in the web.config file:
    <!-- Mailbox Replication Proxy Server configuration -->
    <MRSProxyConfiguration
    IsEnabled="true"
    MaxMRSConnections="100"
    DataImportTimeout="00:01:00" />
    Make sure value of the IsEnabled property is set to true.
    Check the value of the DataImportTimeout property. The minimum value is one minute (00:01:00), and the maximum value is 30 minutes (00:30:00).
    Set a higher value, but make sure the value is less than 30 minutes.
    The recommended value for this field should be 00:20:00 (20 minutes).
    After the values are configured correctly, save and close the web.config file.
    Niko Cheng
    TechNet Community Support

  • Moving mailboxes in Exchange 2007

    Does anyone know what is the effects of moveing VoIP-enabled mailboxes to another Exchange 2007 servers?

    The key text from the link I cited in my initial response:
    Moving Subscriber Mailboxes for Cisco Unity 8.x
    From time to time you may need to move subscriber mailboxes to another server that is faster or has more disk space available, or you may want to move mailboxes when you add new servers to your network. It is possible to move subscribers between servers without having to shut down Cisco Unity.
    Caution If you are moving a group of subscriber mailboxes at once, confirm that you do not inadvertently select the Unity Messaging System, UAmis, UVPIM, UOmni, or USbms Exchange mailboxes. To move these special mailboxes, see the "Moving the Unity Messaging System, UAmis, UVPIM, UOmni, and USbms Exchange Mailboxes for Cisco Unity 8.x" section.
    To move Exchange mailboxes from one server to another, follow the instructions in the Microsoft Exchange documentation. "

  • Move mailboxes and public folders from exchange 2007 to Exchange 2013

    1. How do i move mailboxes from exchange 2007 to exchange 2013. I have more than 1000 mailboxes.
    What is the correct way to migrate. do i need to move a single mailbox. During migration do the mailboxes get corrupted
    2. I want to move public folders from Exchange 2007 to Exchange 2013.
    I ran powershell commands and got these results please do guide me how to move to exchange 2013.and what are the shell commands
    Get-publicfolder
    Name Parent Path
    IPM_SUBTREE
    Get-publicfolder | select AdminDisplayName,FolderPath
    AdminDisplayName FolderPath
    Get-PublicFolderStatistics | select AdminDisplayName,FolderPath
    AdminDisplayName FolderPath
    exchangeV1 schema-root\microsoft\exchangeV1
    Internet Newsgroups Internet Newsgroups
    Get-PublicFolder -Recurse | fl name,replicas > c:\publicfolder.txt
    Name : IPM_SUBTREE
    Replicas : {}
    Name : Internet Newsgroups
    Replicas : {MAIL\Public Folder Storage\Public Folder Database}

    I have started moving mailboxes , i have tried moving few individual mailboxes to see how things go
    MAIL is my exchange 2007 and MAIL1 is my exchange 2013, please do refer the below result
    PS] C:\Windows\system32>Get-MailboxDatabase -server mail
    Name                           Server          Recovery       
    ReplicationType
    Mailbox Database               MAIL            False           None
    [PS] C:\Windows\system32>Get-MailboxDatabase -server mail1
    Name                           Server          Recovery       
    ReplicationType
    Mailbox Database 1460777952    MAIL1           False           None
    [PS] C:\Windows\system32>New-MoveRequest -Identity '[email protected]' -TargetDatabase "Mailbox Database 1460777952"
    DisplayName               StatusDetail              TotalMailboxSize         
    TotalArchiveSize         PercentComplete
    [email protected]          Queued                    363.6 MB (381,217,115 ...                         
    0

  • Mailbox Move from Exchange 2007 to Exchange 2013

    I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
    moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
    Thanks

    When you do a mailbox move it stays connected during the initial sync.  Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
    to access their mailboxes.
    You can control this behavior by setting the SuspendWhenReadyToComplete
    switch either by command line when creating the move request via the EMS
    https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
    Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
    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

  • Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

    I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
    two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
    Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
    Data migrated:                        
    Migration rate:                        
    Error:                        
    MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
    context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server
    FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824        
    Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288  
    StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]   
    Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
    Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624   
    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856   
    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
    prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
    15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115   
    Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970  
    StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
    All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
    The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
    The Source Server is Running Exchange 2007.
    I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
    I would appreciate any help you can give me!
    Thanks,
    Jon

    Any update if you have resolved the issue.
    Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

  • Issue moving remote user from exchange 2007 to 2013

    have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
    during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.  
    outlook was working connecting to both servers, and OWA was working on both servers.
    couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
    but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
    if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
    when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
    could this have caused my outlook connectivity issue?
    I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    any suggestions?

    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    Hi,
    Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
    According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
    Please try to logon OWA to check whether this user works.
    If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
    Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
    Please try to run Outlook under safe mode to avoid AVs and add-ins.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

    Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
    Tried several mailboxes. Same result.
    Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
    Ex 2013 is SP1 aka CU4.
    How to proceed???
    john11

    After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
    btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
    What did work:
    1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
    of the four mailboxes. The other 3 failed.
    2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
    3. Then on the Exchange 2013 box, use this Exchange shell command:
    New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
    This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
    Get-MoveRequest
    The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
    Thanks for the suggestions. I had to get this done and the MS Tech made that happen. 
    john11

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Maybe you are looking for