I have Software use analysis installed .
So We have deployed Upload Software scan as policy. and Initiate scan is deployed whenever the request comes for scanning.
But say we have 100 users in initiate software scan deployment and i need to do individual check for Upload results of machines as the upload is policy and had been running multiple times.
Is there any report on this which will give me Start time and status of action or any report which will resolve my pain…
I’m confused. What are you checking manually and why?
You should have the scan set as a policy but to repeat like once a week or so and distribute it over time.
The upload should run whenever there are results to upload. It should run after a scan completes and then it will not run again until the next scan is done, at least that is how it should work.
I just noticed this other post you made that could be related: SUA Query for Initiate Software scan
Hello @jgstew
The issue is not related to above post.
Let me explain the scenario . I have around 1 Lakh endpoints and i have 1 upload software scan policy.
So 1) Initiate run only when the request comes from the Customer. Like this we deploy initiate software scan based on request .
Now The problem :----
The upload is single policy and it happens many a times that initiate software scan is complete but upload does not take place.
Example : --ABC is a machine on which initiate software scan was ran 2 times(10-Oct-2015 and 12-OCt-2015 ). On ABC Machine upload has happened only once 10-OCT-2015 so it shows completed. and on 12-Oct-2015 it had not ran.
That’s the reason i want a report which will give upload software scan results with Start time and Endtime as well as how many times it has applied and its status.
Let me know if any details required
This issue might be related to how the upload task is deployed. Is it set to repeat an unlimited number of times? Is there any delay set?
It is set to unlimited number of times but it will be applicable only when the initiate Software scan is ran.
So my concern each time i need to go to individual action info of each machine and check the upload had ran or not…
When you take action on the upload task, you should do it something like this:
It is actually important to use the while relevant, waiting instead of whenever it becomes relevant again
I would also recommend having it: on failure, retry with wait until the computer has rebooted.
The reason for this is a bit odd.
If you use whenever it becomes relevant again then it will ONLY reapply if the relevance becomes true, it runs, then it becomes false, then after a while it becomes true again.
If you use while relevant, waiting then this guarantees that it will reapply.
It might seem that both options would guarantee it will reapply, but that is not the case if something wonky happens to cause the relevance not to go to false for some reason. It could be due to a failure, or a locked file, or something else.
If you did not take the action on the upload task this way, then I would bet this is the cause. If you did do it this way, then it could be lack of retry on failure, and if not that… then it is a bit more of a mystery to me and I would investigate the client more closely.
I do believe that with session relevance you can get the info you are looking for about how many times an action has run. You should also be able to determine when the last time the action ran. The session relevance could be used in the console, or WebReports, or through the REST API or other options.
I am also curious, why the SUA scans are initiated with a one off basis rather than run continuously on an interval for the machines that are being tracked?