Installing a Branding Package Only

You can add or remove the contents of a Ivanti Secure Access Client branding package on a client machine by using jamCommand. The jamCommand program is part of every Ivanti Secure Access Client installation. On Windows endpoints, jamCommand is located in the 32-bit program files directory:

Program Files (x86)\Common Files\Ivanti\JamUI\jamCommand.exe

On OS X endpoints, jamCommand is located in the Applications folder:

/Applications/Ivanti\ Secure\ Access.app/Contents/Plugins/JamUI/./jamCommand

The jamCommand program must be run with administrator privileges.

To apply the customizations in PulseWin.PulseBranding (Windows) or PulseMac.PulseBranding (OS X):

1.Run the following command:

jamCommand -brand

To remove your customized Ivanti Secure Access Client user interface from the endpoint and allow Ivanti Secure Access Client to use default strings:

2.Run the following command:

jamCommand -unbrand

jamCommand Usage Notes:

•Running jamCommand with the -brand or -unbrand option causes Ivanti Secure Access Client to restart. Connections are maintained and should be active after the restart. A restart is required to allow Ivanti Secure Access Client to access the customized settings. If you will be rebooting the system manually, or if there is no logged in user, then you can use the -norestart option. To avoid a restart when you run jamCommand, use the following option:

jamCommand -norestart

•jamCommand reports its results using the following numeric error codes:

0 - Success.

1 - General branding error.

2 - Error deleting branding files. This error can also occur when you install new files because the first action -brand performs is to remove the old files.

3 - Error branding Ivanti Secure Access Client. The new branding files cannot be written.

•The Ivanti Secure Access Client version must be R5.0 or later. To verify your current version of Ivanti Secure Access Client, run jamCommand with no parameters. If the result (displayed in a window) shows the branding options (-brand, -unbrand, -norestart), then branding is supported.

The jamCommand errors are not written to the console. To see jamCommand errors, include a script that checks error codes. Additional error message information is written to the Ivanti Secure Access Client log files.