MVP - Most Valuable Professional

Just can't get enough of IT

This blog is about mostly anything in IT. But the primary focuses are Microsoft technologies like Exchange Server, Microsoft 365, Microsoft Teams, and Cloud Security.
Last updated: 2020-03-12 | NOTE: If you are still using v2.1 update to themost recent 


Exchange Server 2013 Exchange Server 2016 Description

This script deletes all Exchange and IIS logs older than X days from all Exchange 2013+ servers that are fetched using the Get-ExchangeServer cmdlet.

The Exchange log file location is read from the environment variable and used to build an administrative UNC path for file deletions.

Optionally, you can use the Active Directory configuration partition to determine the Exchange install path dynamically, if supported in your Active Directory environment.

  • It is assumed that the Exchange setup path is IDENTICAL across all Exchange servers, when not using the UseDynamicExchangePaths parameter
  • The IIS log file location is read from the local IIS Metabase of the LOCAL server where the script is executed and is used to build an administrative UNC path for IIS log file deletions
  • It is assumed that the IIS log file location is identical across all Exchange servers
  • Use IsEdge switch when running on an Exchange Server holding the EDGE role


# Delete Exchange and IIS log files older than 14 days 

.\Purge-LogFiles -DaysToKeep 14

# Delete Exchange and IIS log files older than 7 days with automatic discovery

.\Purge-LogFiles -DaysToKeep 7 -Auto

# Delete Exchange and IIS log files older than 7 days with automatic discovery and send email report

.\Purge-LogFiles -DaysToKeep 7 -Auto -SendMail -MailFrom -MailTo -MailServer

# Delete Exchange and IIS log files older than 14 days, but copy files to a central repository and compress the log files before final deletion

.\Purge-LogFiles -DaysToKeep 14 -RepositoryRootPath \\OTHERSERVER\OtherShare\LOGS -ArchiveMode CopyZipAndDelete

# Delete Exchange Server, IIS, and HTTPERR log files older than 7 days, and send an HTML email. Identify Exchange file paths using AD configuration objects.

.\Purge-LogFiles.ps1 -DaysToKeep 7 -SendMail -MailFrom -MailTo -MailServer -UseDynamicExchangePaths -IncludeHttpErr

Version History

  • 2.3 Option for HTTPERR added, Option for dynamic Exchange install paths added, Html formatting added, tested with Exchange Server 2019
  • 2.21 Issue #12 fixed
  • 2.2 Minor fixes, but no changes
  • 2.14 Issue #9 fixed | IsEdge parameter added
  • 2.13 Issue #7 fixed | SendMail switch query
  • 2.11 Issue #6 fixed | Missing Remove-Item cmdlet
  • 2.1 Logfile archiving and archive compressions added
  • 2.0 CopyFilesBeforeDelete implemented
  • 1.93 Minor chances to PowerShell hygiene
  • 1.92 Count issue fixed to run on Windows Server 2012
  • 1.91 Write DaysToKeep to log
  • 1.9 Global functions updated (write to event log)
  • 1.8 Support for global logging and other functions added
  • 1.6 Count Error fixed 1.7 Email report functionality added
  • 1.5 Sorting of server names added and Write-Host output changed
  • 1.4 Handling of IIS default location fixed
  • 1.3 Check if running in elevated mode added
  • 1.2 Auto/Manual configuration options added
  • 1.1 Variable fix and optional code added
  • 1.0 Initial community release



  • This PowerShell script requires the GlobalFunctions module, described here.
    When using PowerShell 5 or later you can simply use Install-Module GlobalFunctions to install the module to your system.
  • Windows Server 2012 R2 or newer
  • ActiveDirectory PowerShell module
  • Exchange 2013+ Management Shell




Additional Credits

Brian Reid, C7 Solutions,




Read More »

Exchange Server 2013 LogoUninstalling Exchange Server 2013 will fail if the PowerShell MachinePolicy or UserPolicy is set by GPO.

You will receive an error message referencing Microsoft KB article 981474, which refers primarily to Exchange Server 2010.

Screenshot showing the PowerShell Execution Policy Error


The following PowerShell command removes the GPO setting.

Set-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell -Name ExecutionPolicy –Value ""

After setting the ExecutionPolicy attribute to an empty string, Exchange Server 2013 can be uninstalled successfully.




Do you plan to deploy Exchange Server 2016 or do you plan to go hybrid with Office 365?
Check out the enterprise technology services provides by Granikos

Read More »
Last updated: 2016-11-28


The script sends a given number of test emails to a configured SMTP host for test purposes (primarily Exchange queues, transport agents, or anti-virus engines).

Do not forget to adjust script variables to suit your local Exchange infrastructure.



# Send 10 normal emails
.\Send-TestMail.ps1 -Normal -MessageCount 10

# Send an Eicar test email
.\Send-TestMail.ps1 -Eicar


Version History

  • 1.0, Initial community release







Read More »


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 website 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

Version History

  • 1.0, Initial community release
  • 1.1, PowerShell hygiene applied, some typo fixes



Script last updated: 2016-07-28


Additional Credits

Additional credits go to Michel de Rooij,





Read More »
On September 15, 2014
Last updated: 2020-03-01

Exchange Server 2013Exchange Server 2016Exchange Server 2019Exchange 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.


Report and receipt types (Exchange Version independent) used for notification

  • Delivery Receipt (DR)
    A report confirming that a message was delivered to its intended recipient
  • 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 blog here.



Read More »