Exchange 2013 certtificate and FQDN of CAS/MB servers

Good Morning,
I have read articles that say I should not need anything but the fqdn names of things like autodiscover.mycompany.com and mail.mycompany.com on the cert you install on the exchange server. I went that route and installed it on every exchange server
but for some reason, the client gets prompted for credentials with this configuration.
When I create a cert with all the CAS/MB FQDN names ( ie. casmb01.mycompany.pvt) on the cert, they do not get prompted and the exhttp allows the outlook client to connect properly.
this is a 2007 to 2013 migration. I am testing just the connectivity and have not put the 2013 as the proxy yet.
The clients also have an internal host name .pvt in the cert so I would imagine this would be a problem for outlook anywhere unless they vpn in and trust the local CA.
Can I use only the autodiscover and mail .mycompany.com
does anyone else have this set up this was?
thanks
Paul

Here's what I would do:
If you are planning on allowing people to access Outlook Anywhere and Active Sync Externally
Since you can only have 1 cert bound to IIS I would create the cert via a 3rd party CA.  They will only give you a cert for publicly accessible tlds. So on that cert you will need mail.company.com, autodiscover.company.com
and legacy.company.com.  The legacy can really be anything you want, and is needed for OWA and  ActiveSync redirection.  Once I have the cert, I would change all the virtual directories to have their respective *.company.com addresses.  In
order for this to work properly with DNS (internally you get an internal address) you will need to create a dns zone called mail.company.com and point that to your 2013 CAS servers and another one for legacy.company.com and point that to your 2007 Servers.
If you are not allowing any external access then you can just create whatever certs you want to via your internal CA.
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

