opsi manual opsi version 4.0.2 - opsi Download - uib
opsi manual opsi version 4.0.2 - opsi Download - uib
opsi manual opsi version 4.0.2 - opsi Download - uib
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>opsi</strong> <strong>manual</strong> <strong>opsi</strong> <strong>version</strong> <strong>4.0.2</strong><br />
144 / 193<br />
(like you may do with the readVersionFromProfile command) and set a new stamp to the profile (like you may<br />
do with the saveVersionToProfile command). So you may just use this single command in a if statement.<br />
The new string list function getProductMap gives you a hash with all information about the installation states and<br />
report to the actual product. So you may see if this product is installed or was uninstalled.<br />
• Logging<br />
The logs of the userLoginScripts are written to<br />
c:\<strong>opsi</strong>.org\log\_login.log<br />
This log file will be transmitted to the server. At the server they will be stored at<br />
/var/log/<strong>opsi</strong>/userlogin/.log.<br />
This log file is handled in append mode. This means new logs will appended to a existing log file of this client. To<br />
avoid to large log files, the size of the log files are limited by the server to a maximal size of 5 MB.<br />
You may display these log files at the <strong>opsi</strong> management interface (<strong>opsi</strong>-configed) at the tab Log files in the sub tab<br />
userlogin.<br />
19.5 Examples of userLoginScripts<br />
We are starting with examples that are build in a way that they also may used in a domain login script.<br />
A very simple generic example:<br />
[Actions]<br />
requiredWinstVersion >= "4.11.3.2"<br />
Message "Example Profile Patch ...."<br />
Files_profile_copy<br />
Registry_currentuser_set<br />
Patches_profile_ini "%userprofiledir%\<strong>opsi</strong>-winst-test.ini"<br />
[Files_profile_copy]<br />
copy "%Scriptpath%\profiles\*.*" "%CurrentAppdataDir%\ACME"<br />
[Registry_currentuser_set]<br />
openkey [HKCU\Software\ACME]<br />
set "show_greeting_window" = "no"<br />
[Patches_profile_ini]<br />
add [secdummy] dummy1=add1<br />
A example for firefox configuration:<br />
[Actions]<br />
Message "Firefox Profile Patch ...."<br />
DefVar $akt_profile_ini$<br />
DefVar $rel_prefs_path$<br />
comment "check for existing profile ..."<br />
Set $akt_profile_ini$ = "%CurrentAppdataDir%\Mozilla\Firefox\profiles.ini"<br />
if FileExists($akt_profile_ini$)<br />
Set $rel_prefs_path$ = GetValueFromInifile($akt_profile_ini$,"Profile0","Path","")<br />
if FileExists("%CurrentAppdataDir%\Mozilla\Firefox\\"+$rel_prefs_path$)<br />
comment "We found the profile and will now patch it ....."<br />
endif<br />
else<br />
comment "no firefox profile found for user"<br />
endif