Exchange Server 2013 - Mailflow - Transport Rules - Autoreply to External Email Addresses and Customizable Template

Hi There,
I have two question relating to this topic:
Question 1 - Can I set up an auto reply message (e.g. Thank you for submitting your enquiry....) to any emails that are
only external and not including our domain to the organisation for a specific email address. I need to be able to specify other domains also that I don't want this rule to be applied to?
Question 2 - If this is possible, is there a customizable template that can be used for the auto reply message?
Hopefully someone can help!

Hi Eric,
This needs to be completed from another program either exchange / ?
There is a problem if you configure this from an actual mailbox / OWA due to the lack of configuration options available.
Here's a more detailed scenario:
We have a mailbox that our records department use e.g.
[email protected] to register incoming mail from. This also has an alias that external people send to e.g.
[email protected] . We still need staff within our domain to send emails to the
[email protected] and do not want the auto message (e.g. Thank you for submitting your enquiry....) sent to those internal staff. There is the possibility of a looping being created otherwise.
Only people outside the organisation sending an email to
[email protected] should receive the auto reply message (e.g. Thank you for submitting your enquiry....).
We need the ability to add in an exception to the rule to bypass or not process the rule if the sender is a part of *@ourdomain.com which means they will not receive an auto reply. We also need
to be able to add other domain we specify e.g.
*@someoneelsedomain.com not to receive the auto reply.
We currently use MailMarshal to perform the above task but will be decommissioning this during the Exchange 2013 implementation soon to begin. We are not installing an Microsoft Edge Transport server that I believe does allow configurable rules like
this as all of our mail will first be routed through the Symantec / Telstra solution first. I'm still trying to find out if the Symantec solution can complete this process for us but I doubt it.
This is why I'm trying to find out if Exchange 2013 from the admin console somehow can complete the rules and exceptions that we require above.
Thanks
Lisa
Lisa Stanley

Similar Messages

Exchange Server 2013 - Mailflow - Transport Rules - Forwarding Emails with Specific Text to Another Email Address

Hi There,
We are soon to implement Exchange 2013.
Question: Is it possible to have emails with specific text such as "..SND.." to an other email address specified as well as the original recipient?
Thanks very much.
Lisa.

Hi Amit,
Thanks for answering my question. I have one more. To enable rules like this do you need to have an Exchange Edge Transport server installed or is this configured from an admin console within Exchange itself?
Thank you,
Lisa
Lisa Stanley

Exchange Server 2013 Edge Transport Role

Dear,
I have a question regarding Exchange Server 2013 SP1 that, I have installed Edge Transport Server Role on separate box without Domain Joined. Obviously I installed Exchange CAS and Mailbox on Same box with
Domain Joined in Corporate LAN.. But my edge is placed on DMZ and it is ready with all configuration, Mailbox Server Synchronization is also installed with Edge. Means all required configuration are properly configured and it is verified. But I want clients
to OWA Access from Edge only. Because I want to restrict my internal network from the internet. So kindly provide me any possible ways to access OWA from Edge only ??. I have see some another methods like "Web Application Proxy instead of TMG because
TMG is expired"..
Kindly provide me possible ways or URL so I will configure it..
Thanks.
Fuzail (FM)

Hi,
Is there any further question on this thread?
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

Exchange server 2010 - Hub Transport rule not working

Hello,
I'm trying to create a hub transport rule that blocks any incoming / outgoing email with attachments larger than 10MB with an exception of a few users.
I've followed this article https://www.simple-talk.com/sysadmin/exchange/increasing-email-size-limits-for-your-high-profile-users-in-exchange-2010/.
The send connector & receive connector is at 30MB right now and the distribution group has been made.
I added myself to the distribution group which allowed me to send a 20MB size email.
If I remove myself from the distribution group, exchange still allowed me to send the 20MB email size.
Any advise is much appreciated.
Thanks,
Daniel

Hi Daniel,
Thanks for your response.
The Hub Transport server is responsible for handling transport rules. The transport rules can't work without a Hub server.
If there are any problems with Exchange, welcome to our forum.
Best regards,
Amy
Amy Wang
TechNet Community Support

Configuring Multiple domain Email addresses in Exchange server 2013 for Send/Receive

I've setup an exchange server 2013 , I have an requirement to setup email addresses for multiple domain account.
For example - My primary email addresses - [email protected] however i need to setup multiple domain email account for single AD user.
Example
[email protected]
[email protected]
[email protected]
I was able to setup account to receive email from different users to single mailbox users however how can i send mails from other domains email address apart from primary domain email
Thank you
Benhur

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Exchange Server 2013 Port details

In technet and blog exchange 2010 network port requirement are available. But i didn't found Exchange server 2013 network port requirement
Please give me the link and details of Exchange 2013 network port requirement.