Similar Messages

  • Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

    I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
    on our system".
    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
    I've followed this post as a guide but it hasn't resolved my issue.
    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
    My Exchange environment looks like this:
    Site 1:
    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13
    Site 2:
    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13
    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
    Any help is greatly appreciated. I'd love to get rid of Unity. 
    EDIT:
    I just found this event in the event logs:
    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
    but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    9.1.2 I think it is, we upgraded to avoid the known DNS bug
    I cant see how to PM you either
    The crux of it was outlined below with some tweaks
    http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
    as any other CAS based service - point to 2013, and it will handle the rest

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

  • Exchange 2013 migration and Lync server

    hi guys,
    i wanna upgrade my exchange 2010 to 2013 in our company.
    but i faced with a question
    will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
    plz help me 
    thanks guys

    Hi,
    you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
    Here is a guide for enabling IM in OWA:
    http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
    Just remember to point DNS to the New Exchange 2013 server and it should be fine.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

  • Exchange 2013 mailbox added to the CAS array

    We are upgrading to Exchange 2013 from Exchange 2010. Following the development guide, we have
    installed the first mailbox server in the Exchange 2010 environment which has 3 Exchange 2010 CAS server
    in the array. When installing the mailbox role, we did not choose the client access role but after
    the installation we can see that the Exchange 2013 Mailbox server is added to the CAS array and yet
    we did not choose the client access role. How does this happen, and to proceed ?

    I see the same thing in my lab:
    Get-ClientAccessArray | FL
    RunspaceId        : 16b992b3-270f-4ae1-a3c3-fa9e2ea73d69
    ExchangeLegacyDN  : /o=Wingtiptoys/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Ou
                        tlook.wingtiptoys.ca
    Fqdn              : Outlook.wingtiptoys.ca
    Site              : wingtiptoys.ca/Configuration/Sites/Default-First-Site-Name
    SiteName          : Default-First-Site-Name
    Members           : {EXCH-2010, EXCH-2013}
    AdminDisplayName  :
    ExchangeVersion   : 0.1 (8.0.535.0)
    Name              : Outlook.wingtiptoys.ca
    DistinguishedName : CN=Outlook.wingtiptoys.ca,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administr
                        ative Groups,CN=Wingtiptoys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wingtiptoys,DC=ca
    Identity          : Outlook.wingtiptoys.ca
    Guid              : 27968af1-1624-4ff3-85c8-e38e68183afe
    ObjectCategory    : wingtiptoys.ca/Configuration/Schema/ms-Exch-Client-Access-Array-2
    ObjectClass       : {top, server, msExchExchangeServer, msExchClientAccessArray}
    WhenChanged       : 4/12/2014 12:51:18 PM
    WhenCreated       : 4/12/2014 12:51:18 PM
    WhenChangedUTC    : 4/12/2014 7:51:18 PM
    WhenCreatedUTC    : 4/12/2014 7:51:18 PM
    OrganizationId    :
    OriginatingServer : DC-1.wingtiptoys.ca
    IsValid           : True
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 ECP and DAG issue

    Good Day,
    We have Exchange 2013 setup in Coexistence with Exchange 2007. Everything is working well except for two small issues I have noticed.
    Current Setup of 2013:
    SiteA:
    2x CAS Servers on Windows 2012 R2 configured with windows NLB (Internet Facing).
    2x MBX servers Configured in a DAG also running on Windows 2012 R2.
    SiteB:
    2x CAS Server on Windows 2012 R2.
    2x MBX servers Configured in a DAG also running on Windows 2012 R2.
    Issues I am having:
    Issue 1:
    When working on the ECP:
    I can do all tasks on servers in the same site but get some errors when trying to do tasks on servers in the other site.
    When trying to Activate a DB copy on the DAG at SiteB I get "The Microsoft Exchange Replication service does not appear to be running on Server name"
    And just trying to go to the properties of a server at SiteB "An error occurred while accessing the registry on the server servername"
    This happens vice versa.
    I can access all servers on the same site but not between sites with some tasks.
    I have made sure firewall is disabled and remote registry is indeed running but no luck.
    From a network perspective all ports are open between the sites.
    Issue 2:
    When I reboot a DAG member with the active mailbox databases for testing outlook connectivity I get two issues.
    Then I cannot access ECP at all until the server is up again.
    Outlook keeps staying on trying to connect until it is reopened.
    Any Ideas?
    I will gladly give more information if needed.
    Thank You
    Riaan Rourke
    Senior System Engineer

    Since I don't see this with Hyper-V I'll assume this is on ESX. Please let me know it that's not correct.
    In terms of virtualization best practices - whose list was that :) 
    There are multiple configuration things that you *MUST* do when using WLBS on ESX.  It will depend upon multiple things in the environment.  I'd start with this
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1556
    Fix that, and chances are the other item will be also remediated.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

    Hi,
    I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers  and one DAG with 2 mailbox Servers). My
    goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
    Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
    Here is what I have planned so far.
    1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
    2. Prepare AD for exchange 2013.
    3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
    4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
    5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
    6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
    7. Testing outlook setups on new servers. inbound and outbound email tests.
    once this is done, I can migrate over and point all my MX records to the new servers.
    Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration. 
    thank you for your help in advance

    Hi,
    okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
    and so on. It's much more simpler, better and less expensive.
    CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
    http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
    First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
    On channel 9 there is many stuff from MEC:
    http://channel9.msdn.com/search?term=exchange+2013
    Migration:
    http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
    Additional informations:
    http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
    Hope this helps :-)

  • Exchange 2013 or SP1 Installaing Single CAS Role not installaing EWS virtual directory in mixed environment

    Hi Experts,
    I am facing issue while installing exchange 2013 sp1 in mixed(2007, 2010 and 2013) environment, the issue is: CAS role not installing/configuring "Echangeweb" (ews) virtual directory if i install only CAS role. If i install CAS role and mailbox
    role then there is no issue, everything is fine.
    In single CAS role installation, "EWS" folder is creating inside "Exchangeweb" folder but it shows empty folder.
    If any one have any idea please let me know, why this is happening? was i am doing anything wrong while installing?
    Regards,
    Ravi Nalla
    Hewlett-Packard
    ravinalla

    Hi Ravi,
    Agree with Martina. I install Exchange 2013 CAS server and Mailbox server separately. "exchweb" folder exists on Mailbox server only. Here is the exchweb folder information on Mailbox server for your reference.
    Here is the ews folder information on CAS server for your reference.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • We have a Exchange 2013 server and the Mailbox Database folder is filling up with .log files.

    We are migrating from Exchange 2010 to Exchange 2013.  We have installed the Exchange 2013 but it only has a couple of mailboxes on this server, all the mailboxes are still on the Exchange 2010 server.
    I have run a Windows Backup of the Exchange 2013 but I am still seeing a ton a log files in the mailbox folder.
    Also the database file is only about 1.1 GB but the backup is now 40 GB.  
    Is there something that can be done to truncate these logs and make the backup smaller?

    Hi ,
    1.Does the full backup completed successfully ?
    2.what about the status for the below mentioned command ? Does the mailbox database headers updated with the latest time and date ?
    Get-MailboxDatabase -Status | ft name,*full* -au
    3.Just check the application event logs for the event id
     2046  and that should state that the log truncation for the mailbox databases has been initiated or not.
    4.Before initiating the backup just make the exchange writer is not on error.
    vssadmin list writers
    In case if it on error state ,please restart the Microsoft exchange replication service and check the exchange writers status again by using the above mentioned command.
    Thanks & Regards S.Nithyanandham

  • Exchange 2013 - Search SMTPReceive logs on CAS

    Is there a sensible way to search the SMTP Receive protocol logs on the client access servers?  The Get-MessageTrackingLog cmdlet only searches the mailbox servers, but I need to be able to look at what's connecting to the CAS sometimes and manipulate
    those logs.  The transport logs are entirely too verbose for some of my needs.
    I've been parsing the logs via PowerShell using some form of these piped commands I've put together, and it's certainly functional, but I can't help but feel that I'm doing things the hard way.
    Get-ChildItem -Path 'C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive\*' -Include '*.LOG' |
    Where-Object -Filter {$_.LastWriteTime -gt (Get-Date).AddDays(-1)} |
    Sort-Object -Property 'LastWriteTime' |
    Get-Content |
    Where-Object -Filter {$_ -like '*,530 5.7.1 Client was not authenticated,*'} |
    ConvertFrom-Csv -Header 'date-time','connector-id','session-id','sequence-number','local-endpoint','remote-endpoint','event','data','context' |
    ForEach-Object -Process {
    [void]($_.'local-endpoint' -match '(.*):([0-9]*)$')
    $lip = [IPAddress]$Matches[1]
    $lport = [Int]$Matches[2]
    [void]($_.'remote-endpoint' -match '(.*):([0-9]*)$')
    New-Object -TypeName PSObject -Property @{
    'date-time' = [datetime]$_.'date-time';
    'connector-id' = [string]$_.'connector-id';
    'session-id' = [string]$_.'session-id';
    'sequence-number' = [int]$_.'sequence-number';
    'local-endpoint' = [string]$_.'local-endpoint';
    'local-endpoint-ip' = $lip;
    'local-endpoint-port' = $lport;
    'remote-endpoint' = $_.[string]'remote-endpoint';
    'remote-endpoint-ip' = [IPAddress]$Matches[1];
    'remote-endpoint-port' = $rport = [Int]$Matches[2];
    'event' = [string]$_.'event';
    'data' = [string]$_.'data';
    'context' = [string]$_.'context'
    } |
    Format-Table -Property 'date-time','remote-endpoint-ip','data'

    Hi 
     There will be 4 types of message tracking logs in Exchange 2013 unlike in Exchange 2010 we have only 2.
    •MSGTRK   These logs are associated with the Transport service.
    •MSGTRKMA   These logs are associated with the approvals and rejections used by moderated transport. For more information, see Moderated Transport.
    •MSGTRKMD   These logs are associated with messages delivered to mailboxes by the Mailbox Transport Delivery service.
    •MSGTRKMS   These logs are associated with messages sent from mailboxes by the Mailbox Transport Submission service
    For protocol logs 
    We just need to navigate to the below location alone in Exchange 2013 and copy the receive connector logs which will be identical to analyze the protocol logs via excel.
    “C:\program files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\ProtocolLog\SmtpReceive”
    You can refer my blog as well 
    http://exchangequery.com/2014/02/21/analyzing-the-protocol-logs-and-message-tracking-logs-in-exchange-2013/
    Cheers !!
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Connecting to Exchange 2013 Server and Server name is weird

    Hello
    When I connect to my Exchange 2013 Lab Server with a Outlook 2010 Client something shows wrong.
    The Name of the Exchange server that I type in changes from EX01 to !"¤"&#/25278596"&¤%/¤%/.
    What can be the problem?

    Hello
    When I connect to my Exchange 2013 Lab Server with a Outlook 2010 Client something shows wrong.
    The Name of the Exchange server that I type in changes from EX01 to !"¤"&#/25278596"&¤%/¤%/.
    What can be the problem?
    Are you sure that you don't see something like this: [email protected]
    That is what you should see when connecting to Exchange 2013.
    Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of
    mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP address.
    See:
    Whats new in Exchange 2013 - Architecture section.
    Martina Miskovic

  • Exchange 2013 SP1 and SCOM 2012 R2

    Hi there, 
    Hopefully someone can assist me with this issue, if it is one... 
    I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
    76 users in total, roughly 80GB of Public Folders.
    I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected. 
    Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues. 
    Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well. 
    Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010. 
    A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect. 
    Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy. 
    Attempted to reran the probe for EWS and got the error below:
    Is there perhaps anyone that can assist me with these errors?
    Cheers

    FYI... IIS ARR is not supported for Exchange Server.
    Check in event log if you are getting anything related to the issue.
    About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
    Are those mailboxes still moving or in move request?
    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.

  • Exchange 2013 SP1 and Exchange Online Protection (EOP)

    Hello, I have just set up a new install of Exchange 2013 and connected mail flow with EOP. Mail is flowing, and I can access emails through the Outlook Web App. However, I cannot get Outlook 2013 to link up to the new configuration. I got Outlook for Mac
    to work, no problem. But, I get an error on outlook 2013 that says it must sync folders for a first time to open.
    Any help would be appreciated.
    Thanks!

    Hi 
    Use another user to test, check whether he can use Outlook to access his mailbox or not?
    If this user also cannot connect to his mailbox, I suggest you go to check whether all the Exchange services are started, make sure RPC client access service is started.
    You do need to replace the self-signed certificate.
    If you don't want to buy a certificate from a Third-Party Issuer, then install Windows CA and issue a certificate from there.
    Even if it does work with the self-signed certificate using Outlook 2007, it is not a supported configuration and you will not be able to connect with Outlook 2010/2013.
    I have seen new installation of EX13 having SSLOffloading turned on causing the problems. Turn if off if you do.
    Set-OutlookAnywhere -Identity 'SERVERNAME\rpc (Default Web Site)' -SSLOffloading $false
    Let us know the output of the above so that we can proceed further.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • How to configure AD on windows 2012 server for Exchange 2013 internal and external email flow

    Dear Experts,
    I have to configure exchange 2013 on Windows server 2012 STD. Company has registered Static IP addresses and can get the MX record pointing to any of this Static IP.  
    The registered domain name is e.g.  contoso.com. 
    a. What should I use as domain name on AD? contoso.com or contoso.local
    b. Is it recommended to have two different servers  for AD and Exchange?
    c. What should be my connector settings for mail flow?
    d. how can I set 2 email servers in company for load balancing?

    Hi,
    a, I suggest use contoso.com as domain name. It is convenient to add urls into our certificate for internal and external mail flow.
    b, Recommended that installing AD
    and Exchange Server on two separate
    Servers. If Exchange Server downed unfortunately, it can prevent AD server from crushing at the same time.
    c, Found some articles for your reference:
    Configure Mail Flow and Client Access
    http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
    Configuring Outbound Mail Flow in Exchange Server 2013
    http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/
    d, Load Balancing
    http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 journaling and JBOD

    Is anyone using JBOD on exchange journaling servers? If yes, how is that working out for you?

    Hi mombu,
    Microsoft does not support Exchange server deployed on JBOD storage architecture without DAG. JBOD have two main advantages: full space utilization and cost effective. However, if you lose a single disk in the JBOD then there is a high likelihood that you
    will lose data, as the concept of a JBOD does not include not fault tolerance.
    So it is important to point out at this stage that JBODs should not be considered if you do not plan to use DAG.
    More details about Exchange 2013 storage configuration and
    high availability, for your reference:
    http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
    http://technet.microsoft.com/en-us/library/dn789066(v=exchg.150).aspx
    Best Regards,
    Allen Wang

Maybe you are looking for