Unable to install preloginloader to win2k3

[cshields]

I've been playing around with OPSI and I love it. Works well with some XP clients, and now I am trying to install the preloginloader to an existing Windows 2003 install. Below is the output I get (output is scrubbed). Any ideas to what this problem may be are appreciated, I am having a hard time finding an answer in the docs or online. Thanks in advance!

[notice] Querying for ip address of host 'test'
[notice] Got ip address '10.2.71.187' from syscall
[notice] Pinging host 10.2.71.187 ...
[notice] Host 10.2.71.187 is up
[notice] Getting hardware ethernet address of host 'test'
[notice] Found hardware ethernet address '00:50:56:a5:3d:3a'
[notice] Creating client 'test'
[notice] Getting opsi-host-key for client 'test'
[notice] Getting network-config for client 'test'
[notice] Mounting client c$ share
[notice] Copying installation files
[notice] Patching config.ini file
[notice] Installing preloginloader
[error] ERROR: Failed to install preloginloader: Command './winexe --reinstall -U Administrator%passwordscrubbed //test "c:\opsi_Cpd1Lri2dK\files\opsi\utils\winst32.exe /batch c:\opsi_Cpd1Lri2dK\files\opsi\preloginloader.ins c:\tmp\preloginloader.log /PARAMETER REMOTEDEPLOY"' failed (256): ERROR: Cannot open control pipe - NT_STATUS_OBJECT_NAME_NOT_FOUND

[notice] Deleting host 'test' from dhcpd config file '/etc/dhcp3/dhcpd.conf'

[r.roeder]

Hi,

the crucial element in the opsi-deploy-preloginloader script ist the SAMBA winexe call:

[error] ERROR: Failed to install preloginloader: Command './winexe --reinstall -U Administrator%passwordscrubbed //test "c:\opsi_Cpd1Lri2dK\files\opsi\utils\winst32.exe /batch c:\opsi_Cpd1Lri2dK\files\opsi\preloginloader.ins c:\tmp\preloginloader.log /PARAMETER REMOTEDEPLOY"' failed (256): ERROR: Cannot open control pipe - NT_STATUS_OBJECT_NAME_NOT_FOUND

To get this work the user "Administrator" must be a local administrator of the target PC (or a domain user with local admin privileges), and there must be open C$ and Admin$ shares. You may test a winexe call with some trivial windows program call like notepad.exe.

The alternative if this approach does not work is to use the windows script service_setup.cmd from the target pc after mounting the network drive.

Hoping this helps,

Rupert

[cshields]

Yeah, I'm using the Administrator account and have the open C$ and admin$ shares. Interestingly though, I never see any leftover files in c:\tmp even though they claim to be copied successfully.

What I do get on the windows 2003 side is a message in the event viewer that coincides with the crash of winexe. It is an "application popup" message with the following description:

Application popup: winexesvc.exe - Application Error: The instruction at "0x77e01a91" referenced memory at "0x80a73308". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

Here is the debug info on the OPSI side when I try a simple winexe call:

IN: async_open(\pipe\ahexec, 2)
ERROR: smb_raw_open_recv - NT_STATUS_OBJECT_NAME_NOT_FOUND
ERROR: on_ctrl_pipe_error - NT_STATUS_OBJECT_NAME_NOT_FOUND
ERROR: StartService failed. NT_STATUS_IMAGE_ALREADY_LOADED.
ERROR: Failed to install service winexesvc - NT_STATUS_IMAGE_ALREADY_LOADED

I've have tried the setupcmd from the system itself and it ran successfully but never registered itself in the client list in the GUI (it did get added to OPSI though)

Cheers!

[wolfbardo]

Hi,

perhaps you have to recompile the winexe (or try the ubuntu wmi-client-package).

Please check/post your preloginloader.log.

which win2k3-Server (32-bit or 64-bit)? (we had a report about Problems on 64-bit systems in the preloginloader.ins with the section

Code: Alles auswählen

[DosInAnIcon_getMac]
@echo off
cscript "%ScriptPath%\utils\ip2mac.vbs"

)

regards

Bardo Wolf

[d.oertel]

Hi,

there seems to be a problem between the winexe and (your ?) win2k3.
winexe is not a opsi programm but one of the samba project.
Perhaps there is a newer version wich may fix this problem.
What tells
/opt/pcbin/install/preloginloader/winexe -V

I've have tried the setupcmd from the system itself and it ran successfully but never registered itself in the client list in the GUI (it did get added to OPSI though)

If you tried the 'service_setup.cmd' and it doesn't works, so please post the:
%TEMP%\preloginloader.log

regards

detlef oertel

[cshields]

Finally got to the end of this... A freshly compiled winexe would not work, produced the same errors at first...

But it did work after going to the win2k3 box and running 'sc delete winexesvc'

Then, the new winexe worked fine, as did opsi-deploy-preloginloader with that winexe.

Thanks for all of the suggestions here!