BES 7.0 Group Members Issue

Usage and Config Platform
1

(imported topic written by Steve91)

Hi

We’ve recently upgraded to 7.0 (well it was actually a fresh install/database) and I’m seeing a problem with groups and their members.

For instance,

We have 22 servers whose name begins with ULTRA

They are all checked in and licensed, but when I create a group with the following relevance:

computer name as uppercase starts with “ULTRA”

…it only pulls 15 of them into the group.

Another example, we have 1006 servers whose name begins with ENT, again they are checked in and licensed

The group:

computer name as uppercase starts with “ENT”

…only pulls in 583 of them

I can’t see any differences between those in the group and those not, we are running a few different client versions, 6.0.12.5, 6.0.15.7, 6.0.21.5 and 7.0.1.376 but all versions are in and out of the group.

All relays are up and running and are also version 7.

Nothing jumps out in the client logs so does anyone have any suggestions as to where I should start looking?

Cheers

Steve

2

(imported comment written by jessewk)

Hi Steve,

Group membership is determined on the client side, so any machines that are supposed to be in the group will need to gather the group membership action, evaluate it as relevant, and report that back to the server.

It sounds like some portion of your machines either did not receive the group membership action, or did not successfully post their results to the server.

I would find a machine that is supposed to be in the group but isn’t, and check the logs. Make sure it gathered the action, then make sure it’s not having problems posting reports or syncing sites. If everything looks good, then go upstream to the relay and make sure everything seems to be functioning on the relay.

If you can’t find anything obviously wrong, I would open up a support case to investigate further.

Jesse