Exchange 2013 CU11

Leave a reply
Exchange 2013 CU11 was released on 12/10/2015.  CU11 does not contain any schema updates but may contain new RBAC definitions. Update: The current version of Exchange 2013 is CU12, released in May 2016.  For more information see this link. Remember, you can install Exchange 2013 from the CU Rollup itself, saving time (CU12 rollup links above). Noteworthy issues resolved in CU11: After applying CU8 you may experience a large IOPS write increase for FolderUpdateGroup on your Read more [...]

Exchange 2013 CU10

Leave a reply
Exchange 2013 CU10 was released September 15th.  Cumulative Update 10 or higher is required to co-exist with Exchange 2016.  CU10 does not require a schema update unless you were running a version of Exchange 2013 older than CU7. Warning: CU10 contains an issue introduced in CU8 where there is an increased IOPS write load that can cause mail delivery delays to the mailbox database.  I'd recommend skipping CU10 and installing CU11, CU12, or newer as this issue was fixed in CU11. For convenience, Read more [...]

Convert PEM certificate.cer and private.key to PKCS#12 (.pfx .p12)

Leave a reply
Issue: You need to create a composite .pfx certificate file package. Background and pre-requisites: The first steps in your journey should have been to create a certificate request, submit this request to a certificate authority (CA) like GoDaddy or Comodo, and finally download the completed certificate from the CA. The following steps assume you have successfully downloaded a certificate package from your certificate authority. The following example command shows what to do with all the files Read more [...]

Cisco IronPort ESA: Assign https certificate for quarantine and admin web pages

Leave a reply
One of the critical steps in utilizing a new third-party certificate on the Cisco IronPort ESA is to assign the certificate to the IP Interface so it is used in HTTPS communications.  This will enable the Cisco IronPort ESA to utilize your certificate for the administration and quarantine web pages.  Note: These steps assume you have already completed the steps to install an SSL cert on your Cisco IronPort ESA. Step 1) Click Network > IP Interfaces > Select Internal or desired interface Step Read more [...]

maximum number of connections per source (20) for connector has been reached

Leave a reply
Issue: You are having issues with inbound mail or receive the following error in the application event log: "maximum number of connections per source (20) for connector has been reached" Background: Your most likely to see this error on receive connectors that are receiving mail from your spam filtering solution.  This is because your spam filter likely sends large batches of messages in each SMTP conversation.  The receive connector getting mail from your spam filter is in theory receiving Read more [...]