Editing Ivanti Secure Access Client Messages

Ivanti Secure Access Client message strings reside in the StringReference\PulseCombinedMessages_XX.txt file. Modified message strings must reside in the PulseBranding\BrandingMessageCatalog_XX.txt file. (XX indicates the language.)

The BrandingMessageCatalog files hold only the strings that you modify. The default strings in the installed resource files are used for all strings that you do not modify.

It is not always possible to set up the conditions that cause a particular message to appear in Ivanti Secure Access Client. Browsing the contents of BrandingMessageCatalog_XX.txt is the easiest way to identify the strings you might want to change.

You can use HTML tags within the BrandingMessageCatalog entries. For example, you can use <b> and </b> tags to make text appear in bold type. You can use <A href=> tags to include a link to other HTML text you want. Make sure that your link displays the text in a new window. For example:

Keep in mind that Ivanti Secure Access Client might not be connected to the Internet when the error occurs.

Each message includes a short description and a long description. The short description is shown as a title to the longer description. There are no limits to the number of characters that you can include as the long description. However, the long description must be on one line in the message catalog file. Use HTML <br> and </br> tags to insert line breaks when the message is displayed.

To modify a message:

1.Find the string that you want to modify.

Search PulseCombinedMessages_XX.txt for the string. In general, the resource ID indicates where the value is used.

2.Open PulseBranding\BrandingMessageCatalog_XX.txt with a text editor.

3.Copy the string that you want to edit from StringReference\PulseCombinedMessages_XX.txt to BrandingMessageCatalog_XX.txt. Be sure to copy/paste the entire entry. For example:

[1731] ;kMsgCommonCertTrustPulseAuthServerIdentityNotFoundShort-desc = Authentication server not trusted. Long-desc = Authentication server identity not found in client's "Trusted Server List". Contact your network administrator.

4.Modify the string in BrandingMessageCatalog_XX.txt. For example:

5.Edit that same resource ID in each of the language files that your organization supports.

The Ivanti Secure Access Client interface includes separate files for each of the 10 supported languages. If you make a change in the English file, you should make the same change for the other languages you support in your environment. If you do not do so, then the edited English version is always used.