Wednesday, October 10, 2018

Can't receive mail in a hybrid environment after you install a new certificate on the on-premises Exchange 2016 servers



We have established hybrid connection between O365 and on Premises Exchange 2016 CU9, everything has been working fine, until recently the mail flow between O365 and on premises Exchange 2016 stopped working. Here is what we have done recently, CU update from CU7 to CU9 at on premises Exchange 2016, switched Godaddy certificate with COMODO RSA Domain Validation Security Server CA. I opened support with O365 support, they didn't provide me much help. 


I went to O365 admin portal, mail flow, connectors, and outbound connector and do validation for the connector from O365 to on Premises Exchange 2016 server, and got the following error:


450 4.4.317 Cannot connect to remote server [Message=451 5.7.3 STARTTLS is required to send mail] [LastAttemptedServerName=mail.mydomain.com] [LastAttemptedIP=198.171.58.5:25] [BL2NAM02FT047.eop-nam02.prod.protection.outlook.com].
 



I did some community support search and find out a Microsoft KB that makes sense to me. here is the link


https://support.microsoft.com/en-us/help/2989382/can-t-receive-mail-in-a-hybrid-environment-after-you-install-a-new-cer


I checked our Default frontend transport receiveconnector, and found out the certificate was bound to our old Godaddy certification, so I followed Microsoft above link, 


  1. Run the following commands:
    Get-ReceiveConnector "ServerName\Default Frontend ReceiveConnector" | Set-ReceiveConnector -TlsCertificateName $null 
    Get-ReceiveConnector "ServerName\Default Frontend ReceiveConnector" | Set-ReceiveConnector -TlsDomainCapabilities $null 
  2. Rerun the Hybrid Configuration wizard to update the receive connector on the hybrid server with the certificate information.
  3. recheck the receiveconnector's TLS binding, it has updated with new certificate. 

After that 

Get-ReceiveConnector "ServerName\Default Frontend ReceiveConnector" |ft identity, TlsCertificateName, TlsDomainCapabilities
-TlsCertificateName
We found out the new certificate are updated on all Exchange 2016 receiveconnectors and right tls domain is bound on it. Bingo. All mail flow are starting working again. 


Thursday, May 31, 2018

Cannot Export to a PST File from Exchange 2013/2016 eDiscovery

When you are using Office 365 or Exchange 2013/2016 on premises. You are in the Exchange Admin Center and you want to export your eDiscovery search results to a PST file.  You select "Export to a PST file" option and got with the following error:

image

In order to successfully export your mailbox Search results to a PST file from Exchange Online eDiscovery you must use and configure the following:

1) Use IE 10 or newer.  If you are using IE 9, then you must also install the .NET Framework 4.5

2)  Add https://*.outlook.com to the Local Intranet Zone in Internet Explorer

3)  Ensure that the following URL's are listed in the Trusted sites Zone:
4) If you use Exchange 2013/2016 on premises, just login from one of your Exchange servers to do the export to make the things much easier :-) 
  • https://*.outlook.com
  • https://r4.res.outlook.com
  • https://*.res.outlook.com

This should make a successful export

Note: Microsoft eDiscovery is limited 100 mailboxes per search.

 


Thursday, March 15, 2018

very useful filtered netstat command by destination IP address or subnet



C:\Windows\system32>netstat -ano | findstr 10.103.*
  TCP    10.105.12.40:135        10.103.71.156:17118    ESTABLISHED     908
  TCP    10.105.12.40:135        10.103.71.157:1782     ESTABLISHED     908
  TCP    10.105.12.40:135        10.103.71.157:1786     ESTABLISHED     908
  TCP    10.105.12.40:135        10.103.71.219:40169    ESTABLISHED     908
  TCP    10.105.12.40:10457      10.103.71.219:443      ESTABLISHED     51032
  TCP    10.105.12.40:14080      10.103.71.159:443      ESTABLISHED     51032
  TCP    10.105.12.40:15345      10.103.71.159:443      ESTABLISHED     51032
  TCP    10.105.12.40:16241      10.103.71.219:443      ESTABLISHED     51032
  TCP    10.105.12.40:23522      10.103.71.159:443      ESTABLISHED     64528
  TCP    10.105.12.40:25290      10.103.71.159:443      ESTABLISHED     51032
  TCP    10.105.12.40:26783      10.103.71.156:17121    ESTABLISHED     7900
  TCP    10.105.12.40:26783      10.103.71.156:17122    ESTABLISHED     7900
  TCP    10.105.12.40:26783      10.103.71.157:1789     ESTABLISHED     7900
  TCP    10.105.12.40:26783      10.103.71.157:1797     ESTABLISHED     7900
  TCP    10.105.12.40:26783      10.103.71.219:40171    ESTABLISHED     7900
  TCP    10.105.12.40:28611      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:28645      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:28860      10.103.71.182:30435    ESTABLISHED     51032
  TCP    10.105.12.40:29710      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:29711      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:30505      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:30506      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:31217      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:31218      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:31945      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:32739      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:33411      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:34221      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:34883      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:34884      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:35620      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:37020      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:37597      10.103.71.182:30435    ESTABLISHED     51032
  TCP    10.105.12.40:37891      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:38098      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:38099      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:38892      10.103.71.157:25       ESTABLISHED     24292
  TCP    10.105.12.40:38939      10.103.71.159:443      ESTABLISHED     64528
  TCP    10.105.12.40:40820      10.103.71.156:25       ESTABLISHED     24292
  TCP    10.105.12.40:41330      10.103.71.156:25       ESTABLISHED     24292