opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
19.4 New and extended opsi-winst functions
143 / 193
• Command line parameter /allloginscripts
If you are calling opsi-winst in the opsi service context with the additional parameter /allloginscripts this will lead
to the following actions:
– All products which have a userLoginScript will be detected. Only for these products will be the userLoginScripts
executed.
– The logged in user will be identified. All global constants to user specific directories like %CurrentAppdataDir%
will be directed to the directories of the logged-in user. Also the registry operations (Registry sections and
GetRegistryString) which going to HKCU will be executed in a way that they read or write to the current_user
hive of the logged-in user.
• Command line parameter /silent
The command line parameter /silent switches off the opsi-winst standard window in order to not disturb the
user.
• Function GetScriptMode
In order to detect if a script runs as userLoginScript or for example as installation script, the function
GetScriptMode gives you two possible values:
– Machine
The script is not executed as userLoginScript (but e.g. as setup or uninstall script).
– Login
The script is executed as userLoginScript.
• New primary section ProfileActions
This section may be used to the place for calling user profile manipulations. Here a syntax may be used, which
make it possible to use this section as a part of a installation script and as a userLoginScript as well. Therefore
this primary section will be interpreted in different ways according to the fact if it is called at Machine mode or at
Login mode (as userLoginScript):
– Login
If a script is running as userLoginScript and there is a section ProfileActions in the script, the script interpretation
will start at the ProfleActions section (and not at the Actions section, which will be ignored).
– Machine
If a script is running as normal istallation script, you may call the section ProfileActions as a sub section.
But in difference to a normal sub section it has some special rules: For every called Registry section the modifier
/AllNtUserDats is implicit set. gesetzt. For every called Files section the modifier /AllNtUserProfiles is implicit
set.
Since Version 4.11.3.2 : For every called Patches section the modifier /AllNtUserProfiles is implicit set.
• Registry sections
– Registry sections which should work on the HKCU or HKEY_CURRENT_USER hive in the openkey command,
will be executed in login script mode (Login) in a way, that all changes will be made in the registry hive of the
logged-in user. The same applies to the functions GetRegistryStringValue*.
– Registry sections which are called at the normal mode (Machine) with the modifier /AllNtUserDats, may now
contain HKCU resp.. HKEY_CURRENT_USER at the openkey command. This gives you the possibility to
use the same registry sections in both modes.
• Avoid unnecessary script execution:
With the new script command saveVersionToProfile you save product name, version and package version to the
logged-in users profile. These information can be retrieved by the new string function readVersionFromProfile,
so that you may see if this script was executed at this profile before. To make the handling easier there is also a
new Boolean function scriptWasExecutedBefore. This function checks if there is a version stamp in the profile