Migrated Exchange 2013 server - blocking common emails like netflix and amazon?

We were using Exchange 2010 for years, and recently I upgraded to Exchange 2013 and signed up for Exchange Online Protection over the weekend (all at the same time, upgrade, migration, sign up for EOP, etc.). Some mail is making it through just fine,
while a lot of email is being blocked. EOP says the email was "delivered" but MessageTracking on our exchange box says Event ID: FAIL...
I'd like to know more about the FAIL ID... how do I find out what made it fail? I'm guessing it was a transport rule, but when I got to Mail Flow -> Rules - there is NOTHING there.
Running "Get-TransportAgent" returns these values:
I disabled the malware agent manually on my box since I'm using the EOP stuff now... how can I see or edit the rules that are in place if they do not show up as rules in the ECP?
It's big name companies like amazon, netflix, etc that are getting blocked... I can't see a reason why they would be blocked now on a migrated server and not on my old server... Can anyone provide some insight? I'd GREATLY appreciate it!

I would tend to agree with you that you don't need them.
http://www.msexchange.org/articles-tutorials/exchange-server-2013/security-message-hygiene/anti-spam-and-anti-malware-protection-exchange-2013-part1.html
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server

Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server. The command works if you issue directly from the server exchange shell.
I open the remote power shell to the exchange server 2013.
Issue the following commands and getting the following error.
$mailbox = Get-Mailbox -Identity testuser$mailbox.EmailAddresses -= "eum:50004;phone-context=telExt5digits.lync5.com"Then getting the following error:Method invocation failed because [System.Collections.ArrayList] doesn't contain a method named 'op_Subtraction'.
At line:1 char:27
+ $mailbox.EmailAddresses -= <<<< "eum:50004;phone-context=telExt5digits.lync5.com"
+ CategoryInfo : InvalidOperation: (op_Subtraction:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFoundHelp!

Now for an answer - your remote session doesn't have the same object you have on the server itself. Notice it says this is an array list, not a ProxyAddressCollection. If you need to work around this, you'll need to massage the addresses another
way that the system will accept. I'd try the following:
$NewAddresses = $mailboxEmailAddresses | ? { $_ -notlike "eum:50004;phone-context=telExt5digits.lync5.com" }
See what you get in the $NewAddresses variable when you do this.

Second Exchange 2013 server in remote site

Just finished migrating from 2007 to 2013 and decommissioned 2007. Exchange 2013 is running in site A with 350 mailboxes on it. However, almost half of those users reside in site B so the plan is to introduce a second Exchange 2013 server to
this site and migrating mailboxes to it. There already exists a DC & GC in both sites.
My question is, immediately after I introduce Exchange 2013 into site B with CAS & MBX role, client computers from that site will start to receive certificate errors. Will updating the SCP on the new exchange server to point to the SCP on the exchange
server in site A be enough to mitigate that problem? What other precautions will I need to take? Has anybody been down this road?

Hi
You can introduce the second exchange server in the remote site and also setup a DAG. If you are using the same name on your certificate like mail.domain.com then you can use the cert for your second server as well. You need to make sure you have autodiscover
records setup correctly.
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.

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.

External Mail Flow not coming into Exchange 2013 Server

We just finished migrating from Exchange 2007 to Exchange 2013 and when I disable a certain receive connector on Exchange 2007 we stop receiving external emails. I have reviewed all of the Exchange 2013 Receive Connectors and everything looks to be fine
but the server does not get mail flow. If anyone could assist with this issue that would be great.
Thanks,
Ryan

Hi,
According to your description, all your inbound mails cannot be received in your Exchange 2013 server after you disable a receive connector in your Exchange 2007 server. If I misunderstand your meaning, please feel free to let me know.
If yes, since your MX record has been configured properly for your Exchange 2013 server, we can begin with checking the A record for the Exchange 2013 server and confirm if all external mails cannot come in your organization. And we can depend on the following
troubleshooting to narrow down the mail flow issue:
1. Check the NDR information if there is NDR.
2. Check Telnet to test the mail flow:
http://technet.microsoft.com/en-us/library/bb123686(v=exchg.150).aspx
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Can't recover exchange 2013 server using recoverserver switch

CU5 crashed while installing on one of our 4 DAG members. I was able to coax it back to life with some manual steps and doing a repair of sp1, but was unable to get cu5 to install or to cleanly uninstall sp1 despite repeated tries.
Finally I decided to rebuild it and use recoverserver (after removing database copies and removing it from the DAG). I built a new server with the same name, reset the AD account, domain joined it, and then ran the /recoverserver switch. But
I get this error every time:
"Can't specify installation mode because no Exchange Server is installed on this machine. Install Exchange Server."

Hi,
As far as I know, to remove Exchange 2013 server, here are the additional steps except with removing objects through ADSIEdit:
1. Delete the Exchange Server installation folder: C:\Program Files\Microsoft\Exchange Server
2. Delete the Exchange Back End and Front End websites with the IIS-Manager.
3. Delete the container in AD Users and Computers:
DiscoverySearch Mailbox{GUID}
Exchange Online-ApplicationAccount
FederatedEmail.GUID
Migration.GUID
*SystemMailbox{GUID}
*HealthMailboxGUID
4. Delete the following registries:
the key “ExchangeServer” under: HKLM\Software\Microsoft
the keys “MSExchange*” under: HKLM\CurrentControlSet\Services
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

First Exchange 2013 server in 2010 Deployment - 2010 edge is routing SOME inbound mail to new server where it fails.

I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ). I have one 2010 edge server and one 2010 ht,cas,mailbox server. I have added a 2013 server and started working
on configuring virtual directories. This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.
My issue is the edge server is already passing inbound internet mail to the new 2013 server. I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox
users never receive.
Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?
And why is it delivering to a server with now mailboxes on it yet?
Thank you for any help
dean

