Thomas Stensitzki is a leading technology consultant focusing on the Microsoft messaging and collaboration technologies and the owner of Granikos GmbH & Co. KG.
He is an MVP for Office Apps & Services since 2018.
Thomas is an MCT Regional Lead for Germany and delivers Microsoft Learning training courses for Office 365, Microsoft Teams, and Exchange Server.
He holds Master certifications as Microsoft Certified Solutions Master Messaging and as Microsoft Certified Master for Exchange Server 2010. These certifications make him a subject matter expert for any messaging topic related to Microsoft Exchange, Exchange Online, Microsoft 365, and hybrid configurations.
Follow Thomas: LinkedIn, Twitter
His sessions: https://sessionize.com/thomas-stensitzki
MVP Blog: https://blogs.msmvps.com/thomastechtalk Personal blog: http://justcantgetenough.granikos.eu Personal website: http://www.stensitzki.de Thomas' Tech Talk: youtube.com/ThomasStensitzki
Contact Thomas at thomas@mcsmemail.de
Add remote IP address ranges to an Exchange Server 2013/2016 receive connector.
Create a new text file containing the new remote IP address ranges
Example:
192.168.1.1 192.168.2.10-192.168.2.20 192.168.3.0/24
The script creates a new subfolder named ReceiveConnectorIpAddresses and saves the currently configured remote IP address ranges first.
While adding the new remote IP address ranges, the script checks, if the new ranges already exist.
# Add IP addresses from ip.txt to MYCONNECTOR .\Add-ReceiveConnectorIpAddress.ps1 -ConnectorName MYCONNECTOR -FileName D:\Scripts\ip.txt .\Add-ReceiveConnectorIpAddress.ps1 -ConnectorName REMOTECONNECTOR -FileName .\ip-new.txt -ViewEntireForest $true
When testing the Outlook Anywhere configuration using the Exchange Remote Connectivity Analyzers (ExRCA) you might encounter the following error message:
Autodiscover settings for Outlook Anywhere are being validated. ExRCA wasn't able to validate Outlook Anywhere Autodiscover settings. The AuthPackage wasn't specified in the EXPR section of the Autodiscover response.
If you encounter this error, you need to verify the following two attributes of the Outlook Provider configuration:
Remove any dedicated server configuration.
Get-OutlookProvider EXPR | Set-OutlookProvider -Server $null
Now the appropriate CAS FQDN will be used.
The CertPrincipalName attribute must match the common name (CN) of the SSL certificate. If a wildcard certificate is being used, it is required to configure the CertPrincipalName for the certificate
Set-OutlookProvider EXPR | Set-OutlookProvider -CertPrincipalName msstd:*.mcsmemail.de
This post had originally been posted at SF-Tools in the German language.