In technet and blog exchange 2010 network port requirement are available. But i didn't found Exchange server 2013 network port requirement
Please give me the link and details of Exchange 2013 network port requirement.
From my painful experience today - I've just built an Exchange 2013 Enterprise box today.
I can say your router switch or whatever needs 3 holes:
Port 25, 443 and 444 - exchange should create all the firewall rules for you on install.
Be prepared for a bit of jiggery pokery with power shell, dns, and your cPanel.
Quite apart from all the BPA queries (100's of 'em) across three 2012R2 servers:
AD1 + AD2(backup)+Exch2013 - it really is pitiful that Microsoft haven't built an install routine that ALSO covers best practice configuration AT THE SAME TIME - each box needs to be run for 24 hours at least to ensure you've captured enough issues
to correctly set the boxes up to speak with one another.
Hope this helps a load of you - this is a good resource and the blanks can be filled in by a little further research.
http://technet.microsoft.com/en-us/library/jj218640%28v=exchg.150%29.aspx
Cheers
Simon
PS - I should also add - Ignore this and all other messages like. The resolution is far more adverse than the issue. Your exchange will come to a crunching halt. I feel a massive service pack coming on :-)
Problem:
Application pool 'MSExchangeOWACalendarAppPool' is set to run as an administrator, as local system, or to 'Act as part of the operating system'.
Impact:
The application pool can execute high-privileged code, including potentially malicious code that can negatively affect your server.
Resolution:
Set the application pool to run as the application pool identity.

How to Block spam,malware in exchange server 2013

How to block spam,junk mails inexchange server 2013 with out blocking normal mail. when i tried enable antispam on my sonicwall some important mails also removed. how to rectify these issues

Hi ,
To get it corrected , please contact sonicwall vendor to reduce the aggressive blocking in sonicwall.
If you are not interested in third party solutions please use the EDGE SERVER as your smarthost and on that EDGE server you can enable Anti-Spam features to block the forged connections and fake mails.
http://exchangeserverpro.com/installing-exchange-server-2013-edge-transport-server/
http://exchangeserverpro.com/add-ip-block-list-provider-exchange-server-2013-edge-transport/
http://exchangequery.com/2014/03/21/comparing-the-differences-between-antispam-agents-from-exchange-2010-to-exchange-2013/
Thanks & Regards S.Nithyanandham

Exchange Server 2013 failover design

Hello:
I'm designing a failover Exchange Server 2013 solution. I only need mail and calendar services.
I'm planning to put two physical servers with Windows Server 2012 R2 with (or without) Hyper-V to run one virtual machine in
each physical server.
I don’t have external storage device, I like to use database replication
Also, I have a physical third party anti-spam firewall
The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server?
I need a third server to avoid brain duplication, or isn’t needed?
Exchange Server 2013 supports POP3 connections?
Thanks for your time, and sorry for my bad English!
Un saludo! Juan Segura

The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server? - Definitely you can go for multi-role servers
to combine MBX+CAS and in fact that's
recommended except couple scenarios.
I need a third server to avoid brain duplication, or isn’t needed? You need a witness server but that can be non-Exchange server too. You need to add Exchange trusted subsystem
in Local Admin group of that server
Exchange Server 2013 supports POP3 connections? - Yes, you can have POP3 connections
Blog |
Get Your Exchange Powershell Tip of the Day from here

Mails struck in Drafts folder after Transport Agent installed in Exchange Server 2013

Hi all,
I created Transport Agent and installed successfully in exchange server 2013.
After that mails are struck in drafts folder.
I thought because of My Custom transport Agent , then i Uninstall Transport agent.
but still no use.
I restart Microsoft Exchange Transport Service and restart my server also.
Here is the code i used
public sealed class MyAgentFactory : RoutingAgentFactory
public override RoutingAgent CreateAgent(SmtpServer server)
return new MyAgent();
public class MyAgent : RoutingAgent
public MyAgent()
this.OnSubmittedMessage += new SubmittedMessageEventHandler(this.MySubmittedMessageHandler);
public void MySubmittedMessageHandler(SubmittedMessageEventSource source, QueuedMessageEventArgs e)
e.MailItem.Message.Subject = "This message passed through my agent: " + e.MailItem.Message.Subject;
I search in google about mails struck in drafts folder, all replies are
restore Default Receive Connectors. How can i restore it.
here is the link i see
http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts

Hi Martina
Miskovic,
Here I am facing some weird situation.
Mails again stuck in Drafts folder.
i didn't installed anything. just checking again after some
time gap .
I tried again by restarting all services
, but no use.

Exchange Server 2013 does not deliver mail as they arive.

