Hi pdijkgraaf
I’m sorry this has caused an issue and alerts may have been missed for a period of time. It is due to a change in character encoding from SP20, I will request documentation is updated to list this change and list the known issue.
This issue only occurs where an existing Galaxy.csv file was created with a different character encoding, e.g. ANSI, then from SP20 SCOM output uses Unicode. If unicode characters are appended to the existing file, this results in the file containing invalid characters.
The hotfix resolves this situation by creating a new Galaxy.csv file if an existing one is found, to avoid appending unicode characters to an existing file the may have been created with a different character encoding set.
So, this hotfix essentially automates the workaround you have already implemented to detect the presence of any existing Galaxy.csv file and if so, ensure new Galaxy.csv is used from SP20 onwards.
Thanks,
Stuart