Hello Dean,
I understand that the message tracking log indicates the email delivered to Exchange 2013 server. Please check the message tracking log on both Exchange 2013 server and Exchange 2010 server.
How about the result? Have you created new 2013 mailbox and tested if it works?
As for the send connector, actually an intra-org send connector will be involved for internal mail flow within an organization. So there is no need to create another send connector.
In addition, I’d like to share you an article about Edge Subscriptions:
Title:
Understanding Edge Subscriptions
Link:
http://technet.microsoft.com/en-us/library/aa997438(v=exchg.141).aspx
Regards,

Exchange 2013 server to new Exchange 2013 server

Hello,
We have a Exchange 2013 server that is hosted outside the company and would like to move the server in house.
To do this we plan on standing up our own Exchange 2013 server and move the mailboxes and such over to the new server. My question is there any kind of documentation with steps to take to make sure nothing is left behind\missed?
THank you.
Tom

Hi Tom,
Its two different organization and you need to follow cross forest migration to migrate mailbox from one organization to another. Below links has the details steps to perform cross forest migration for exchange 2010 and you could follow the same step for
Exchange 2013 as well.
http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
http://blogs.technet.com/b/meamcs/archive/2011/10/25/exchange-2010-cross-forest-migration-step-by-step-guide-part-ii.aspx
http://blogs.technet.com/b/meamcs/archive/2011/10/25/exchange-2010-cross-forest-migration-step-by-step-guide-part-iii.aspx
Alternatively, you could also use some third party tool like Exchange Server Manager to perform this task much easier
http://www.lepide.com/exchange-manager/
Regards,
Krishna
http://smtpport25.wordpress.com

Replace Exchange 2013 Server

Hi All,
Hopefully this is somewhat of an easy process.
I have a single Exchange 2013 server running on Windows Server 2012 R2. The server itself is a decent server; however, it was built with a poor design to it so we keep running out of resources.
I now have a newer system and I'd like to replace our current Exchange Server with this one. I've tried searching the web and the only results I seem to find is upgrading/migrating from an older version of Exchange.
How easy would this be to just replace hardware?

Couple of options:
- You can stand up a new 2013 server, move mailboxes.
- You could create a DAG, add 2nd server, seed DB's, make DB's active on new server, remove DB's from first server, decommission first server.
Mike
NOTICE: 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 2013 issues - (new send email Stuck in Drafts not send)

Exchange 2013 issues - (new send email Stuck in Drafts folder not send)