I need Help and guidance on this problem. I have installed Exchange server 2013 with SP1 on Server 2012. Install Went perfect no error. It on a server with 2 TB storage. 16G
memory. Exchange 2013 is the only application running on the box. DNS service is also running on the box. I can see the mail arrive in the mail Box Queue with the Queue Viewer and they would just sit there and then after a 15 to 30 min delay it release the
mail to the mail boxes. The only error or warning I am seeing in the logs are the 6002 warning. Any suggestion would be greatly appreciated.

Please share message header of one of the delayed message. It will help to narrow down the issue.
Do you see any connection failures in connectivity logs.
Do you have multiple 2013 servers in your exchange environment ?
Lets fix it.
Received: from Xchngsvr.A.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Mailbox
Transport; Fri, 25 Apr 2014 13:31:33 -0400
Received: from Xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 25 Apr
2014 12:30:44 -0400
Received: from xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server id 15.0.847.32 via Frontend
Transport; Fri, 25 Apr 2014 12:30:37 -0400
Received: from mia0vm-cass03.colo.sonicwall.com ([208.17.117.5])
by
xchngsvr.a.com (SonicWALL 7.4.5.1391)
with ESMTP id 201404251630370000228;
Fri, 25 Apr 2014 12:30:38 -0400
Received: from mail1.fieldsolutions.com ([98.129.95.107])
by
mia0vm-cass03.colo.sonicwall.com (SonicWALL 7.4.4.8439)
with ESMTP id
201404251631070343409; Fri, 25 Apr 2014 09:31:07 -0700
Received: from localhost (localhost [127.0.0.1]) by mail1.fieldsolutions.com
(Postfix) with ESMTP id F32731031781
for <[email protected]>; Fri, 25 Apr 2014
11:31:06 -0500 (CDT)
MIME-Version: 1.0
To: <[email protected]>
From: Field Solutions <[email protected]>
Subject: WIN#: 649890 NEW Signage - Reply-To: <[email protected]>
Content-Type: multipart/alternative;
boundary="=_747eac72d0ea92652b25d7d469d7165b"
Message-ID: <[email protected]>
Date: Fri, 25 Apr 2014 11:31:06 -0500
X-Mlf-KeyWords: preapproved,dollars$$$,pay,toner,expectations,fl,dollars,guarantee,voltage,confi
X-Mlf-Language-Detected: NoLanguageFilter_English
X-Mlf-Connecting-IP: 50.244.134.141
X-Mlf-Country-Code: US
X-Mlf-Rules: rn;7.24
X-Mlf-Rules-Pos-Features: WORD_voltage_2.97;WORD_configuration_2.51;WORD_inputs_2.50;WORD_documentation_2.
X-Mlf-Rules-Neg-Features: WORD_preapproved_-1.85;SUBJ_dollars$$$_-1.74;SUBJ_pay_-1.56;WORD_toner_-1.53;WOR
X-Mlf-Sliderbars: N4,B4,S4,L4,Q4,G4,A4,I4
X-Mlf-Version: 7.4.4.8439
X-Mlf-Threat-History: nothreat
X-Mlf-Threat-Detailed-History: nothreat;none;none;none
X-Mlf-UniqueId-History: i201404251631070343409
X-Mlf-Connecting-IP: 208.17.117.5
X-Mlf-Country-Code: --
X-Mlf-Threat: nothreat
X-Mlf-Threat-Detailed: nothreat;none;none;cloud-nj
X-Mlf-UniqueId: i201404251630370000228
Return-Path: [email protected]
X-MS-Exchange-Organization-Network-Message-Id: 5ea15b9c-561d-4a2a-d03e-08d12ebad75d
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: Xchngsvr.a.com
X-MS-Exchange-Organization-AuthAs: Anonymous
There is only one Exchange server in the Organization

Blocking Spam Emails by subject name in Exchange Server 2013

Hello Guys,
I need to know how to block spams by subject from Exchange Server 2013's Anti-spam/message filter.
In general, I'm using Exchange's anti-spam agents and configured spam blocking by domain name.. but I need to filter unnecessary emails by subject name also.
So, if you know how to resolve this issue, please post here the real solution..
Thanks a lot,

Hi GMG,
Thank you for your question.
We could install Exchange 2013 edge server, then we could create item which block spam base on subject name in “Protection”, we could refer to the following link:
https://technet.microsoft.com/en-us/library/bb124701%28v=exchg.150%29.aspx
There is a another method, we could use transport rule to filter spam by subject name by the following link:
https://technet.microsoft.com/en-us/library/dd351127(v=exchg.150).aspx
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

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

Exchange Server 2013 Update from to CU3 to CU8 stuck, Exchange completely down

