Vista support on the client side was only introduced freely in OPSI 4.4. We'll need to uprgade to it before we can roll out OPSI on the Talos slaves. This bug will track testing the upgrade in staging. OPSI 4.4 is currently in the Release Candidate phase - we should probably wait until the full release before upgrading production. https://forum.opsi.org/viewtopic.php?f=10&t=764&sid=6a6cc7df344d46e79469d524c5c03ac2 To start with, I've created a snapshot of the staging-opsi VM and will be upgrading it to 4.4.
Can we test this RC on the talos staging machines? We've still no idea if opsi causes any number variance which would prevent us from using opsi...
That's what I'm doing....
(In reply to comment #2) > OPSI 4.4 is currently in the Release Candidate phase - we should probably wait > until the full release before upgrading production. > https://forum.opsi.org/viewtopic.php?f=10&t=764&sid=6a6cc7df344d46e79469d524c5c03ac2 err... this link talks about opsi 3.4, not 4.4. Maybe you did a typo?
Summary: test upgrade to OPSI 4.4 on staging-opsi server → test upgrade to OPSI 3.4 on staging-opsi server
After some pain this seems to be working fine on a Vista slave - I still need to test upgrading an existing build slave to the latest preloginloader.
Upgrade notes: opsi upgrade: edit /etc/apt/sources.list aptitude update aptitude upgrade apt-get install opsi-depotserver download and install preloginloader,opsi-adminutils package from http://download.uib.de/opsi3.4/produkte/essential/
I installed the latest preloginloader (through OPSI!) on win32-slave21 and everything is fine so far. I've done a re-installation of MB1.4 with the new preloginloader and there were no issues. I'm going to do win32-slave03, win32-slave04, and the staging try slave (try-w32-slave05) too.
Status: NEW → ASSIGNED
(In reply to comment #7) > I installed the latest preloginloader (through OPSI!) on win32-slave21 and > everything is fine so far. I've done a re-installation of MB1.4 with the new > preloginloader and there were no issues. I'm going to do win32-slave03, > win32-slave04, and the staging try slave (try-w32-slave05) too. These are all upgraded now.
more upgrade notes: Had to download http://download.uib.de/opsi3.4/modules to /etc/opsi and change the 'license_management' option to 'no'
Summary: test upgrade to OPSI 3.4 on staging-opsi server → upgrade OPSI servers to 3.4
Here's complete upgrade instructions: * In /etc/apt/sources.list change this line: 'deb http://download.uib.de/debian etch opsi3.3' to 'deb http://download.uib.de/debian lenny opsi3.4'. Do NOT change any other lines to 'lenny'. * Run the following commands (you will have to confirm your actions for some of them): # upgrade the debian packages aptitude update aptitude upgrade aptitude install opsi-depotserver opsi-utils opsi-configed python-opsi opsiconfd # and the opsi packages wget http://download.uib.de/opsi3.4/produkte/essential/opsi-adminutils_3.4-5.opsi wget http://download.uib.de/opsi3.4/produkte/essential/opsi-adminutils_3.4-5.opsi.md5 wget http://download.uib.de/opsi3.4/produkte/essential/opsi-winst_184.108.40.206-2.opsi wget http://download.uib.de/opsi3.4/produkte/essential/opsi-winst_220.127.116.11-2.opsi.md5 wget http://download.uib.de/opsi3.4/produkte/essential/preloginloader_3.4-27.opsi wget http://download.uib.de/opsi3.4/produkte/essential/preloginloader_3.4-27.opsi.md5 opsi-package-manager -i opsi-adminutils_3.4-5.opsi opsi-winst_18.104.22.168-2.opsi preloginloader_3.4-27.opsi * Drop the modules file into /etc/opsi (currently located at staging-opsi.build:/etc/opsi/modules) * Edit /etc/opsi/backendManager.d/21_mysql.conf and set 'load' to 'False'. * Edit /etc/opsi/backendManager.d/30_vars.conf and set self.clientManagingBackend to '[ BACKEND_FILE31 ]' and remove the 'self.licenseBackend' line. * Restart opsiconfd: /etc/init.d/opsiconfd restart
(In reply to comment #10) > Here's complete upgrade instructions: > * In /etc/apt/sources.list change this line: 'deb http://download.uib.de/debian > etch opsi3.3' to 'deb http://download.uib.de/debian lenny opsi3.4'. Do NOT > change any other lines to 'lenny'. > * Run the following commands (you will have to confirm your actions for some of > them): > # upgrade the debian packages > aptitude update > aptitude upgrade cancel the upgrade part - we do NOT want to do that. I just finished doing the rest, though. I rebooted one of the production Windows slaves as a test and everything went well. We're done here.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.