
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-05-2016 11:20 PM
I've looked for a report that will only show active pings so then I can deploy a package to those systems only. This way I don't have to sift through the logs to see which systems failed due to something other than it not being on.
If this is already possible please point me in the right direction.
I have reports that will give me those systems that do not have the most current version of Dot Net. I know I can sort the results by ping, but the systems that are powered off are still getting a deployment.
Example: I'd like to ping my workstations, and only deploy the update to the ones that are on.
Thanks.
If this is already possible please point me in the right direction.
I have reports that will give me those systems that do not have the most current version of Dot Net. I know I can sort the results by ping, but the systems that are powered off are still getting a deployment.
Example: I'd like to ping my workstations, and only deploy the update to the ones that are on.
Thanks.
Labels:
- Labels:
-
General Discussion
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2016 07:45 PM
In my opinion this feels like a kind of bug, after scanning deployments are not supposed to be triggered in offline machines.
I remember one time that I had to deploy something urgently, the way I did it was in Scanning - Scanning Targets. Normally here you define IP ranges or subnets, but what I did was setup a report instead.
In my case I set it to scan the report every few hours. But you can also press "Scan now" for manual triggering.
Hope that help
I remember one time that I had to deploy something urgently, the way I did it was in Scanning - Scanning Targets. Normally here you define IP ranges or subnets, but what I did was setup a report instead.
In my case I set it to scan the report every few hours. But you can also press "Scan now" for manual triggering.
Hope that help

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2016 07:47 PM
Thank you! I had to rework a couple reports, but that looks good! I didn't consider the scheduled deployments since I was just trying to get a list of what was out of date first. 
EDIT: Nope - Not quite right. I started seeing errors in the log for systems that were not on. Almost as if the scan hadn't finished before the task kicked off. Which you would think the ping cmd would be the first thing to scan against.

EDIT: Nope - Not quite right. I started seeing errors in the log for systems that were not on. Almost as if the scan hadn't finished before the task kicked off. Which you would think the ping cmd would be the first thing to scan against.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2016 12:28 AM
Try to setup a scheduled deployment using your custom report, with after scanning. Then open the same report and rescan them all, the deployment will be triggered to the online assets, only.
