In Triofox, admins can brand the windows client. There are two types of windows client branding.
. brand icons and language
As an admin, in windows client branding, specify the Application Icon, Drive Icon, and UI Language, click 'SAVE SETTINGS'.
Here, the application and drive icon has to be valid .ico files. Should not use other types of image files and rename it to .ico suffix.
The branding will not touch the installation package. When downloading a windows client from the web portal, it will still use the default white labeled package in Triofox. After the client is installed, it reads the branding icons/language configuration from the Triofox server and uses them in the windows client display.
. the deep brand with manufacture name, support info, and EULA
Admin can brand the windows client with its own EULA and manufacture name. In windows client branding, specify the Manufacturer's name, the support email, and the EULA. Here, the EULA has to be in RTF format.
When brand this way, Triofox will expand the installation package and replace the files inside. Then re-build the installation package. The process will break the codesign in the original installation package. Thus need to specify the admin's own code sign certificate and password. The branding will use the new codesign certificate to sign the EXE files in the package, and the package itself.
After specifying the information, click "Save settings and brand MSI" to brand the package. The process will also create windows client/server agent upgrade package, to use the branded files.
In the background, Triofox will create a temp folder under 'C:\Program Files (x86)\Triofox\portal\gcebranding'. The temp folder has a name like '228284953'. Inside the folder, the branding task will expand the installation package, replace files like EULA, sign the EXE files, then recreate the package and sign it.
After that, the final branded packages will be uploaded to a "43811DCD-8C5A-4EF9-B903-2EEA9CE88487\CSBranding" folder under the admin's home folder.
. When there is an issue with the process, the branding task may hit an error.
In a case like this, need to enable trace on the Triofox server, set up a dbgview, and retry the branding task. We can check the dbgview trace on what has failed. See the article here on Capture trace on Triofox via debugview.
Most of the time the issue is related to the co-design process. The dbgview may show errors like:
00000838 23.48246384  [csb][e]Sign Fail, cmd like below
00000839 23.48746109  [csb][e]sign /t http://timestamp.comodoca.com/authenticode /f "C:\Program Files (x86)\Triofox\portal\gcebranding\23449562\sign.pfx" /p "signpwd" /d "Brand Client Drive" "C:\Program Files (x86)\Triofox\portal\gcebranding\23449562\UpgradePackage\WindowsPkg\ClientShell.exe"
Here, need to RDP to the Triofox server and open a command prompt. In the command prompt, go to 'C:\Program Files (x86)\Triofox\portal\gcebranding' and run signtool.exe with the parameters recorded in the dbgview trace.
signtool.exe sign /t http://timestamp.comodoca.com/authenticode /f "C:\Program Files (x86)\Triofox\portal\gcebranding\23449562\sign.pfx" /p "signpwd" /d "Brand Client Drive" "C:\Program Files (x86)\Triofox\portal\gcebranding\23449562\UpgradePackage\WindowsPkg\ClientShell.exe"
Check the output from the command line and fix the error.