Exchange 2013 prevent spam from my own domain

Dear All,
Back in Exchange 2007 we used to prevent spam from own domain by modifying permissions on the Receive Connector, as show on this link.
http://exchangepedia.com/2008/09/how-to-prevent-annoying-spam-from-your-own-domain.html
When I modify the same permissions on Exchange 2013 Default Front Receive Connector, the spam is still allowed threw.
Is there a different aproche to achieve the same result in Exchange 2013?
Thank you
Bujar

Hi Bujar,
Have you tried to modify the permissions on Exchange 2013 default Hub transport Receive connector?
As we know, for Exchange 2013, there have been major architectural changes to the Exchange server roles. Instead of the five server roles that were present in Exchange 2010 and Exchange 2007, in Exchange 2013, the number of server roles has been reduced
to three: the Client Access server and the Mailbox server, and with Service Pack 1, the Edge Transport server role.
The Exchange 2013 Mailbox server includes all many of the server components found in Exchange 2010: client access protocols, transport services, mailbox databases, and Unified Messaging services (the Client Access server redirects SIP traffic generated from
incoming calls to the Mailbox server). The Client Access server is a thin and stateless server that doesn’t do any data rendering. There’s never anything queued or stored on the Client Access server.
So, I recommend you try to modify the permissions on default hub transport receive connector, it may achieve your requirement .
Best regards,
Niko Cheng
TechNet Community Support

