In Centrestack, admins can brand windows client. There are two types of windows client branding.
. brand icons and language
As admin, in windows client branding, specify the Application Icon, Drive Icon and UI Language, click 'APPLY'.
Here, the application and drive icon have to be valid .ico files. Should not use other type of image files and rename it to .ico suffix.
The branding will not touch the installation package. When download windows client from web portal, it will still use the default white labeled package in Centrestack. After the client is installed, it reads the branding icons/language configuration from Centrestack server and use them in windows client display.
. deep brand with manufacture name, support info and EULA
Admin can brand the windows client with it's own EULA and manufacture name. In windows client branding, specify the Manufacture name, the support email and the EULA. Here, the EULA has to be in rtf format.
When brand this way, Centrestack will expand the installation package and replace the files inside. Then re-build the installation package. The process will break the code sign in the original installation package. Thus need to specify the admin's own code sign certificate and password. The branding will use the new code sign certificate to sign the exe files in the package, and the package itself.
After specify the information, click BRAND MSI to brand the package. The process will also create windows client/server agent upgrade package, to use the branded files.
On the background, Centrestack will create temp folder under 'C:\Program Files (x86)\Gladinet Cloud Enterprise\portal\gcebranding'. The temp folder has 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 43811DCD-8C5A-4EF9-B903-2EEA9CE88487\CSBranding folder under the admin's home folder.
. When there is any issue with process, the branding task may hit error.
In case like this, need to enable trace on Centrestack server, setup dbgview and retry the branding task. We can check the dbgview trace on what has failed. See the article here on how to collect trace on Centrestack server.
Most of the time the issue is related with the code sign process. The dbgview may show error 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)\Gladinet Cloud Enterprise\portal\gcebranding\228284953\sign.pfx" /p "signpwd" /d "Brand Client Drive" "C:\Program Files (x86)\Gladinet Cloud Enterprise\portal\gcebranding\228284953\UpgradePackage\WindowsPkg\CoDesktopClient.exe.exe"
Here, need to RDP to Centrestack server and open command prompt. In the command prompt, go to 'C:\Program Files (x86)\Gladinet Cloud Enterprise\portal\gcebranding' and run signtool.exe with the parameters recorded in the dbgview trace. For example:
signtool.exe sign /t http://timestamp.comodoca.com/authenticode /f "C:\Program Files (x86)\Gladinet Cloud Enterprise\portal\gcebranding\228284953\sign.pfx" /p "signpwd" /d "Brand Client Drive" "C:\Program Files (x86)\Gladinet Cloud Enterprise\portal\gcebranding\228284953\UpgradePackage\WindowsPkg\CoDesktopClient.exe.exe"
Check the output from the command line and fix the error.