Exchange 2013 mailbox rule and mail forwarding

HI All,
when user is forwarding messages from owa to same exchange organization (same smtp domain) or external domain is not working.
please suggest.

Hi,
As ManU suggested, please take your time to post the error information for my further research.
What's more, please verify if this user can send messages (not forwarding) directly to others.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2013 Transport Rules and Exchange 2007 Decommissioning

    Hello,
    I recently migrated from Exchange 2010 to Exchange 2013, I do have a few traces of Exchange 2007 in the Active Directory that I would like to completely remove. The Exchange 2007 server failed earlier and wasn't decommissioned properly. I read a few articles
    on how to completely remove it from AD, I am still concerned to make the changes in "ADSI Edit". 
    Here is the error message I receive when creating transport rules in Exchange 2013:
    "You are about to create a rule in an organization where Hub Transport servers running Exchange Server 2007
    exist. To ensure the rule is applied consistently across all Hub Transport servers in the organization, you must create an equivalent rule from the Exchange Management Console on an Exchange 2007 server."
    I also noticed that the version of the rules remain Version: 14.0.0.0 for any new rules that I am creating in Exchange 2013.
    I would really appreciate if someone can provide their views and the best practices to remove the traces of Exchange 2007 in AD.

    Hi Sathish,
    How about the result after using ADSI Edit ?
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Exchange 2007 edb to Exchange 2013 - mailbox extraction and mounting

    Hello everyone, here is my question:
    I have a client who has Exchange 2007 running on a Domain Controller which is a Server 2008 and that is the only domain controller in his environment. That said, his domain controller crashed and all the AD data is now lost along with Exchange except the
    EDB files. He wants to create a new domain controller with Server 2012 and wants to deploy Exchange Server 2013. Since the Domain Name will be the same, is it even possible to extract the mailbox information from Exchange 2007 EDB and attach it with new Exchange
    Server 2013 and point them to newly created users on Exchange? If yes, how exactly will this work? Thanks in advance.

    Excellent and factual responses from the others and the instructions/guidance should serve you well. If however you want to avoid building a new server etc you could use Lucid8's DigiScope
    http://www.lucid8.com/product/digiscope.asp to open the 2007 EDB on a 64 bit machine and then you could take 1 of 2 actions to resolve your issue.
    1. You could then export all mailboxes to PST and then Import them into the 2013 environment
    2. OR you could have DigiScope migrate/recover the data directly from the offline 2007 EDB into the Production 2013 server on the fly, i.e. no end user downtime is required.
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

    Hello guys,
    I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
    When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
    When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
    We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
    What should I check and configure to make it work?

    Hi,
    I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact  EMC supplier to improve it.
    By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
    A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Exchange 2013 mailboxes not accessible in outlook

    Hi,
    In the middle of migration from one exchange 2010 server to 2013 server and thought things were going well.  However migrated mailboxes to exchange 2013 are not accessible through outlook although they are through OWA most of the time.
    I ran test connectivity comandlet on 2013 server on mailboxes and they tested okay.
    However when you connect to mailbox it says exchange unavailable.  
    I have a new ucc certificate on the exchange 2013 server that includes mail.contoso.com and autodiscover.contoso.com.  These are both setup to point to 2013 server with split brain dns.  The 2010 server has a certificate for mail.contoso.com.
    The SC for autodiscovery right now for both the exchange 2010 and 2013 servers are https://mail.contoso.com/autodiscover/autodiscover.xml
    When I run outlook connectivity test I get the following failure: 
    Test Steps
    Attempting to ping the MAPI Address Book endpoint with identity: exg:6004.
    The attempt to ping the endpoint failed
    Additional Details
    The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
    Elapsed Time: 24085 ms
    Test Steps
    Attempting to ping the MAPI Address Book endpoint with identity: exg:6004.
    The attempt to ping the endpoint failed.
     <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl07_ctl00_tmmArrow">Tell
    me more about this issue and how to resolve it</label>
    Additional Details
    The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
    Elapsed Time: 24085 ms

    Hi
    Did you migrate your DNS to point to the new Exchange 2013 Server?
    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

    Hi Team,
    I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
    Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
    open and throws an error of some "cannot open set of folders".
    Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
    Kindly share some KB or tip. Any help is appreciated. Thank You.
    Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

    I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

    I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
    for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
    the following command:
    Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
    The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
    how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
    Many thanks.

    Hi Dennis,
    Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
    Please check your connection authentication. We can  run the following command to set your Outlook Anywhere for Exchange 2013:
    Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
    In Outlook side, please ensure the following settings in Account Settings:
    In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Mailbox Role Installation Error

    Hi All,
    I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
    Error:
    The following error was generated when "$error.Clear();
              Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
    . HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
       at System.DirectoryServices.DirectoryEntry
       at System.DirectoryServices.DirectoryEntry.Bind()
       at System.DirectoryServices.DirectoryEntry.RefreshCache()
       at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
       at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Any views on this is appreciated.
    Regards
    Boniface
    Senior Systems Administrator

    Hi,
    After uninstalling the IIS, please run the following command to install prerequisites.
    Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
    Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
    Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
    Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
    In addition, please disable any third-part software for troublwshooting.
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

    Hi All,
    we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013  and i have to add the 2013
    servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
    Thanks, Venkatesh. &quot;Hardwork Never Fails&quot;

    For a step by step follow the deployment assistant
    http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 mailbox added to the CAS array

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

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

  • Performance counters for exchange 2013 mailbox & cas servers?

    what are the Performance counters for exchange 2013 mailbox & cas servers?
     similar to rpc request for troubleshooting exchange slowness, I haven't found any technet article for exchange 2013. 

    Hi,
    Please see this:
    Ask the Perf Guy: Sizing Exchange 2013 Deployments
    http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
    Hope it is what you need.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013: Inbox rules don't work on Journal Mailbox

    Hello,
    I've Exchange 2013 server with 2 databases:
    * First database has all user mailboxes & is journaled to second database
    * Second database has only 1 mailbox: Journal which collects all messages send / received  from / to first database.
    I made Inbox Rules on Journal Mailbox  to delete unnecessary messages e.g. :
    * HealthMailbox messages with Subject: Client submission probe
    * [email protected] messages with Subject: Inbound proxy probe.
    I noticed that these rules don't work. Why ?
    best regards Janusz Such

    Hi,
    How do you create these Inbox Rules on journal Mailbox? Please share the detailed rule content here and we can check whether the rule was created correctly or not.
    Instead of journaling all mailboxes residing on a mailbox database, I suggest we can configure journal rules to match your organization's needs by journaling individual recipients or members of distribution groups. For more information about
    journal rules, please refer to:
    https://technet.microsoft.com/en-us/library/jj651670%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
    Regards,
    Winnie Liang
    TechNet Community Support

  • After Migration Exchange 2013 does not send mail outside the organization

    Dear,
    After Migration Exchange 2010 to exchange 2013. We does not send email from the organization but we can received mail from others organization.
    Delivery has failed to these recipients or groups:
    [email protected] ([email protected]) The server has tried to deliver this message,
    without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.
    Diagnostic information for administrators:
    Generating server: OGMAIL.domain.net Receiving server: gmail.com (2607:f8b0:400c:c01::1a)
    [email protected] 6/11/2014 10:16:10 AM - Remote Server at gmail.com (2607:f8b0:400c:c01::1a) returned '550 4.4.7 QUEUE.Expired; message expired' 6/11/2014
    10:03:49 AM - Remote Server at gmail.com (2607:f8b0:400c:c01::1a) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10051, Win32 error code: 10051." Attempted failover
    to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 2607:f8b0:400c:c01::1a:25'
    Original message headers:
    Received: from OGMAIL.domain.net (192.168.10.12) by ogmail.domain.net
     (192.168.10.12) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 9 Jun
     2014 16:13:30 +0600
    Received: from OGMAIL.domain.net ([::1]) by ogmail.domain.net ([::1]) with
     mapi id 15.00.0847.030; Mon, 9 Jun 2014 16:13:30 +0600
    From: Administrator <[email protected]>
    To: Administrator <[email protected]>
    CC: IT.HW-Masudur Rahman-MRT <[email protected]>, "[email protected]"
        <[email protected]>
    Subject: RE: Migration batch mrtmove has completed successfully.
    Thread-Topic: Migration batch mrtmove has completed successfully.
    Thread-Index: AQHPd1JEcid9YEi4F0ue6m1039EwR5top+xp
    Date: Mon, 9 Jun 2014 10:13:29 +0000
    Message-ID: <[email protected]>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    x-originating-ip: [192.168.10.2]
    Content-Type: multipart/alternative;
          boundary="_000_6b0d846f503942d99d44be9aff8d6adfogmaildomainnet_"
    MIME-Version: 1.0
    Queue viewer:
    Identity: ogmail\8786\3470333575194
    Subject: testing
    Internet Message ID: <[email protected]>
    From Address: [email protected]
    Status: Active
    Size (KB): 4
    Message Source Name: SMTP:Default OGMAIL
    Source IP: 192.168.10.12
    SCL: -1
    Date Received: 6/23/2014 3:22:49 PM
    Expiration Time: 6/25/2014 3:22:49 PM
    Last Error: 
    Queue ID: ogmail\8786
    Recipients:  [email protected];2;2;[{LRT=};{LED=};{FQDN=};{IP=}];0;CN=SendMail,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=domain,DC=net;0
    Md. Ramin Hossain

    What I notice is Queue expired. The message is not going out.
    Failed to connect. Winsock error code: 10051, Win32 error code: 10051." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
    This error states that It tried to connect to the target system but failed to connect out.
    Is Exchange 2013 server added in the firewall rule to send communication over port 25?
    Do you have use Front end proxy checkbox checked on the Send connector to internet that was created on 2013 (if created)?
    If use front end proxy checkbox is checked, then you need to add permissions for your CAS server's IP in the Firewall for outbound port 25 rule. As it appears that the mail is originating from CAS to the firewall. If that checkbox is not checked, we need
    to add the Mailbox server's IP on the outbound rule for port 25.

  • Exchange 2007 - Exchange 2013 Mailbox Migration Issues

    Exchange 2013 -  Mail Flow is working.   OWA Access is great.   We have issues connecting Outlook 2010 Clients.  If I create a new user and mailbox Outlook 2010 works fine.   However, if we migrate a user's mailbox to the new Exchange
    2013 server.  Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server"  There is something different about a newly created account and a migrated account.  Any help would be great.   I did check
    inheritance in AD and it was on for these accounts.  This occurs with any account migrated to the new server.

    1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
    generates and provides the correct information.
    2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
    Step by Step Screencasts and Video Tutorials

  • Outlook 2010 prompt for credential when connecting to Exchange 2013 mailbox

    I have 4 server Exchange 2010 with DAG and one server Exchange 2013, i've migrated some mailbox to the new 2013 server.
    I'm having a problem with some Outlook 2010 that sometimes (not always) requires credential to connect to mailbox in a server Exchange 2013, but only
    when Cache mode is enabled.
    The client ask for credential and dont connect to mailbox until I change in online mode.
    In Online Mode, everything works fine.
    I don't have Public Folders, so the check box Download Public Folder is not selected and the authentication mode is "Negotiate".
    Thanks in advance.
    Elisa

    Hi,
    As far as I know, by default, shared mail folders not public folders are downloaded in Cached mode in Outlook 2010 and Outlook 2013:
    http://support.microsoft.com/kb/982697/en-us
    Please check if there is shared folder in the problematic Outlook 2010 client and try to check if the issue still exists with the same account on other Outlook client.
    Best regards,
    Angela Shi
    TechNet Community Support

Maybe you are looking for