forum.opsi.org

We're having two issues with 3.4-27, currently. On Windows Server 2003 the following happens * loginblocker does not work, the machines in question perform their automatic login while OPSI is working * possibly related to that, some of our startup processes do not happen correctly while OPSI is inst...

I'm not sure exactly what version I need, I don't know which one was working. Is there a full archive anywhere? Also, is there a ChangeLog specific to preloginloader? It would be helpful to know the differences between the versions in figuring out which one I need.

We're having issues with the current stable version of the preloginloader package and I'm hoping to find older versions somewhere. Is there an archive?

Hi, I've noticed that when OPSI encounters an error when trying to contact the server (eg, 403 unauthorized), my automatic login does not succeed. The system hangs at the OPSI screen until the screen saver starts. Then, once the mouse is moved to deactivate the screen saver the automatic login succe...

I was finally able to get a verbose log from a stuck slave. Here it is: http://people.mozilla.org/~bhearsum/mis ... entd.log.2

This machine required a hard reboot before it was usable again.

Hi again,

We ended up downgrading to preloginloader 3.4-27 across all of our machines. Unfortunately, there was no time to properly test and debug 3.4-30.

Thank you all for your help in this matter.

Will opsiclientd mode work properly on Windows Server 2003 and Windows XP?

I don't have an opsiclientd.log on this machine. Here's what I do have: clientconnect: 10/28/2009 9:41:45 AM ============================ pcptch Version 3.9.3 ============================ 10/28/2009 9:41:47 AM starting pcptch 10/28/2009 9:41:54 AM ipconfig /all ::: 10/28/2009 9:41:54 AM ~ 10/28/2009...

I've got another question about version 3.4-30. Has it changed the way installations happen? I've noticed that there is no OPSI dialog on boot now, but products still get installed as requested. loginblockerstart is set to "on". Is this another bug with Windows 2003 and the preloginloader?

We recently upgraded to preloginloader version 3.4-30 to help with problems on our Vista machines. Now I'm noticing that deinstall.cmd doesn't work properly on Windows server 2003 - it errors out saying it's not supported.

Is this intentional?