ReferencePlatforms/Test/Vista: Difference between revisions

 
(3 intermediate revisions by the same user not shown)
Line 60: Line 60:


== Buildbot ==
== Buildbot ==
  cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -d buildbot mozilla/tools/buildbot
  cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -r BUILDBOT_0_7_6_BRANCH -d buildbot mozilla/tools/buildbot
  cd buildbot
  cd buildbot
  c:\python24\python setup.py build
  c:\python24\python setup.py build
Line 156: Line 156:
= Post-cloning Setup for Pool =
= Post-cloning Setup for Pool =
== OPSI Installation ==
== OPSI Installation ==
* Start Menu -> Right click 'Command Prompt', hit 'Run as Administrator'
* FOR STAGING SLAVES ONLY:
* Run the following in the command line:
** Open c:\users\mozqa\install-opsi.bat in Wordpad and change the IP address to 10.2.71.216
* For all slaves:
** Logon to the OPSI server (production-opsi or staging-opsi) and run the following:
opsi-admin -d method deleteClient $hostname.uib.local
** Start Menu -> Right click 'Command Prompt', hit 'Run as Administrator'
** Run the following in the command line:
  cd c:\users\mozqa
  cd c:\users\mozqa
  install-opsi.bat
  install-opsi.bat
You will be prompted twice for a username and password. The first time, use 'pcpatch' and the standard root password. The second time, use 'root' and the standard root password.
You will be prompted twice for a username and password. The first time, use 'pcpatch' and the standard root password. The second time, use 'root' and the standard root password. The console may freeze when or right before the password prompt appears. Simply type the password and hit enter to fix it.


Then,
Then,
Line 166: Line 171:
** Highlight the slave, go to Log Files, and then opsiconfd - look for errors in that log.
** Highlight the slave, go to Log Files, and then opsiconfd - look for errors in that log.


If the slave shows up in the OPSI client, and there's no errors in the opsiconfd log, you're done! If it doesn't, or there is errors, cry (and talk to bhearsum)
If the slave shows up in the OPSI client, and there's no errors in the opsiconfd log, you're done! If it doesn't, or there are errors, do the following and try again (or talk to bhearsum):
On the slave:
Run c:\program files\opsi.org\preloginloader\uninst\deinstall.cmd
On production-opsi:
opsi-admin -d method deleteClient $hostname.uib.local


== The rest ==
== The rest ==
canmove, Confirmed users
6,441

edits