Duplicate Contacts when migrating mailboxes to exchange 2013 SP1 CU7

Hello,
We started to notice that when we move a user from our legacy exchange 2007 to exchange 2013, the contact list appears twice for users.  I heard CU6 was suppose to fix this issue but we went ahead and downloaded the latest version and we are still seeing
this.  Can anyone provide guidance on how to stop this for the remaining migrations?
Thanks

Hi Joey,
I'm back : )
According to your description, I know that the contact list appears twice for users after moving users from Exchange 2007 to Exchange 2013.
I notice that you want to install CU6 to fix this issue, based on my knowledge, CU6 can cause an known issue when you are using Exchange 2007 and 2013 coexistence and query mailbox move request via EMS. However is known issue has fixed in CU7, I suggest
install CU7 for testing.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

  • Migrate mailboxes from Exchange 2013 to Exchange 2010

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

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

  • Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

    Dear All,
    We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
    error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
    [PS] C:\Windows\system32>New-MoveRequest -Identity
    '[email protected]' -TargetDatabase "CI-DB01"
    MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
    Diagnostic context:
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
        Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 53361   StoreEc: 0x977
        Lid: 51859
        Lid: 33649   StoreEc: 0x977
        Lid: 43315
        Lid: 58225   StoreEc: 0x977
        Lid: 39912   StoreEc: 0x977
        Lid: 54129   StoreEc: 0x977
        Lid: 50519
        Lid: 59735   StoreEc: 0x977
        Lid: 59199
        Lid: 27356   StoreEc: 0x977
        Lid: 65279
        Lid: 52465   StoreEc: 0x977
        Lid: 60065
        Lid: 33777   StoreEc: 0x977
        Lid: 59805
        Lid: 52487   StoreEc: 0x977
        Lid: 19778
        Lid: 27970   StoreEc: 0x977
        Lid: 17730
        Lid: 25922   StoreEc: 0x977
        + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
        + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
       0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
    MoveRequest
      + PSComputerName        : Exch01.domain.local
    Please help as we are stuck here!!
    Thanks in advance!!

    Can yo ping server by name not by FQDN? e.g. ping server1.
    Make sure firewall/antivirus not blocking communication. Disable antivirus and try
    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.

  • ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

    Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
    users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
    I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
    As you can see from the error above  ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
    virtual folders?!
    What I’m missing here?! Please help.

    Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
    To check whether inheritance is disabled on the user:
    1.Open Active Directory Users and Computers.
    2.On the menu at the top of the console, click View > Advanced Features.
    3.Locate and right-click the mailbox account in the console, and then click Properties.
    4.Click the Security tab.
    5.Click Advanced.
    6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
    Ref:
    http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
    Also check the Virtual directory authentication
    Microsoft-Server-ActiveSync
     •Basic authentication
     •SSL required
     •Requires 128-bit encryption
    Ref:
    http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
    Check the IIS log if you are able to find any error message on it
    Exchange Queries

  • Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

    I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
    I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error.  Is this even possible?  I cannot find any documentation on this scenario yet.
    VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
    version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
    VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    Hi Steve,
    I'm a little confused what you are saying. Here is my understanding:
    When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
    If I have misunderstood your concern, please let me know.
    For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
    2007.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

    Hi Everybody,
    For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
    When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
    This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
    So i did the traditional cmdlet
    Get-SendConnector
    Set-SendConnector -Indentity "connector name" -Port 551
    Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
    When i type Get-ExCommand
    Any reference to SendConnector and ReceiveConnector are not on the list.
    Am I missing somethings?  This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
    I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
    The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials.  However, i very much doubt the on-premise installation add-on to SBS would cause any issues
    to missing cmdlets.
    I searched all over the internet and found nothing.
    Now my biggest fear is to re-install Exchange and import the mailboxes manually.
    Any help is greatly appreciated.
    MattLok

    Hello
    check role asigment for your user:
    Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
    sorry my english

  • Mailbox migration between two Exchange 2013 servers is horribly slow

    Hi,
    when migrating mailbox between 2 exchange 2013 servers,it s horribly slow. I have found some articles which describing problems about content indexing and missing AD group. This is not my problem, I have tried solutions but it didn't work. Both exchange
    are next to each one, same VLAN, same switch. Just migrating between databases.
    When I start batch jobs it is migrating only 1 mailbox at once and speed is really slow (2000 - 3000 mail items per 5 minutes). So mailboxes which have 10GB it's migrating 3 hours. My server is on 1gbps LAN.
    I have also checked MsExchangeMailboxReplication.exe.config on both servers:
        MaxActiveMovesPerSourceMDB="20"
        MaxActiveMovesPerTargetMDB="20"
        MaxActiveMovesPerSourceServer="100"
        MaxActiveMovesPerTargetServer="100"
        MaxTotalRequestsPerMRS="100"
    Do you have any idea where to look why only 1 mailbox is migrating at once?
    Thanks

    Hello,
    For the reason why only 1 mailbox is migrating at once when you start batch jobs, there is no official articles or blog to explain it.
    I recommend you check if the speed is slower when you move a smaller mailbox. If the issue doesn't occur, I recommend you set
    the AllowLargeItems parameter.
    Here are some articles for your reference.
    New-MigrationBatch
    http://technet.microsoft.com/en-us/library/jj219166(v=exchg.150).aspx
    Exchange 2013 Local Mailbox Moves
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server

    Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server. The command works if you issue directly from the server exchange shell.
    I open the remote power shell to the exchange server 2013.
    Issue the following commands and getting the following error.
    $mailbox = Get-Mailbox -Identity testuser$mailbox.EmailAddresses -= "eum:50004;phone-context=telExt5digits.lync5.com"Then getting the following error:Method invocation failed because [System.Collections.ArrayList] doesn't contain a method named 'op_Subtraction'.
    At line:1 char:27
    + $mailbox.EmailAddresses -= <<<<  "eum:50004;phone-context=telExt5digits.lync5.com"
        + CategoryInfo          : InvalidOperation: (op_Subtraction:String) [], RuntimeException
        + FullyQualifiedErrorId : MethodNotFoundHelp!

    Now for an answer - your remote session doesn't have the same object you have on the server itself.  Notice it says this is an array list, not a ProxyAddressCollection.  If you need to work around this, you'll need to massage the addresses another
    way that the system will accept.  I'd try the following:
    $NewAddresses = $mailboxEmailAddresses | ? { $_ -notlike "eum:50004;phone-context=telExt5digits.lync5.com" }
    See what you get in the $NewAddresses variable when you do this.

  • Outlook 2010 clients cannot access their Online Archive mailbox in Exchange 2013??

    Hello,
    I have an issue where my Outlook 2010user cannot see/access their Archive mailbox when they are migrated from Exchange 2010 to Exchange 2013.
    Both the live and archive mailbox is in Exchange 2013, the user can launch Outlook but if they click on their Archive mailbox it is unavailable.
    Once the user is upgraded to SP2 or Outlook 2013 they have no issues accessing their archive mailbox.
    These users have the minimum required Outlook version (14.0.6126.5000),
    they are running 14.0.6129.5000.
    Is there a different requirement on the Outlook client if the user has an archive mailbox in Exchange 2013 as well?
    Thank you.

    Hi,
    Is there any update on this thread?
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If
    you have feedback for TechNet Subscriber Support, contact [email protected]
    Simon Wu
    TechNet Community Support

  • Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

    Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
    Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
    I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
    Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
    move them to the new server and mount them and relocate the mailboxes?
    Frank.

    Hi,
    According to your description, I recommend you consider using DAG to achieve your requirement.
    The following steps for your reference:
    1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
    2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
    3.After replication, you can mount all the databases on the new server.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support
    This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
    Please Unmark it!
    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.

  • Error when upgrading to exchange 2013 SP1

    * First, I install Exchange 2013 SP1 on my server, so step 14 of 18 to 100% then alert error:
    =======================
    Error:
    The following error was generated when "$error.Clear();
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
              if( $dismbx -ne $null)
              $srvname = $dismbx.ServerName;
              if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
              Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -eq $null )
              Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
              mount-database $dismbx.Database;
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -ne $null )
              $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
              $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
              if( $dmRoleGroup -ne $null )
                trap [Exception]
                  Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
                  continue;
                Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
            " was run: "Failed to mount database "Mailbox Database 0487331505". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing:
    Unable to mount database. (hr=0x80004005, ec=-543)
    Diagnostic context:
        Lid: 65256  
        Lid: 10722   StoreEc: 0xFFFFFDE1
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 45120   dwParam: 0x667F9F
        Lid: 57728   dwParam: 0x668155
        Lid: 46144   dwParam: 0x66851E
        Lid: 34880   dwParam: 0x66851E
        Lid: 34760   StoreEc: 0xFFFFFDE1
        Lid: 41344   Guid: 581e05de-0b68-45e0-af85-c1d96eb3e939
        Lid: 35200   dwParam: 0x548
        Lid: 46144   dwParam: 0x66885A
        Lid: 34880   dwParam: 0x66885A
        Lid: 56264   StoreEc: 0x1388    
        Lid: 46280   StoreEc: 0xFFFFFDE1
        Lid: 1750    ---- Remote Context End ----
        Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: Mailbox Database 0487331505, Server: ex2013.dothanhauto.com]".
    ========================
    * After I run install Exchange 2013 SP1 again, so go to step 5 of 9 then alert error.
    * Now, my Exchange 2013 not run. So bad. Please help me fix it! Thank you so much!

    * Thank you, Amit Tank, i passed step 4 of 9, but to step 5 of 9 then alert error:
    Error:
    The following error was generated when "$error.Clear();
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
              if( $dismbx -ne $null)
              $srvname = $dismbx.ServerName;
              if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
              Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -eq $null )
              Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
              mount-database $dismbx.Database;
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -ne $null )
              $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
              $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
              if( $dmRoleGroup -ne $null )
                trap [Exception]
                  Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
                  continue;
                Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
            " was run: "Failed to mount database "Mailbox Database 0487331505". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing:
    Unable to mount database. (hr=0x80004005, ec=-543)
    Diagnostic context:
        Lid: 65256  
        Lid: 10722   StoreEc: 0xFFFFFDE1
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 45120   dwParam: 0x35AF49
        Lid: 57728   dwParam: 0x35B062
        Lid: 46144   dwParam: 0x35B3EC
        Lid: 34880   dwParam: 0x35B3EC
        Lid: 34760   StoreEc: 0xFFFFFDE1
        Lid: 41344   Guid: 581e05de-0b68-45e0-af85-c1d96eb3e939
        Lid: 35200   dwParam: 0x1BA0
        Lid: 46144   dwParam: 0x35B757
        Lid: 34880   dwParam: 0x35B757
        Lid: 56264   StoreEc: 0x1388    
        Lid: 46280   StoreEc: 0xFFFFFDE1
        Lid: 1750    ---- Remote Context End ----
        Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: Mailbox Database 0487331505, Server: ex2013.dothanhauto.com]".
    * Please can you help me?! Thank you so much.

  • Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

    Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
    I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
    Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
    Error look like - cannot find exchange server.
    I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
    Someone have the same problem with migrated mailbox? How to solve it?
    Truly, Valery Tyurin

    You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
    Moreover, you can try this utility (
    http://www.exchangemigrationtool.com/ ) to accomplish this task.

  • Cannot disable a mailbox in Exchange 2013 CU6!?!?!?!

    I cannot disable a mailbox in Exchange 2013 CU6. I get the following error:
    Anyone seen this error? As you know, I just want to remove the Exchange attributes from the user object in Active Directory. Of course, deleting the user object works just fine but don't want to go that route. 

    I tried with the EMS (Powershell) and I still get an error:
    [PS] C:\>disable-mailbox [email protected]
    Confirm
    Are you sure you want to perform this action?
    Disabling mailbox "[email protected]" will remove the Exchange properties from the Active Directory user object and mark the mailbox in the database for removal. If the mailbox has an archive or remote archive, the archive will also
    be 
    marked for removal. In the case of remote archives, this action is permanent. You can't reconnect this user to the remote archive again.
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): 
    Y
    Active Directory operation failed on LocalDCName.local.com. This error is not retriable. Additional information: The parameter is incorrect.
    Active directory response: 00000057: LdapErr: DSID-0C090CB9, comment: Error in attribute conversion operation, data 0, v2580
        + CategoryInfo          : NotSpecified: (:) [Disable-Mailbox], ADOperationException
        + FullyQualifiedErrorId : [Server=LA-MBX01Server,RequestId=6ed97c1e-ae68-4670-a097-c4e65f683274,TimeStamp=11/18/2014 7:50:07 PM] [FailureCategory=Cmdlet-ADOperationException] 8D6C0FEB,Microsoft.Exchange.Management.RecipientTasks.Disable 
       Mailbox
        + PSComputerName        : LocalDCName.local.com
    I captured everything with the START-TRANSCRIPT cmdlet and changed the specific values to our organization (i.e., "[email protected]" and "LocalDCName.Local.com"). I've tried this on other mailboxes and I receive the same error whether
    I use EMC or EMS. I believe this might be AD schema related just not sure where.

  • Configure a Catch-All Mailbox in Exchange 2013

    Is it possible to create a catch-all rule which delivers mail sent to a non- existing mail address inside the organization (*@contoso.com), to a specific
    mailbox?
    Exchange 2013 Standard

    Hi All
    I have also used the Catch all agent from Codeplex, with great success.
    The only issue is, that the catch all transport agent HAS TO be installed, while your still at level CU3 or lower.
    We are now at exchange 2013 CU7, and the Catch all agent still works like a charm.
    Forget about journaling rules, these doesn´t work, in my experience

  • 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

Maybe you are looking for