How does mst file chaining work with SafeGuard Easy unattended installations?

  • Artikel-ID: 107776
  • Aktualisiert: 29 Apr 2010

SafeGuard Easy multi-platform 4.5x

Client OS

Windows XP SP2 Professional Edition

Server OS



How does mst file chaining work with SafeGuard Easy unattended installations?


Please be aware of possible dependencies of several .mst files chained when installing Safeguard Easy unattendedly.

Example for install string:
msiexec /i C:\Software\Sgeasy.msi /L*vx C:\Software\easy.log CFGFILE=C:\Software\Install.cfg TRANSFORMS=C:\Software\sgeasy1.mst;C:\Software\sgeasy2.mst;...

It is possible, that some settings made in the transform file will be applied to the SafeGuard Easy installtion from the first .mst file in line and some from one of the following ones.

Each change in the respective .mst file will be checked against "default setting". The last modification from one of the transform files (latest in chain) will be applied.

Default setting: SERVERNAME=.OFFLINE

sgeasy1.mst: SERVERNAME=
sgeasy3.mst: SERVERNAME=.OFFLINE (default)

In this scenario the effective setting after the installation will be SERVERNAME=SERVER1.
Note: The last .mst file setting will be ignored, because it is the default setting again and will therefore not be set. So, the servername will not be set to default again, even if the last .mst file change in the chain is the default setting again.

keywords: sge

Wenn Sie weitere Informationen oder Unterstützung benötigen, wenden Sie sich bitte an den technischen Support.

Artikel bewerten

Ungenügend Hervorragend