I am also having this issue.
server 2012 VM with exchange 2013. plenty of resources, more than recommended so cannot be a BAck Pressure issue especially as no clients are connected yet.
In the early stages of setup and testing, mail sent to other mailboxes worked fine in outlook 2007 and OWA but after a few issue that developed and are now resolved, any e-mail send within outlook or OWA just goes straight into the drafts folder.
I tried, DNS setting changes under roles, on the server, on DNS server, MX DNS records, increased resources, looked at received connectors, changed and even deleted send connectors as this is not required for internal mail. Tried changing authentication
types but then outlook won't connect to, staying with Basic Auth.
Have not been able to test inbound e-mail as this is going to replace a production server and is not ready, although I could probably simulate a route from another server and push e-mail to it. Will try tomorrow.
I have spent about 20 hours trying to figure this out and made probably 40 changes. Change, test, rollback etc. Been searching through loads of forums and technet sites all with no help.
All services are started, server has been rebooted several times.
It is also an AD server and has both Exchange roles installed. There is no reason why it should not work. This is so frustrating, we don't have these issues with the now end of life Scalix, or MDaemon or Zimbra. Pity the client wanted a Microsoft solution.
To be honest there are not a lot of things that cannot be changed in ECP although there is more under exchange powershell however I am not familiar with all the commands yet. I have resorted to watching training videos even though I am a seasoned IT Pro, although
not so much with exchange it seems.
I have seen many people have this issue on Exchange 2007, 2010 and 2013. Someone must know how to resolve this or find a work around?
So far I have an expensive solution the client has purchased that I cannot get running properly.
Aside from this issue, I really like the new Server 2012 and new Hyper-V.
I was about to install Exchange Server 2013 on a physical machine due to this f#ckin' issue. But a post for the DNS change has saved my life:
http://social.technet.microsoft.com/Forums/en-US/exchangeserverpreview/thread/04c0147b-f4e3-4041-a566-310854e71068/ (rafael9908's answer)
And thanks Jesper Bernle for excellent info provided by your link.

Exchange 2013 Server ECP Not Loading

Running Exchange 2013 (with all roles installed). I tried going to the ECP via https://servername.domain.com/ecp/
It keeps loading on and on forever (in a loop, never fully loads the page). Any help?
Running Windows Server 2012 DataCenter RTM with Exchange 2013
Thanks!

Hi,
Before we can go further, I'd like to confirm the following information and recommen the troubleshooting:
1. Is there only Exchange 2013 server in your environment? If there is other Exchange server, the proper URL is as following:https://CASServerFQDN/ecp?ExchClientVer=15
2. Please try to access the ECP URL with your CAS server IP address.
3. Check if there is any error about ECP in your IIS log.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2013 stops receiving external email after about 8 hours

Hello,
Just installed 2013 excahnge server 3 days ago. We noticed after the first night that we did not receive any external emails throughout the night. I could not find anything wrong with receive connectors. Telnet works internally when this
happens but NO access from public side testing with telnet. After I reboot the exchange server everything functions just fine and normal for about 8 hours until it happens again.
I dont know what to check or look for at this point. Very new to exchange 2013. Any kind of advice would be helpful at this time.
It is not a firewall issue. Same firewall and set of rules that we use for other/old mail servers. We only have 1 exchange server that has all roles.
Lead Pusher

OK... Did alot of testing and spent some time with Microsoft's support on the phone.
I believe there is actually two problems going on in this thread.
1. Exchange 2013 Admins that have changed the default receive connectors are experiencing a conflict on the scope settings. Make sure that none of the receive connectors are using the same ports, and that you have not modified the security settings in anyway
unless you really know what you are doing.
If you are unsure of what the settings should be after you have change them, the only suggestion I have right now, (as I have not taken the time to do screen shots or write down all the default settings) is to install Exchange 2013 on a virtual machine and
look at them, then change back the settings that do not match.
2. The Malware Agent has a flaw that is causing the the Microsoft Exchange Transport service to endlessly wait on the Malware Agent to process a message that it just can't handle. (Two reboots of the entire server may be needed to clear this, or sometimes
you can get away with restarting the Microsoft Exchange EdgeSync service.)
The Microsoft technician had me perform a sequence of steps that highlighted this. To see if this is infact your problem you can perform the following steps.
A) Once the Exchange server stops processing messages, figure out the rough time it stopped processing messages.
B) Open the event viewer.
C) Under "Windows Logs", right click "Application", select "Filter Current Log...", check "Warning" and "Error", then click "OK".
D) Scroll down the log to the rough time that your Exchange Server stopped processing messages. You are looking for a slew of errors about the same time from "MSExchange Extensibility" (1051), "MSExchange Transport" (9201), "MSExchange
Transport" (9201), "MSExchange Extensibility" (1056), "MSExchangeTransport" (10003), and "MSExchange Common" (4999).
It is the "MSExchangeTransport" (10003) that I believe is the real problem. The Microsoft technician agreed. He did not want to spectulate as to exactly what was going on, but it seems to me that since he had me disable the "Malware Agent"
for now, that it is indeed the problem.
E) So.... Open the Exchange Management Console and type "Disable-TransportAgent", followed by enter. It will prompt "Supply values for the following parameters:". Enter "Malware Agent", press enter again. Type "A",
for yes to all.
or
http://technet.microsoft.com/en-us/library/jj150526.aspx"
F) Go to run, enter "services.msc". On the window that opens, find "Micorosoft Exchange Transport" and restart it.
I know this is NOT a fix, but a work around that is less than desired as the Malware Agent is a filter to keep unwanted emails out. I highly recommend running some sort of 3rd party spam/Malware filter that has been fully tested to run with Exchange
2013 if you do this.
Microsoft is to contact me back once they can figure out why this is happening, and I believe in the end a patch for Exchange 2013 will be produce to correct the problem.
In the mean time.... don't waste your money on paying Micorosoft for support, as I have already done this.
For the individuals who say they are not experiencing trouble, I am going to go out on a limb here and say that either you have a 3rd party software program that is filtering the mail before it reaches the Malware Agent, you have disabled the Malware Agent,
or you are using another mail server to forward email to your Exchange 2013 server. With either of these cases you are much less likely to see this problem.
One last issue that a few people may be experiencing, is Exchange 2013, running on Server 2012 that is a VM. Several VM setups have a bug with the VM NIC management interface and Windows Server if you are using the same NIC for both. For example Xen
Server 5.6 and XEN XCP both have this bug. There is an patch for XEN Server 5.6, but so far nothing for Xen XCP.
I have spent many hours trying to figure my problems with Exchange 2013 and I will not swear that my entire post is correct, but I have gotten very much closer to a stable mail server after much work. If you feel that anything is incorrect, please reply
back and let me know why, so that we may all benifit.
P.S. Sorry for the mis-spellings and what not, I am very tired at the moment, and was forced to use explorer, because this site is not liking Chrome at the moment. (Will not let me login)

