Use case: we are installing the RA agents using packages (company policy). The packages basically check a few things like availability of keystores and passwords, generate the response file based on a template with placeholders, run the installer and do a few configurations.
No big deal.
The problem is, when creating the actual response file based on the template file, and using default windows setup, the generated file format is:
Little-endian UTF-16 Unicode text, with CRLF, CR line terminators
With this format, the RA agent installer ignores the response file without any hint at what the problem could be. The request is, the RA agent installer on windows should accept a wider range of file formats, especially default file formats. The above listed format is the default format on our servers. When specifying -encoding ascii, the response file got accepted.