Step 1

In ASDM go to Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Customization/Localization > GUI Text and Messages.

Step 2

Click Add. The Add Language Localization Entry window displays.

Step 3

Click the Language drop-list and specify the language as English (en). The translation table for English displays in the list of languages in the pane.

Step 4

Click Edit to begin editing the messages.

The Edit Language Localization Entry window displays. The text between the quotes of msgid is the default English text displayed by the client and must not be changed. The msgstr string contains text that the client uses to replace the default text in msgid. Insert your own text between the quotes of the msgstr.

In the example below, we insert “Call your network administrator at 800-553-2447.”

Step 5

Click OK and then Apply to save your changes.

Step 1

Download the desired translation table from www.cisco.com.

Step 2

In ASDM go to Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Customization/Localization > GUI Text and Messages.

Step 3

Click Import. The Import Language Localization Entry window displays.

Step 4

Choose the appropriate Language from the drop-down list.

Step 5

Specify where the translation table will be imported from.

Step 6

Click Import Now. This translation table will be deployed to AnyConnect clients with this preferred language. Localization will be applied after AnyConnect restarts and connects.

Step 1

Download the Gettext utilities from http://www.gnu.org/software/gettext/ and install Gettext on a computer that you use for administration (not a remote user computer).

Step 2

Retrieve a copy of the AnyConnect message template AnyConnect.po on a computer with AnyConnect installed.

Step 3

Edit the AnyConnect.po file (use notepad.exe or any plain text editor) to change strings as desired.

Step 4

Run the Gettext message file compiler to create the .mo file from the .po file:

Step 5

Place a copy of the .mo file in the correct message template directory on the user’s computer.

Step 1

Export the latest AnyConnect Translation Template from Remote Access VPN > Language Localization > Templates. Export the template with the filename as AnyConnect.pot. This filename ensures that the msgmerge.exe program recognizes the file as a message catalog template.

Step 2

Merge the AnyConnect Template and Translation Table.

Step 3

Import the merged translation table to Remote Access VPN > Language Localization. Click Import, specify a language, and select AnyConnect as the Translation Domain. Specify the file to import as AnyConnect_merged.po.

Step 1

In ASDM go to Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Customization/Localization > Resources.

Step 2

Click Import. The Import AnyConnect Customization Objects window displays.

Step 3

Enter the name of the file to import.

Step 4

Select a platform and specify the file to import. Click Import Now. The file now appears in the list of objects.

Step 1

Write and test your scripts.

Step 2

Choose how to deploy the scripts:

• Use ASDM to import the script as a binary file to the Secure Firewall ASA.

  Go to Network (Client) Access > AnyConnect Customization/Localization > Script.

  If you use ASDM version 6.3 or later, the Secure Firewall ASA adds the prefix scripts_ and the prefix OnConnect or OnDisconnect to your filename to identify the file as a script. When the client connects, the security appliance downloads the script to the proper target directory on the remote computer, removes the scripts_ prefix and leaves the OnConnect or OnDisconnect prefix. For example, if you import the script myscript.bat, the script appears on the security appliance as scripts_OnConnect_myscript.bat. On the remote computer, the script appears as OnConnect_myscript.bat.

  If you use an ASDM version earlier than 6.3, you must import the scripts with the following prefixes:

  • scripts_OnConnect

  • scripts_OnDisconnect

    To ensure the scripts run reliably, configure all Secure Firewall ASAs to deploy the same scripts. If you modify or replace a script, use the same name as the previous version and assign the replacement script to all of the Secure Firewall ASAs that the users might connect to. When the user connects, the new script overwrites the one with the same name.

• Use an enterprise software deployment system to deploy scripts manually to the VPN endpoints.

  If you use this method, use the script filename prefixes below:

  • OnConnect

  • OnDisconnect

    Install the scripts in the following directory:

    Table 1. Required Script Locations

    OS	Directory
    Microsoft Windows	%ALLUSERSPROFILE%\Cisco\Cisco AnyConnect Secure Mobility Client\Script
    Linux (On Linux, assign execute permissions to the file for User, Group and Other.)	/opt/cisco/anyconnect
    macOS	/opt/cisco/anyconnect/script

Step 1

Open the VPN Profile Editor and choose Preferences (Part 2) from the navigation pane.

Step 2

Check Enable Scripting. The client launches scripts on connecting or disconnecting the VPN connection.

Step 3

Check User Controllable to let users enable or disable the running of On Connect and OnDisconnect scripts.

Step 4

Check Terminate Script On Next Event to enable the client to terminate a running script process if a transition to another scriptable event occurs. For example, the client terminates a running On Connect script if the VPN session ends and terminates a running OnDisconnect script if AnyConnect starts a new VPN session. On Microsoft Windows, the client also terminates any scripts that the On Connect or OnDisconnect script launched, and all their script descendents. On macOS and Linux, the client terminates only the On Connect or OnDisconnect script; it does not terminate child scripts.

