ReleaseEngineering/OPSI: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 42: Line 42:


Once OPSI is finished installing it will forcibly reboot the system. In a few minutes it should come back up and the client should be listed in the OPSI GUI.
Once OPSI is finished installing it will forcibly reboot the system. In a few minutes it should come back up and the client should be listed in the OPSI GUI.
== Installing OPSI on a slave that has been recloned ==
If a slave with OPSI on it gets recloned the OPSI server will still have a reference to it. Before the client install can happen you must remove it from the OPSI server. To do so, do the following:
* Open /etc/opsi/pckeys and delete the line containing the hostname of the slave.
* Delete /var/lib/opsi/config/clients/$hostname
You may then proceed with the reinstall of OPSI.


=== Autoit ===
=== Autoit ===
Line 55: Line 48:
  cvs -d:ext:cltbld@cvs.mozilla.org:/mofo co ref-platforms/win32/autoit-v3-setup.exe
  cvs -d:ext:cltbld@cvs.mozilla.org:/mofo co ref-platforms/win32/autoit-v3-setup.exe
* (as Administrator), run the installer, accept the defaults
* (as Administrator), run the installer, accept the defaults
== Installing OPSI on a slave that has been recloned ==
If a slave with OPSI on it gets recloned the OPSI server will still have a reference to it. Before the client install can happen you must remove it from the OPSI server. To do so, do the following:
# as root
opsi-admin -d method deleteClient $slave
Then look at /etc/opsi/pckeys to make sure it was removed.
You may then proceed with the reinstall of OPSI.


== Installing a package on a client ==
== Installing a package on a client ==
canmove, Confirmed users
6,441

edits

Navigation menu