I’m wondering if it would make sense to help group our machines by adding a computer property that would have each entry for each department that the machine is used by.
For example, for ComputerX I would add new custom properties with values like this:
Custom Property 1 Department = “Accounting”
Custom Property 2 Department = “Networking”
I would then use automatic groups to look for those properties.
I’m open to ideas of how to solve this problem.
I often have machines that end up in the wrong group…and this way I change the computer and then I’m not updating the 5 manual groups I already have.
This is what I’ve been thinking about because we have too many nested groups and cross-functional machines that belong to multiple groups.
You should use the “Location property wizard”. It’s designed for exactly this purpose, i.e. mapping one value to another. The primary path through the wizard maps subnets to locations, but you can use any criteria you want by crafting a custom relevance expression.
How do you identify that a particular computer is in “accounting”?
That is the million dollar question. It would seem that the machines look very similar and have very few or no unique identifiers.
The target machines are in multiple subnets, use applications and software used by other departments, so they may not have a single unique property; at least not that I can think of. Does that make sense?
I will try the location wizard and see what I come up with there. Otherwise, would it make sense to tatoo each machine with a department name and group them that way?