Hello,
We tried to update a Exchange 2013 server to CU8 because we needed support from Microsoft (certificate revoked, so OWA not working anymore) and they could only help us after updating to CU8 first. The problem is that the update got stuck and now Exchange
is not working at all anymore. Since it is a production enviroment and there is mail in all outboxes we do not want to turn back to a snapshot but solve the problem and continue the update. Any help is welcome because all mail is down now :-(
The error we received at the Exchange Server is:
C:\Users\administrator.DOMAINNAME\Downloads\Exchange-cu8>setup.exe /m:upgrade /In
stallWindowsComponents /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup
COMPLETED
Stopping Services COMPLETED
Language Files COMPLETED
Removing Exchange Files COMPLETED
Preparing Files
COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Mailbox role: Transport service FAILED
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Externe POP3 mailboxen". Receive connectors assigned to differen
t Transport roles on a single server must listen on unique local IP address & po
rt bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Default Frontend SERVER-EXCHANGE". Receive connectors assigned t
o different Transport roles on a single server must listen on unique local IP ad
dress & port bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Hello Gadget,
Please find the solution as follows
This error is concern about WMSVC certificate which was deleted, we could refer to the following steps:
1- Go to IIS Manager and select server certificate,
2- Select “Create Self-Signed Certificate”,
3- For Server 2012 in the Friendly Name Field type: WMSVC and select the personal (certificate Store),
4- Now go to ” Management Service”,
5- From SSL Certificate choose the newly create “WMSVC” Self-Signed Certificate,
6- Apply,
7- Now start service of “Web Management service”.
https://social.technet.microsoft.com/Forums/office/en-US/eac00dc2-6e43-45ae-939c-aad82a144908/cu8-install-fails?forum=exchangesvrgeneral
Exchange Queries

Exchange Server 2013 - Lab setup with internal emails only

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

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

Exchange server 2013 content filter rejecting all incoming messages as spam.

Hello All,
Today out of the blue our Exchange server 2013 install started rejecting any inbound message as spam. It first started with only one user not being able to receive any mail because of this anomaly and
then after 12 or so hours all users were getting their mail rejected.
I currently had the threshold set to 5 on external messages only. Internal is disabled.
I have tried setting the threshold to 8 and 9, and rebooted the server after restarting
all services just to make sure everything reset. Even dished out a IISRESET just in case. Whatever I tried still does not work.
The install is a stand alone server facing the outside world (no edge server) living
in a 2 domain controller environment with a share point farm thrown in (ESXI5.5 environment)
Everything works just fine and dandy if I disable the content filter all together. Not seeing anything in the application logs out of the ordinary. Everything was working great and the same settings I used on this server worked well for a totally different
server that runs just fine.
Any ideas?
fr0stsp1re

RunspaceId                            : 87157b62-a061-436b-8fb9-dab446be3473
Name                                  : ContentFilterConfig
RejectionResponse                     : Message rejected as spam by Content Filtering.
OutlookEmailPostmarkValidationEnabled : True
BypassedRecipients                    : {}
QuarantineMailbox                     :
SCLRejectThreshold                    : 6
SCLRejectEnabled                      : False
SCLDeleteThreshold                    : 9
SCLDeleteEnabled                      : False
SCLQuarantineThreshold                : 9
SCLQuarantineEnabled                  : False
BypassedSenders                       : {}
BypassedSenderDomains                 : {}
Enabled                               : False
ExternalMailEnabled                   : True
InternalMailEnabled                   : False
AdminDisplayName                      :
ExchangeVersion                       : 0.1 (8.0.535.0)
DistinguishedName                     : CN=ContentFilterConfig,CN=Message Hygiene,CN=Transport Settings,CN=Smith And
                                        Smith,CN=Microsoft
                                        Exchange,CN=Services,CN=Configuration,DC=XXXXXXXXXXX,DC=com
Identity                              : ContentFilterConfig
Guid                                  : 8f86e0b6-da37-42d3-b7cd-b9635b7db271
ObjectCategory                        : XXXXXXXXXXXXXXXXXXX/Configuration/Schema/ms-Exch-Message-Hygiene-Conten
                                        t-Filter-Config
ObjectClass                           : {top, msExchAgent, msExchMessageHygieneContentFilterConfig}
WhenChanged                           : 5/28/2014 12:15:21 PM
WhenCreated                           : 5/1/2014 4:17:55 PM
WhenChangedUTC                        : 5/28/2014 7:15:21 PM
WhenCreatedUTC                        : 5/1/2014 11:17:55 PM
OrganizationId                        :
OriginatingServer                     : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
IsValid                               : True
ObjectState                           : Unchanged
This is what it is set at now. Completely disabled. It worked fine for quite some time filtering out spam pretty nicely then one day everyone's mail was being rejected as spam by the content filtering agent. I know of someone else who also had this
issue except their box was running 2008R2 with EX2007. They too disabled the content filter as it was giving them too many problems with mail being rejected.
fr0stsp1re

Exchange Server 2013 - Mailflow - Transport Rules - Autoreply to External Email Addresses and Customizable Template

Similar Messages

Maybe you are looking for