ReferencePlatforms/Win32: Difference between revisions

Jump to navigation Jump to search

ReferencePlatforms/Win32 (view source)

Revision as of 18:06, 10 December 2009

2,865 bytes removed ,  10 December 2009
→‎RelEng stuff
No edit summary
Line 494: Line 494:


== RelEng stuff ==
== RelEng stuff ==
=== OPSI Setup ===
OPSI must be reinstalled on all ref platform clones. For the purposes of the below instructions a staging slave is any machine that will be '''permanently''' in staging. Any other machines are production (regardless of the fact that they will be run in staging before moving to production).
All of the OPSI setup should be done as administrator.
==== Uninstall OPSI ====
You must uninstall the OPSI client so the new slave doesn't claim to be the reference platform. To do so, browse to ''' c:\program files\opsi.org\preloginloader and run 'deinstall.cmd' '''.
When running deinstall, you will see a warning that you should use deactivate instead of deinstall.  Ignore this.  There will also be a warning that the system will reboot, click yes for that.
If you're using a hostname that OPSI already knows about (eg, a slave that was recloned) you must remove it from the OPSI server before proceeding. To do so, do the following on the approriate OPSI Server (production-opsi.build or staging-opsi.build):
# as root
opsi-admin -d method deleteClient $hostname
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"
==== Firewall setup ====
'''For staging slaves only''' (the ref platform is already setup correctly for production slaves).
* Open firewall (only to opsi server)
** Control Panel -> Windows Firewall -> Exceptions
** Enable "File and Print Sharing", click "Edit"
** For each entry:
*** Click "Change Scope"
*** Select "Custom List"
*** Enter the IP address of the staging OPSI server (10.2.71.216).
==== The rest ====
(Applicable to staging and production).
* Security Settings
** Start Menu -> Run -> \\$ipOfOpsiServer (staging: \\10.2.71.216, production: 10.2.71.64)
** Use 'pcpatch' and the root password when prompted.
** Right click 'opt_pcbin' and select 'Map Network Drive'. Use the default mapping to Z:
** Browse to z:\install\preloginloader
** Double click 'opsi-prep.vbs'
** Double click 'service-setup.cmd', hit a key when prompted
** When prompted for a username and password use 'root' and the appropriate password.
Once OPSI is finished installing it will forcibly reboot the system. It will come up with an error on the first reboot. Do the following
* Logon to the slave with VNC
* Click the red 'X'
* Click the 'OK' button until the dialogs go away
OPSI will work fine on the next reboot. Before rebooting, update the state table for the slave with the [[ReleaseEngineering:OPSI#Definitions |OPSI client]] to match the state table for the win32 ref platform. Also:
* buildbot-production should be set to 'setup'
* passwordupdate should be set to 'always'
Now, reboot again. Once the reboot is done 'passwordupdate' should be 'installed' according the OPSI client.


== Setup Slave ==
== Setup Slave ==
Bhearsum
canmove, Confirmed users
6,441

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/188668"

Navigation menu