Issue:
After installing Exchange Server on a Chinese Traditional OS Language, when running Health Checker, you are unable to run against the server. This is caused by an encoding issue of the applicationHost.config file on the system. More information described in #2027.
Because of the failure, we were not able to get the Xml output of the data collected. Ended up updating the export logic to account for this scenario.
Reason:
We need to be able to collect the correct information from the server and properly display it if we are able to convert it.
Fix:
Use Get-Content -Raw -Encoding UTF8 when getting files off the system.
Resolved #2027
Resolved #2017
Validation:
Lab tested. Ran Remotely, against 2013/2016/2019 on both English and Chinese Traditional/Simplified languages (2019 only). Also ran with -BuildHtmlServersReport which works as well.
Issue: After installing Exchange Server on a Chinese Traditional OS Language, when running Health Checker, you are unable to run against the server. This is caused by an encoding issue of the
applicationHost.configfile on the system. More information described in #2027.Because of the failure, we were not able to get the Xml output of the data collected. Ended up updating the export logic to account for this scenario.
Reason: We need to be able to collect the correct information from the server and properly display it if we are able to convert it.
Fix: Use
Get-Content -Raw -Encoding UTF8when getting files off the system.Resolved #2027 Resolved #2017
Validation: Lab tested. Ran Remotely, against 2013/2016/2019 on both English and Chinese Traditional/Simplified languages (2019 only). Also ran with
-BuildHtmlServersReportwhich works as well.