@Sebastian-Roth : then don’t rush for me. What I can do for now is install the fog client and then copy the modules.dll that uses codepage 850. I have already created a script that does this. I will use this script to roll out the Fog client to all existing workplaces with psexec.

I was able to deploy an image on the following hardware:

Dell XPS 13 7390 (via an TP-Link UE300 USB ethernet adapter)
Dell Latitude 5300
Dell Latitude E5570

All with the following settings:

• UEFI mode
• Secure Boot: Off (can be switched to ‘on’ after imaging)
• Fog 1.5.7
• ipxe.efi kernel
• Disk mode: AHCI

@Sebastian-Roth : then don’t rush for me. What I can do for now is install the fog client and then copy the modules.dll that uses codepage 850. I have already created a script that does this. I will use this script to roll out the Fog client to all existing workplaces with psexec.

@Sebastian-Roth Our plan was to roll out the clients by the end of this week. Thursday or Friday.

@Sebastian-Roth We would be happy with that.

@Sebastian-Roth We tested the DLLs and both are working fine for us.
My gut feeling says that codepage 850 is better, as it has more readable characters in it.

Can you implement this in a new version of the client, so that we can roll out the client via the MSI installer?

Thanks. I’ll test and let you know.

Great, thanks!

Hi Sebastian,
The suggested option: Control Panel > Region > Administrative Tab > Copy Settings indeed makes the extraction of the snapin pack work.

Especially, setting the option “Copy Settings -> to Welcome screen and system accounts” works for us.

But, as we’re starting to deploy the fog client on a number of existing machines, that would mean that we have to manually do that on all machines. I will see if we can automate that, but can you look if you can build it into the client as you suggested? I’m happy to test.

Hi,

We are trying to deploy a snapin pack, but when the fog client tries to unzip the snapin pack, we get this error.
I have read this post: https://forums.fogproject.org/topic/11616/snapinpack-snapinclient-error-1-is-not-a-supported-code-page-parameter-name-codepage as it looks quite the same we have. Our envrionment:

• Fog project 1.5.7
• Fog client 0.11.16
• Windows 10 Pro version 1809 and newer
• Language: English (United States)
• Keyboard: US English

I have tried to zip the snapin pack with various zip tools: 7zip, Windows builtin zip tool, download a zip from Gitlab (linux), but all gives the same error:

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 03/09/2019 14:05 Client-Info Client Version: 0.11.16
 03/09/2019 14:05 Client-Info Client OS:      Windows
 03/09/2019 14:05 Client-Info Server Version: 1.5.7
 03/09/2019 14:05 Middleware::Response Success
 03/09/2019 14:05 SnapinClient Running snapin Onetrail MailSignature Install
 03/09/2019 14:05 Middleware::Communication Download: http://fog.onetrail.net/fog/service/snapins.file.php?mac=1C:39:47:2E:F8:9B|E0:94:67:A6:E1:37|E2:94:67:A6:E1:36|00:FF:1E:AA:B0:FA|00:FF:52:22:4A:DF|00:FF:C9:DC:0C:28|00:FF:62:19:D9:92|E0:94:67:A6:E1:36&taskid=38
 03/09/2019 14:05 SnapinClient C:\Program Files (x86)\FOG\tmp\mailsignature-master.zip
 03/09/2019 14:05 SnapinClient Processing SnapinPack mailsignature-master.zip
 03/09/2019 14:05 SnapinClient Extracting SnapinPack
 03/09/2019 14:05 SnapinClient ERROR: 1 is not a supported code page.
Parameter name: codepage
 03/09/2019 14:05 Middleware::Communication URL: http://fog.onetrail.net/fog/service/snapins.checkin.php?taskid=38&exitcode=-1&mac=1C:39:47:2E:F8:9B|E0:94:67:A6:E1:37|E2:94:67:A6:E1:36|00:FF:1E:AA:B0:FA|00:FF:52:22:4A:DF|00:FF:C9:DC:0C:28|00:FF:62:19:D9:92|E0:94:67:A6:E1:36&newService&json
------------------------------------------------------------------------------

What else can we try?
Thanks in advance!
/Jurgen.

Hi Sebastian,

Thanks for the answer.
This was indeed the root cause.
On our Linux servers we set the umask to 0027 instead of 0022.
That has the consequence that /opt/fog did not have access permissions for the apache user as the R and X for others missed. Maybe an improvement for the installer as the other directories under /opt/fog have their rights set explicitely by the installer?