ReferencePlatforms/Win32: Difference between revisions

Jump to navigation Jump to search
Line 537: Line 537:
You also might need to uninstall and re-install opsi if the slave is connecting to production-opsi.
You also might need to uninstall and re-install opsi if the slave is connecting to production-opsi.


In c:\program files\opsi.org run deinstall.cmd, slave will reboot then disconnect the mapped drive for production opsi, then do this:
In c:\program files\opsi.org\preloginloader\uninst run deinstall.cmd, slave will reboot then disconnect the mapped drive for production opsi, then do this:


    *  Start Menu -> Run -> \\10.2.71.216
*  Start Menu -> Run -> \\10.2.71.216
    * Use 'pcpatch' and the root password when prompted.
* Use 'pcpatch' and the root password when prompted.
    * Right click 'opt_pcbin' and select 'Mount as Network Drive'
* Right click 'opt_pcbin' and select 'Mount as Network Drive'
    * Browse to z:\install\preloginloader
* Browse to z:\install\preloginloader
    * Double click 'opsi-prep.vbs'
* Double click 'opsi-prep.vbs'
    * Double click 'service-setup.cmd', hit a key when prompted
* Double click 'service-setup.cmd', hit a key when prompted
    * When prompted for a username and password use 'root' and the appropriate password.
* When prompted for a username and password use 'root' and the appropriate password.
 
OPSI forces reboot on completion of install and then you can manage it through the opsi client.


=== Set Buildbot to install ===
=== Set Buildbot to install ===
977

edits

Navigation menu