OCSInventory-NG / Agent-Deployment-Tool

Allows you to remote setup OCS Inventory NG agent on Windows and Unix/Linux/BSD computers
GNU General Public License v3.0
10 stars 9 forks source link

"Error: unable to open or read setup log file on remote host" but deployment completes successfully #5

Open enribar opened 3 years ago

enribar commented 3 years ago

Hi, I am trying do deploy agent 2.8 on some Windows 10 x64 and Windows 7 x32 PCs, but Deployment tool always fails with error "Error: unable to open or read setup log file on remote host". Actually the deployment completes successfully, because I can see PCs on OCS inventory web interface and also in OCS agent logs installation results completed successfully.

image

It is a bit frustrating since there is no way to know on which clients the deployment completed successfully or not.

bontiv commented 3 years ago

https://github.com/OCSInventory-NG/Agent-Deployment-Tool/blob/ae58346777df36ea272e85dedd30d95ebaad9fd5/WinAgentSettings.h#L44

The setup log file name is hard coded...

pimu commented 2 years ago

https://github.com/OCSInventory-NG/Agent-Deployment-Tool/blob/ae58346777df36ea272e85dedd30d95ebaad9fd5/WinAgentSettings.h#L44

The setup log file name is hard coded...

and also the logfile name, I suppose, see for example for 64-bit version,

OCS-NG_Windows_Agent_Setup_x64.nsi

; Setup log file !define SETUP_LOG_FILE "$exedir\OCS-Windows-Agent-Setup-x64.log"

and unfortunately they don't match..

thenamelessthing commented 1 year ago

it will be cool to fix that... it's rather disabling not to know whether the deployment has worked or not...

@charleneauger est-ce quelque chose que vous pouvez corriger? Je confirme avoir également le même problème.

Cordialement,