NiInst32.EXE (Installer)
The following parameters are supported by the Installer:
Parameter |
Description |
---|---|
/Execute:MDSID:PolicyInstance. %PolicyInstanceID% |
Install single package. %PolicyInstanceID% denotes the Base ID of the policy instance that has been created during the assignment of the package. Whether or not the package will be installed on a client is determined by the compliance state of the policy instance:
|
/Silent |
No status dialog appears during installation |
/Login |
Useful in conjunction with /AI. Results in the repositories always being read even if the file date has not changed. Cached Conditions are also checked (see explanation below); the installation of new packages can, for example, mean that related packages must also be executed; this happens immediately. Repositories are read up to five times if Cached Conditions have changed following a package execution. The /AI /LOGIN parameters are automatically set if the Agent (started without parameters) starts the Installer. |
Explanation of Cached
Conditions:
The DSM Client stores all conditions that can change during a session
in the client registry:
DiskFree, ExistIcon, Exist,
FileDate, FileVersion,
IsFileInUse, IsSwPackageRevInstalled,
IsInstalled, IsInstalledEx,
RegKeyExists.
The following operating
modes are supported by the Installer:
Without any parameter the
Software Shop is started.
Operating Mode |
Description |
---|---|
/W |
Wait 5 seconds prior to executing the package (only in conjunction with /Execute) |
/Service |
Starts the Installer as Service Installer. The parameter is used if the DSM Runtime Service starts the Installer to execute the computer portion of packages before a user logs on. Supported parameter: /Login
Note: |
/AI |
Starts the Installer as AutoInstaller. Supported parameter: /Login. The /AI parameter is automatically set if the Agent (started without parameters) starts the Installer. If there are Cached Conditions on the managed computer, the Agent starts the Installer each time polling takes place in order to check the Cached Conditions, but otherwise only when the data of the repositories has changed. |
Explanation of Cached
Conditions:
The DSM Client stores all conditions that can change during a session
in the client registry:
DiskFree, ExistIcon, Exist,
FileDate, FileVersion,
IsFileInUse, IsSwPackageRevInstalled,
IsInstalled, IsInstalledEx,
RegKeyExists.