Client Language

[Former Member]

Hi,

Is there anything that can be done to prevent the client language being changed when it is updated? I want it to remain as set by the user rather than reverting to the locale default.

Regards

[Former Member]

The only solution I could find to this was to edit the setup msi file in b1_shr, removing all lrf files other than the one I want.

I have taken the request for persistent settings to Ideas Place to hopefully have a cleaner solution one day.

[Johan_Hakkesteegt]

Hi,

Considering that on average any given installation shouldn't be updated more than once a year, and the average amount of clients per installation is maybe 5, is this really an issue ?

For larger installations with 10+ clients, you can look into running the B1 client with Microsoft's Remote Desktop service, which can be found in WIndows Server 2008. This solution would at least allow you to only change the language once.

Regards,

Johan

[Former Member]

Hi,

Thank you for responding.

I find having to log into 25 machines every 3-4 months as part of an upgrade a massive inconvenience - I have to wait for each update to finish before I start the next one as SAP rightly does not allow multiple logins. If it wasn't an issue, the introduction of the client agent (which is useless to us under these circumstances) wouldn't have come about.

A patch upgrade currently requires somebody who has the menu positions memorised in order to navigate to the correct setting despite everything being in Czech.

Switching a terminal server model when we have adequately provisioned workstations seems an unappealing alternative to finding a proper solution.

Regards

[Johan_Hakkesteegt]

Hi,

I am not talking about terminal server, but about Remote Desktop. The difference is that you only run certain applications of your choice (for example B1) directly on the server. Everything else happens on the normal workstations, just like before. So those workstations certainly are not going to waste, assuming that you run other software too.

When you run an application through Remote Desktop, all you do really is create a normal looking shortcut on each workstation's desktop (or where ever), so the user can't even tell that the application is not running locally.

Two other advantages:

• by the time you need to replace your workstations, you can make do with cheaper models (= good for your budget).
• a VPN scenario is very easy to set up, and again, once the connection has been made, the user simply clicks that same old trusted shortcut, and to them it looks like the application is running on their own machine.

Regards,

Johan