Built-in domain Administrator account not given full access to new Exchange 2013 server

I migrated from Exchange 2010 to 2013 over the weekend. I cannot log into the EAC with my domain administrator account I use to log into all my other servers. I also cannot run the clean-mailboxdatabase cmdlet logged in as this user. I
had no trouble moving mailboxes from the old server to the new server with this account though.
This account is a member of: Domain Admins, Enterprise Admins, Exchange Full Admin, Exchange Organization Admin, Organization Management, Schema Admins, Server Management.
I can log into the EAC with another admin account that has the same memberships as the Administrator account.
I tried giving the account the role of "Databases" as suggested by others to fix the clean-mailboxdatabase issue but that did not work for me either.
The Administrator mailbox has been moved to the new database on the Exchange 2013 server. The Exchange 2010 has been decommissioned and is turned off.

Hi,
Based on my research, to retrieves the mailbox statistics for the disconnected mailboxes for all mailbox databases in the organization, we can try the following command:
Get-MailboxDatabase | Get-MailboxStatistics -Filter 'DisconnectDate -ne $null'
http://technet.microsoft.com/en-us/library/bb124612(v=exchg.150).aspx
Additionally, The Identity parameter specifies the disconnected mailbox in the Exchange database and it can be display name instead of mailbox GUID.
http://technet.microsoft.com/en-us/library/jj863439(v=exchg.150).aspx
Hope it can help you.
Thanks,
Angela Shi
TechNet Community Support

Rethinking Exchange 2013 Server Setup

Hello, I'm currently rethinking my Exchange 2013 install, I have a network of 20 users and 2 servers, one is my domain controller/file server and the other is my Exchange 2013 server. I have setup the Exchange server as a member server and configured
all of the network and Exchange settings. Everything is working fine and I currently have the Client Access and Mailbox Server roles installed. I have all of the users and mailboxes working and mail is flowing. I have NIC1 configured for my internal
network and NIC2 disabled. Here is where I'm rethinking my setup and need some advice. With having one Exchange server should I install the Edge Transport Server role, I currently have Exchange 2013 SP1 CU7 installed. If the answer is yes how should
I go about re-configuring my settings for the server.
Thanks Ryan.

Giving you a definite answer is difficult, because the only disadvantage every extra layer of security has, is the extra cost. So I will just give you following quotes to help you decide, whether the Edge Transport role is a useful addition to your email
infrastructure.
Edge Transport servers minimize the attack surface by handling all Internet-facing mail flow, which provides SMTP (Simple Mail Transfer Protocol) relay and smart host services for your Exchange organization. Agents running on the Edge Transport server
provide additional layers of message protection and security. […] Because the Edge Transport server is installed in the perimeter network, it's never a member of your organization's internal Active Directory forest and doesn't have access to Active Directory
information.
(https://technet.microsoft.com/en-us/library/dn635117%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396)
We recommend that the Edge Transport role be installed in a perimeter network outside of your organization's internal Active Directory forest.
(https://technet.microsoft.com/en-us/library/bb124701%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396)

Migrated Exchange 2013 server - blocking common emails like netflix and amazon?

Similar Messages

Maybe you are looking for