I would like to understnd the differene between the On Demand Scan in ENS. I have migrated the ODS from legacy to ENS where the options looks like the above.
Where as I have imported a client task that looks this. I can see this task in the policy, a bit confusing, can some one clarify me.
Solved! Go to Solution.
When scheduling your weekly scan, our best practice would be to run a policy based on demand scan. They you can supplement this scan with custom on-demand scans for more targeted scans, such as daily memory scans.
The main difference is only Policy-based On Demand Scan Tasks for ENS will populate Queries/Reports and return these events. Custom On-Demand Scan Tasks will not. The settings for the ODS scan regardless of policy-based or custom are the same.
I would like to let you know that in the custom scan, we do not have the options for target scan etc. Where as in Policy based scan we do have the options.
My big question mark is that despite I have VSE ods client tasks which I have migrated are becoming custom scans and they are not seen as Weekly On Demand Scans, what could be done. Do I assume the existing VSE ODS are created for quick,memory scans?
Also, I have to assing a client task to 650 odd nodes, where the machines are scattered across. Suggest me the best way to assign a client task for 650 odd numbers in one go as I am finding it difficult to assign the task for each and every individual nodes.
Thank you in advance,
When scheduling your weekly scan, our best practice would be to run a policy based on demand scan. They you can supplement this scan with custom on-demand scans for more targeted scans, such as daily memory scans.
The main difference is only Policy-based On Demand Scan Tasks for ENS will populate Queries/Reports and return these events. Custom On-Demand Scan Tasks will not. The settings for the ODS scan regardless of policy-based or custom are the same.
I would like to let you know that in the custom scan, we do not have the options for target scan etc. Where as in Policy based scan we do have the options.
My big question mark is that despite I have VSE ods client tasks which I have migrated are becoming custom scans and they are not seen as Weekly On Demand Scans, what could be done. Do I assume the existing VSE ODS are created for quick,memory scans?
Also, I have to assing a client task to 650 odd nodes, where the machines are scattered across. Suggest me the best way to assign a client task for 650 odd numbers in one go as I am finding it difficult to assign the task for each and every individual nodes.
Thank you in advance,
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: