In a large network, how can I limit the Discovery Task to one domain? At present the computers from all domains are included.
I wish there was a way to limit discovery, but I don’t think so. I asked for a limit by IP subnet (that would help in my environment). Perhaps in a future release. Hopefully the NEAR future :-).
To limit the discovery to a single domain shouldn’t be a problem, but how about the IP subnets?
I’m still not sure how this would be done. The thing is, all we get from the ActiveDirectory (or domain) query is domain and computer name (Netbios name). Now we can do a DNS lookup for that host name - this should theoretically return its IP address (assuming the DNS names and NetBIOS names match - not always the case).
But what else? How should we recognize the hosts by subnets?
Perhaps I’m making this too difficult. Since you’re querying AD, how about a limit by AD container? Many of my larger customers organize AD by site (which might include one or several IP subnets), That would be great if you would present a Container Map of AD, and allow discovery by containers specified.
The next update will have the possibility to limit the discovery to one or more domains (or workgroups).
Voltorb, your suggestion is appreciated but doesn’t sound so easy to implement - maybe in the next version. Thanks.
No problem. Please keep it on the list. I appreciate your consideration!
It’s a shame that you don’t feel this feature should be given more serious consideration. After all, surely it’s quite simple to read the OU structure from AD? I’d have thought it more simple than building the domain structure from something as unreliable as the LAN Manager browse list?
In our network we use active directory and are currently looking to replace our anti-virus solution (Sophos). A notable number of our machines act as terminal server only clients and have been automatically configured as such based on their OU membership. Had we been able to simply import the OU structure from Active Directory, we would give Avast serious consideration. Alas, it looks like it will get passed over in favour of McAffees offering.
Disgruntled,
Lancs
Could you please elaborate a bit more? I don’t quite understand what exactly you’d like the deployment task to do? To query AD and based on certain attributes of the machines decide whether to include it to the result set or not?