Terminal Server | Multi Country and Codepages

This blog is as much as informative and subject to change/discussion.

At one of my Dutch customers we are implementing two subsidiaries in Lithuania. These are simple offices that do accounting, sales and purchases with pretty much standard NAV which also the HQ does.

Since the LT localisation is not very exiting we decided to have them all in one database. I know this is not officially best practice from a technical and upgrade point of view, but as most of you know the advantages of having it in one system weigh more than the disadvantages.

The implementation goes very well as for training, setup etc. But today we ran into an unexpected issue. I think...

I already realised that we would run into the codepage issue as described in my blog.

http://dynamicsuser.net/blogs/mark_brummel/archive/2009/05/09/tip-5-multiple-country-databases-validate-codepage.aspx

I took this as a fact and disabled the flag, told the management and users what to expect. Everyone happy.

Until we went into the Terminal Server. We are running Terminal Server 2008 and for what we have found out (and I am not expert) we can only run TS in one codepage that is determined at startup. So we figured, what if we use the LT codepage? Would that effect Dutch users. Testing proved (we tought) that this would work as we don't have strange characters in NL and the LT ansi codepage has all dutch characters.

But then we got a call from order entry that tbe barcodes where not printing anymore. Investigation proved that the barcode font is also ANSI based and did not work on LT codepage.

Al and al I did not have a very good feeling about running NL on a LT codepage and we decided to create a new terminal server for the LT users since we have VMWare and a TS license is not that expensive.

Any feedback? Has anyone managed to setup TS with multiple codepages for different users?

Cheers