The GroupFixTool will fix most of these "peculiar items" on a single or all groups.
The Group Fix Tool performs the following:
What the tool does NOT do:
Usage: java -jar GroupFix.jar [ -dLvA ] [ -e <keystore> ] [ -h <host> ] [ -p <port> ] [ -Z <encrypted connection> ] -D <the DN of the object used for authentication> [ -w <bind password> ] [ -G <groupDN> ] -d enable API debug output - Default=false -e Path to a Java Keystore. A valid certificate in the keystore enables an encrypted TLS connection. See also the -Z option. - Default="" -L Print Groups and Group Members in LDIF format (no operations performed) - Default=false -h host name or IP address. A port can be specified with the host name as hostname:port, i.e. myhost:389. See also the -p option - Default="localhost" -p host IP port number. See also the -h option - Default=389 -v enable verbose output - Default=false -Z sets the type of encrypted connection. A Keystore must be specified with the -e option to enable an encrypted connection. SSL - Establishes an encrypted connection using SSL. The default port is 636 TLS - Establishes an encrypted connection using TLS. The default port is 389 - Default="TLS" -D cn=admin,ou=administration,dc=willeke,dc=com - Required Argument -w the password for the DN of the object used for authentication - Default="" -G the baseDN where groups are or the FDN of a single group - Default="dc=willeke,dc=com" -A True if we should fix ALL groups or false if to fix a single group - Default=falseSo running:
java -jar GroupFix.jar -dvA -h 192.168.1.4 -p 389 -D cn=admin,ou=administration,dc=willeke,dc=com -w secret -G ou=groups,dc=willek,dc=comWould be (d)ebug output, (v)erbose output (A)ll groups on (h)ost 192.158.1.4 on (p)ort 389 binding as (-D) cn=admin,ou=administration,dc=willeke,dc=com with a password of (-w) secret and fixing all (G)roups that are in the container "ou=groups,dc=willek,dc=com"
Just do not try to make money with it.