The server environment localization just means adding Czech (or other) locale to Debian configuration - as root run:
dpkg-reconfigure locales
and choose desired locale - in our case it was cs_CZ.UTF-8 UTF-8 and en_US.UTF-8 UTF-8
Then it is possible to chose one of the two available UTF-8 encoding.
We are running a few Evergreen installations and din't came across previously encountered errors until now - we use any characters in organizational unit names (e.g. Člověk v tísni, containing "č" and "ě") but we avoid using extended ASCII characters in organization unit policy code (just in case).
However, I guess the encoding problems described in this and related bugs might be bound to XUL client only. We are planning to test the issue again in detail after a new version of Evergreen is available and check if using the localized server environment is still necessary in "XUL client free" Evergreen version.
The server environment localization just means adding Czech (or other) locale to Debian configuration - as root run:
dpkg- reconfigure locales
and choose desired locale - in our case it was cs_CZ.UTF-8 UTF-8 and en_US.UTF-8 UTF-8
Then it is possible to chose one of the two available UTF-8 encoding.
We are running a few Evergreen installations and din't came across previously encountered errors until now - we use any characters in organizational unit names (e.g. Člověk v tísni, containing "č" and "ě") but we avoid using extended ASCII characters in organization unit policy code (just in case).
However, I guess the encoding problems described in this and related bugs might be bound to XUL client only. We are planning to test the issue again in detail after a new version of Evergreen is available and check if using the localized server environment is still necessary in "XUL client free" Evergreen version.