Visitor Stats

Visits today:20
Visits yesterday:72
Visits in this month:1043
Visits total:103850
Bots today:16

3. Selection


The program does operate on a selection of users. There are three main selection options:

- All users of a context (and subcontexts)
- Based on an attribute of an object. e.g. Member attribute of a Group object.
- File based: CSV, LDIF or simple text-file.
The selection can be narrowed with the filter options. There are a few buildin filter options, and it is possible to create a custom filter-dll for special filter actions.
Massuser can also do some limited operation on Groupwise External Entities, at the moment it is only possible to create/delete an extra-directory for a Grouwise External Entity, see also other tab
Massuser does have another selection option, the selection is not a collection of users but a collection of directories that needs to be created/deleted. The directories are indepent of a user. See also Directory Only.

3.1. Context selection.

Select the selection button, the program will show a treeview of the eDirectory, here you can select the root (=all users in the tree) or any Organization or Organizational Unit. It is possible to include "User Alias objects" in the selection. The program will use the referenced user objects. At the moment there is no check for possible double user references.

If the option "External GW entity instead of user" is selected, the program will select the "Groupwise External Entity" objects instead of user-objects (alias reference is also possible).
Select the object you want and select the OK-button.

Sometimes the proggram shows the button with the Add-sign. If the button is available it is possible to create objects.Sometimes only certain objects can be created. In most cases you can create container objects (country, location, organization, organizational unit and domain).
The program will always show the find button. It is possible to enter the start of the objectname you want to find, the program will add a wildcard to the end for the search. If the program find an object with the correct name and class type the program will show a list of objects found

Select the correct object and the the treeview will show the object. If the search results into one object, then the program will show that object.

3.2. Multiple context selection


If the option "context select" is set, then the program lets you select one or more contexts.

The program will select all the users of the context lb.wb and as.wb. All the users of al.wb without the users in the context will be selected. So you can select and unselect certain context's. On selection of a context without pressing the ctrl-key, all subcontexts will be selected/unselected. If the ctrl-key is pressed during a selecttion, only the selection state of that container is changed. At the moment the program only supports selection of containers.


3.3. Object selection.

First select the class of the object you want to use for the selection. In the ini-file (homes.ini) it is possible to define which object-type and attribute must be used for the selection. There are a few object-types and attributes defined. e.g. The member attribute of a Group. (=group members).
Object type "user" will select only one user. If "External GW entity instead of user" is selected, then Object type "user" will act as a seletion for a "Groupwise External Entity".

warning: The program will show simple NDS-users in red, if the userobject has a posixAccount class attatched then the user object will showup green and if there is also a apple-user class attached, then the user object will be blue. This is also true for the objects person and organizational person. Its is different than Nwadmin and Console One!

3.4. File selection.

Select the file to be used by selecting the selection-button. The program will use the first line of the selected file for determination of the "type" of the file. It will not use the extention of the file. There are three types of selection files:

- Simple text file, only the (full) name of the users are in the file.
- LDIF-file. The program will read the file and will use the dn: attribute of the records in the file. It is possible to use the HomeDirectory attribute in the file for creating the homedirectory. The program will not look at the LDIF-operation in the file it will just look at the dn: attribute!
- CSV-file. The program uses a combnation of two files. One is the csv-data file and one is the control-file. In Homes.exe the csv-file can be used for the selection and optional the HomeDirectory. It is also possible "Userspace and/or Directory Space limits". MassUser can use the CSV-file also for creating of user-objects or updating User-objects.

3.4.1. Simple text-file

With a simple text-file you can provide a list of users for which you want to modify. A simple text file must contain on the first non-comment line the string: homes text 1. (dot not included). If you want to put comments in the file, start the line with one of these characters # ; . : !
Sample simple-input-file.

#Sample file
homes text 1

3.4.2. LDIF-selection file.

The program reads the LDIF file and uses the dn: lines for the selection of users. I you select the option "use Home directory from the selection file" then the program will also look for the attribute homedirectory: or ndshome directory: The program uses this field as the value to be used for the home directory. Any other information in the file will be ignored, so you can use the same file for this program as for the creation of users with ICE or Console One. The structure of the LDIF-file must comply with the standards, only UTF-8 files are supported.

3.4.3. CFL/CSV.

If you want to use a csv-file for the selection of users, you have to create a Command FiLe, so the program knows which column of the csv-file contains the needed information. In this command-file you can also set the way the program "calculates" the context. If the option "use Home directory from selection file" is selected then you have to set the home directory parameters in this file.

3.4.4. CFL-Command file

There are few "sections" in the command-file.
- "describe" the structure of the csv-file
- selection section
- optional the home directory section.
- optional UserSpace or Directory section(s).
- optional user attribute information (for create/update user objects MassUser only).
The first non-comment line must contain the string CFLv1 (Command FiLe version 1). The program will treat any line starting with ! # ; : . as a comment line. All other lines start with parameter=value
The order of the parameters isn't important.
You always have to give the following parameters:


give the filename of the csv-file in the same directory as the Commandfile,
don't add the path to the filename.


set the character to be used as the field separator, in most cases a , (comma)


set the character to be used as the string quote character, in most cases a ", or if there is no quote character, then set quote=none

title=0 or 1

A csv-file can contain a title-line, is this is the case, set title to 1 otherwise 0

3.4.5. selection section

The CVS-file is probably an export of some other system, in most cases these systems do not have a NDS-compatible context. e.g. in a HRM-system there are only functions and not a full NDS-context. The program provides you with a few options for composing the context for a user.

You always have to give the parameters:



Give the column number of the "user" in the csv-file.

userfl=0 or 1 or 2


the user-column in the csv-file contains a full distinguish name.



the user-column only contain the "login-name" of the user and the context is determined by the parameter contextfl



