Mail flow in exchange 2013 and lotus domino coexistence

scenario: Exchange 2013 CU3 running Windows 2012. coexsisting with lotus domino 8.5.1
there two cas server and two mailbox server. users migrated using quest tool. distribution groups are still lotus notes.
in one of distrbution group which containing around 5 users, 4 users are migrated to exchange 2013 cu3 one user still in lotus notes. the above mentioned distribution group members complaining they are not reciving mail which address to distribution group.
I used exchange shell for message tracking and I found below entries.
in source field the entry is mailboxrule i have verified there is no mail box rule in the user front
in eventid field the entry is receive
in the sourcehostname its show exchange 2013 server.
recipientstatus {unknown}
Since the distribution group is in lotus notes I want find event which sates that the message or exchange 2013 forwarding or checking the members of DL .
which field will give the required details currently i am finding anything.
please suggest

Thanks.
In current scenario we cant create any dl in the exchange 2013 front. I want to know what this mean
recipientstatus {unknown}.
secondly I have followed the link below
http://social.technet.microsoft.com/Forums/exchange/en-US/194c0bd8-9c77-4750-9f47-944451f2dd40/message-tracking-in-large-distribution-list-challenges-please-help?forum=exchangesvrgenerallegacy
I ran the below command:
Get-MessageTrackingLog -MessageSubject
"messageTrack" |select eventId, sender,@{l="recipeints";e={[string]($_.recipients)}}|ft
-Aut
oSize -Wrap
I am getting enventid, sender field details but recipeints field is empty.
Please suggest.

