Exchange 2013 / 2016 / 2019 Default Receive Connector Settings
Default Receive Connectors KB ID 0001314 Problem Out of the box, Exchange 2016 (&2013) has five receive connectors. Three for the frontend transport service and two for the mailbox transport service. Front End Transport Service: Does not alter, inspect, or queue mail. It is the first port of call for ALL mail coming into (and out of) the Exchange organisation. This service creates THREE receive connectors All are bound to 0.0.0.0...
Exchange 2016 / 2019 Adding a New Email Domain
KB ID 0001297 Problem On EE this morning someone asked this question and I realised I’ve never written it up. So If you want to add a new domain to an already working Exchange deployment how do you do it? Solution Firstly, you need to have purchased the new domain name, and have the DNS records setup properly for the new domain name. See the following article; Setting up the Correct DNS Records for your Web or Mail Server Add...
Exchange – Event ID 205 and Event ID 16025
KB ID 0001251 Problem At a client this week, they were having a LOT of mail flow problems. Looking at the queue viewer, I could see that all their mail was sat in queues waiting to go into their mails stores. There was a queue for each mail store, and the error on each was “451 4.4.0 DNS query failed Exchange Server error in message queue”. Looking in the Application log it was full of Event ID 205, and 16025 Errors...
Outlook – Constantly Prompts for a Password
KB ID 0001227 Problem I did an Exchange 2010 to 2016 Migration for a school this week. They are going to reimage all their PCs to Windows 10 and install Office 2016 over the summer holidays. But a few staff members were working over the holidays and needed their Win7/Outlook 2010 clients pointing to the new Exchange server. This I did (I simply created new mail profiles and let auto discover do its work). But then the Outlook clients...
Exchange 2016 (& 2013) Enable Circular Logging
KB ID 0001224 Problem Let’s be clear about this, the correct way to flush/clear the Exchange logs is to perform a backup of the mailbox database in question, with an ‘Exchange aware’ piece of backup software. This will clear down the logs properly. Why Do We Need Logs? Well I’m glad you asked, if there’s a problem, and we lose the database, we can ‘play’ the log files back into the database to...