| 2011-07-03 13:34:35 |
Holger Schletz |
description |
The 2.0.0.22 installer creates an ocsinventory.ini like this:
[OCS Inventory Agent]
ComProvider=ComHTTP.dll
Debug=0
Local=
HKCU=0
NoTAG=1
IpDisc=
[OCS Inventory Service]
TTO_WAIT=0
All important information like SERVER is missing.
2.0.0.20 with the same options behaves correctly, but only if used interactively. Silent installs create the missing entries, but ignore the command line options, providing default values instead.
As a consequence, the agent has no information about the server to contact once the installer has finished, effectively cutting it off with no means to fix it remotely.
This is the command line I used:
OCS-NG-Windows-Agent-Setup.exe /S SERVER=myserver.example.com/ocsinventory /NOSPLASH /notag /NO_SYSTRAY |
The 2.0.0.22 installer creates an ocsinventory.ini like this:
[OCS Inventory Agent]
ComProvider=ComHTTP.dll
Debug=0
Local=
HKCU=0
NoTAG=1
IpDisc=
[OCS Inventory Service]
TTO_WAIT=0
All important information like SERVER is missing. As a consequence, the agent has no information about the server to contact once the installer has finished, effectively cutting it off with no means to fix it remotely.
2.0.0.20 with the same options behaves correctly.
This is the command line I used:
OCS-NG-Windows-Agent-Setup.exe /S /SERVER=myserver.example.com/ocsinventory /NOSPLASH /notag /NO_SYSTRAY
The Problem also occurs with interactive setup. |
|
