Michael, at the moment, smart server groups only filter on properties. Therefore, if you want to create server groups based on regular expression results, you should use an NSH script and the BLCLI.
You'll need the following commands:
You'll also need to create a user_info.dat file in which to cache your BLCLI user credentials. See this document for more information:
So you're saying set a property for each server that belongs in the group? That would be just as painful as simply manually placing them into a static server group.
I'm shooting for adding a host into RBAC, putting it into a Resource profile (or 2 or 3) and pushing ACLs to it. It should just show up in the smart groups it belongs in.
I'll work with manually adding a property for now. I hope whomever adds the host remembers to set all the correct properties we need for exceptions like these.
But, if it's not already on the radar, can the fields for smart groups be nested/grouped/XOR'ed/etc and the strings to match be PCRE aware, please? My problem would be solved if I coudl make a single rule that reads:
(HOST ends with \d && HOST does not begin with uc)