ReleaseEngineering/OPSI: Difference between revisions

Jump to navigation Jump to search
Line 169: Line 169:
** Open regedit and browse to HKEY_LOCAL_MACHINE\SOFTWARE\opsi.org\pcptch
** Open regedit and browse to HKEY_LOCAL_MACHINE\SOFTWARE\opsi.org\pcptch
** "opsiServiceURL" key should point to XXX for production or "https://10.2.71.216:4447" for staging.
** "opsiServiceURL" key should point to XXX for production or "https://10.2.71.216:4447" for staging.
** If a change is needed remove any previous entry on the OPSI.jar manager for that specific master
 
** After that, I believe rebooting should be good enough (not verified - armenzg)
* Staging slaves (after re-imaging)
*** Further instructions are explained in [[ReferencePlatforms/Win32#Change_OPSI_server_.28staging_slaves_only.29|Win32#Change OPSI server]]
** change the opsiServiceURL to point to staging (explained above)
** In c:\program files\opsi.org\preloginloader\uninst run deinstall.cmd
*** the slave will reboot
** Remove the slave's entry on the OPSI.jar manager (you will notice that the slave hasn't synced up since it was taken down for re-imaging)
** disconnect the mapped drive for production opsi
** install OPSI from staging-opsi
*** Start Menu -> Run -> \\10.2.71.216
*** Use 'pcpatch' and the root password when prompted. (Use the geTxxxx password until {{bug|519989}} is solved)
*** Right click 'opt_pcbin' and select 'Mount as Network Drive'
*** Browse to z:\install\preloginloader
*** Double click 'opsi-prep.vbs' (you won't see anything happen)
*** Double click 'service-setup.cmd', hit a key when prompted
*** When prompted for a username and password use 'root' and the appropriate password (the current one unlike for "pcpatch")
*** Press any key (I assume it should have reboot after this but it didn't - armenzg)
 
[really? it didn't happen to me - armenzg] OPSI forces reboot on completion of install and then you can manage it through the opsi client.
 
NOTE: This instructions were build up from [[ReferencePlatforms/Win32#Change_OPSI_server_.28staging_slaves_only.29|this]] page.


* Check that the hostkeys on the master and the slave are the same
* Check that the hostkeys on the master and the slave are the same
Line 178: Line 195:
** TODO determine how to fix this case
** TODO determine how to fix this case


=== How to update the opt_pcbin drive mapping password ===
=== How to update the opt_pcbin drive mapping password - "pcpatch" ===


'''NOTE:''' this has never been tested.  
'''NOTE:''' this has never been tested.  
Confirmed users
3,990

edits

Navigation menu