Are you sure the following is covered:
You are scanning all of the ip address ranges you need to scan
A good way to find out is to create a dummy targeted multicast job for cache only and then see the subnets identified in the multcast console when the job starts since it breaks the job into the detected subnets in the inventory automatically
All of the machines are definitely on at the time that you scan
Your number appears to have increased against your first post so is it just that machines are coming back online over time?
Your machines have their firewall configured correctly for communication
Just because they had an 8.7 agent on them doesn't mean 100% that they were still contactable by ping
Identify 'missing' machines on a target subnet and try this yourself when you know for certain they are online
If you are really confident that all 350 machines should be contactable at the time of your ping sweep then use your old 8.7 server and target them with a very simple script such as an inventory scan. How many devices in that task report as being non-contactable? if they all come back positive then there is something wrong with the ping sweep either in the settings or a bug.
In short, you suspect that the results are innacurate. this is either incorrect configuration on the sweep, systems not responding, a bug in UDD, or incorrect expectations. Using the above you should be able to work out which is the case.
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk
