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
This script reconfigures the IIS log folder to use a different folder instead of the default C:\inetpub\logs folder.
Additionally the log settings can be adjusted as well. The script changes the default log file location and settings on a server level.
By default the settings are inherited by websites. If manual changes have been made on a webite level, not all settings will be inherited.
Change the IIS log file location to D:\IISLogs
.\Set-Webserver.ps1 -LogFolderPath D:\IISLogs
Change the IIS log period to an hourly period
.\Set-Webserver.ps1 -LogFilePeriod Hourly
Use the local time for filenames and log file rollover
.\Set-Webserver.ps1 -LocalTimeRollover $true
Additional credits go to Michel de Rooij, https://eightwone.com
Exchange and other MTAs use DSNs (Delivery Status Notifications) and NDRs (Non-Delivery Reports) to notify the sender or sending MTAs (Message Transfer Agents aka Mail Servers) about the various statuses of a given email message. In Exchange, those messages are generated primarily by the categorizer component of the transport service.
You can use the New-SystemMessage cmdlet to create new messages. These messages can even be localized and can contain Html tags for properly styled notifications.
From a system perspective, the various notifications used are named and fulfill a specific purpose.
Delivery Status Notification (DSN) A report describing the result of an attempt to deliver a message
Message Disposition Notification (MDN) A report describing the status of a message after it has been successfully delivered to a recipient. Examples: read notification (RN) or non-read notification (NRN) Defined by RFC 2298 and controlled by Disposition-Notification-To header
Non-Delivery Report (NDR) A report indicating to the message sender that the message could not be delivered to the intended recipients
Non-Read Notification (NRN) A report indicating that a message was deleted before it was read when a read receipt was requested
Out Of Office/Facility (OOF) A report indicating that the recipient will not respond to a new message OOF refers to the Microsoft original term „out of facility“
Read Notification (RN) A report indicating that a message was read
Recall Report (RR) A report indicating the status of a recall request for a specific recipient A recall request is used when a sender tries to recall a sent message by using Outlook
This post has first been published in my personal legacy blog here.
Add remote IP address ranges to an Exchange Server 2013/2016 receive connctor.
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 sub folder 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 Anyhwere 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 attriobutes 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 German language.