How to brand Centrestack installation

Some vendors want to brand Centrestack installation themselves, to allow their customers to install the branded Centrestack.

1. To brand the web installer itself

. Download the branding tool from Gladinet 

http://gcbuild.gladinet.com/releases/branding/GladUpdateRes.exe

. Download the latest web installer from https://www.centrestack.com/p/download_gce.htm

. Run the branding:

GladUpdateRes.exe installEntGUIxxxx.exe s 131 "Install <your Centrestack cluster name> Package"
GladUpdateRes.exe installEntGUIxxxx.exe s 132 "<your Centrestack cluster name> Installation"
GladUpdateRes.exe installEntGUIxxxx.exe s 133 "Install <your Centrestack cluster name> Package"
GladUpdateRes.exe installEntGUIxxxx.exe s 138 "<your Centrestack cluster name>"
GladUpdateRes.exe installEntGUIxxxx.exe s 140 "<your company name>"
GladUpdateRes.exe installEntGUIxxxx.exe s 141 "<your Centrestack cluster name>"

Need to change installEntGUIxxxx.exe to the name of the web installer you downloaded.

Here, the Centrestack cluster name is product name you want to call your Centrestack cluster.

Please notice that when run GladUpdateRes.exe to update the web installer, it breaks the web installer's code sign. Can sign the updated web installer with your own code sign certificate.

2. By default, the installation/configuration uses 'Centrestack' as the product name. To use the branded product name during Centrestack configuration, you'll need to brand the installation package directly.

. Can download the installation zip file from https://s3.amazonaws.com/gladinetsupport/GCE/zip/buildxxxx.zip

Here, replace xxxx with the 4-digt build number. For example, 6751

. In the buildxxxx.zip, extract build\root\web.config and build\root\web.config.NoSSL

. Edit both files. Add line

<add key="Brand_ProductName" value="<Centrestack cluster name>" />

in AppSettings section. Make sure the line is inserted between

<appSettings file="branding.config">

and

</appSettings>

Replace the updated two files in buildxxxx.zip

. Store the branded installation zip file on your own web server.

. Update the web installer to point to the branded installation package via command:

GladUpdateRes.exe installEntGUIxxxx.exe s 129 "URL to the branded buildxxxx.zip"

For example, let's say you store the branded installation package at https:\\my.company.com\GCE\buildxxxx.zip. To point the installer to the branded package, run

GladUpdateRes.exe installEntGUIxxxx.exe s 129 "https:\\my.company.com\GCE\buildxxxx.zip"

The vendor can brand any pages in the installation package. Then host the branded installation zip directly and brand the web installer, to use the branded zip file.

3. use branded upgrade package

If the branded files exist on both installation zip and upgrade zip, can brand the upgrade zip too. 

. Download the latest upgrade zip file from https://www.centrestack.com/p/download_gce.htm

. Similar as the installation zip, replace any branded files in the upgrade zip and store it on your own web server.

. Run the command to brand the web installer, to use the new upgrade zip file.

GladUpdateRes.exe installEntGUIxxxx.exe s 143 "URL to the branded upgradexxxx.zip"

4. Notice for branding like this, need to do it for each release you want to use.