userspace:howto_use_the_scripts_-_a_short_description
Differences
This shows you the differences between two versions of the page.
|
userspace:howto_use_the_scripts_-_a_short_description [2011/12/16 12:57] Thomas_H |
userspace:howto_use_the_scripts_-_a_short_description [2021/08/23 08:37] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Howto ====== | ||
| - | ===== ...use the listed scripts ===== | ||
| - | |||
| - | written by // | ||
| - | |||
| - | Welcome to the wiki, initiated by users using opsi very proudly and successful. If you want to use Opsi (**O**pen **P**C **S**erver **I**ntegration) be aware, that this system is - like many other servers - none "out of the box". So get rid of any illusion, that you simply install opsi and right after installing you can install every software and operating system. Some work has to be done before you can do this! And nevertheless there are very(!) good instructions and manuals for opsi it's your's to create the most contents and packages for future installations. | ||
| - | |||
| - | This wiki shall help to avoid much work to be done twice, because once a package is created successfully, | ||
| - | |||
| - | This Howto is mostly for the newbies, starting with opsi, trying out the features. With this little Howto they should have the first success by creating a package, without knowing the " | ||
| - | |||
| - | Of course: best is at last to get some training, you can get informations about training on opsi [[http:// | ||
| - | |||
| - | |||
| - | ==== Some words before beginning... ==== | ||
| - | |||
| - | * Read the manuals! We expect that you already have installed and configured your opsi-server on the manual named " | ||
| - | * The published scripts are tested and they all work | ||
| - | * If software is free, so you should find links above the scripts where to get it. If a software is free, and there is no link, so you can add it as a member of the [[http:// | ||
| - | * Commercial software has to be bought from the manufacturer and has not to be asked for in the [[http:// | ||
| - | * If a script don't work, so ask politely in the [[http:// | ||
| - | * If you need changes, so don't expect that others do this for you (except you pay UIB for doing this ;) ) Try it first for your own, and if it don't work ask the [[http:// | ||
| - | |||
| - | And of course I expect, that you know how to open a terminal, or using putty and how to copy and paste some text to a terminal, depending on the way you choose to create a new package. If you work on a Windows-Machine via remote on the opsi-server you might use putty, if you use a VM, you might copy and paste directly to the VM... however, I will not describe the way how to do all these things. I think, if you are going to use a remote installation server, you have to know the basics. | ||
| - | |||
| - | |||
| - | ==== The " | ||
| - | |||
| - | Sometimes in the description of the scripts you will find something like this: | ||
| - | |||
| - | Tree:\\ | ||
| - | < | ||
| - | TightVNC.jpg | ||
| - | TightVNC.reg | ||
| - | Tightvnc_win7.reg | ||
| - | delsub.ins | ||
| - | setup.ins | ||
| - | tightvnc_*version*-setup.exe | ||
| - | uninstall.ins | ||
| - | </ | ||
| - | |||
| - | This shows the tree, so you can see, where to place the files. It always show the content of the CLIENT_DATA folder. | ||
| - | |||
| - | |||
| - | ==== Using the scripts... ==== | ||
| - | |||
| - | For easily creating packages you better install 2 tools on the opsi-server: | ||
| - | |||
| - | * joe (an easy-to-use editor) | ||
| - | * wget (if not installed) | ||
| - | |||
| - | Me for myself created a folder named "/ | ||
| - | |||
| - | First follow the instructions on the manual " | ||
| - | Localboot means, the pc starts from it's own HDD. | ||
| - | |||
| - | After entering some informations on the product-information-screen you enter exactly the names " | ||
| - | We will not create any dependencies at this moment. | ||
| - | |||
| - | Dependencies are needed is a software needs another package before installed. For example: CDBurnerXP needs .NetFX installed. So you can define, that the package " | ||
| - | |||
| - | For VNC we also will not define any product-properties. | ||
| - | |||
| - | When done opsi-newprod we will have a new folder in / | ||
| - | |||
| - | In folder we will find three more other folders, named CLIENT_DATA, | ||
| - | |||
| - | <code winst> | ||
| - | --- vnc | ||
| - | | - CLIENT_DATA | ||
| - | | - OPSI | ||
| - | | |- control | ||
| - | | |- postinst | ||
| - | | |- preinst | ||
| - | | - SERVER_DATA | ||
| - | </ | ||
| - | |||
| - | Change now to the folder " | ||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | |||
| - | ==== Getting the setup-program ==== | ||
| - | |||
| - | First we need to download the setup-program, | ||
| - | Follow the link and watch for the self-installing package for Windows. Do a rightclick on the link and copy the URL of the file. | ||
| - | |||
| - | Do a | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | (Attention! The Version-Number 2.0.4 might have changed, when you read this HOWTO!) | ||
| - | |||
| - | so the setup-file is stored directly in the folder CLIENT_DATA. | ||
| - | |||
| - | Now we need the setup.ins, the uninstall.ins and the delsub.ins. To get them and to fill them with content do the following: | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | Now open in the wiki the page [[userspace: | ||
| - | Now find the line with a | ||
| - | <code winst> | ||
| - | Set $Inst_Prg$ | ||
| - | </ | ||
| - | and change it to the name of the setup-program you have downloaded before. | ||
| - | |||
| - | To save the file press < | ||
| - | |||
| - | Do the same with uninstall.ins and delsub.ins: | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | to avoid any errors during the automated installation also do a | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | and leave it empty. This file normally contains the registry-settings of TightVNC made after a test-installation on a client. It contains the password for the administrator. | ||
| - | |||
| - | |||
| - | ==== Where to get the bitmap? ==== | ||
| - | |||
| - | Try Google, searching for TightVNC and have a look in the pictures. If you find one you like so you can copy it and resize it to 160x160 pixel. Save it as TightVNC.jpg. | ||
| - | |||
| - | |||
| - | ==== Packing the package ==== | ||
| - | |||
| - | Well done. Now leave the folder CLIENT_DATA | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | and pack it by using opsi-makeproductfile. | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | The software will be packed now. This takes a lil bit of time depending on the amount of files and the size which have to be put into the package. | ||
| - | After packaging do a | ||
| - | |||
| - | < | ||
| - | minhas-tirith:/ | ||
| - | </ | ||
| - | |||
| - | to install the new created package. Do a reload on the localboot-products in the configed, if it's open during installing the new package, otherwise you will not see your new created package. | ||
| - | |||
| - | Now you can test it with an opsi-client. | ||
| - | |||
| - | Have fun! | ||
userspace/howto_use_the_scripts_-_a_short_description.txt ยท Last modified: 2021/08/23 08:37 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
