Has anyone used the "Endpoint Initiated" (wepscan.exe) scan feature in
Inventory 4.0 on OS2 endpoints?
I follow this steps to perform a inventory scan at OS2 endpoints start
up :
1- The OS2 endpoint logs in the Tivoli environment.
2- Distribute an Inventory Config profile which sends the configuration
file (config.dmp) and the methods if these were necessary.
3- Load the LCF environment variables
4- Run the wepscan program with the following instruction:
C:\Tivoli\lcf\inv\scan\>wepscan.exe -d
On Windows 2k endpoints, this process generate a file named INV_SA.DAT
which is sent to the Collector Gateway with the comand "wepscan -s."
In the OS2 ep's the command returns the prompt but it does not create
any file. After that we try to generate the SA_CONFIG.LOG file (created
using "wepscan -c"
which explains all the operations that the
inventory profile will perform, but no files are created.
My environment is compounded by OS2 4.5 (fixpack 2).
Thanks by advance, José Luis Calleja (jlcallejal@terra.es).
Inventory 4.0 on OS2 endpoints?
I follow this steps to perform a inventory scan at OS2 endpoints start
up :
1- The OS2 endpoint logs in the Tivoli environment.
2- Distribute an Inventory Config profile which sends the configuration
file (config.dmp) and the methods if these were necessary.
3- Load the LCF environment variables
4- Run the wepscan program with the following instruction:
C:\Tivoli\lcf\inv\scan\>wepscan.exe -d
On Windows 2k endpoints, this process generate a file named INV_SA.DAT
which is sent to the Collector Gateway with the comand "wepscan -s."
In the OS2 ep's the command returns the prompt but it does not create
any file. After that we try to generate the SA_CONFIG.LOG file (created
using "wepscan -c"
which explains all the operations that the inventory profile will perform, but no files are created.
My environment is compounded by OS2 4.5 (fixpack 2).
Thanks by advance, José Luis Calleja (jlcallejal@terra.es).