Adding external address to Exchange 2013 Contact

When editing a Contact in Exchange 2013, you go to the Email Options of the Contact to add additional email addresses and there is now a drop down box so you can only add email addresses from your internal domain.
In previous versions of Exchange if was just a field you could type in and you could add email addresses from any domain including external ones.
Anybody know how I can do this or if this functionality has been removed and why?
Many thanks in advance. 
This topic first appeared in the Spiceworks Community

For single ID
Set-DistributionGroup Office365 -EmailAddresses @{Add="[email protected]"} -Verbose
For Bulk ID
Change the CSV file location.
SecondaryEmailID is your CSV header - Test before executing it
Import-csv C:\EmailID.csv | %{
Set-DistributionGroup "Office365" -EmailAddresses @{Add=$_.SecondaryEmailID} -Verbose
Regards Chen V [MCTS SharePoint 2010]

Similar Messages

  • What is the easiest way to create alias email addresses in exchange 2013?

    For example my official domain is [email protected]
    Within my company i want to make it look like certain departments are sending from bicycles.com skateboards.com
    and skooters.com and receive to those addresses even though the emails are really going through the
    [email protected] domain. but it appears to be coming from three other domains.
    appearance is everything. What is the easiest way to accomplish this.
    Step by step with examples if possible. I am not well versed in exchange server 2013 yet.
    Droid Hacker

    In Exchange 2013 you can use the ECP to add additional email addresses to mailboxes. In order for a mailbox to send using an address, that address needs to be set as the reply address. One mailbox cannot send as multiple addresses. Doing that would require
    a mailbox for each address. To set a new primary address on a mailbox log into the ECP and choose mailboxes under the recipients option on the left. Then search for the mailbox you want to add the address to and click the edit symbol. Navigate to the
    Email Address tab on the left. To set a new primary address you will likely need uncheck the box for "Automatically update email addresses based on the email address policy applied to this recipient". Then click the plus button, enter the new address,
    and check the box for "Make this the reply address"
    Before you do this you should ensure that the proper MS records exist for these other domains, and that they are properly configured for mail flow. Once you set this as the reply address for a mailbox, that is the address external users will use for replies.

  • Adding second domain in Exchange 2013

    Dear all, 
    I am migrating our mail server from Exchange 2007 to 2013. Untill now not many problems encountered, I have set up a 2 members DAG for redundancy and most of Exchange functions and services are working like a charm (except sharing schedule's when you work
    with Outlook 2007 on the Exchange 2013 server).
    Now comes the challenge: Our company has bought another company. They have their own domain. We need to migrate all their mailboxes to our mailserver, with as little downtime as possible. Their mail addresses needs to be kept the same, but they will work
    in our mail server. 
    I wonder if someone has experience on doing this? How can I connect the mailboxes to our domain, keeping the old known address to clients. This company delivers very critical services to diverse clients, and every 5 minutes downtime is actually too much,
    and changing addresses is not possible. Can someone help me with this? 
    All help will be appreciated! 
    Regards, 
    Cornelius 

    If both networks are interlinked and if you have control on remote exchange you could try this
    configure the remotedomain as external relay in your exchange http://technet.microsoft.com/en-us/library/bb676395(v=exchg.141).aspx 
    create a receive connector in the remote exchange to allow relay
    http://technet.microsoft.com/en-us/library/bb232021.aspx
    So if the receipt if not exists locally it will forward to the next exchange. 
    Same way configure one relay domain in remote exchange and receive connector to allow relay.
    Slowly move the users using ADMT to your Exchange (near to no down time). 
    Please check this http://social.technet.microsoft.com/Forums/exchange/en-US/6dc39d94-92a0-4341-9db5-6048997527af/connecting-exchange-2010-in-network-a-to-send-email-to-exchange-in-network-b?forum=exchange2010
    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.

  • CMWS CANNOT SEND EXTERNAL MAIL WITH EXCHANGE 2013

    Hi, all. i have integrated the cmws 1.5 server with exhcange 2013 mail server , now the webex can send mail to the user which in exchange, but cannot send mail to external mail server, how can i  fix this trouble? thank you.

    Hi Bin,
    Please look into exchange configuration, as it is not allowing emails from CWMS to be relayed to the Internet. This is not due to CWMS configuration.
    Thanks,
    Derek Johnson
    Conferencing TAC

  • Address Book, Exchange Account, Contact Photos with iPhone and EntourageEWS

    In SL Address Book I cannot assign a picture to a contact in my Exchange AB. For my local AB this still works fine. Bug or by design?
    With my iPhone I can assign pictures to my Exchange contacts and this pictures will also displayed in Address Book and Entourage 2008 EWS.
    If I assign a picture in Entourage EWS it will show up in Address Book, but NOT on the iPhone.
    Any Ideas?

    So in regards to this issue, what's the best way of getting photos assigned to contacts when using an Exchange server. I have a bunch of contacts stored locally on my Mac address book which I had since copied over into the Exchange server. You state I can only assign photos from within the iPhone. So what's the best way to get a photo on the Mac to the iPhone. Do I get photos into the iPhoto, sync my iPhone with my Mac, and then go to the iPhone and manually add the photos to contacts one a time? Is there a faster/better way?

  • SBS 2008 to Exchange 2013 - "Create legacy Exchange host name"... Single External IP?

    Migrating a customer to Exchange 2013 from SBS 2008.
    Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
    The customer only has a single external IP address...
    So what do I do for this external DNS of legacy.customer.com?

    Hi Allister - 
    You shouldn't need an EXTERNAL dns entry for legacy. Here's how it works:
    Client from outside -> External IP to Exchange 2013 (now here's where the interesting thing happens)
    Exchange auto-magically proxies mailboxes on the old environment. Reason being: New Exchange Servers always know how to get to old servers. You just change all the internal URLs to legacy. (or you can even do oldmail., whatever you like) and since this information
    is inside AD, Ex2013 will find it.
    These are the URLs you need to change in 2007/2010
    ClientAccessServer
    webservicesvirtualdirectory
    oabvirtualdirectory
    owavirtualdirectory
    ecpvirtualdirectory
    ActiveSyncVirtualDirectory
    AutodiscoverVirtualDirectory You can read more on how to set these here:
    http://social.technet.microsoft.com/wiki/contents/articles/5163.managing-exchange-2010-externalinternal-url-s-via-powershell.aspx
    Here's the Million dollar question though: being SBS 2008, does this have exchange 2007 or 2010 on it? If it's 2010, you don't need the legacy namespace anymore. 2007, you do. Connect to https://ex2013server/owa and log into a mailbox on the 2010 environment.
    If you can get there (you'll know cause it flipped over to a 2010 interface) then it's working.
    A wise man is a fool, with a good memory.

  • Exchange 2013 - External Windows XP/Outlook 2007 Password Prompt

    I have an Exchange 2013 server and everything is working correctly internal with XP clients that are connected to the domain.  My problem is that the Windows XP computers that are connecting from outside of the office that aren't connected to the domain
    and have local usernames and passwords keep getting the password prompts.  I put in the correct domain\username and password and it connects.  The if I close and reopen it asks me for the password, I have saved the credentials but it still asks.
     I have look and applied these settings from these articles but I'm still having the issue.  All of the internal and external names match my GoDaddy SSL certificate (mail.domain.com). Get-OutlookAnywhere shows:
    ExternalHostname                   : mail.domain.com
    InternalHostname                   : mail.domain.com
    ExternalClientAuthenticationMethod : Negotiate
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/
    http://pickettsproblems.wordpress.com/2013/04/08/windows-xp-users-not-connecting-to-exchange-2013-server/

    Here is my XML log from Test E-mail AutoConfiguration if you need it:
    <?xml version="1.0" encoding="utf-8"?>
    <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
      <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
        <User>
          <DisplayName>Ryan Laurie</DisplayName>
          <LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=03614938e08f481b8f7e1bbc7346aa22-Ryan</LegacyDN>
          <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
          <DeploymentId>463444fb-5651-4b0f-91e5-6356fc132a95</DeploymentId>
        </User>
        <Account>
          <AccountType>email</AccountType>
          <Action>settings</Action>
          <MicrosoftOnline>False</MicrosoftOnline>
          <Protocol>
            <Type>EXCH</Type>
            <Server>[email protected]</Server>
            <ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
            <ServerVersion>73C08204</ServerVersion>
            <MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
            <PublicFolderServer>Exchange.mydomain.local</PublicFolderServer>
            <AD>SERVER2.mydomain.local</AD>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EmwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EmwsUrl>
            <EcpUrl>https://mail.mydomain.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.local</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=mydomain.local</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-extinstall>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://mail.mydomain.com/OAB/a9a90db6-fd7f-492b-9e29-4848f16cae2f/</OABUrl>
            <ServerExclusiveConnect>off</ServerExclusiveConnect>
          </Protocol>
          <Protocol>
            <Type>EXPR</Type>
            <Server>mail.mydomain.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Ntlm</AuthPackage>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EmwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EmwsUrl>
            <EcpUrl>https://mail.mydomain.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.local</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=mydomain.local</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-extinstall>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://mail.mydomain.com/OAB/a9a90db6-fd7f-492b-9e29-4848f16cae2f/</OABUrl>
            <ServerExclusiveConnect>on</ServerExclusiveConnect>
            <EwsPartnerUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsPartnerUrl>
          </Protocol>
          <Protocol>
            <Type>WEB</Type>
            <Internal>
              <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.mydomain.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXCH</Type>
                <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </Internal>
            <External>
              <OWAUrl AuthenticationMethod="Fba">https://mail.mydomain.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXPR</Type>
                <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </External>
          </Protocol>
          <Protocol>
            <Type>EXHTTP</Type>
            <Server>mail.mydomain.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Ntlm</AuthPackage>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EmwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EmwsUrl>
            <EcpUrl>https://mail.mydomain.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.local</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=mydomain.local</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-extinstall>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://mail.mydomain.com/OAB/a9a90db6-fd7f-492b-9e29-4848f16cae2f/</OABUrl>
            <ServerExclusiveConnect>On</ServerExclusiveConnect>
          </Protocol>
          <Protocol>
            <Type>EXHTTP</Type>
            <Server>mail.mydomain.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Ntlm</AuthPackage>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EmwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EmwsUrl>
            <EcpUrl>https://mail.mydomain.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.local</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=mydomain.local</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.local</EcpUrl-extinstall>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://mail.mydomain.com/OAB/a9a90db6-fd7f-492b-9e29-4848f16cae2f/</OABUrl>
            <ServerExclusiveConnect>On</ServerExclusiveConnect>
          </Protocol>
        </Account>
      </Response>
    </Autodiscover>

  • Exchange 2013 co-existence with 2007 can not send from 2013 - receives OK

    2013 SP1  -separate servers for MBX and CAS - 4 of each. Exchange 2007 configured as a CCR
    I am in co-existence mode but have not yet switched on the legacy.domainname.com. I have a new certificate installed on all servers - 2007 and 2013 with the legacy namespace included
    I can receive on the exchange 2013 servers and can send to exchange 2013 users but cannot send to 2007 users or externally. I have enabled protocol logging and I'm seeing:
    2014-04-02T00:57:31.476Z,Outbound Primary,08D1120CF8FEEDBA,0,,10.0.9.1:25,*,,attempting to connect
    2014-04-02T00:57:52.521Z,Outbound Primary,08D1120CF8FEEDBA,1,,10.0.9.1:25,*,,"Failed to connect. Winsock error code: 10060, Win32 error code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a
    period of time, or established connection failed because connected host has failed to respond 10.0.9.1:25"
    The client has a pair of Axway mailgateway appliances (Tumbleweed). We can Telnet between the exchange 2013 servers and the Axways. There is a firewall between these mail gateways and the exchange servers and the following ports were opened - 25,443,465,995,110
    I used the existing send connectors from 2007 and just added the mailbox servers to them. I created 2 new receive connectors to match 2 specialist 2007 connectors.
    But I still can't send mail. Any suggestions where next to check?

    Hi Tony 
    Based on the protocol logs error looks like there is connectivity problem between Ex2007 and Ex2013
    First you can try dropping an email through Telnet from Exchange 2013 to Exchange 2007 to see the message failure happens at which transit.
    You can add the IP address of Exchange 2013 in Exchange 2007 default receive connector and vice versa.
    Restart the transport service and try sending an email from exchange 2013 to Exchange 2007 and see the results
    Also you can try creating a dedicated receive connector for Exchange 2007 in Exchange 2013 and vice versa if the above step does not work 
    Also try disabling the firewall and see if it helps.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

  • 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

  • OWA problem Exchange 2013 coexistence with 2010

    Hi all,
    I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
    successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
    to access OWA with a mailbox that is still on 2010 it fails with the following error:
    something went wrong
    A problem occurred while you were trying to use your mailbox.
    X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
    X-OWA-Version: 15.0.913.21
    X-FEServer: <name of 2013 server>
    X-BEServer: <name of 2013 server>
    Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
    Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
    This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
    Any help is greatly appreciated!
    Best regards
    Daniel

    Hi,
    How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
    Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
    According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
     for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

    Hello,
    we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
    using Outlook Anywhere.
    The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
    Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
    #554 5.6.0 STOREDRV.Deliver; Corrupt message content##  from the external provider's servers.
    When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
    We have no problems using the company's Exchange 2013 servers.
    Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
    Thank you
    Sascha

    Hi,
    The problem should be related to the External Exchange 2007.
    Please refer to this kb below:
    http://support.microsoft.com/kb/2203381/en-us
    This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body.  If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
    that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
    To resolve this problem, you should let the External Provider install the following update rollup:
    2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
    Hope this helps.
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

    We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them. 
    With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
    For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
    In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
    I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
    I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
    So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
    In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
    Questions are, Is this the right way to migrate all the users to Exchange 2013?
    Will it affect the operation of existing Exchange 2007 server?

    Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
    For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
    However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
    2013 for standardization.
    Refer article for configuring URLs -
    http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
    - Sarvesh Goel - Enterprise Messaging Administrator

  • Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

    I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of.  I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
    clients get prompted for a security warning.  I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine.  My Outlook 2013 client doesn't prompt me with the message but I have other users who are
    still getting the "The name of the security certificate is invalid or does not match the name of the site" error.  The domain on the cert error show up as server.mydomain.local.  I've gone through all the virtual directories and pointed
    all of my internal and external URL's to https://mail.mydomain.com.   This made one of the two warnings go away but not the second.  I've dug around on google and gone through everything I could find here and as far as I can tell my internal
    and external url's are configured properly and I can't figure out where this error is originating from.  Any ideas on where I should look outside of the virtual directories? 
    I'm including a good link I found that contains all of the virtual directories I updated.  I've checked them through both CLI and GUI and everything looks good.
    http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
    http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

    Hi,
    When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
    Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
    Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
    Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Monitoring external mailflow of Exhange 2013

    Hi
    I need to use SCOM 2012 R2 to monitor external mailflow on Exchange 2013.  Please help!

    Hi,
    Please import Exchange 2013 management pack to your management group:
    http://www.microsoft.com/en-hk/download/details.aspx?id=39039
    I hope there are monitors that can be used to monitor mail flows within the management pack.
    And there is a powershell command Test-Mailflow which can be used to check mail flow:
    http://technet.microsoft.com/en-us/library/aa995894(v=exchg.150).aspx
    Hope this helps.
    Regards,
    Yan Li
    Regards, Yan Li

  • Exchange 2013 External Relay gives me a headache... Anonymous relay fail to external address

    I tried to set up external relay on my Exchange 2013 but was not able to do it. I don't know what else to do. I tried these:
    http://technet.microsoft.com/en-us/library/bb232021.aspx
    and these (which is pretty much same thing)
    http://www.shudnow.net/2013/06/04/how-anonymous-relay-works-in-exchange-2013/
    http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
    http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
    http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx
    But still no luck. Here is somewhat detailed description what I tried do accomplice. 
    Server which need  to send mail reports is sending these from web server on another location connected with site-to-site VPN to location server resides like on picture. I am able to send relay to all of
    addreses of local domain but when I tried to send mails to my clients to external e mail addresses exchange return me message unable to relay.
    Here is log from unsuccessfully operation
    Connecting to [smtp.mydomain.com] port [25]...
    220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 17:19:45 +0100
    >HELO webserver
    250 smtp.mydomain.com Hello [89.x.x.x]
    >MAIL FROM: <[email protected]>
    250 2.1.0 Sender OK
    >RCPT TO: <[email protected]>
    ERR: Received the following unexpected repsonse:
    550 5.7.1 Unable to relay
    >QUIT
    221 2.0.0 Service closing transmission channel
    Here is log from successfully operation:
    Connecting to [89.x.x.x] port [25]...
    220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 18:04:52 +0100
    >HELO webserver
    250 smtp.mydomain.com Hello [89.x.x.x]
    >MAIL FROM: <[email protected]>
    250 2.1.0 Sender OK
    >RCPT TO: <[email protected]>
    250 2.1.5 Recipient OK
    >RCPT TO: <[email protected]>
    250 2.1.5 Recipient OK
    >DATA
    354 Start mail input; end with <CRLF>.<CRLF>
    >From: Dane <[email protected]>
    >To: [email protected]
    >Subject: asd
    >Date: Fri, 24 Jan 2014 18:03:08 +0100
    >X-Mailer: Qm Version 2.1
    >MIME-Version: 1.0
    Content-type: text/plain
    >
    >test>
    250 2.6.0 <3ffb1fd6-e5e0-4232-9a6e-cac7b59db9df@exchange.mylocaldomain.local> [InternalId=6240587481093] Queued mail for delivery
    >QUIT
    221 2.0.0 Service closing transmission channel
    And here is picture:

    Hello,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Regards,
    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

  • How is the best way to make a mirror of your site for a Spanish version that links to the English and Visa versa

    I will need to have my site be multilingual and was wondering what the best approach to this is. The sites will be identical with the text changing from one language to another.

  • Error during PO creation from contract

    Hi all, my requirement is to change the Handling type field of that purchase order that is referred from contract using the BADI ME_PROCESS_PO_CUST and Method PROCESS_ITEM. but i am getting an error message " Data from Business Add-In ME_PROCESS_PO_C

  • SAP EP 6.0 Installation Problems -- Please Help

    Hi, I am new to the SAP EP Technology (any SAP for that matter) - I figured out that downloading the EP Sneak Preview would be a good idea to learn it. So I downloaded the WAS (Java 6.4) and installed it without any problems. The JRE is working fine

  • Error in configuring File Sender Adapter with File Content Conversion

    Hi i am designing a File to File scenario using file content conversion in which the input is comma separated file and output is a XML document. mentioned below are the configuration information: Recordset Name: Substr Substr.fieldSeparator: , Substr

  • Help with my Ipad and talk talk

    I have the first ipad not the ipad 2 my question is I know if I go where there is wifi  ( like a friends house ) I can connect if I have the password . But my friend is using Talk Talk wireless he saids he was not given a password . So how can i conn