Anyone know how I can create a dynamic device group filter easily based on a Windows domain? I was hoping I could create the group based on the "NIC Properties/Windows Domain Name" but that filter is apparantly not available when filtering on the "Devices -> Manage Device Group Filters" selection page (although it is on the "Services -> Device Services -> Windows Service -> Manage Windows Service" page).
I had also hoped that it would be available via Manage Monitored Devices, allowing me to edit the Org/Division property for multiple devices at the same time...but the filter option isn't there, either (at least not in 3.5.1). Any other suggestions?
Otherwise, I may just have to slug it out and fill in the Org/Device attribute for all 1000 windows servers to make it easier the next time.
Well, the slug it out part may not be as bad as you think...
Use the Filtering display at the top of the Manage montiored devices screen to show just your Windows Servers, then use the Selection boxes to highlight all the ones that exist in the domain you want.
You can then hit the modify button at the bottom, and once you edit the attribute and apply it, it will be saved for all the servers you selected.
You can then create your device group off the attribute you populated.
Yeah, I know I can edit multiples -- I did it before to change the attributes for a division that ran a remote collector. I was just hoping that it would be easier to filter on the domain so that I had an easier way of finding the needles in the haystack. I just added four new domains with a total of 100 servers (bringing my grand total to around 850), and the names and IP addresses will be intermingled, so there isn't a very clean way of sorting them, either.
Unfortunately, I was lazy when I started collecting from our corporate domains -- since I didn't have to break them down into their own groups for reporting purposes, I left most of the device info blank -- I reckon I'll need to add that info now so that I can filter with a NOT IN attribute later (even though we'll hopefully be using more of the RC methods for additional sites).
Couldn't agree with you more Jeff. 1300 windows servers + same issue. We had to bite the bullet and mass populate the device attribute data, and filter off that. We have just under 30 domains to manage and being able to filter on it is a HUGE bennefit.
After a while we really got hooked on it and started adding more custom attributes. They work really well for other devices to... take firewalls for example, we can now device group on role-based functions like "all internet facing firewalls", "all internal firewalls", "all vpn firewalls" etc. Allows you to really slice and dice them up by what they do... rather than just attributes about what they are.
Have you looked at using ipaddr.tab? You can use the Category and Department fields. It's mean't to be used to set traffic as inbound or outbound but you might be able to setup ipaddr.tab with the address of the servers and assign the domain in one of the six fields (3 Category and 3 Dept)
Just a thought
He was referring to the six fields that appear in some of the reporting tables - Department1,2,3 and Category1,2,3
IPADDR.TAB does not populate the device attributes in Manage Monitored Devices area.