Similar Messages

  • Email forwarding from my own domain to my verizon email account is taking a long time...

    Email forwarding from my own domain to my verizon email account is taking a long time.
    I have email addresses registered at moniker.com.  When I send an email to an email address that is forwarding to my verizon email, it takes a long time to arrive.

    Hmmm ... none of the header is showing this hitting the Verizon edge anywhere along the line.   At some point the header has to show the mail transiting vztpa.verizon.com or vzsac.verizon.com which are intake servers for messages headed for Verizon.   What I'm see in the header so far is that it took about 4-6 seconds (depending on what clocks you believe) to make from one end of the connection to the other.
    You got this out of your Verizon mailbox?

  • Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

    Hi all,
    I could really do with your help!
    We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site.  Site C has links to both sites A & B, but the link is a lot slower.
    We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites.  Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
    however we can have both roles on the same server if required.
    What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
    From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
    I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
    Has anyone else come across this situation and how did you get round it?
    Thanks in advance :)

    Hi Johnson,
    Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
    Please check whether the CAS server that in site C is healthy.
    If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
    Also found a useful blog for your reference:
    Exchange 2013 Client Access Server Role
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • DLP to prevent emails from a speciifc domain from being forwarded.

    Hello,
    Can Exchange 2013 DLP be used to prevent an email from a specific domain from being forwarded?
    Shawn

    Looking through the options for DLP and transport rules I don't see a way to perform that function. 
    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

  • Outlook can't connect with Exchange 2013 after migration from Exchange 2007

    <style type="text/css">P { margin-bottom: 0.21cm; }</style>
    Hello,
    recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
    But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
    To try to resolve it we've done:
    - Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
    - Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
    records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
    - In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
    Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
    - Check Outlook Anywhere block: we've cheked.
    Currently server state:
    - Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
    unless the mailbox. After a restart it can't start.
    -The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
    I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
    Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
    We continue to try to resolve the problem.
    Thanks to all in advance!
    Testing RPC / HTTP connectivity.
    Error in testing RPC / HTTP.
    additional Details
    Elapsed time: 24295 ms.
    Test steps
    Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
    Error in automatic detection test .
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Attempting each method of contacting the Autodiscover service .
    Failed to properly contact the Autodiscover service using all methods.
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 1509 ms.
    Test steps
    Attempting to resolve the host name in DNS empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 80.36.252.194
    Elapsed time: 507 ms.
    Testing TCP port 443 on the host to ensure empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 464 ms.
    Testing the SSL certificate to make sure it is valid.
    The SSL certificate is not exceeded one or more certificate validation checks .
    additional Details
    Elapsed time: 537 ms.
    Test steps
    Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
    Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
    additional Details
    Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
    Elapsed time: 454 ms.
    Validating the certificate name .
    The certificate name was validated successfully .
    additional Details
    Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
    Elapsed time: 1 ms.
    Is validating the trusted certificate .
    Validation Error trusted certificate.
    Test steps
    Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = ​​mail.empresa.com .
    Could not build a certificate chain for the certificate.
    Tell me more about this issue and how to resolve
    additional Details
    The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
    Elapsed time: 31 ms.
    Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 21723 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 498 ms.
    Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
    The specified port is blocked , not listening or does not generate the expected response .
    Tell me more about this issue and how to resolve
    additional Details
    Network Error communicating with the remote host.
    Elapsed time: 21224 ms.
    Attempting to contact the Autodiscover service with the HTTP redirect method .
    Error when trying to contact the Autodiscover HTTP redirect method .
    additional Details
    Elapsed time: 606 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 14 ms .
    Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 202 ms.
    Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
    Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
    additional Details
    Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
    lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
    Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
    Elapsed time: 388 ms.
    Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
    Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
    additional Details
    Elapsed time: 186 ms.
    Test steps
    Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
    Not the Autodiscover SRV record in DNS found .
    Tell me more about this issue and how to resolve
    additional Details
    Elapsed time: 186 ms.
    Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
    Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
    Tell me more about this issue and how to resolve
    additional Details
    No Autodiscover CNAME record for your domain ' empresa.com ' .
    Elapsed time: 268 ms.
    jspt

    Hello,
    We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
    below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
    Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
    $AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
    RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
    Name                                 : EXCHANGE13
    Fqdn                                 : EXCHANGE13.domain.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : EXCHANGE13
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
    Identity                             : EXCHANGE13
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
    ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 09/03/2014 12:46:07
    WhenCreated                          : 08/03/2014 19:15:54
    WhenChangedUTC                       : 09/03/2014 11:46:07
    WhenCreatedUTC                       : 08/03/2014 18:15:54
    OrganizationId                       :
    OriginatingServer                    : severdc.domain.local
    ObjectState                          : Unchanged
    I hope this stuff can help you.
    Thanks!!
    jspt

  • Exchange 2013 / 2010 coexistence with different public domains

    Currently in my organization
    1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
    1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
    1x Exchange 2010 Standard w/SP3 - Mailbox
    In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
    miles away. We have no IT staff in any of our field locations.
    We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
    domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
    domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
    domain.local - Our internal Active Directory domain.
    We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
    severely underutilized.
    Goals for the Exchange migration
    My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
    final topology is:
    2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
    2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
    1x VM with Exchange 2013 Standard w/SP1 - Client Access
    1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
    I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
    We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
    until Exchange 2013 SP3 is released.
    Deployment Plan
    Install Exchange 2013 on new VMs.
    Create CAS Array object.
    Configure Exchange 2013 to publish under the new namespace.
    Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
    Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
    Unknowns
    My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
    since we'll be using the new domain for each mailbox we move.
    My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

    Hi,
    From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013. 
    About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
    About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
    About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
    Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
    Checklist: Upgrade from Exchange 2010
    Install Exchange 2013 in an Existing Exchange 2010 Organization
    Upgrade from Exchange 2010 to Exchange 2013
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 DNS for internal and external domain

    Hi All,
    I have been assigned a task to implement Microsoft Exchange Server 2013. I need some help in setting up DNS namespaces and design a strategy to have same internal and external names. Let me share some details here.
    We have an Active Directory domain myinternaldomain.net, and we have a public domain
    mypublicdomain.com and we have setup email policy to have
    mypublicdomain.com as the SMTP domain for all the users. We have created another DNS zone in Active directory integrated DNS and created a records for
    mail.mypublicdomain.com and autodiscover.mypublicdomain.com which will point to CAS NLB IP. We have 2 CAS servers and 2 MBX servers, we have configured DAG for MBX High availability and planning to implement WNLB for CAS as
    hardware LB is out of scope due to budget constrains.
    We want to have same URLs for OWA, Autodiscover, ECP and other services from internal network as well as from public network. Users should not be bothered to remember two URLs, using one from internal and other from public networks. I also want to confirm
    that with this setup in place do i need to have myinternaldomain.net and server names in SAN certificate?
    Thanks

    Hi Sccmnb,
    You can easily achieve this using split DNS.
    Internal DNS hostname "mail.mypublicdomain.com" will be pointing to your internal CAS NLB IP and the external public DNS hostname"mail.mypublicdomain.com" will be pointing to the Network device or
    Reverse proxy server IP.
    Depending upon users access location(internal\external) the IPs would vary and they should be able to access the website with same name.
    The names that you would require on the certificate(Use EAC or powershell to raise the request) for client connectivity would be
    SN= mail.mypublicdomain.com
    SAN= autodiscover.mypublicdomain.com
    You don't need to have the active directory domain name present in the certificate.
    Additional  to this you need to update the AutodiscoverURI for all servers and OWA,ECP,Autodiscover Virtual Directories InternalURL and ExternalURL fields with appropiate public names.
    Some additional Info:
    *Internal vs. External Namespaces
    Since the release of Exchange 2007, the recommendation is to deploy a split-brain DNS infrastructure for the Internet-based client namespaces. A split-brain DNS infrastructure enables different IP addresses to be returned for a given namespace
    based on where the client resides – if the client is within the internal network, the IP address of the internal load balancer is returned; if the client is external, the IP address of the external gateway/firewall is returned.
    This approach simplifies the end-user experience – users only have to know a single namespace (e.g., mail.contoso.com) to access their data, regardless of where they are connecting. A split-brain DNS infrastructure, also simplifies the configuration of Client
    Access server virtual directories, as the InternalURL and ExternalURL values within the environment can be the same value.
    *Managing Certificates in Exchange Server 2013 (Part 2)
    *Nice step by step article
    Designing a simple namespace for Exchange 2013
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Prevent SPAM from Leaving the network. (ISP)

    Hi,
    I am working for an ISP, and we are having a few issues, im not sure how to fix.
    My Scenario:
    We are an ISP with 4 uplink providers and BGP sessions to 3 of them. We get full tables from 2 of them and partial tables from 1 of them.
    Our business is the rental of servers, and we have about 500 servers at the present moment.
    Every single server is on its own vlan with something like a /27.
    When i get a customer asking for more than a /27, or when they ask the many different c-class subnets, i KNOW they way to use the server as a mail server.
    I have created an ACL that looks like the following:
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++
    EDGE01.PRIVATELAYER.CH#show access-lists SPAM
    Extended IP access list SPAM
        9 permit icmp any any (787857 matches)
        10 deny tcp any any eq pop3 (8106 matches)
        11 deny tcp any any eq pop2 (38 matches)
        12 deny tcp any any eq 27 (65 matches)
        13 deny udp any any eq 27 (2369 matches)
        14 deny tcp any any eq 58 (243 matches)
        15 deny udp any any eq 58 (2365 matches)
        16 deny tcp any any eq 61 (13 matches)
        17 deny udp any any eq 61 (2352 matches)
        18 deny tcp any any eq 24 (7 matches)
        19 deny udp any any eq 24 (2306 matches)
        20 deny tcp any any eq 143 (1266 matches)
        21 deny tcp any any eq 174 (3 matches)
        22 deny udp any any eq 174 (2347 matches)
        23 deny tcp any any eq 209 (468 matches)
        24 deny udp any any eq 209 (2326 matches)
        25 deny tcp any any eq 220 (3 matches)
        26 deny udp any any eq 220 (2328 matches)
        27 deny tcp any any eq 3206 (42285 matches)
        28 deny udp any any eq 3206 (2463 matches)
        29 deny tcp any any eq 3332 (42816 matches)
        30 deny tcp any any eq smtp (238570513 matches)
        31 deny udp any any eq 3332 (2354 matches)
        32 deny tcp any any eq 1723 (43657 matches)
        33 deny udp any any eq 1723 (2345 matches)
        40 deny tcp any any eq 585 (18 matches)
        50 deny tcp any any eq 993 (820 matches)
        60 deny tcp any any eq 995 (1233 matches)
        70 deny tcp any any eq 8080 (2025630 matches)
        100 permit ip any any (7969222 matches)
    EDGE01.PRIVATELAYER.CH#
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++
    To my knowledge, this ACL should be catching ALL email ports, and dropping those packets.
    I then get an email from Spamhaus, telling me that this server is sending email (SPAM)
    When i asked them, they said that the customer might be using GRE tunnels to the server or asymmetric routing.
    Im not familiar with asymmetric routing, but after doing some research, i think that GRE tunnels are normally configured ion port 1723, which is blocked as well.
    Can anyone point me to the best way to prevent email from leaving an Interface Vlan (SVI)
    I am working on a 65095 Series Switch.
    If i should add something to the EDGE ACL, or something else, please advise.
    Best Regards,
    Ezequiel Pineda

    Hi,
    We have had this issue with very few people.
    It looks like they are part of the Rosko Spam operation, which is a big deal, and being spammers with a LOT of spamming experience, they somehow have found a way to avoid ACL's.
    At the moment yes, this is the only server that was causing the issue, but i have killed the account already, and shut the vlan.
    I did however, create another ACL with the following statement, to try seeing exactly what was going on but couldnt see much to be honest
    # 1 permit tcp any any log-input
    # 2 permit udp any any log-input
    I tried this with the log and log-input options, but i dont see Session information, Only TCP-IP source and destination traffic.
    Can you elaborate more on that span session you mentioned?
    Thanks again,
    Ezequiel Pineda

  • Exchange 2013 mailbox migration from third party cloud to on premises

    Hi,
    we are currently utilizing a third party exchange 2013 cloud service to host user's mailboxes (  intermedia), now we implemented an exchange 2013 on-premises environment in Hyper V infrastructure and want to plan migration of mailboxes and related configuration.
    cloud and on-premises environment have same SMTP domain ( Eg: XYZ.ORG) and currently an additional Temporary SMTP domain ( XYZ.CO ) used to test the external mailflow of on-premises since xyz.org is registered with cloud.
    we need to migrate all mailboxes to on premises and enable XYZ.ORG for on-premises.
    Pls suggest the prerequisites,steps, best practices for migration
    Thanks in advance.

    Hi Sumesh,
    1. Please make sure your mails are flowing correctly using XYZ.CO domain. Hope you have XYZ.ORG also created in Exchange.
    2. Hope you already created the users in your Exchange2013 server and distribution groups for current users 
    3. You plan a weekend for changing your MX records. 
    4. Change MX and A records to a lower TTL days before the migration to decrease DNS update time on migration day
    5. Export Hosted Exchange data for each user to PST files  using the PST capture tool and move your PSTs to a centralized location.
    6. Change MX and A records to point to on-premises Exchange 2013
    7. Import Hosted Exchange data from PST files into the new Exchange profiles
    Please check these as well
    http://community.office365.com/en-us/b/office_365_community_blog/archive/2011/08/15/exchange-hybrid-configuration-tips-moving-cloud-based-mailboxes-to-the-on-premises-organization.aspx
    http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/microsoft-pst-capture-tool-part1.html
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Migrating AD Exchange 2013 Objects to a new AD Domain

    I have a client 'new company' (NC) who is splitting from the 'parent company' (PC).  They are using a 3rd party tool to conduct the AD migration/split.
     The PC AD domain is on Windows 2012 Servers and has trust relationship with the NC AD domain also running on windows 2012 server.  The users and computers have been successfully migrated/stubbed to the NC domain, however, the Exchange 2013 objects
    are not migrating over to the NC AD domain using the 3rd party AD migration tool.   
    Question, does any one have suggestions on how to migrate the exchange 2013 objects from the PC AD to the NC AD ?
    What techniques can be used ?
    Thanks in advance 
    RK

    What 3rd party tool are you using and have you contacted their support already? You can use the native tools to migrate mailboxes (I do all the time) but I wouldn't try and mix the native tools and a 3rd party tool on the same migration unless I was sure
    what the end result would be.

  • Exchange 2013: how to set up multiple domain for OWA and ECP

    Exchange 2013 on Windows 2012R2
    Currently we have set this up using the guide below:
    http://mouzzamh.wordpress.com/2013/02/04/accessing-owa-from-multiple-domain-url/
    We can access OWA and ECP using the internal IP address/owa or ECP but when we use the URL it fails.
    We gave it an external IP address as well just to check if it will externally since the external DNS are pointing to the correct records: same issue it only works on IP address/owa or /ecp
    We were able to follow the guide from start to finish including the certs..
    The only difference on the guide and our exchange IIS environment for the new website is when he mentioned "Under IIS Settings / ISAPI and CGI Restrictions" we only have "ISAPI filters"...." ISAPI and CGI Restrictions" is only
    applicable to the default and backend website..
    Also, when the guide points to the path, should it be the new website path?
    Or maybe to avoid confusion, can anyone guide me on how to do it or any other guide that helped you if ever you had the same issue as mine?
    Thanks.

    Hi,
    Please run the following to check your OWA virtual directories for all web sites:
    Get-OWAVirtualDirectory | FL Identity,*URL*,path
    Personal suggestion, please consider to deploy another new CAS server. Then we can configure different OWA URLs in different servers. And pointed mail.domain.com and webmail.domain.com to two CAS servers respectively.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Is it possible to migrate Small Business Server 2008 to Exchange 2013 install on it's own member server?

    Trying to figure out of migration to Exchange 2013 is possible on a existing SBS 2008 with Exchange 2007.  If it's possible, is it support by Microsoft as well?
    Thank you!

    Are you planning to get rid of the SBS server or you would like to keep it as a DC, DHCP, DNS, and SharePoint server?
    You should be able to upgrade to Exchange 2013, but there are more details to consider. The following six part series outlines this process:
    Migrate from SBS 2008 or 2011 to Standard Edition Products
    Step by Step Screencasts and Video Tutorial

  • How many system mailboxes should be in exchange 2013 after moving from exchange 2010?

    Hi, I am moving mailboxes from exchange 2010 to exchange 2013, I noticed that in exchange 2013, besides discovery search mailbox, there are other 5 system mailboxes.(especially, there are 2 x Microsoft Exchange system mailboxes) Please see the pic attached.
    Does this look right? thanks

    Looks perfectly fine - Why MS decided to name two of the five arbitration mailboxes the same (Microsoft Exchange) is unclear but it is what it is :)
    In EMS:
    Martina Miskovic

  • Mail from my own domain

    I’m a newbie to the IPhone and also Mail on the Mac. For years now, I’ve just been using the Yahoo Mail web interface. I’m a ‘Plus’ subscriber, so I can use the web interface to send emails so that they appear to come from ‘[email protected]’.
    From what I understand, using the MAIL application, mails will appear to be sent from Yahoo.
    1. Is there a way of sending emails from ‘[email protected]’.
    2. Is there a way of permanently changing the “Reply To” field within the MAIL application?
    Thanks
    Brad

    It works for me! I use five different email addresses, with a variety of domain names including two I own, one from my ISP, one Bigfoot and one using the domain name of a company I do work for. All the outgoing messages appear with the appropriate 'From' email address. All replies come to dedicated inboxes on my ISP account according to where they were sent from, except that replies to the 'company' address (the last one on the list above) go to that company before being forwarded to me.
    All are IMAP accounts.
    The only slight difficulty is in trying to send when roaming away from my own internet connection, when some ISPs won't allow sending and showing a different 'From' address. Using an authenticated smtp server seems to fix that, although my ISP says it can't be done!?
    I put all the information in the usual 'Accounts' section of the mail preferences and it just seemed to work. The settings have replicated across to my laptop and iPhone as well without a problem. Keep trying!

  • Exchange 2013 Servers booting from SAN

    Hi,
    One of my client has decided to go with NetApp Flexpods for implementing Exchange 2013 in their environment.
    It has also been decided that these servers will boot from SAN and
    Exchange 2013 will also be installed on SAN. 
    We are planning to Install Win 2012 R2 for OS and E2k13 CU8. Few questions:
    1) Is it supported to boot Windows Server 2012 R2 from SAN, Specially if that server is going to used for E2k13
    2) Is it supported to Install Exchange 2013 CU8 on SAN
    I researched about this and understood that this is supported from Windows OS perspective. I am more concerned about the whole configuration falling within support boundary of Exchange 2013. I found an article which talks about the complexity involved in
    troubleshooting and indicates that its mainly SAN vendor who would be troubleshooting if running into any issues.
    https://support.microsoft.com/en-us/kb/305547- This article is not yet applicable to 2012 R2. Its applicable only till 2008 R2.
    http://www.enterprisenetworkingplanet.com/datacenter/the-pros-cons-of-booting-from-san.html - Pro & Cons of booting from SAN
    The booting from SAN for Exchange servers concerns me a lot as i have never seen any implementation in Exchange 2003, 2007 & 2010 doing this in my 10 years of experience. I have supported about 10 different enterprise exchange deployments and never saw
    this. So this is an unknown territory for me, hence looking for some best practices, articles and guidance around this if its supported by Microsoft Exchange team to run Windows and Exchange from SAN.
    Thanks
    Siva

    Hello,
    Please see the “Supported storage architectures” in the following article:
    https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

Maybe you are looking for