Problem: Mixed Exchange 2007 / 2013 CAS Servers with wildcard certificates in Europe and non-wildcard Certficate in China

Hi,
we have following problem. We have a mixed multi-domain one-forest AD environment. We also have still a mixed exchange 2007 / 2013 environment. We also have different CAS Servers for 2007 SP3 (RU15) and 2013 (CU8) in europe and one 2007 SP3 (RU15) CAS Server
in China, because of bad connection to Europe. For the Migration to 2013 in Europe we installed a wildcard-certificate *.xyz.com and used the Set-OutlookProvider EXPR -CertPrincipalName msstd:*.xyz.com, so the wildcard certificate is accepted. Everything in
Europe works fine, inside and outside also between exchange 2007 and 2013 (both CAS Server 2013 and 2007 use the same wildcard certificate). But since the change of the Set-OutlookProvider EXPR we are facing problems with our CAS Server in China, because this
server has a different non-wildcard certificate and a different domain name (cas-server.xyz-china.com instead xyz.com). Now we have the problem that this Chinese CAS server the Outlook Anywhere does not work anymore and prompts always for the username. As
I see it is because of the EXPR change. Is it possible to set the the Outlook-Provider EXPR per Cas-Server ? (They also have their own Autodiscover on this front-end server). Because I see that the Outlook-Provider can only be stored forest-wide.
If not the other solution would be to register the chinese cas server in our xyz.com domain and use the same wildcard certificate on this system right ?
Any help would be appreciate….