the user-column contains the shortname (common name),
cvalue contains the "search top" in the eDirecotry

optional parameters.



give the column number of the context in the csv-file, only needed as userfl=1 and contextfl is 0,1 or 2.

contextfl=0, 1, 2 or 3


The column context in the csv-file contains the real context of the user.



The column context in the cvs-file contains a value that is looked up in the NDS for resolving. cvalue must be set, see also samples.



The column context is the cvs-file contains a value that will be resolved
with the file given by the parameter cvalue. See also sample.



The csv-file has no context-column, the value given by cvalue is used as a "fixed" context.



value is the attribute name to match the value of context in the csv-file. Important: attribute names are case sensitive.



value is the filename of the file in which the value of the context given in the csv-file is matched.



a fixed context, no leading dot.



search top for lookup users.

section home directory.
You have to set a few of the parameters below if you selected the option "use Home directory from selection file". The program needs an UNC-path for the home directory. (\\server\volume\dir[\dir....]).




program does not use CSV-file for home directory, 1



use csv-file for home directory specification.

homefl=0, 1, 2, 3


The column homedir in the cvs-file contains the full unc-home directory.



The column homedir in the csv-file contains the basic unc-home directory
path, and the program will add the login-name as a subdirectory to it.



The home directory path is based on the settings of serverfl,contextfl and



Same as 2 but the program will add the login-name as a subdirectory to it.

home directory=<val>


Column number of the home directory information, must be given in case the: homefl is 0 or 1 or homefl=2 or 3 and pathfl=1

serverfl=0, 1


the parameter servername= gives the server part of the unc-home directory



the parameter server= give the column in the csv-file for the server



gives the hostname of the home directory unc-path. (serverfl=0)



gives the column number of the server in the csv-file (serverfl=1)

volumefl=0, 1


the parameter volumename= gives the volume part of the unc homedir path



the parameter volume= give the column in the csv-file for the volume part.



gives the volume of the home directory unc-path. (volumefl=0)



gives the column number of the volume in the csv-file (volumefl=1)

pathfl=0, 1


the parameter pathname= gives the (basic) path part of the unc homedir path



the parameter homedir= give the column in the csv-file for the path part.



gives the path-part of the home directory unc-path. (volumefl=0).
Warning if you set homefl to 2 and pathfl to 0, all users get the same
home directory!

UserSpace or DirQuota restrictions

You can set the userspace restrictions or Directory Quota's with a CSV-file import. See the sample.



no userspace info in csv-file.



userspace info in csv-file give usespace.



<value> is column number in csv-file with the new-value of the userspace limit, If value=0, then usespace limit will be removed.




No dirquota info in csv-file.



DirQuota info in csv-file, give dirquota.



<value> is column number in csv-file with the new-value of the dirquota
limit, If value=0, then dirquota will be removed.

Extra attributes for updating or creating an user or groupwise accounts (massuser only)



Column number of the password for the user account, if option "GW password is NDS password" is set then the password is also set on the Groupwise mailbox



Column number of the password for the Groupwise Account. Will overwrite any password on the mailbox.




Column number of where the program can find the surname. Surname is mandatory for new user objects, if now given the program will use the loginname as the surname.

Other attributes for user/groupwise account update/create.

If other attributes must be set with the CSV-file, then add the following lines after any options from above:



A CSV-file may contain more information than needed (more columns), extra columns are ignored.

Structure of a context translation file: (userfl=1 and contextfl=2)

For every possible value of the context-column in the csv-file the translation file must contain a line like:

value1 from csv file=dn of the context.
Sample: In the HRM-system there are two groups: automation and management. The translation file could look like this:


The program will translate every `automation' in the csv to auta.hbr.hbw.

See chaper Samples for more information.

3.5. Dir Only

Only available in MassUser. The program will show the only tab-page that is available with this selection option. This function is added because sometimes the users are deleted but the homedirectory is still there and the function "find obsolete homedirectories" can't do the job (too complex mapping between (deleted) user and homedirectory) or if you just wish to delete some directory structures. See Directory Only chaper for more information.

3.6. Filter

There are two filter subtabs



Filter I


only include users that have there (current) home directory on server:

This option can be useful if there is not a ono-to-one relation between the selection and the server where the home directory is located. This option is most useful for delete/update operations in the MassUser version.

only include users that have no home directory in the NDS.

This option can be handy if there are a few users without a home directory, and you want to create a directory for them.


User defined filter with extra DLL.

It is possible to create a filter-DLL, the needed information is in the last chaper.
New filters will be added in the next version.

- Only disable accounts,
- Only enabled accounts
- Not logged in longer than (xx weeks, months,years)
- Account Expired longer than xx weeks,months,years
- Exclude users that are member of a group or groups.
Changed in version 3.02: In previous versions one one filter could be selected. From now multiple filters can be selected. All filters will be applied.

3.6.2. Filter II



On this page are a few filters that are based on attributes of a user objects.
- not logged in longer than
- expiration date before
- only disabled accounts
- only not disabled accounts
- only if user has Groupwise account
- only if user has no Groupwise account.
Not logged in longer than

It is possible to select how many weeks,month or years (1..99) a user isn't logged in, before it is included in the list.
Warning: There is a report that the condition "Not Logged in longer than" not always find the correct last login date (the program doesn't find the "Last Login Date" at all). A workaround: set the option "Do not include unused account:", the program will not delete homedirectories of users where the lookup goes wrong. Because this bug occurs randomly, it is still around.


Expiration date before

The program will lookup the expiration date, and will only include users with an expiration date before the number of weeks, months or years. There is no problem with this function.


Only if user is (not) Disabled.

If both options are set, no users will be selected.


Only if user has (no) Groupwise account.

If both options are set, no users will be selected.