Similar Messages

  • Establish mail flow from Exchange 2007 to Exchange 2013

    I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
    Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

    Was this question answered.  We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped.   Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
    using "Custom Settings" - manually entered IPs for DNS in the Exchange  Admin Center "DNS Lookups".
    Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.  
    Any assistance will be greatly appreciated.  

  • Exchange 2013 and exchange 2000

    Hy guys...
    I have this problem...i have a dommain controller x.com and i installed Exchange 2013 on it. I have another dommain controler
    y.com with Exchange 2000. Thex.com dommain sends and receives mails from other Exchange 2013 servers but when it comes to
    y.com dommaind i am only able to send emails to
    [email protected] I cannot send emails from y.com
    (Exchange 2000) tox.com (Exchange 2013).
    Bothx.com dommain controller and y.com dommain controller are in the same network and i fave connectivity between them.
    What might be the problem?
    Than u,
    M.S

    Hi,
    Firstly, it’s not supported to install Exchange 2013 and Exchange 2000 in the same organization and it’s not recommended to install Exchange server on Domain Controller.
     http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.exchange2000or2003presentinorg(v=exchg.150).aspx
    To understand more about the mail flow issue, I’d like to confirm your meaning that two DCs are in the same network.
    If they are in the same forest, it’s by design that Exchange 2013 and Exchange 2000 cannot coexist.
    For general mail flow troubleshooting , we can use telnet to check it.
    For more information, you can refer to the following articles:
    http://technet.microsoft.com/en-us/library/bb123686(v=exchg.150).aspx
    http://msexchangeguru.com/2013/07/29/troubleshooting-mail-flow-issues/
    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

  • Introduction of New OAB Architecture in Exchange 2013 and Some General Troubleshooting methods

    Exchange 2013 is different from previous versions of Exchange server on architecture, some of the old features have been changed. In this FAQ, I will demonstrate the changes on OAB and list a common issue for your reference.
    [Agenda]
    1. Differences between Exchange 2007/2010 OAB and Exchange 2013 OAB
    a. Generation
    b. Distribution
    c. Download
    2. Common issue and troubleshooting
    3. More information
    [Difference between Exchange 2007/2010 and Exchange 2013 on OAB]
    As we know, OAB in Exchange 2007/2010 has 3 points, OAB files generated from MBX server, distributed to CAS server and downloaded to Outlook client. However in Exchange 2013, these 3 points have a little different from previous servers. For example, the OAB
    Distribution process doesn’t depend on Microsoft Exchange File Distribution service anymore. Now let me show you the changes of OAB in Exchange 2013.
    [OAB Generation]
    ====================
    Exchange 2007/2010:
    1. OAB generation server is the specific MBX server which has –server property.
    2. If MBX01 is down, OAB generation will be affected.
    3. Previous Server using Microsoft Exchange System Attendant service for OAB generation.
    4. OAB generation is a scheduled process. By default, OAB files generated at 5:00AM every day.
    5. The OAB files which generated from MBX server are located in following path:
    C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
    Exchange 2013:
    1. OAB generation server is the MBX server that hosts a special type of arbitration mailbox, called organization mailbox. Thus, the same OAB files could be generated from multiple
    MBX servers.
    2. If one of the MBX server down, other MBX server still have the ability to generate the specific OAB files.
    3. Exchange 2013 server using OABGeneratorAssistant for OAB Generation.
    4. OAB generation is a throttled process. It depend on the Server workload.
    5. The OAB files which generated from MBX server are located in following path:
    C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
    [OAB Distribution]
    ====================
    Exchange 2007/2010:
    Previous Servers use Microsoft Exchange File Distribution service to distribute OAB files from MBX server to CAS server. The distributed oab files stored in CAS server.
    Exchange 2013:
    The OAB files doesn’t distributed to CAS server. The OAB files only stored in MBX server.
    [OAB Download]
    ====================
    Exchange 2007/2010:
    If Autodiscover works fine, Outlook should use OAB URL to get the OAB files and download it.
    If Autodiscvoer doesn’t work, authenticated users can also get the OAB from the CAS server local disk.
    Exchange 2013:
    Microsoft Exchange File Distribution service has been removed from Exchange 2013 and the OAB files stored in MBX server. CAS server will proxy all OAB download requests to the appropriate MBX server.
    Outlook also use Autodiscover to get the OAB URL and download it.
    [Common issue and Troubleshooting]
    Issue: Outlook doesn’t download OAB files automatically. When I try to manually download OAB, get this error: Task xxx reported error (0x80190194): The operation failed.
    Troubleshooting:
    1. First, please run following command to check the information of OAB Generation Server.
    Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like “*OAB*”} | ft Name, Servername, Database
    Example result as below:
    2. Please make sure the authentication settings and URLs are set properly.
    3. Try to verify whether the OAB files generated from MBX server successfully. Path as below:
    C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
    4. If all of the settings above set correctly, please try to check Autodiscover. Run “Test E-mail Autoconfiguration” to check whether there is anything abnormal on OAB. If has, please search the error code on MS official documents.
    5. If this issue is related to local cache, please try to delete the OAB caches from local PC and re-download OAB for testing. Path as below:
    C:\Users\Administrator.CU1(different)\AppData\Local\Microsoft\Outlook\Offline Address Books
    [More information]
    http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
    http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi Techy,
    According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
    1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
    2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
    3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
    Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
    to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
    The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
    Regards,
    Winnie Liang
    TechNet Community Support

  • Certificate configuring for exchange 2013 and office 365 hybrid deployment

    Please advise on what digital certificate requirements for hybrid deployment and to configure it.

    Hi sphilip,
    If you want to deploy AD FS with Single Sign-On(SSO), we need use certificate to establish secure trust between on-premises Exchange 2013 and Office online.
    We can use and configure a trusted third-part CA within all on-premises Exchange 2013 Mailbox and Client Access servers to ensure secure mail transport, more details about
    Office 365 Hybrid Configuration Certificate Planning, for your reference:
    http://blogs.technet.com/b/neiljohn/archive/2011/08/25/office-365-hybrid-configuration-certificate-planning-adfs-exchange-web-services-owa-oa.aspx
    Best Regards,
    Allen Wang

  • Integrate with BEA Portal and Lotus Domino R5.0.12

    Deal all:
    I got a problem when I integrate with BEA Portal and Lotus Domino R5.0.12.
    my environment is below:
    - Domain Server :
    Lotus Domino Server R5.0.12
    BEA Personal Messaging API 4.3
    (test successful on local host)
    - Application Server:
    BEA Weblogic 8.15
    BEA Groupware portlets 2.5
    I got connection successful message when I using "Domino Service Connection"
    but I got "CZ: VERSION CONFLICT" error message when I add a new account by
    Compoze_Groupware-Edit Account user interface.
    Have anybody met the error message before... and know how to sovle the problem..
    I appreciated any suggest or comment~~~
    detail error message is below:
    portlets.compoze.groupware.exception.ConnectionException: CZ: VERSION CONFLICT at portlets.compoze.groupware.controls.provider.SessionControlImpl.createSession(SessionControlImpl.jcs:142) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:381) at $Proxy19.createSession(Unknown Source) at portlets.compoze.groupware.controls.provider.GroupwareProviderControlImpl.updateAccount(GroupwareProviderControlImpl.jcs:4825) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:249) at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:85) at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224) at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:109) at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:207) at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54) at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:168) at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:46) at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161) at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315) at $Proxy11.updateAccount(Unknown Source) at portlets.compoze.content.options.accounts.editAccount.editAccountController.saveChangesAccountAction(editAccountController.jpf:534) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1512) at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1447) at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:778) at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211) at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:608) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1504) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:674) at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527) at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1734) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1754) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:561) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:121) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:98) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:150) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:109) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:224) at com.bea.netuix.nf.ControlLifecycle$3.visit(ControlLifecycle.java:171) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:355) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:126) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:173) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:333) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:196) at com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:772) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:150) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

    Hi,
    The reason why you are seeing this exception is because there is a mismatch between the version of the WLPM API used by the portlets, with the version of the service that you have installed on you Domino server.
    To explain a little, there are two sides to the API that is used to communicate with Lotus Domino:
    1) the Java API side (used by the portlets that you have installed in the portal)
    2) the Domino Service side (installed as a DSAPI filter in the HTTP task of a Domino Server)
    Each Java API jar and Domino Service Executable are branded with a version number, which in your case does not match because the portlets came with one version of the Java API, and you have installed a non-matching version of the service on the Domino Service side (you probably extracted the executable for the service installation from the "BEA Personal Messaging API 4.3" bundle or installer).
    The solution for this is to:
    1) uninstall the Domino Service that you have plugged into the domino service
    2) extract the Domino Service installer which was included with the portlet bundle. This is located in the "Program Files\compoze\groupware_portlets_bea-2.5\8.1\service\domino" directory if you ran the portlet installer, or in the "groupware_portlets_bea81-noinstall-25\groupware_portlets_bea-2.5\8.1\service\domino" directory if you used the "no-install" zip file.
    As a tip, to quickly check whether the versions of the service and Java API’s that you are using are matching, perform the following steps:
    1) hit the domino server with the following URL and notice the "service version": http://domino_service_url:http_port/compoze.czdo. This should be something like "Service Version: 3.6.102"
    2)in your portal application (or in the portlet install bundle), open the harmony_portlets.jar file with winzip, then find the "compoze_products_information.properties" file. In this file, notice the "product.domino" version (e.g. product.domino = 3.6.102)
    3) the two versions you have inspected must match in order for the connection between the portlet and service to succeed.
    If you have verified that the "service" version and "java API" version (located in %portal_app_dir%/APP-INF/lib/harmony_portlets.jar, and you are still getting the exception, it is likely that there is a "harmony_portlets.jar" that included an old version of the Java API located somewhere in the portal server classpath. In this case, make sure that the only harmony_portlets.jar in the classpath is the one that was included with the portlet bundle that you have installed.
    Regards,
    Lev

  • Create failover cluster to host Windows 2012 DC, Exchange 2013 and SQL as VMs

    One of our clients has running Windows Essential 2012, SQL and exchange 2007 as VM on VMware for 4 years without major issue. However, the physical server is getting old and have some hardware issues recently. They have budgets to buy two Dell servers, EqualLogic
    SAN, Windows server 2012 Datacenter and Exchange 2013. Is it possible for them to create failover cluster to host Windows 2012 DC, Exchange 2013 and SQL as VMs?
    Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on
    http://www.ChicagoTech.net
    How to Setup Windows, Network, VPN & Remote Access on
    http://www.howtonetworking.com

    We will move all VMs from VMware to Hyper-V. Thank you.
    Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on <p><a href="http://www.chicagotech.net"><span style="color:#0033cc">http://www.ChicagoTech.net<br/> </span></a></p>
    How to Setup Windows, Network, VPN &amp; Remote Access on <p><a href="http://www.howtonetworking.com"><span style="color:#0033cc">http://www.howtonetworking.com<br/> </span></a></p>

  • Exchange 2013 and Exchange 2010 coexistense

    We have a and exchange 2010 organization with SP3 on most servers except for one 2010 CAS server that still requires SP1 for the purpose of legacy application compatibility. Can we introduce exchange 2013 in the org or will the setup detect
    that there is an exchange 2010 server still with SP1 and fails to continue?

    Hi,
    For Exchange 2013 coexistence with Exchange 2010, the mininum version of Exchange server is Exchange 2010 SP3 on all Exchange 2010 servers in the organization. For more information about it, please refer to the Coexistence of Exchange 2013 and earlier versions
    of Exchange server part in the article below:
    http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    Personal suggestion, please upgrade your legacy application to the latest version which is supported with Exchange 2010 SP3 or higher Exchange version.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Mail with Microsoft exchanger servers and encryption

    My campus is requiring certain e-mails to be encrypted. When I am on the Windows machines using outlook, there is a simple option to do this. But most of my time I am working on my Mac, thank goodness, and I would like to know if there is a setting somewhere that permits encryption of selected e-mails in a way compatible with the exchange server?
    So far tech support has not gotten back to me yet, and searches of this subforum with 'encrypt + exchange + server' just bring up posts about using Mail with an Exchange server, and no 'encrypt'.

    I am new as well. I am now getting mail from exchange, but it doesn't seem to want to use exchange as the outgoing mail server.
    Also is there anything else that needs to be done in order to sync with my exchange calendar and contacts?

  • Exchange 2013 and Outlook 2007

    Is there a new way to connect EX2013 to Outlook 2007 SP3?
    MSB

    Hi  Baker,
    According to the description, I notice that you want to migrate from Exchange 2010 to Exchange 2013 and want to know how to connect Exchange 2013 with Outlook Client 2007.
    Following is an article about the migration, for your reference:
    Upgrade from Exchange 2010 to Exchange 2013
    http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    Outlook client uses Autodiscover and Outlook Anywhere to connect to Exchange server, please make sure services’ URLs configured correctly.
    If you want to communicate with external users, you need to apply a certificate issued from a Public CA.
    After configuring all the points above, please run “Get-Mailbox –Identity allen | FL *GUID*” in EMS to get mailbox GUID of allen’. Input the GUID into server name filed.
    More details on “Manual configuration guide for Outlook 2010 (Exchange 2013)” for your reference:
    http://support.sherweb.com/Faqs/show/manual-configuration-guide-for-outlook-2010-exchange-2013
    Disclaimer:
    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.
    Best Regards,
    Allen Wang

  • Mail flow problem between Exchange 2013 and 2010

    Hi,
    we have 4 exchange 2010 servers, 2 mailbox and 2 hubcas. we are migration to 4 exchange 2013 servers, 2 mailbox and 2 hubcas.
    exchange 2013 user can send and receive emails  from/to internet without problems, but when i try to send email to internal users located to 2010 server i have no success.
    i also can receive from exchange 2010, so the problem is only i cannot sent emails to exchange 2010 users.
    is this a problem with receive connector of exchange 2010 or something else ???

    one more thing, when i open exchange queue i got this error:
    451 5.7.3 cannot achieve exchange server authentication. attempted failover to another host but that did not succeed. either there are no alternate hosts, or delivery fail
    For this error refer to the following article:
    http://support.microsoft.com/kb/979175
    Thanks, MikeV MCSE 2012

  • External companies with Barracuda firewalls not able to deliver mail to our Exchange 2013 environment reliably.

    We upgraded to Exchange 2013 about a year ago. Since that time we've been having issues with certain companies having their mail delayed or rejected when sending to us. No problems us sending to them though.  Eventually through troubleshooting I have
    determined that all of these different companies have one thing in common: a barracuda firewall.
    In the year since the installation I have updated Exchange all the way to SP1 but we still have this issue. The messages usually arrive to us, but quite often a day later, etc.  Here is the message from one from the 26th that was rejected:
    #< #4.0.0 X-Spam-&-Virus-Firewall; conversation with
    mail.domain.ca[64.46.58.226] timed out while sending MAIL FROM> #SMTP#
    Original message headers:
    X-ASG-Debug-ID: 1406427098-0499ef4412c2d00001-3TTufb
    Received: from DEVPMTLEXC2.devp.org ([192.168.1.202]) by
    barracuda.devp.org
     with ESMTP id EiJxT4ex1jxAnxdL; Sat, 26 Jul 2014 22:11:38 -0400 (EDT)
    X-Barracuda-Envelope-From: [email protected]
    X-ASG-Whitelist: Client
    Received: from DEVPMTLEXC2.devp.org ([192.168.1.202]) by
    DEVPMTLEXC2.devp.org
     ([192.168.1.202]) with mapi id 14.03.0195.001; Sat, 26 Jul 2014 22:11:37
     -0400
    From: "Farid, Sara" <[email protected]>
    To: >
    Subject:
    X-ASG-Orig-Subj:
    Thread-Index: AQHPqUAYJnlCbEpneUasDGYYczT9uw==
    Date: Sun, 27 Jul 2014 02:11:37 +0000
    Message-ID: <[email protected]>
    References: <[email protected]>,<[email protected]>,<[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator:
    Content-Type: multipart/mixed;
                boundary="_015_7FA4F0153A8D4D739357AED074A05ECFdevporg_"
    MIME-Version: 1.0
    X-Barracuda-Connect: UNKNOWN[192.168.1.202]
    X-Barracuda-Start-Time: 1406427098
    X-Barracuda-URL: http://172.16.1.200:8000/cgi-mod/mark.cgi
    X-Virus-Scanned: by bsmtpd at devp.org
    X-Barracuda-BRTS-Status: 1
    Our Environment:
    2x Exchange 2013 Std. SP1 Servers, All roles, DAG. We only use the built-in Exchange tools for anti-spam, traffic flows to and from exchange directly through NAT.

    Hi, yesterday we had a very large outbound queue on our Barracuda's.
    I did some investigation and found that all remote servers are Exchange servers. After some telnet smtp tests they all had the same problem. After sending the RCPT TO: command it takes between the 60 and 120 seconds to get the Recipient OK response. While
    other servers answer in a second.
    Before I contacted Barracuda I found your article.
    I contacted Barracuda about this and they said it's a problem of the remote exchange servers which won't respond within the accepted time and not a Barracuda issue. The barracuda disconnects after 60 seconds and the official RFC describes that
    the whole process should only take a few seconds.
    They said that I could be that the remote server is doeing a spam or RBL lookup which cannot be done and causes too much delay. And because of this timeout the SMTP process takes much too time and the barracuda will disconnect before the
    exchange server responds OK.
    The outgoing timeout in the barracuda can't be changed manually and it should be fixed at the recipients side but the Barracuda support did make a change deep level in the config so our time out has been set to 120 seconds now and works for us but this only
    works until we apply new firmware.
    I suggest that you do some Telnet tests with your exchange if you could find if and why the RCPT TO: hangs for such a long time to respond. Please let me know if you'll find something so I can inform the remote companies which affects this.
    Regards
    Gert

  • Exchange 2013 and 2010 co-existance

    We will have 2013 and 2010 exist together for a while...we plan to move away from using Unified Access Gateway for HTTP redirection to our Exchange services and implement Kemp
    load balancers...two at our HQ site and two at our DR stie...
    We plan to have a one arm configuration...from what I gathered...each load balancer will have a network connection and only one network connection and be on the same network as
    our new Exchange 2013 servers.  Can someone take a look at my config and give some input whether or not this will work and some suggestion on Ex13 urls, cert SAN names, etc.
    HQKemp 2400 A    
    HQKemp 2400 B               
    DCKemp 2400 A        DCKemp 2400 B
    172.16.1.104        
    172.16.1.105                     
    172.25.1.104          
    172.25.1.10
    Virtual IP   172.16.1.106          
                             Virtual IP 
    172.25.1.104
    From the video I’ve watched for Kemp install…we’ll create the following internal DNS records for the Exchange services that will be configured on balancers.
    OWA/ECP   
        mail.corp.local.com
                  172.16.1.107
    EWS               ews.corp.local.com          
    172.16.1.108
    OAB               oab.corp.local.com           
    172.16.1.109
    ActiveSync      mobile.corp.local.co         
    172.16.1.110
    OA                 oa.corp.local.com            
    172.16.1.111
    Autodiscover   autodiscover.corp.local.com 172.16.1.112
    Question: 
    We will configure the Exchange services with these ip addresses linked to each service on all four load balancers? 
    Or will DR site load balancers have different IPs configured for same Exchange services?
    Exchange services are split between our two sites…meaning Outlook Anywhere is configured for our CAS servers at our DR site and ActiveSync comes to HQ CAS servers as an example…so
    I want all Exchange services to come through the newly installed load balancers at HQ and if they don’t respond…the Exchange services get redirected to the load balancers at our DR site. 
    Can you give some insight on the config of load balancers as to how we can do that?
    I have a question about the cert we will have. 
    Our Microsoft rep says we should get a new wildcard cert…currently we have a UCC cert with the following SANs attached.
    Will this new cert have to be installed on load balancers? 
    If so…can you suggest some ideas as to what new SANs I need if any of the new cert with Exchange 2010 and 2013 co-existing for a while. 
    Below are the SANs on our current UCC cert.
    Outside resolvable SANs
    Webmail.corp.local.com          
    205.223.19.25           portal.corp.local.com     205.223.27.78
    Portal2.corp.local.com             
    205.223.19.25         
    Autodiscover.corp.local.com     
    205.223.19.25
    Internal SANs  
    Hqcas1.corp.local.com              
    Hqcas2.corp.local.com              
    Dccas1.corp.local.com              
    Dccas2.corp.local.com              
    Owamail.corp.local.com     
    (this CAS Array server name that HQ CAS servers create)
    What do you suggest we use for the external urls on Exchange 2013 for these services?
    Our firewall guy says we’ll use same names, 
    but I’m not sure if we try to use same name if we’ll get an error? 
    Active Directory may say name already in use?
    We plan to have firewall to just redirect requests for external urls to load balancers…sound correct? 
    Meaning load balancer won’t have an external NIC defined…which makes it a one arm config…correct?

    Hi Techy,
    According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
    1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
    2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
    3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
    Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
    to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
    The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
    Regards,
    Winnie Liang
    TechNet Community Support

  • Autodiscover exchange 2013 and 2007

    hello,
    i am in the process of setting up autodiscover properly for a coexistence environment of exchange 2007 and 2013.
    currently, exchange 2007 has the active CAS server role. let's call it server1.contoso.com. Exchange 2013 is installed with the CAS and Mailbox role. let's call that server server2.contoso.com
    Assuming all certificates have been installed, i assume that server2.contoso.com has to point to the autodiscover of server1.contoso.com until i have fully moved all mailboxes over to 2013 CAS, correct?
    the powershell command i used to set autodiscover on server2 is as follows,
    Set-ClientAccessServer -AutodiscoverServiceInternalUri  https://server2.contoso.com/Autodiscover/Autodiscover.xml
    it then asks for identity and i enter "server2.contoso.com".
    Currently, when i type "get-clientaccess server | fl server,*uri I get the follow results,
    AutoDiscoverServiceInternalUri : https://server1.contoso.com/autodiscover/autodiscover.xml
    AutoDiscoverServiceInternalUri : https://server2.contoso.com/autodiscover/autodiscover.xml
    Should they both be "AutoDiscoverServiceInternalUri : https://server1.contoso.com/autodiscover/autodiscover.xml" since server1 is the active CAS server?
    Again, once everything has been migrate i will then change the CAS server to server2.contoso.com
    Thanks!!

    Apologies if I have confused everyone here.
    we need 2 urls for Owa and EWS in 2007 and 2013. My this blog should help
    http://msexchangeguru.com/2013/12/31/e20132007-urlsauth/
    Undying: Answers are in line.
    1. What I understand from the post marked as Answer is there is no need for legacy namespace for Exchange2007/Exchange2013 co-existence, meaning after the installation of Exchange 2013 in the environment there is no need to modify the virtual dirs on exchange
    2007 side. Both 2013 and 2007 will be using the mail.domain.com namespace for all the services and once the virtual directories have been configured on the Exchange 2013 CAS it will redirect the request to Exchange2007 CAS for the Exchange2007 mailboxes. And
    since there's no need for legacy namespace, it should also mean that there would be no need for any additional publishing rule in the reverse proxy (ISA/TMG), just modifying the current one (mail.domain.com) to point to the Exchange 2013 CAS should do the
    trick. Am I correct?
    Just to summarize, all the redirection from Exchange 2013 to Exchange 2007 will be done without the need of legacy namespace and without modifying any URls on the Exchange 2007 side.
    PN Answer:
    You need 2 urls for OWA and EWS.
    legacy.domain.com and mail.domain.com
    Also need
    autodiscover.domain.com
    Basically you need to change these urls on 2007 side to legacy.domain.com
    This means you need to get this url added into the cert.
    On TMG side direct all the traffic to 2013 and it will redirect to 2007.
    you would need a new public host record for the legacy url.
    2. If all that is indeed correct then why the Technet article still make it sound like that the legacy host name is mandatory?  http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx 
     (Step 7)
    PN Answer: Yes we need legacy url
    Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

  • Exchange 2013 and 2007 - Coexistence and ActiveSync

    Good morning all,
    We're currently in the process of migrating our Exchange server from 2007 to 2013, and am experiencing a few problems. At the moment, OWA redirection works fine, but ActiveSync does not. At the moment the 2013 Server isn't public facing, it's internal until
    all testing is complete. However despite being on the LAN, when an iPhone is configured to target the 2013 server, it isn't proxying to the 2007 CAS, but instead provides a vague error of being Unable to Verify account information. No mail is retrieved.
    Has there been a step I've missed to allow this to work seamlessly? 

    Generally, both the internal and external Exchange 2007 ActiveSync URL should be pointing to the legacy namespace - legacy.yourdomain.com. If you've set correctly the internal name resolution (resolving the legacy namespace to the internal Exchange 2007
    IP address), ActiveSync should be working fine.
    Have you tried Android phones as well?
    Alternatively, you can set the Exchange 2007 ActiveSync External and Internal URL to $NULL, forcing Exchange 2013 CAS to proxy all requests to the Exchange 2007 CAS. This way devices are not affected by a redirect.

Maybe you are looking for