OcsPackager uses wrong PsExec-Params: Login failed: unknown username..

[mehdi]

OcsPackager.exe Version 1.0.3.2 as downloaded on 2011-10-20
PsExec.exe Version 1.9.8 as downloaded on 2011-10-18 from sysinternals.com
-------------------------------------------------------------------------------------------

First of all: thanks very much for OcsPackager. It's really a cool tool .
But sadly it has a bug:

When I execute ocspackage.exe (that was created with the above mentioned tools) via loginscript with

    call OcsLogon.exe /PACKAGER /SERVER=https://ocs.mydomain.local/ocsinventory /DEPLOY=2.0.1.0

I get this ocspackage.log on my Windows XP-Client in C:\Temp:

   ...
   ocspackage.exe_:_User= "georg" AccountType= "User" IsUserAdmin= "false"
   ocspackage.exe_:_Current user is not admin:
   ocspackage.exe_:_Launching setup by Psexec.exe...
!!!!! ocspackage.exe_:_Psexec options: \\localhost /user:mydomain\clinstaller /pwd:******** !!!!!!!
   ocspackage.exe_:_Waiting for Psexec.exe log:.1
   ocspackage.exe_:_============== Start of Psexec.exe log =============

   PsExec v1.98 - Execute processes remotely
   Copyright (C) 2001-2010 Mark Russinovich
   Sysinternals - www.sysinternals.com

   Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.
Here's the error in english: Login failed: unknown username or wrong password

   PsExec could not start instocs.exe:
   ...

As you can see above between the !!!!!-marks the cause of the problem are the parameters for
username and password which OcsPackager passes to PsExec.exe.

But the parameters should be: \\localhost -u mydomain\clinstaller -p ********
The Parameters /user: and /pwd are from RemCom.exe as mentioned in http://wiki.ocsinventory-ng.org/index.p … s:Packager.

So I hope the programmer of OcsPackager.exe would provide us with a corrected version very soon.
Thanks in advance
Sherlock

[dwe (dirk-westfal)]

Having been hit by this one myself, i digged a little in the source an found:

This bug is a misleading logged message,resulting from an unfixed logging statement couple lines before psexec is called.
Psexec is called correctly.

If you run into this error, check wether psexec is aviable/executable on the remote host in the calling security context/profile.