Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

Hello guys,
I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
What should I check and configure to make it work?

Hi,
I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact  EMC supplier to improve it.
By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
If there are any questions regarding this issue, please be free to let me know. 
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Similar Messages

  • HELP - Exchange Server 2007 Transport Rule Issue

    Hi all,
    sorry if here is not the place to put my question but I did not find another forum, so if anyone can help me I appreciate.
    - I have an Exchange Server 2007 SP3 environment with 1 MBX Server and 3 CAS/HUB Servers.
    - I have created a Transport Rule that said:
    "all emails that have @test.com in BCC field are dropped off except one group can send" .
    The issue is the rule doesn´t work.
    Anyone can help me, please?
    Thanks in advance.
    Luiz

    The Exchange previous versions forums are here: 
    http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 mailbox rule and mail forwarding

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

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

  • Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

    Hi Team,
    Need urgent help in resolution of following error:
    Environment Details: VMware ESXi 5.5 (vMotion)
    Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
    Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
    OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
    Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
    Prerequisites: Installed
    Error: Installation gives Error at Step 10 during installation of Mailbox Service
    Error Details Below:
    Error:
    The following error was generated when "$error.Clear();
    if ([Environment]::OSVersion.Version.Major -ge 6)
    $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
    $reg= join-path (join-path $env:SystemRoot system32) reg.exe;
    $servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
    if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
    if ((get-service wsbexchange).Status -eq "Running")
    Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
    Exchange /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
    Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
    " was run: "Process execution failed with exit code 1.".

    Resolved ! :)
    Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
    As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
    Thanks to all.

  • Outlook no resolving Exchange Server name , resolving another name like SID Object

    Hello All ,
    I Have Exchange 2013 installed on windows server 2012 , Outlook no resolving Exchange Server name , resolving another name like SID Object . Please see the attached file below .
    how can fix the issue ?
    Thank you

    Hi,
    Please run following command to verify whether the Outlook resolved the correct Exchange Server GUID:
    Get-Mailbox MailboxName | FL name, ExchangeGUID
    Following Screenshot is the test result in my lab, for your reference:
    If we get the correct GUID, it means we have already connected to Exchange Server successfully.
    The GUID format for the server name in Exchange 2013 is an expected behavior.
    Found a similar thread for your reference:
    Outlook is not resolving CAS server Name
    http://social.technet.microsoft.com/Forums/exchange/en-US/5868d45a-ee93-4c55-927b-4dd2b9eaeec5/outlook-is-not-resolving-cas-server-name?forum=exchange2010
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange Server 2013: incoming messages are not delivered into user mailboxes occasionally

    Exchange Server 2013 CU1, two mailbox servers (DAG, only one mail database), two CAS servers (NLB cluster). Two Sendmail/CentOS-based SMTP relays route mail between Exchange servers and Internet (incoming mail is routed to NLB cluster name).
    Usually mail flow is OK: messages are sent and received normally. However, I've got several complains from different users. They state that occasionally they don't receive messages that were sent to them from outside. Tomorrow morning I've decided to
    investigate the issue.
    So, we have a message sent from Gmail account that was not delivered in user mailbox. It was received and routed to Exchange by Sendmail host:
    Jun 27 22:06:37 MX01 sendmail[12169]: r5RG6HC8012166: to=<USER_ADDRESS>, delay=00:00:19, xdelay=00:00:19, mailer=smtp, pri=124702, relay=NLB-FQDN [NLB-IP], dsn=2.0.0, stat=Sent (<CAHgK_sjEkj41htuVsutMP3XhgR5RRDs8-EgSC-UfHoaiHWFj=A@mail.gmail.com>
    [InternalId=13069585481819] Queued mail for delivery) 
    Running Get-MessageTrackingLog applet on the mailbox servers displayed the followed log entries for the message:
    DB Server #1:
        22:11:18 HAREDIRECT
        22:11:18 RECEIVE
        22:11:18 AGENTINFO
    DB Server #2:
        22:11:18 HARECEIVE
        22:12:44 HADISCARD
    So, we can see that the message was placed into shadow queues, but was NOT delivered into mailbox (no DELIVER status entries). Also pay attention to the timing. Time on all the servers is in sync, but Sendmail timestamp is 22:06, and Exchange timestamps
    are 5 minutes behind it.
    Today a message sent to the same address from the same Google mailbox was received by Exchange and placed into user mailbox with no glitches.
    We use Exchange antispam system activated on Exchange mailbox servers. Spam is never dropped silently. It is either returned to sender (SCL 9) or placed into quarantine mailbox (SCL 6 and above). I'm pretty sure that the lost message was not in the quarantine
    mailbox this morning, and the sender didn't receive any NDRs.
    Any ideas what to investigate next?

    Hi,
    Do you mean the emails are placed in the Shadow Redundancy queue?
    Shadow Redundancy
    http://technet.microsoft.com/en-us/library/dd351027(v=exchg.150).aspx
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • How to get list of Users[MailBoxes] in Exchange Server 2013 by using EWS Managed API

    Hi all,
    I need list of Users exists in my Exchange server 2013 , i.e Mail Box Users login name.
    I was  created Full Access permissions of all users to Admin user account,  to access each user Mailbox programatically 
    i need the list of Mailboxes in exchange server .
    MailBox  mailbox = new MailBox("user");
    Please share your ideas

    Hi,
    We can run the following command in Exchange Management Shell to get all user mailboxes name and export it to a .csv file:
    Get-Mailbox -ResultSize Unlimited | Select Name,Alias,RecipientTypeDetails | Export-Csv c:\Users.csv
    If you want to retrieve the list of users by using EWS Managed API, I suggest you can ask a question in Exchange Development forum for more suggestion:
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads
    Regards,
    Winnie Liang
    TechNet Community Support

  • Error During Exchange 2013 Mailbox Transport Role Install On Server 2012

    I was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past
    the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:
    Step 8 of 15: Mailbox role: Transport service
    Error:
    The following error was generated when "$error.Clear();
              $maxWait = New-TimeSpan -Minutes 8
              $timeout = Get-Date;
              $timeout = $timeout.Add($maxWait);
              $currTime = Get-Date;
              $successfullySetConfigDC = $false;
              while($currTime -le $timeout)
                $setSharedCDCErrors = @();
                try
                  Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
                  $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
                  if($successfullySetConfigDC)
                    break;
                  Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
                catch
                  Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
                Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
                Start-Sleep -Seconds 30;
                $currTime = Get-Date;
              if( -not $successfullySetConfigDC)
                Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "Unable to set shared config DC.".
    The only option on the screen was exit, so I did.  I checked the start menu, and there were two new Exchange icons, but I did not click them.  I ran the installer again, and it detected an incomplete install, the only option was to click next to
    finish the install, so I clicked next.  This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service."  I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013
    came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh.  Any suggestions?

    I've tried three times since my last post, following
    http://msexchange2010.info/archives/2330 as closely as possible the most recent time.  I am consistently getting the same error that appears to imply I don't have write access to the domain.  I don't understand this, because I am using the
    same domain admin account I have been using all along.  Nonetheless, here is the powershell output starting with the first Exchange setup.exe step (all other steps were already performed, all available updates were installed, and the server was rebooted
    prior to this):
    Windows PowerShell
    Copyright (C) 2012 Microsoft Corporation. All rights reserved.
    PS (domain admin home)> D:
    PS D:\> .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis COMPLETED
    Configuring Microsoft Exchange Server
    Extending Active Directory schema COMPLETED
    The Exchange Server setup operation completed successfully.
    PS D:\> .\Setup.exe /PrepareAD /OrganizationName:PRD-INC /IAcceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis COMPLETED
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
    een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
    aspx
    Configuring Microsoft Exchange Server
    Organization Preparation COMPLETED
    The Exchange Server setup operation completed successfully.
    PS D:\> .\Setup.exe /Mode:Install /Roles:ClientAccess, Mailbox, ManagementTools /t E:\Exchange /IAcceptExchangeServe
    rLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Languages
    Management tools
    Mailbox role: Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Client Access role: Front End Transport service
    Client Access role: Client Access Front End service
    Performing Microsoft Exchange Server Prerequisite Check
    Configuring Prerequisites COMPLETED
    Prerequisite Analysis COMPLETED
    Configuring Microsoft Exchange Server
    Preparing Setup COMPLETED
    Stopping Services COMPLETED
    Copying Exchange Files COMPLETED
    Language Files COMPLETED
    Restoring Services COMPLETED
    Language Configuration COMPLETED
    Exchange Management Tools COMPLETED
    Mailbox role: Transport service COMPLETED
    Mailbox role: Client Access service COMPLETED
    Mailbox role: Unified Messaging service COMPLETED
    Mailbox role: Mailbox service FAILED
    The following error was generated when "$error.Clear();
    if ($RoleIsDatacenter -ne $true)
    if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
    $sysMbx = $null;
    $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
    $dispName = "Microsoft Exchange";
    Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
    $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
    if ($mbxs.Length -eq 0)
    Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
    $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
    if ($dbs.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
    $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
    if ($arbUsers.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
    $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
    ].Identity;
    else
    if ($mbxs[0].DisplayName -ne $dispName )
    Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
    Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
    $sysMbx = $mbxs[0];
    # Set the Organization Capabilities needed for this mailbox
    if ($sysMbx -ne $null)
    # We need 1 GB for uploading large OAB files to the organization mailbox
    Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
    set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
    :$true -MailRouting:$true -MaxSendSize 1GB -Force;
    else
    Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
    else
    Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
    " was run: "Database is mandatory on UserMailbox.".
    The following error was generated when "$error.Clear();
    if ($RoleIsDatacenter -ne $true)
    if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
    $sysMbx = $null;
    $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
    $dispName = "Microsoft Exchange";
    Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
    $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
    if ($mbxs.Length -eq 0)
    Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
    $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
    if ($dbs.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
    $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
    if ($arbUsers.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
    $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
    ].Identity;
    else
    if ($mbxs[0].DisplayName -ne $dispName )
    Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
    Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
    $sysMbx = $mbxs[0];
    # Set the Organization Capabilities needed for this mailbox
    if ($sysMbx -ne $null)
    # We need 1 GB for uploading large OAB files to the organization mailbox
    Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
    set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
    :$true -MailRouting:$true -MaxSendSize 1GB -Force;
    else
    Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
    else
    Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
    " was run: "Database is mandatory on UserMailbox. Property Name: Database".
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS D:\>
    I am cleaning out in ADSI and rebuilding the server for now, because the server is behaving oddly (not as oddly as it was with 6GiB, but oddly, nonetheless).  I probably won't try to install Exchange again before tomorrow.  What should I do to prevent
    encountering the above again and/or if I encounter it again?

  • Recover mailbox from Exchange server 2010 information store to exchange server 2013

    I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
    I would like to recover a couple of mailboxes to an exchange server 2013.
    Can anyone give me a detailed walk through of how I can accomplish this?
    Thank in advance

    Well if your AD is messed up that leaves you in a jam for sure because;
    1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
    2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
    3. Here is a good article on how to accomplish
    http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
    4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
    That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB.   We make a product that can do this (DigiScope), however if you don't
    have any budget to handle its a non-issue.
    The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
    BTW if you AD is messed up, where are you putting this new 2013 server?
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Mailbox Recovery From Disaster Exchange Server 2013

    I have to exchange server EX01 and EX02. Now EX01 have to down didn't run anyway. Default database on EX01 that have to Administrator mailbox and the default database was not member of dag. now i can't move administrator database another database location.
    Md. Ramin Hossain

    Hi Ramin,
    Thank you for your question.
    By our understanding,  Ex01 didn’t run any way, we could take a disaster recovery by the following steps:
    Reset the computer account for the down server;
    Install the operating system and name on the new server with the same name as the lost server. Recovery won't succeed if the server on which recovery is being performed doesn't have the same name as the lost server;
    Join the server to the same domain as the lost server;
    Install the necessary prerequisites and operating system components;
    Log on to the server being recovered and open a command prompt;
    Navigate to the Exchange 2013 installation files, and run the following command:
    Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
      7. After Setup has completed, but before the recovered server is put into production, reconfigure any custom settings that were previously present on the server, and then restart the server.
    The following link is about Exchange 2013 prerequisites:
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
    We could learn more about Exchange 2013 disaster recovery by the following link:
    http://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx
    Then, we could recovery database from a backup or copy of a database by the following steps:
    Create the recovery database;
    This example creates the recovery database RDB2 on the Mailbox server MBX1 using a custom path for the database file and log folder:
    New-MailboxDatabase -Recovery -Name RDB2 -Server MBX1 -EdbFilePath "C:\Recovery\RDB2\RDB2.EDB" -LogFolderPath "C:\Recovery\RDB2"
       2. Copy a recovered database and its log files, or restore a database and it log files, to the location we will use for our recovery database.
       3. Use Eseutil to bring that database into a clean shutdown state.
    In the following example, EXX is the log generation prefix for the database (for example, E00, E01, E02, and so on).
    Eseutil /R E01 /l E:\Databases\RDB1 /d E:\Databases\RDB1
      4. Create a recovery database. Give the recovery database a unique name, but use the name and path of the database file for the EdbFilePath parameter, and the location of the recovered log files for the LogFolderPath parameter.
    The following example illustrates creating a recovery database that will be used to recover DB1.edb and its log files, which are located at E:\Databases\RDB1.
         New-MailboxDatabase -Recovery -Name <RDBName> -Server <ServerName> -EdbFilePath "  E:\Databases\RDB1\DB1.EDB" -LogFolderPath "E:\Databases\RDB1"
      5. Restart the Microsoft Exchange Information Store service:
    Restart-Service MSExchangeIS
      6. Mount the recovery database:
        Mount-database <RDBName>
    We could refer to the following link:
    http://technet.microsoft.com/en-us/library/dd876954(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know.
    Best Regard,
    Jim

  • Accessing Exchange 2013 Mailboxes from Terminal Server hosted on Server 2003 Std - Cert Issues

    We are in the midst of deploying an Exchange 2013 SP1 CU5 environment and have run into some issues.  Currently there is a good coexistence between a single Exchange 2007 server and the 5 2013 servers.  Mail is flowing through 2013 and then being
    relayed to 2007 when necessary.  
    We have a number of Server 2003 Terminal Servers.  On two separate machines, both running the lastest rollups of Outlook 2010, any user with a 2013 mailbox receives a password prompt after launching Outlook.  It is trying to connect to one of the
    two CAS, fills in the user's account, and will not accept any password.  In addition, a window pops up behind stating "There is a problem with the proxy server's security certificate.  the name on the security certificate is invalid or does
    not match the name of the target site mail.pvschemicals.com.  Outlook is unable to connect to the proxy server.  (error code 0)."  2007 mailboxes are not affected.
    We have checked pretty much everything that we can think of.  Virtual Directories are good, certificate is good, etc.  The strange thing is that only happens on 2003 TS machines, so I have to think that it's related.  Our 2008 TS' are just
    find.
    We have applied the 2003 SHA2 certificate hotfix. 

    Hi,
    According to your description, the configurations of Outlook Anywhere are proper. And based on my research, the issue can be related to the version of the terminal server 2003. Thus, please check if your terminal 2003 server is 2003 R2 SP2 or later.
    For more information, you can refer to the following thread:
    http://social.technet.microsoft.com/Forums/exchange/en-US/295bf2bc-584b-4de2-85fb-94096fac52e7/outlook-connectivity-problem-on-2003-term-server-exchange-2013?forum=exchangesvrclients
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Blocking Spam Emails by subject name in Exchange Server 2013

    Hello Guys,
    I need to know how to block spams by subject from Exchange Server 2013's Anti-spam/message filter.
    In general, I'm using Exchange's anti-spam agents and configured spam blocking by domain name.. but I need to filter unnecessary emails by subject name also.
    So, if you know how to resolve this issue, please post here the real solution..
    Thanks a lot,

    Hi GMG,
    Thank you for your question.
    We could install Exchange 2013 edge server, then we could create item which block spam base on subject name in “Protection”, we could refer to the following link:
    https://technet.microsoft.com/en-us/library/bb124701%28v=exchg.150%29.aspx
    There is a another method, we could use transport rule to filter spam by subject name by the following link:
    https://technet.microsoft.com/en-us/library/dd351127(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Exchange Server 2013 Mailbox - High CPU Usage

    Hi,
    We are having an issue with our Exchange 2013 Mailbox Server.
    The process Microsoft.Exchange.Store.Worker consumes most of the CPU utilization.
    Have anyone encountered this issue? How were you able to resolve it?
    Thanks

    Hi,
    According to your description, your database is not active. And to understand more about the issue, I’d like to confirm if there is some user experience slow connection or other performance issue.
     However, since in Exchange 2013 single Store Worker Process is only responsible for one database, we can firstly confirm if the specific mailbox database causes the high CPU:
    http://msexchangeteam.in/how-to-identify-which-microsoft-exchange-store-worker-process-is-owned-by-mailbox-database-in-exchange-server-2013/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Multiple owa sites on a single server 2012 with exchange 2013 (mailbox, cas)

    hi,
    I'm trying to
    set up an exchange server 2013 on windows 2012 with all roles installed for 2 owa virtual directory, one for integrated windows authentication and the other for forms-based authentication.
    I followed a tutorial for exchange 2010.
    http://technicaljeditrials.info/2011/02/28/exchange-2010-multiple-owaecp-directories-part-1/
    Step 1: IP Address
    Obtain a second IP address and add it to the NIC of your server.
    Step 2: DNS
    Add a DNS entry for That secondary IP address for the name we will want to use in the new FBA OWA Web site.
    I have chosen "testwebmail."
    Be sure there is a valid SSL certificate (recommended to have UC or SAN
    SSL certs) on the server Which has the new name "testwebmail" that will be used in the certificate.
    Step 3: New Web Site
    Create a new web site in IIS on the Client Access Server and bind it to the new IP address used in step 1.
    Step 4: Adding Exchange Virtual Directories
    The web site has been created and bound to the secondary IP address of our server.
    Also the DNS record That will be used to access the OWA FBA new page was added to DNS.
    The next step is to go into EMS and begin adding our virtual directories for OWA and ECP.
    Login to the Exchange server and open the Exchange Management Shell.
    Then run Get-Get-OWAVirtualDirectory and ECPVirtualDirectory to see the default OWA and ECP directories.
    New-OWAVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/owa
    New-ECPVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/ecp
    Step 5: Configure the Virtual Directories
    To configure the virtual directories we will disable FBA on the Default Web Site OWA and ECP virtual directories
    Set-OWAVirtualDirectory -Identity "OWA (Default Web Site)" -WindowsAuthentication
    $true -BasicAuthentication $false  -FormsBasedAuthentication $false
    Set-ECPVirtualDirectory -Identity "ECP (Default Web Site)"
    -WindowsAuthentication $true -BasicAuthentication $false  -FormsBasedAuthentication
    $false
    Step 6: iisreset
    now if I access the default site I log in with
    windows integrated authentication, but when I try to access the second site with forms authentication tells me username or password incorrect
    Tell me you know where I'm wrong?
    thanks
    Greetings
    Daniele

    Hello,
    Something like this:
    New-OWAVirtualDirectory -WebSiteName "FBA"
    Enable the Basic authentication via running the following command:
    Set-OWAVirtualDirectory -Identity "yourservername\owa (FBA)" -BasicAuthentication $true
    Restart the IIS admin service in services.msc
    Thanks,
    Simon Wu
    TechNet Community Support

  • Best practice on mailbox database size & we need how many server for deployment exchange server 2013

    Dear all,
    We have  an server that runs Microsoft exchange server 2007 with the following specification:
    4 servers: Hub&CAS1 & Hub&CAS2 & Mailbox1 & Mailbox2 
    Operating System : Microsoft Windows Server 2003 R2 Enterprise x64
    6 mailbox databases
    1500 Mailboxes
    We need to upgrade our exchange server from 2007 to 2013 to fulfill the following requirment:
    I want to upgrade the exchange server 2007 to exchange server 2013 and implement the following details:
    1500 mailboxes
    10GB or 15GB mailbox quota for each user
    How many
    servers and databases  are
    required for this migration<ins cite="mailto:Mohammad%20Ashouri" datetime="2014-05-18T22:41"></ins>?
    Number of the servers:
    Number of the databases:
    Size of each database:
    Many thanks.

    You will also need to check server role requirement in exchange 2013. Please go through this link to calculate the server role requirement : http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
    2TB is recommended maximum database size for Exchange 2013 databases.
    Here is the complete checklist to upgrade from exchange 2007 to 2013 : http://technet.microsoft.com/en-us/library/ff805032%28v=exchg.150%29.aspx
    Meanwhile, to reduce the risks and time consumed during the completion of migration process, you can have a look at this proficient application(http://www.exchangemigrationtool.com/) that would also be
    a good approach for 1500 users. It will help you to ensure the data security during the migration between exchange 2007 and 2013.

Maybe you are looking for