ISP Client Installation Windows

UPDATE February 22nd, 2017:

started to update and finish this guide

This Installation Guide is a „pictured“ quick guide leading through all steps of the installation and configuration of the ISP Client software for Windows. We choose Windows 10 Enterprise 64Bit Edition as it is now the newest Windows available and most of our customers are allowed to obtain it (it is officially supported with the new TSM/ISP clients in version and newer). Nearly all steps are the same for the “pro” or “home” version and for older Windows versions. Perhaps some dialogs (e.g. pop-up windows) may differ. For this guide the ISP Client software in version was used, other versions may differ in detail, but are similar in general.

ISP 8.1 only supports windows in 64bit flavor,

for 32bit windows choose ISP 7.1.7!

The following chapters guide through the steps of the installation, each illustrated with a screen shot. Please click on the pictures to enlarge.

Summary on set up

For this guide a virtual machine was set up, it runs a bare Windows 10 Enterprise x86-64 (build 1607), fully patched and without any additonal software besides notepad++ (7.3.2).

The ISP client is actually the newest version (, the server runs TSM 7.1.3-100. TSM / ISP supports a difference of “1” in the major version of client and server, so this server supports as well TSM 6.3.X as ISP 8.1.X clients.

Parameters for the ISP configuration (notation according to the original IBM notation with mixed low- and upcase letters):

  • SErvername SM131 : Server SM131 as used for nearly all University Göttingen Users
  • NODEName wxtest : just a name for testing
  • TCPPort 2131 : Port at which the ISP server listens to incomming ISP connections
  • TCPServeraddress : FQDN of the ISP server
  • PASSWORDAccess GENERATE : store the password encrypted and do not ask for it everytime
  • LANGuage AMENG : switch language of CommandLineInterface (CLI) or GraphicalUserInterface (GUI) to AmericanEnglish

Obtaining the ISP Client software

The ISP Client software is available from a variety of ftp servers. The GWGD runs an own ftp mirror at

We suggest to take always the newest client version.

Installation of the TSM client software

  • Start the installation by clicking on the downloaded file “”

  • or chose “Run” in your browser:

  • ISP first extracts the files from the binary

  • Remember to delete these files after installation!
  • Then you must start the File Explorer (right click onto the windows icon) and …

  • … get to the “Downloads” folder with the extracted files in it

  • Double click on the ispinstall to start the installation

  • Ordinarily the UAC asks for confirmation, you have to admit to install the ISP client – no choice …

  • Chose the installation language (do not ask why the language of the window is german, it’s an English windows 10 running :-| ).
    Please DO chose “Englisch” because it’s the common ISP language and especially the translation of the error messages are mostly silly and not clear.

  • In many cases, some runtime libraries need to be installed. You have to accept Install otherwise ISP will not run.

  • After installing the runtime packages the TSM installation starts …

  • … with some configuration issues: When asked for the installation directory, you may accept the default

  • In most cases, the setup type Typical will be the best choice …

  • … as custom give the possibility to add features that won’t be need (in most cases).
    The normal (user) CLI is always included, while the admin CLI ist not necessary.

  • Next the installation is ready to go

  • Keep waiting …

  • … until finished

excurse: where to find ISP in the windows menue

  • right after installation, you will find ISP within Recently added

  • It's also located at IIBM Spectrum Protect

excurse: on language settings

As mentioned many times, the localization of TSM / ISP causes more confusion than it helps. Therefore we strongly suppose to set TSM/ISP to American English. Up to TSM 6.2 this was simpe to achieve, just do not install the language pack :-) With TSM/ISP 7 the language packs became part of the client, but using the LANGuage option the client could set up in english completly. Now with ISP 8 the option only affects the error messages, so it's necessary to use a more brutal way to switch the client: replace the language files and iwth the english ones.

the following commands entered in the windows administrative command line (run cmd.exe as Administrator) will do so:

# get to the folder
cd "\Program Files\Tivoli\TSM\baclient"
# remove old files
rmdir de_DE /S /Q
del dscdeu.txt
del dsc30deu.dll
del dsmc_deu.hlp
del fcmdeu.txt
# create new de_DE folder
mkdir de_DE
# copy en_US files to de_DE
copy en_US\* de_DE\
copy dscenu.txt dscdeu.txt
copy dsc30enu.txt dsc30deu.txt
copy dsmc_enu.hlp dsmc_deu.hlp
copy fcmenu.txt fcmdeu.txt

