How to deploy new software with OPSI (Part 2)
Create package from scratch
This number ome step is the number six from the previous part :
- Input of the opsi-winst script names for different actionsAt this step if you have a 32 or 64 or both you have to choose for example for setup : setup.ins, setup32.ins, setup64.ins, setup3264.ins. Follow the uninstall.ins script with the type of name.
Setup scriptis named
Uninstall scriptis named
Update-Scriptwill be used for minor changes on existing big installations. If this product is switched to the required action setup, then the update script will be automatically executed after the setup script.
Always-Scriptwill be executed at the beginning of every activity of opsi-client-agent (e.g. on every boot).
Once-Scripthas the resulting state
not_installed. It is a very special kind of script, and you should only use it if you really know what you are doing.
Custom-Scriptdoesn’t change the resulting state. It is a very special kind of script, and you should only use it if you really know what you are doing.
userLoginScriptis used to modify the user’s profile after the user logs into the system. It only works with the opsi extension User Profile Management, which is described at the User Profile Management chapter in the opsi-manual.
- Create product dependency : No/YesFor example our projectlibre OPSI product need java first, keepass need .NET, etc.
- A(nother) product property to create ? NoIn general not used for local product
- A new folder as been created in /home/opsiproducts.Go to CLIENT_DATA folder and download or copy the installation file and the logoCopy setup.ins, uninstall.ins, delsub.ins script from the opsi-template folder script where you have the script basis in your CLIENT_DATA folder
- Edit setup.ins and uninstall.ins file and change these line to fit with your product ; name, minimum space needed, path after install, name of the install file (“/S” mean silent install);$ProductId$ should be the name of the product in opsi
; therefore please: only lower letters, no umlauts,
; no white space use ‘-‘ as a seperatorSet $ProductId$ = “7zip”
Set $MinimumSpace$ = “140 MB”; the path were we find the product after the installationSet $InstallDir$ = “%ProgramFiles64Dir%\7zip”
Set $LicenseRequired$ = “false”[Winbatch_install]
“%ScriptPath%\7z1700-x64.exe” /SRename script name in each file as you named them in the step 6.
- Go to the root folder of your product, create the .opsi file for installation then install it :# /home/opsiproducts/7zip/# opsi-makeproductfile# opsi-package-manager -i 7zip_17.00-1.opsi
SERVER_DATA folder is automatically created after the product is used in OPSIReload the opsi conf editor, the new product is ready to be add for automatic installation