when version 10.x comes ?
when version 10.x comes ?
what new functions will be?
Network discovery?!!!
It's been a while since I've checked into this forum, but I seem to remember requesting this a couple of years ago.
In fact I was going to ask if you'd looked at implementing something similar to NMAP. Since you have a pretty nifty set of IP Tools already, generating a list of hosts and basic characteristics (open ports, for instance) would be pretty easy. That, in turn, could point to a particular 'test profile' to apply to each discovered host, speeding the adoption/implementation of AHM in a a new or changing environment.
I'm looking forward to seeing how you utilize network discovery.
It's been a while since I've checked into this forum, but I seem to remember requesting this a couple of years ago.
In fact I was going to ask if you'd looked at implementing something similar to NMAP. Since you have a pretty nifty set of IP Tools already, generating a list of hosts and basic characteristics (open ports, for instance) would be pretty easy. That, in turn, could point to a particular 'test profile' to apply to each discovered host, speeding the adoption/implementation of AHM in a a new or changing environment.
I'm looking forward to seeing how you utilize network discovery.
I would suggest for large networks establishing a distributed discovery model.
Maybe use Remote Monitoring Agents to collect info that is 'pumped' to a 'discovery repository' on the AHM server. Or allow the admin to 'target' machines to do discovery on their subnets, or as part of their AD OU. (I assume you're going to use AD discovery as one of your methods)
Other products like Open-AudIT, do something similar to that.
Otherwise it's going to take days to complete, and will be subject to failure. One other suggestion... any discovery should be restartable, in case the process is interrupted.
And if you are going to set up scheduled discovery/auditing, have the discovery ignore systems that have been discovered in {x} days. This way only newly deployed systems are scanned.
Maybe use Remote Monitoring Agents to collect info that is 'pumped' to a 'discovery repository' on the AHM server. Or allow the admin to 'target' machines to do discovery on their subnets, or as part of their AD OU. (I assume you're going to use AD discovery as one of your methods)
Other products like Open-AudIT, do something similar to that.
Otherwise it's going to take days to complete, and will be subject to failure. One other suggestion... any discovery should be restartable, in case the process is interrupted.
And if you are going to set up scheduled discovery/auditing, have the discovery ignore systems that have been discovered in {x} days. This way only newly deployed systems are scanned.
Actually, I would say there are a few discovery options needed:
Discover only
[tab](i.e. ping sweep or AD query)
Discover & scan
[tab](Netbios, SNMP, WMI, etc.)
Discover & scan - new only
[tab](discover would verify existing, find any new, but only scan the new ones)
Discover & scan single
[tab](give IP or DNS name)
Rescan all
[tab](no discovery, just rescan already known devices.
Discover only
[tab](i.e. ping sweep or AD query)
Discover & scan
[tab](Netbios, SNMP, WMI, etc.)
Discover & scan - new only
[tab](discover would verify existing, find any new, but only scan the new ones)
Discover & scan single
[tab](give IP or DNS name)
Rescan all
[tab](no discovery, just rescan already known devices.