• 0 Vote(s) - 0 Average
  • 5
  • 4
  • 3
  • 2
  • 1
Thread Modes

Import Software from Discovery
#1
Hi,

I have populated Software Catalog with Discovery and there are some entries.
I have created a Detection rule on one of the Software items and as per documentation I should now run a Scheduled Alert called "Import Software from Discovery". It finishes one second after it was run, but nothing happens.

Could someone please shed some light on to this Alert:
- what should it actually do
- should the Software Catalog be emptied and repopulated again with new detection rules applied (i hope it doesn't show a software marked inside detection rule, but only one software which should include all those items defined in Detection rule - at least this is what i am aiming for and understand this functionality).

After some investigation i have found out that on the installation i need this, the SQL statement in Alert definition is empty, while in the demo VM from EZV it has an execute import_discovery statment. I have tried with this one, too, but the results is same - nothing.

Thanks for any useful information on this matter.

(12-05-2018, 08:29 AM)cebokli Wrote: Hi,

I have populated Software Catalog with Discovery and there are some entries.
I have created a Detection rule on one of the Software items and as per documentation I should now run a Scheduled Alert called "Import Software from Discovery". It finishes one second after it was run, but nothing happens.

Could someone please shed some light on to this Alert:
- what should it actually do
- should the Software Catalog be emptied and repopulated again with new detection rules applied (i hope it doesn't show a software marked inside detection rule, but only one software which should include all those items defined in Detection rule - at least this is what i am aiming for and understand this functionality).

After some investigation i have found out that on the installation i need this, the SQL statement in Alert definition is empty, while in the demo VM from EZV it has an execute import_discovery statment. I have tried with this one, too, but the results is same - nothing.

Thanks for any useful information on this matter.

So, I have found the stored procedure and from what i can tell it doesn't actually find any records.
This is the statement it does at the beginning:
DELETE FROM AM_SOFTWARE WHERE AUTOMATIC_INSERT = 1 AND ASSET_ID IN (SELECT ASSET_ID FROM AM_ASSET WHERE UPDATED_BY_DISCOVERY = 1)

I have only one record in am_software and even that one is not marked as automatic_insert = 1.
So i amclearly missing something. Is there something we need to do in the discovery import step at the first place, so that the software is marked for insertion? I don't really get it Sad

------- EDIT

Looking further through the stored procedure, also the SELECT statement, which seems to identifiy all the installed software etc, to process, doesn't find anything. I have a suspiction here Smile

Does the Equipment discovered by the Discovery need to be "moved" - activated  to Assets so that licences and everything is workng correclty? Specifically this stored procedure and detection rules?


Thanks
cebokli, proud to be a member of EV CONNECT FORUM since Oct 2016.

#2
(12-05-2018, 08:29 AM)cebokli Wrote: Hi,

I have populated Software Catalog with Discovery and there are some entries.
I have created a Detection rule on one of the Software items and as per documentation I should now run a Scheduled Alert called "Import Software from Discovery". It finishes one second after it was run, but nothing happens.

Could someone please shed some light on to this Alert:
- what should it actually do
- should the Software Catalog be emptied and repopulated again with new detection rules applied (i hope it doesn't show a software marked inside detection rule, but only one software which should include all those items defined in Detection rule - at least this is what i am aiming for and understand this functionality).

After some investigation i have found out that on the installation i need this, the SQL statement in Alert definition is empty, while in the demo VM from EZV it has an execute import_discovery statment. I have tried with this one, too, but the results is same - nothing.

Thanks for any useful information on this matter.

(12-05-2018, 08:29 AM)cebokli Wrote: Hi,

I have populated Software Catalog with Discovery and there are some entries.
I have created a Detection rule on one of the Software items and as per documentation I should now run a Scheduled Alert called "Import Software from Discovery". It finishes one second after it was run, but nothing happens.

Could someone please shed some light on to this Alert:
- what should it actually do
- should the Software Catalog be emptied and repopulated again with new detection rules applied (i hope it doesn't show a software marked inside detection rule, but only one software which should include all those items defined in Detection rule - at least this is what i am aiming for and understand this functionality).

After some investigation i have found out that on the installation i need this, the SQL statement in Alert definition is empty, while in the demo VM from EZV it has an execute import_discovery statment. I have tried with this one, too, but the results is same - nothing.

Thanks for any useful information on this matter.

So, I have found the stored procedure and from what i can tell it doesn't actually find any records.
This is the statement it does at the beginning:
DELETE FROM AM_SOFTWARE WHERE AUTOMATIC_INSERT = 1 AND ASSET_ID IN (SELECT ASSET_ID FROM AM_ASSET WHERE UPDATED_BY_DISCOVERY = 1)

I have only one record in am_software and even that one is not marked as automatic_insert = 1.
So i amclearly missing something. Is there something we need to do in the discovery import step at the first place, so that the software is marked for insertion? I don't really get it Sad

------- EDIT

Looking further through the stored procedure, also the SELECT statement, which seems to identifiy all the installed software etc, to process, doesn't find anything. I have a suspiction here Smile

Does the Equipment discovered by the Discovery need to be "moved" - activated  to Assets so that licences and everything is workng correclty? Specifically this stored procedure and detection rules?


Thanks

Hello,

With reference to wiki : https://wiki.easyvista.com/xwiki/bin/vie...anguage=en

Exclamation Once scheduled alerts are enabled, the software table (AM_SOFTWARE) will be cleared.
Arrow Detection rules are enabled when the Import Software from Discovery scheduled alert is enabled. 


Detection rules is used to convert presence of a registry key, component or executable (discover by Discovery) into a software catalog and installed software

______

"I have only one record in am_software and even that one is not marked as automatic_insert = 1."
=> Software can be accessible and not installed like Easyvista. You can add a software manually to an asset or to a user

"So i amclearly missing something. Is there something we need to do in the discovery import step at the first place, so that the software is marked for insertion?" 
=> Check on Discovery/Inventory/Sofware that you have lot of sofware discover
=> Go to AssetManagement/Catalog/Sofware-Licence, active filtrer 'none', select software to be managed and managed them
=> After manage some sofware, relaunch a new inventory (evagent.exe), relaunch import (evsend.exe) and you see now your software on 'installed software' in computer form

"Does the Equipment discovered by the Discovery need to be "moved" - activated  to Assets"
=> reconciliation rule between AM_ASSET and AM_DISCOVERY is asset_tag>network_identifier>serial number. If a discvered equipement is not already before in AM_ASSET then it have 'to be check' status

"licences" 
=> No it's installed software

P.ABBE
ABBE Philippe, proud to be a member of EV CONNECT FORUM since Nov 2015.

#3
Thanks for replying to this thread and helping out.
I actually discovered that the stored procedure is not working properly. 
Had to change the select statements that are enclosed in double quotes as the referenced database/tables were not found in execution.

Works fine now.
cebokli, proud to be a member of EV CONNECT FORUM since Oct 2016.






Users browsing this thread: 1 Guest(s)