Yes setting the EXPR value is most likely the cause of your issue.  When you set this value you are telling Outlook to only accept connections from connections that have the cert with the subject name you specify here.
Unfortunately, based on my experience I believe this is an organization wide setting and cannot be configured on a CAS by CAS basis (If I'm wrong someone please keep me honest :)).  
So the only option would you have is to change all the URLs to be on *.xyz.com domain.  There's no need to change the domain the server actually resides on.  The other option would be to purchase a UCC Cert with all the names you need and apply
to all your CAS servers and reset the EXPR value. 
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

  • Can Exchange 2007 to be integrated with SharePoint 2013

    Can Exchange 2007 to be integrated with SharePoint 2013?

    In the sense of using Incoming and Outgoing email, absolutely. But not for other things, like Site Mailboxes, which require Exchange 2013.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Exchange 2007 - 2013 switch mailflow

    Hello,
    Currently we are in a coexistence scenario.
    We have installed:
    EXchange 2007 => 2 CAS/HUB servers, 2 MBX servers and 1 EDGE server
    Exchange 2013 => 2 MBX servers, 2 CAS servers (load balanced with NLB)
    There is an EDGE subscribtion, so all the incoming and outgoing mails are going through the EDGE server.
    Now all the mailboxes are migrated we need to cchange the mailflow.
    How do I handle this?
    - redirect mail traffic in the firewall (managed externally by another company)
    - Disable the connectors created by the EDGE subscription or remove them?
    - Create a new Send connector where the mails are going directly to the internet?
    Does somebody have experience with this and can give me some tips? I am not sure about the step with the EDGE subscription...
    Thanks!

    Hi Yannick,
    Base on my knowledge, you can remove the old edge subscription and recreate a new edge subscription for exchange 2013.
    I recommend you refer to the following articles:
    Use an Exchange 2010 or 2007 Edge Transport server in Exchange 2013
    The procedures to deploy a new Exchange 2007 or Exchange 2010 Edge Transport server in your Exchange 2013 organization are basically the same as in previous versions of Exchange. However, any procedures that are performed on the Hub Transport server are
    performed on the Mailbox server in Exchange 2013.
    Configure Internet Mail Flow Through a Subscribed Edge Transport Server
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

    Hi people,
    What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
    Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
    Thanks

    Hey AlbertWT,
    Can you clarify exactly what you mean when you say "server patching?"  Do you mean patching at the ESXi host level or something within the guest?
    As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer.  Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role.  NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
    If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
    Matt
    http://www.thelowercasew.com

  • I can't upgrade my Mac to OS Mavericks. I still don't know the problem why. I have my mac with OS 10.8.5 and also a 2012 model . Please help me :((

    I can't upgrade my Mac to OS Mavericks. I still don't know the problem why. I have my mac with OS 10.8.5 and also a 2012 model >.< Please help me :((

    Oh that really works ;D Thanks

  • Need help on Cross Forest Exchange 2007 - 2013 with Linked Mailboxes

    Hey all,
    So I'm in a bit of a pickle with my Exchange design and am trying to figure out if there's a way to migrate mailboxes across forests where Linked mailboxes are being used. I've done a bit of reading and have noted stuff like preparing the move request in
    AD, etc. But I'm wondering if someone can break it down for me.
    http://1drv.ms/1lWjLqG
    The above is a OneNote diagram of how we have moved over time. Please forgive my sloppy handwriting but I hope it gets the point across. I will text it out here as well:
    Original Design
    The original design of the domains when I joined the company were fabrikam and contoso. Contoso is a domain that sits entirely in the "DMZ". Fabrikam was the internal AD forest where most services and users authenticated to. In Contoso, there
    are 2 domain controllers, the "Front End" Exchange Server (Edge Transport), and the "Back End" server, which is CAS/Mailbox.
    There is a forest trust between contoso and fabrikam where "Linked Mailboxes" are created in Contoso, and then the LinkedMasterAccount is set to Fabrikam.
    Migration/Hybrid Design
    Due to the fact that these two domains were configured massively inappropriately, riddled with security holes as well as strange permissions configurations, the decision was made to create a new internal AD domain. In my OneNote, I've labeled this 'specialbank.com'.
    A long while ago we migrated users from Fabrikam to SpecialBank via trusts. To facilitate access to Exchange, a new trust was created between Contoso and SpecialBank to allow us to update the LinkedMasterAccount parameter to the new Specialbank domain.
    We have most of our users authenticating to their mailboxes via SpecialBank, while the mailboxes still reside in Contoso.
    Migration from Exchange 2007 to Exchange 2013
    I am attempting to now figure out the best way to migrate the mailboxes from Contoso to a new set of Mailbox servers in SpecialBank. This will also be an upgrade from Exchange 2007 (Current) to an Exchange 2013 installation.
    The latest Service Packs and CUs are installed in both.
    What would be the best procedure to move these mailboxes? To my knowledge, the current best practice/recommended way is to perform a user/SID migration from Contoso to SpecialBank. But I already have accounts in
    SpecialBank that users are actively using.
    I'm not opposed to doing a simple PST export from Contoso to SpecialBank, but we're looking at around 120 mailboxes. So I'm trying to make my life a little easier instead of spending a weekend here.
    If I try to do it in batches, I need to figure out how to handle autodiscover and CAS. Since I'm creating an entirely new Exchange environment, I'm trying to limit what I place in the existing configuration. But I'm not opposed to setting up something temporarily
    if I need to in order to make the migration transparent to users.
    Can anyone help?

    Hi ,
    From you description i came to know contoso is the resource forest and special bank is the account forest .
    You just wanted to migrate the linked mailboxes from resource forest to account forest and also you would want the migrated mailboxes to get merged to the respective user accounts in the account forest to become as a normal user mailbox.Am i right ?
    Please correct me if i am wrong . I have found some blogs in internet please have a look in to that especially the first one.
    http://www.outlookforums.com/threads/60210-cross-forest-mailbox-move-and-linked-mailbox/
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27974905.html
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange 2013 SP 1 + Lync 2013 CAS servers 100% CPU Load.

    Hello. Can somebody explain about one issue?
    We have Exchange 2013 CU6 + Lync 2013 (5.0.8308.556) integration.  After install Exchange SP1 all Client Access Servers begun to consume all CPU time.  In process
    explorer there are w3wp.exe (MSExchangeServicesAppPool) and lsass.exe (netlogon context). In IIS logs a lot of events about
    GET /EWS/Exchange.asmx/s/GetUserPhoto email=[email protected]&size=HR648x648&CorrelationID=<empty>;&cafeReqId=07966a0b-99a4-4f0a-8a38-a8a83264e46c; 443 - 10.10.10.10 OC/15.0.4659.1001+(Microsoft+Lync) - 401 1 2148074254 46
    GET /EWS/Exchange.asmx/s/GetUserPhoto email=[email protected]&size=HR648x648&CorrelationID=<empty>;&cafeReqId=c7fb9499-1dc7-48d9-add6-64156a910de6; 443 Contoso\username 10.10.10.10 OC/15.0.4659.1001+(Microsoft+Lync) - 200 0 0 437
    IIS logs are grow up very quickly, about 1GB per day. Before to installing SP1 was not problems.  Thanks in advance.

    Hi,
    From your description, you said that you have Exchange 2013 CU6 + Lync 2013 (5.0.8308.556) integration, then you install Exchange 2013 SP1 on all CAS servers.
    Do you mean your Exchange 2013 Mailbox server is CU6, and all CAS servers are SP1?
    We had better have the same version on Exchange servers in our environment, if that is the case, please upgrate all to CU6, Exchange 2013 latest version, to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 CAS servers cannot accept connections on Exchange ports

    Exchange 2013 Enterprise SP1 / Windows Server 2008 R2 SP1
    I have configured site resilience setup with the following at two sites:
    - two CAS servers
    - six MB servers
    Traffic to the CAS servers pass through HLB.
    I just discovered that the "01" CAS server at each site is not accepting Exchange traffic.
    If I telnet to one of the Exchange ports, it looks like there is a connection, however the moment any character is entered, the connection dies.
    For example
    - telnet Site01CAS01 25
    -   ( screen goes blank and DOES NOT display the expected "220 servername Microsoft ESMTP ...." message )
    - when I attempt to enter  "ehlo" the moment I enter "e" the session is disconnected.
    I can successfully perform a telnet connection to the CAS02 server and run through the complete send a test message through telnet process. The session disconnect occurs on the CAS01 server at each site for ANY port controlled by Exchange: 25, 143, 587,
    717, 993
    I can successfully telnet to ports NOT controlled by Exchange: 80, 81, 8080, 443
    There appears to be nothing essentially wrong with IIS
    The firewall is DISABLED.
    I discovered this issue yesterday.
    I upgraded to Excahgne 2013 SP1 10 days ago.
    I cannot say for sure if this condition existed before the SP! upgrade. I upgraded from CU1 to SP1
    Any thoughts?
    Thanks! Tom

    Well, port 25 doesnt have anything to do with IIS regardless.
    Since this is the CAS, port 25 is handled by the Microsoft Exchange Frontend Transport service .
    A couple of things I would check.
    Check the server component state. Get-ServerComponentState -Identity <server> to ensure everything is "active".
    I assume all the services are running and you have rebooted the server to ensure things start up clean.
    Also ensure the NIC on this server is set to register itself in DNS.
    Finally, If you have disabled the firewall service on the server, its not supported. You should enable the firewall service and then disable it logically netsh advfirewall set Allprofiles state off
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

    We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server. 
    Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one? 
    Old Server:
    SBS2008 running Exchange 2007
    New Server:
    Server 2012
    Exchange 2013
    Any help is appreciated!

    Hi Dave,
    It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
    you in the past).
    For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model.  In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
    up to 2 Virtual Machines on same host).
    There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration. 
    You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration.  But the high points are in here. If it looks
    like something you would be comfortable with then you should research more.
    http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
    Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
    http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
    If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
    and migrate your workstations out of old domain into new domain.  Whether this is more or less work at your workstation count is dependent upon a lot of variables.
    If you have more questions about the process, update the thread and we'll try to assist.
    Hopefully this info answered your original question.
    Cheers,
    -Jason
    Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

  • Exchange 2007 SP3 RU compatibility with Exchange 2013 lattest CU

    Hi Team,
    I have question, I want to migrate my exchange 2007 to 2013.
    right now exchange 2013 already provide CU7. 
    My question is, is exchange 2013 CU7 compatible with Exchange 2007 SP3 lattest RU (SP3 RU15) ?
    is there any limitation of version if i want to upgrade Exchange 2007 to 2013
    Thanks Before

    Hello,
    The first thing I would say, is that the MINIMUM supported update for Exchange 2007 is SP3 RU 10, so you should be ok with RU15 installed with Exchange 2013 Cu7.
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    The second thing I would say, and I am not sure how you're current environment is configured and how you plan on configuring your future environment, but if you are using Public Folders, Exchange 2013 CU7 changes the way public folders are handled during
    coexistence.  I would recommend taking a look at this blog post from The Exchange Team
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx 
    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

  • ActiveSync 500 error and Exchange 2007/2013 coexistence

    Hello,
    We have Exchange 2007, and we've deployed Exchange 2013 and coexistence appears to be working.  We have done a small pilot migration of 11 users, and I have 2 of those users that are not able to get iPhone/ActiveSync working.  OWA and Outlook access
    work without a problem.  https://testconnectivity.microsoft.com/ is telling me "The test of the FolderSync command failed." and "Exchange
    ActiveSync returned an HTTP 500 response (Internal Server Error)"
    The error I'm receiving on the mailbox server event log is:
    An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case,
    Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. 
    URL=
    --- Exception start ---
    Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
    Exception message: A null value was received for the NTSD security descriptor of container CN=ExchangeActiveSyncDevices,CN=LASTNAME\, FIRSTNAME.,OU=XXX,OU=People,DC=DOMAIN,DC=local. 
    Most articles I've found with this issue say to confirm that "Inherit parent permissions" is check on the AD object, but that is already checked?
    The funny thing is that most of our pilot users don't have this issue.  It is only for some of them.
    Any help is appreciated.

    An update here, I was able to get the 2 pilot user's iPhone/ActiveSync access working by adding the following permissions by hand:
    Add Exchange Servers, in Apply onto select
    msExchActiveSyncDevices objects (note it's plural) and selecting
    Full Control.  
    Once I did this, my problems went away.
    So the big question is why aren't these permissions in place already?  Isn't this something that the adprep/domain prep should have taken care of?
    Thanks!

  • HTTP 500 error when opening a legacy shared mailbox in OWA 2013 (Exchange 2007/2013 coexistence environment)

    Hi,
    Our Exchange 2013/2007 coexistence environment is set up and all is working apart from this:
    Mailbox A has full permissions to Mailbox B. Mailbox A is migrated to Exchange 2013, but Mailbox B remains on Exchange 2007. If I login to Outlook Web App 2013 as Mailbox A and then "Open another mailbox..." and select Mailbox B, a new window opens
    up saying "HTTP 500 Internal Server Error". The URL it is trying is :
    https://webmail.ourdomain.com/owa/[email protected]/?offline=disabled
    ( I can open Mailbox A in Outlook 2010 and do "Open Other users's folder.." and Mailbox B opens up just fine. )
    Our legacy CAS server's External and Internal URLs are set to :
    https://legacy.ourdomain.com/owa
    and the Exchange 2013 CAS server's External and Internal URLs are set to :
    https://webmail.ourdomain.com/owa
    We have FBA enabled on both the E2K7 and E2K13 OWA
    In the IIS logs:
    2015-03-02 16:36:50 <E2K13_IP> POST /owa/service.svc action=SubscribeToNotification&UA=0&ID=-25&AC=1&CorrelationID=c2899211-568d-4da4-a163-351a8621c9fd_142531419466924;&cafeReqId=7ffae082-a96f-42fd-85f8-bf23775ed5de; 443 ourdomain.com\MailboxA
    <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
    https://webmail.ourdomain.com/owa/#path=/mail 200 0 0 109
    2015-03-02 16:36:50 <E2K13_IP> GET /owa/ offline=disabled&CorrelationID=<empty>;&cafeReqId=7c8e137f-cdb7-4449-9cb8-f36f94539244; 443 ourdomain.com\MailboxA <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
    - 500 0 0 265
    In the OWA HTTP Proxy logs:
    2015-03-02T16:36:50.096Z,7c8e137f-cdb7-4449-9cb8-f36f94539244,15,0,913,7,,Owa,webmail.ourdomain.com,/owa/,,FBA,True,ourdomain.com\MailboxA,ourdomain.com,[email protected],Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2;
    .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0),<LoadBalancer_IP>,<Exchange2013ServerName>,500,,ServerNotFound,GET,,,,,ExplicitLogon-SMTP-Header,,,,0,,,,40,9,,0,7;,7,,0,7,,0,46.8643,0,,,,,,,,,1,10,0,,10,,50,50,?offline=disabled,,BeginRequest=2015-03-02T16:36:50.049Z;CorrelationID=<empty>;ProxyState-Run=None;ServerLocatorRefresh=beebf732-0f99-47a0-9f36-d266573f1510;RefreshingCacheEntry=CacheEntry(BackEndServer
    <Exchange2007ServerName>.ourdomain.com~1912832083|ResourceForest |LastRefreshTime 2015-03-02T16:01:29.3265514Z|IsSourceCachedData False);ProxyState-Complete=CalculateBackEnd;EndRequest=2015-03-02T16:36:50.096Z;I32:ADS.C[<DC_Name>]=1;F:ADS.AL[<DC_Name>]=6.6401;I32:ATE.C[<DC_Name>.ourdomain.com]=1;F:ATE.AL[<DC_Name>.ourdomain.com]=0,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
    The server <Exchange2013ServerName>.ourdomain.com was not found in the topology. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: The server <Exchange2013ServerName>.ourdomain.com was not found in the topology.   
    at Microsoft.Exchange.Data.Storage.ServiceTopology.GetSite(String serverFullyQualifiedDomainName)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetServiceTopologyWithSites(String serverFqdn  ServiceTopology
    topology)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer
    mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox  BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1
    operationToTrack  Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass3b.<OnCalculateTargetBackEndCompleted>b__3a()   
    --- End of inner exception stack trace ---;
    Hoping that somebody can help ?
    Thanks

    Hi Ansev,
    Thank you for your question.
    By my testing, user who was migrated to Exchange 2013 cannot access mailbox on Exchange 2007 with 500 error, although user account have “Full Access Permission” to mailbox on Exchange 2007.
    I suggest we migrate account which has “Full Access Permission” for other user  to Exchange 2013.
    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 - Lab setup with internal emails only

    Hi,
    I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
    go over the internet. 
    I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
    Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
    Regards,
    Nithin

    Hi,
    You need not to configure send/receive connectors for internal email.
    The following article for your reference:
    http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
    Default Receive connectors created during setup
    Certain Receive connectors are created by default when you install the Mailbox server role.
    Default Receive connectors created on a Mailbox server running the Transport service
    When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
    These connectors are the following:
    Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
    Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
    Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
    mentioned, their TransportRole value is HubTransport.
    To view the default Receive connectors and their parameter values, you can use the
    Get-ReceiveConnector cmdlet.
    Default Receive connectors created on a Front End Transport server
    During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
    connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
    Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
    Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
    Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
    In a typical installation, no additional Receive connectors are required.
    Niko Cheng
    TechNet Community Support

  • What is the order for upgrading exchange server 2013 SP1 servers to CU7?

    Hi All 
    I am planning to upgrade my exchange server 2013 SP1CU4 to CU7 . As per my understanding , we always proceed with the CAS servers and then the Mailbox Servers during up-gradation.
    But I am confused now , since I have seen articles stating , that the Mailbox servers has to be upgraded first and then the CAS servers in exchange 2013. 
    What will be the correct order . My environment consists of 2 Mailbox servers in DAG and 2 CAS servers (Exchange server 2013 SP1)
    Thanks in Advance .
    Joyso Senior Messaging Admin

    Hi Joyso,
    The Microsoft recommendation regarding the order in which the Exchange 2013 server roles should be installed or Upgraded is Mailbox and then CAS.
    It makes sense as the CAS Role is a stateless server and all major components are held by the Mailbox Role.
    Until a 2013 mailbox server comes online, the CAS server is pretty much useless. Hence, the recommended installation order in 2013 is the reverse of 2010 – Mailbox role first & then CAS
    Note: If your DAG have more nodes, you need first upgrade all non-PAM nodes and then upgrade PAM node.
    Some References:
    The recommendation from the Product Group is to install Exchange 2013 Preview Mailbox Role first, and then the
    CAS role.
    If you're separating your server roles, we recommend installing the Mailbox server role first.
    Upgrade your Exchange 2013 server roles in the required order. First, upgrade Mailbox servers
    and then upgrade Client Access servers. -Upgrade DAG Mailbox servers
    Exchange 2013 Server Roles Installation Order – Mailbox First:
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Mail Delivery betweek Exchange Server 2013 co-existance with Exchange server 2010

    Hello Guys
    I have a mailflow issue, hoping someone can help with detail description, below is the setup
    Exchange server 2010 SP3 with all roles in one server
    Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010
    to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole
    server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the
    queue ..
    Can someone please provide detailed solution what needs to be configured?
    MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

    Hi,
    1.please check the mailbox send and receive quota for exchange 2013 migrated mailbox.
    2.Please check the email attributes of the exchange 2013 migrated mailbox because it seems to be a problem with that particular mailbox.
    3.Then do the message tracking and that would be the only way to find the where the send messages has gone.
    4.Please check and confirm you have an enough space on the disk where exchange queue database is residing.
    I think I need to create a receive connector in the 2013 to receive from 2010 ?
    No need ,by design  exchange 2013 cas server default frontend receive connector will be having an
    entire ipv4 and ipv6 segment and anonymous connection is checked by default.
    I think I also need to create a send and receive connector for 2013 users to each other?
    No need , an intra organisation send connector and the default receive connectors in exchange will be used
    for internal mail flow between the exchange 2013 users.
    Please reply me if you have any queries .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

Maybe you are looking for