I'm trying my luck on the forum as this is not too urgent, and I'm not sure whether this is related to OpsMgr or nworks. If required I can make an official case for this. Here goes...
I'm trying to create a new group with a dynamic membership of datastores larger than 1 TB. The idea is to target this group when making an override on the free space monitor.
For some reason I don't get the expected members, and I don't see what I'm doing wrong. This is the first dynamic membership I'm creating, so I hope it's not a newbie error
but this seems to be quite straight forward...
We already have a group called nworks VMware Datastores
, which comes by default with the MP I guess. The query is ( Object is DATASTORE AND True )
. It has 1266 members.
I created a new group called nworks VMWare Datastores > 1024 GB
with query ( Object is DATASTORE AND ( diskSize GB Greater than 1024 ) AND True )
. To my surprise there are still 1265 members
Just clicking random datastores I see all kinds of sizes like 250, 300, 600, 750, 1300 etc.
I started experimenting with the query. Lowering the value to 600GB only seems to give me the datastores larger than 600GB (as expected), but... also gives me the local ESX 63GB disks, and none of the datastores larger than 1TB
When changing the value again, this time to 900GB, the group doesn't have any members at all
As I know we have a couple of 900GB datastores I changed the query to ( Object is DATASTORE AND ( diskSize GB Greater than 899 ) AND True )
. The result is 3 members that are 900GB in size (not sure if we have others), and the larger datastores are missing again.
What's going on here?