Step 5

Check Enable Post SBL On Connect Script (enabled by default) to let the client launch the On Connect script (if present) if SBL establishes the VPN session.

Step 1

Make sure that the script has an OnConnect or OnDisconnect prefix name. Write, Test and Deploy Scripts shows the required scripts directory for each operating system.

Step 2

Try running the script from the command line. The client cannot run the script if it cannot run from the command line. If the script fails to run on the command line, make sure the application that runs the script is installed, and try rewriting the script on that operating system.

Step 3

Verify that there is only one OnConnect script and only one OnDisconnect script in the scripts directory on the VPN endpoint. If the client downloads an OnConnect script from the Secure Firewall ASA, then downloads a second OnConnect script with a different filename suffix for another Secure Firewall ASA, then the client might not run the script you intended to run. If the script path contains more than one OnConnect or OnDisconnect script, and you are using the Secure Firewall ASA to deploy scripts, then remove the contents of the scripts directory and re-establish a VPN session. If the script path contains more than one OnConnect or OnDisconnect script, and you are using the manual deployment method, then remove the unwanted scripts and re-establish a VPN session.

Step 4

If the operating system is Linux, make sure that the script file permissions are set to execute.

Step 5

Make sure that the client profile has scripting enabled.

Step 1

Obtain and prepare the translation table files used by your AnyConnect deployment.

1. From the AnyConnect Secure Mobility Client Software Download page on www.cisco.com, download and open the AnyConnect-translations-(date).zip file.

   This zip file contains *.po files for all language translations provided by Cisco.

2. (Optional) Locate any other translation table files (*.po files) that you have customized or created for your own environment.

3. Run the gettext message file compiler to create a *.mo file from each *.po file you are using:

   msgfmt -o AnyConnect.mo AnyConnect.po

Step 2

Assemble the translation table files used by your AnyConnect deployment.

1. Create a directory named l10n in a working area on your local computer.

2. Create a directory under l10n for each language you want to include whose name is the language code.

   For example fr-ch for French (Canadian).

3. Put each compiled translation table file that you want to include into the appropriately named directory.

   Do NOT put any *.po files in the compiled translation table. Only *.mo files should go into this file.

l10n\fr-ch\AnyConnect.mo
    \he\AnyConnect.mo
    \ja\AnyConnect.mo

Step 3

(Windows only) Obtain and prepare the language localization transform files used by your AnyConnect deployment.

1. From the AnyConnect Secure Mobility Client Software Download page on www.cisco.com, download and open the zip file containing the language localization transform files, which apply translations to the installer screens.

   The zip file is named anyconnect-win-(version)-webdeploy-k9-lang.zip .

   Note	The version of the language localization files must match the version of AnyConnect used in your environment. When upgrading to a new version of AnyConnect, you must also upgrade the language localization files used in the localization bundle to the same version.

   The zip file is named secureclient-win-(version)-webdeploy-k9-lang.zip .

   Note	The version of the language localization files must match the version of AnyConnect used in your environment. When upgrading to a new version of AnyConnect, you must also upgrade the language localization files used in the localization bundle to the same version.

2. Locate any language localization transform files that you have customized or created for your own environment.

Step 4

(Windows only) Assemble the language localization files used by your AnyConnect deployment.

1. Create a directory named mst in the same working area on your local computer.

2. Create a directory under mst for each language you want to include whose name is the language code.

   For example fr-ch for French (Canadian).

3. Put each language localization file that you want to include into the appropriately named directory.

l10n\fr-ch\AnyConnect.mo
    \he\AnyConnect.mo
    \ja\AnyConnect.mo
mst\fr-ch\AnyConnect_fr-ca.mst
   \he\AnyConnect_he.mst
   \ja\AnyConnect_ja.mst

Step 5

Zip up this directory structure using a standard compression utility into an appropriately named file, such as AnyConnect-Localization-Bundle-(release).zip, to create your AnyConnect Localization Bundle.

Step 1

Create the described directory structure in a working area of your local computer.

Step 2

Populate the resources directories with your custom AnyConnect GUI files for each platform. Verify files are all named appropriately and icons and logos are sized appropriately.

Step 3

Populate the binary directories with your custom help_AnyConnect.html file.

Step 4

Populate the binary directories with your VPN OnConnect and OnDisconnect scripts, and any additional scripts they call.

Step 5

Populate the transform directories with your platform specific installer transforms.

Step 6

Zip up this directory structure using a standard compression utility into an appropriately named file, such as AnyConnect-Customization-Bundle.zip , to create your AnyConnect Customization Bundle.