Remoting and localized output from executables

Question

Hello all, I am in need of a bit of assistance.
We have client computers which have non-English Windows 7, and thus any executable that produce output produce non-English output. This is not a problem when using PowerShell locally, all localized output is displayed properly.
Problems arise when using PowerShell remoting, where output does not display non-English characters correctly. Examples of native executables which produce incorrect output: ipconfig, ping, wingmmt.
Host's output encoding:
IsSingleByte      : True
BodyName          : ibm850
EncodingName      : Western European (DOS)
HeaderName        : ibm850
WebName           : ibm850
WindowsCodePage   : 1252
IsBrowserDisplay  : False
IsBrowserSave     : False
IsMailNewsDisplay : False
IsMailNewsSave    : False
EncoderFallback   : System.Text.InternalEncoderBestFitFallback
DecoderFallback   : System.Text.InternalDecoderBestFitFallback
IsReadOnly        : True
CodePage          : 850
Remoting output encoding:
IsSingleByte      : True
BodyName          : iso-8859-1
EncodingName      : Western European (Windows)
HeaderName        : Windows-1252
WebName           : Windows-1252
WindowsCodePage   : 1252
IsBrowserDisplay  : True
IsBrowserSave     : True
IsMailNewsDisplay : True
IsMailNewsSave    : True
EncoderFallback   : System.Text.InternalEncoderBestFitFallback
DecoderFallback   : System.Text.InternalDecoderBestFitFallback
IsReadOnly        : True
CodePage          : 1252
Following command can be run to change console output encoding to UTF8:
[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
However, running this on remote session will result in "Exception setting "OutputEncoding": "The handle is invalid." Running this on host works, but has no effect on remote session.
Apparently $OutputEncoding only works for input, not output. But I tried to set it to UTF8 anyway, with no effect.
This problem does not affect PowerShell cmdlets, as Write-Host and Write-Output produce correct output even in remote session.
Previously host had PowerShell 3 and client had PowerShell 2, now both have PowerShell 4 and problem still persists.
Anyone know how I can receive correct output from localized native executables? Thanks in advance.

Answer 1

Actually I am using PS remoting from server to client workstations.
I have provided several examples of commands that produce incorrect characters in place of non-English characters in the first post. Likewise I have provided encoding info in the first post.
As for culture info, info below.
Get-Culture on host:
LCID             Name             DisplayName
1035             fi-FI            Finnish (Finland)
Get-Culture in remote session:
LCID             Name             DisplayName
1035             fi-FI            Finnish (Finland)
Get-Culture locally on client:
LCID             Name             DisplayName
1035             fi-FI            Finnish (Finland)