if your computer runs a different localized windows, just replacedeu or de_DE with your “wrong” language.

unfortunately this steps will be necessary every time you update the client :-(

initial basic configuration

There's no special configuration tool for ISP, it's done within the GUI client or using a text editor. If you prefer the GUI, the UAC asks again for your admission at the the first time:

Because the ISP client starts with the systems language we strongly suggest to do the basic configuration in the text file before you start the GUI, otherwise it maybe in german:

basic configuration (directly within the configuration file)

  • Open a texteditor, e.g. notepad or notepad++, even if you're already Administrator, right click and choose Run as Administrator – otherwise you cannot save your config file in TSM folder.

  • UAC asks another time for your admission ..

  • then you can enter the basic settings (see introduction above) as
    • SErvername – an unique identifier for the TSM server, we suggest to take the server's name
    • TCPServeraddress – the FQDN of the TSM-Server
    • TCPPort – the Port TSM is listening for the clients connections
    • NODENAME – Name of your client as it is registered at the TSM server
    • PASSWORDAccess GENERATE – this tells the client to store the password in the registry
    • LANGuage AMENG – sets american english as the language for CLI and GUI

  • save the file as dsm.opt

  • … at C:\Program Files\Tivoli\TSM\baclient\

  • make sure, it's an .opt file and no text file (.txt). Using notepad++ you have to change the type:

basic configurations in the graphical user interface (GUI)

* As mentioned before, you'll find ISP within Recently added right after installation

  • It's also located at IIBM Spectrum Protect

  • Every time you start the TSM client software you have to admit access rights:


  • At the first time start of TSM, it will look for the configuration file dsm.opt. If no such file can be found, the configuration wizard will be started:

further configuation (GUI)

volumes / shares to be backed up

excluding files and folders

setting up encryption

controlling the logging

... maybe something more ...

further configuation (config file)

volumes / shares to be backed up

excluding files and folders

setting up encryption

controlling the logging

... maybe something more ...

first backup (GUI)

first backup (CLI)

using the CLI the initial backup can be initiated easily, just type:

tsm> i

the ISP client starts to backup all configured DOMAINS using the incremental approach.

You can speed up the backup bypassing the all file tests using the -absolute option:

tsm> i -absolute

using the -absolute option forces the ISP client to backup all data (excepts those excluded by exclude rules) even if they are already stored on the ISP server. So do not use this option for regular backups, it will as well increase the backup time as the occupied capacity on the ISP server!


Excurse on "DSMCAD vs. DSMSCHED"

First, we have do make a descision: Should the backup service run the whole time or only if needed?

Because the TSM Schedule service (DSMSCHED) needs some memory, IBM invented a solution (called DSM Client Acceptor Daemon (DSMCAD)) to start it right at the moment when it's needed and save memory in the meanwhile. This was of great importance as memory was a rare ressource, a couple of years ago. Today the memory consumption vanishes if compared with other services running on a modern PC or server.

Therefore the question has to be asked differently:

Should only backup be done or is there a need to run a web based client on your PC / server?

Obviosly running a webserver for the web based client might be a critical security issue, so we strongly suggest not to configure the webclient. If you do not, there's no need to use the DSMCAD for starting the DSMSCHED.

using linux it's completely different: the most common approach for linux is to use the DSMCAD, therefore IBM provides a start / init script for the DSMCAD but just a few informations for starting the DSMSCHED without DSMCAD.

Detailed information you can find in the IBM documentation.

Configuring the DSMSCHED

Best configure the DSMSCHED using the GUI, manually or by using powershell it a mess.

Testing the scheduler configuration

A soon as the scheduler is started, it should ask the server for it's schedule to run the backup. Unfortunately the scheduler isn't reliable :-(

So it's better to run the request manually. The easiest way is done in the CLI by typing:

tsm> q sched

or in the windows cmd:

dsmc.exe q sched

This command should return all schedules associated with this node. Usually the scheduler daemon logs this request in it's log file. So please check the scheduler log for new entries according to the associated schedules looking like these: