Confirmed users
1,377
edits
ReferencePlatforms/Win32: Difference between revisions
Jump to navigation
Jump to search
→Installing OPSI on a slave that has been recloned
| Line 473: | Line 473: | ||
==== Installing OPSI on a slave that has been recloned ==== | ==== 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: | 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 on the correct OPSI Server (production-opsi.build or staging-opsi.build): | ||
# as root | # as root | ||
opsi-admin -d method deleteClient $hostname | opsi-admin -d method deleteClient $hostname | ||
Then check /etc/opsi/pckeys to make sure the slave was removed. | Then check /etc/opsi/pckeys to make sure the slave was removed. | ||
$hostname is what the hostname command would return on the slave with .uib.local appended, for example "win32-slave30.uib.local" | |||
==== Uninstall OPSI ==== | ==== Uninstall OPSI ==== | ||