On October 26th ENow hosted the webinar "Deploy Exchange 2016 On-prem and Hybrid Webinar".
"Support for Office 365 is part of the Exchange 2016 DNA. Yet, traditional on-premises deployment still make up a large number of Exchange deployments worldwide. In this session, we will cover the various deployment options and take a peek into what it takes to install, configure and manage an Exchange 2016 on-premises or Exchange 2016 hybrid deployment."
The script published by the Exchange Team requires an update when run on a system that does not use the en-US locale as Culture.
When the script analyses the saved log file information, a DateTime error is beeing thrown:
Cannot convert value "21/05/2010" to type "System.DateTime"
Note Version 2.1 of the script published by the Exchange Team works without the fix.
See: http://blogs.technet.com/b/exchange/archive/2013/10/07/analyzing-exchange-transaction-log-generation-statistics.aspx
Additional credits go to Microsoft Exchange Team.
The script published by the Exchange Team (Analyzing Exchange Transaction Log Generation Statistics) requires an update when run on a system that does not use the en-US locale as Culture.
When the script analyses the saved log file information, a DateTime error is being thrown:
See the original blog post for examples: http://blogs.technet.com/b/exchange/archive/2013/10/07/analyzing-exchange-transaction-log-generation-statistics.aspx
The script utilizes the Get-UICulture cmdlet to fetch the culture settings required to have [DATETIME]::Parse() work as expected.
DateTime values are stored in the CSV file using the UICulture setting, but [DATETIME]::Parse() uses the local culture settings to parse values by default.
To check your settings in PowerShell use the following cmdlets: