Rule Group executes perfectly when started manually, but it does not work when executed via scheduled task, even though task shows successful completion. Running on Server 2012 R2. Any ideas?
More information on what we are doing. Starting with Landesk 9.5, we use data analytics to do Discovery Services SNMP scans on our network address ranges in which printers reside. Special Data Map and Data List Rules are then run daily to manipulate the raw collected data into a Standard Form. A special view was created in the LDMS data base to collect the resulting Data Asset data, and then this is automatically imported into LANDesk Service desk where we have created a Printer Manager Application. We have over 350 networked printers statewide, and this process has enabled to better keep track when new printers are added, when old ones are retired, or when a printer has been replaced, and made it easier for Admin Assistants to verify we are not paying for leases or maintenance on printers we do not have.
When we went to Landesk 9.6, DA Discovery Services had too many bugs to move this process off of the LANDesk 9.5 Server. We are now in process of moving to LANDesk 10 (2016), and I am happy the report the problems with 9.6 Discovery Services have been fixed. However, so far, I have been unable to get the Data Map and Data List rules to run as a scheduled task.
I do notice that each time the schedule tasks are started on in LD 10, there is an ERROR entry in the System Event log on the server, Event ID 7023. The Interactive Services Detection service terminated with the following error: Incorrect Function. My thinking that maybe that when the rules are run as a scheduled task they are trying to produce the same interactive popup that manual run of the rules produces, and this is not being allowed, thus killing the process.
For those who have LANDESK 10, can you successful schedule in Data Map, or Data List rule to run successfully? By successful, I do not mean the schedule task show success, but that results produced by the rule are actually carried out. I am trying to figure out if this is a LANDesk bug, or a configuration issue.