Table of Contents


Introduction

Part 1:  Program Description
     1.1  Program Brief
     1.2  Program Functionality

Part 2:  Installing Mass User Management
     2.1  System Requirements
     2.2  Installing the Program
     
Using MUM

Part 3:  Managing Templates
     3.1  Creating Templates
     3.2  Setting Account Restrictions using Templates
     3.3  Changing Contexts

Part 4:  Adding Users
     4.1  How MUM Adds Individual Users
     4.2  How MUM Adds Users from a List
     4.3  User name and Full Name Options
     4.4  Password Options
     4.5  Account Exists Options
     4.6  Type of Run Options
     4.7  Text File Format for Adding Users
     4.8  Examples of Adding Users
     4.9  Personalizing the User name Algorithm
     4.10 Run Batch Files

Part 5:  Deleting Users
     5.1  Overview
     5.2  Deleting an Individual User
     5.3  Deleting Members of a Group
     5.4  Deleting Disabled Accounts
     5.5  Deleting Expired Accounts
     5.6  Deleting Users using a File
     5.7  Deleting Directories
     5.8  Type of Run Options

Part 6:  Modifying Users
     6.1  Overview
     6.2  User Restrictions that can be Modified
     6.3  Modifying an Individual User
     6.4  Modifying All Users in a Context
     6.5  Modifying Members of a Group
     6.6  Modifying by Expiration Dates
     6.7  Modifying by Login Dates
     6.8  Modifying Disabled User Accounts
     6.9  Modifying  Users Listed in a File

Part 7:  Generating Reports
     7.1  Overview
     7.2  User Restrictions that can be Displayed
     7.3  Reports for an Individual User
     7.4  Reports for All Users in a Context
     7.5  Reports for a Group of Users
     7.6  Reports by Expiration Dates
          Reports by Login Dates
     7.7  Reports for Disabled User Accounts
     7.8  Reports for Users Listed in a File
     
Part 8:  Viewing Report Files
     8.1  Overview
     8.2  Controls While Viewing Files
     
Miscellaneous

Part 9:  Getting Help
     9.1  How to Get Help With MUM

Part 10:  List of Menus
     10.1 Quick Menu Search



Part 1:  Program Description


1.1  Program Brief

Mass User Management for NetWare Directory Services (MUM) facilitates the 
management of four critical areas Novell system managers frequently 
encounter.  These include adding, deleting, updating and monitoring user 
accounts.  

You must have SUPERVISOR rights in the contexts you wish to administer in a 
Novell 4.1x tree for Mass User Management to function properly.   Certain NDS 
information can only be accessed by a user with SUPERVISOR rights.

1.2  Program Functionality

Mass User Management will allow system managers to do the following

     1)   Add large numbers of users from lists generated by a database, 
spreadsheet or word processing program.  Mass User Management will 
verify names of existing users and add those who do not have accounts.  
Accounts can be created in many different contexts.
     2)   Delete users from a text file listing user names, a certain group, 
disabled accounts and expired accounts.
     3)   Modify user restrictions for all users in a context, users in a certain 
group, users with expirations dates older than a specified date, users 
with login dates older than a specified date and users in a text file.
     4)   Generate Lists of user restrictions for all users in a context, users in a 
certain group, users with expirations dates older than a specified date, 
users with login dates older than a specified date and users in a text file.











Part 2:  Installing Mass User Management


2.1  System Requirements

Minimum system requirements to run Mass User Management for NDS v1.0:
     Novell NetWare 4.1x Server
     Microsoft Windows 3.1, Windows NT, or Windows 95
     Minimum of 1.5 megabytes (1,500 kbytes) of free hard disk space
     The NDS NetWare client software for the Windows operating system you 
are using.

2.2  Installing the Program

Installing Mass User Management
     1)   Enter the MUM System Disk into drive a (or b).
     2)   From Windows Run a:install
     3)   Answer any questions the install program prompts you for.
     4)   Make sure the unicode tables are in the path (the unicode tables are 
usually    located in the \windows\nls directory).

Adding the MUM Icon to your Desktop in Windows 3.1 and Windows NT 
(3.51)
     1)   In the Program Manager select the New menu item under the File 
Menu.
     2)   Select a new program item
     3)   Enter the path and program name in the Command Line text box.  (e.g. 
c:\mumds\mumds.exe)

Adding the MUM Icon to your Desktop in Windows 95
     1)   Right click on your desktop and create a shortcut..
     2)   Enter the path in the Command Line text box.  (e.g. 
c:\mumds\mumds.exe).  You can use the browse button to find it.  
Press Next.
     3)   Enter the name of the program (e.g. Mass User Management for NDS).  
Press Next.
     4)   If the path checks out press Finish.



Part 3:  Managing Templates


Figure 3.0.1:  File menu options.

 

3.1  Creating Templates

Mass User Management uses a template to connect NDS groups and restrictions 
to a particular user while adding or modifying users.  When adding or 
modifying from a list, templates are matched with a field in the text file 
representing the department identifier.  Templates allow you to define which 
NDS groups the user belongs to; it also allows you to specify volume 
restrictions, home directory locations, login scripts to use, account restrictions, 
etc.

For example, using the text file listed in Table 1, you will need to make the 
following MUM templates:
     Development
     Marketing
     Sales Group
     Tech Support 
     (case is not important)


A template file (*.tmp) can contain up to 100 individual templates and you can 
have as many template files as your heart desires.

3.2  Setting Account Restrictions using Templates

The Current Settings windows reflects a summary of the account restrictions for 
the current template.  To edit these restrictions choose the appropriate button in 
the Edit Settings section of the window.

You may set the following parameters for users assigned to the particular 
template:

Context:
     Enter the context in which the accounts will be created.  Each template can 
have a different context.  The context is displayed next to the words Current 
Settings.

Account Expiration Date:
     Enter the month, day and year you wish the account expiration date to be 
changed to or check the "No Expiration" box to make the accounts have no 
expiration date.  You can also enter the number of days before the account will 
expire, and MUM will determine the appropriate expiration date.  The "Days 
Before Account Expires" is not saved in the Directory Services information -- it 
is only for convenience while running MUM.  Only the "Account Expiration 
Date" or "No Expiration" fields are saved in NDS information.



Enable/Disable/Remain Same Buttons:
     Check whether to enable or disable the account (default is to remain same).  
If you choose "Remain Same", the account status will remain the same as it is 
currently configured for each user.

Account Balance:
     Enter the amount to set the account balance to (-99,999,999 to 99,999,999).  
Make sure accounting is set up on the server before modifying the account 
balance.

Account Low Limit:
     Enter the amount to set as the account low limit (-99,999,999 to 
99,999,999) or check the "Unlimited" check box to allow unlimited credit.  
Make sure accounting is set up on the server before modifying the account low 
limit.

Add to Balance:
     Enter the amount to add to the user's current account balance (-99,999,999 
to 99,999,999).

Change Password:
     You may change the password if you are modifying an individual user.  
Press the "Change  Password" button and then enter the new password.  Retype 
the password to make sure you entered the correct password.

Require Password:
     Check the "Require Password" check box to force the users to have a 
password.  If the users are not forced to have a password, they may still have a 
password however.

Minimum Password Length:
     Enter the minimum length of login passwords (1-20).

Unique Passwords Required:
     Check the "Unique Passwords Required" check box to force the users to 
supply a unique password when they change their password.

Require Periodic Change:
     Check the "Require Periodic Change" check box to force the users to 
supply a new password periodically.  The length of this period is defined in the 
"Days Between Change" edit box.

Days Between Change:
     Enter the number of days between forced password changes.  When you 
enter the number of days between changes, the password expiration date is 
automatically calculated for you.  You can un-check the "Require Periodic 
Change" check box to make the password never expire.

Password Expiration Date:
     Enter the month, day and year you wish the password to expire or un-check 
the "Require Periodic Change" box to make the password never expire.  The 
password expiration date does not have to match the "Days Between Change" 
edit box.  You can set the password to expire earlier or later than the "Days 
Between Change".  Once the password has expired, the "Days Between Change" 
will calculate the next password expiration date.

Maximum Connection:
     Enter the number of connections a user may simultaneously login (1-200) 
or check the "Unlimited" box to allow an unlimited number of connections.

Grace Logins Allowed:
     Enter the number of logins allowed (after the password has expired) to 
change the password before the account is disabled (1-20) or check the 
"Unlimited" box to allow unlimited logins after the password has expired.

Grace Logins Remaining:
     Enter the number of logins remaining to change the password (1 to Grace 
Logins Allowed).

Volume Restrictions:
     Highlight the volume name and press "Edit" to set the space restriction for 
that volume.  Indicate whether or not to limit space; if space is limited, indicate 
the limitation.  

Show Restrictions in Sub-contexts:
     If enabled, check the "Show Restrictions in Sub-contexts check box to 
show any volume restrictions for that user in all contexts below the current 
context.  By default this is unchecked.  Checking this option may take several 
minutes depending on the number of sub-contexts below the current context.

Groups Belonged To:
     The "Groups Belonged To" are shown on the left list box, and the other 
"Available Groups" are displayed on the right list box.  To make the users 
belong to a group displayed in the "Available Groups", either highlight the 
group in the "Available Groups" list box and press the "Insert" button or double 
click on the group.  To remove a group from the "Groups Belonged To", either 
highlight the group and press the "Delete" button or double click on the group.



Remove Other Groups Belonged To:
     Check the "Remove Other Groups Belonged To" check box to make the 
users only belong to the groups you specify.  If you do not check the "Remove 
Other Groups Belonged To" check box, the groups shown in the "Groups 
Belonged To" list box will be added to the user's list of groups belonged to.  For 
instance, if you want to make sure the users you are modifying are in the APPS 
group, double click on the APPS group in the "Available Groups" list box so the 
group is displayed in the "Groups Belonged To" list box.  By leaving the 
"Remove Other Groups Belonged To" check box unchecked, the users modified 
will belong to all groups they previously belonged to plus be added to the APPS 
group.

Create Group:
     MUM gives you the ability to create a new group on the fly.  Just press the 
"Create Group" button and enter the new group name.  The recently created 
group will then appear in the "Available Groups" list box.

Home Directory:
     Enter the NDS volume and path for the base directory.  The Home 
Directory will be the base directory plus the user name.  If the user name is 
DOEJ and MUM_USR:STUDENT is indicated as the home directory, the real 
Home Directory will be: MUM_USR:STUDENT\DOEJ.  A browse facility is 
provided to browse existing directories.  If the directory you enter does not 
exist, MUM will attempt to create the directory.

Login Script Path:
     Enter the path name and name of the login script file (i.e. 
F:\USERS\ADMIN\login.scr ).  The login script file is an ASCII text file 
containing individual login script information for users assigned to the template.  
A browse facility is provided to browse existing files.  An edit facility is also 
provided to allow you to edit the file.

Batch File:
     Enter the path name and name of the batch file to be run in conjunction 
with adding users (i.e. F:\USERS\ADMIN\addbat.bat).  This will not be 
executed when the users are added but can be run from the menu when an add 
run is completed (a DOS program called RunBatDS.exe is spawned when this 
menu is selected.)  A browse facility is provided to browse existing files.  An 
edit facility is also provided to allow you to edit the file.

 

3.3  Changing Context

To facilitate the use of Mass User Management within your tree structure, you 
may select a desired context.  You will need to have the appropriate rights in the 
given context to make MUM fully functional in that context..



Part 4: Adding Users


Figure 4.0.1:  The adding menu for Mass User Management allows managers to 
add individuals users or add users from a list.  It also allows managers to 
run a batch file for added users.  Report files are viewed with the View 
menu.

 

4.1  How MUM Adds Individual Users

Mass User Management allows you to enter an individual's name and criterion 
to use to add the user.  You have the following options:

     1)   Use a personalized user name algorithm or supply your own user name
     2)   Use a password algorithm or supply your own password
     3)   Define what to do if the account exists
     4)   Define which template to use for the users restrictions
     5)   Actually add the user or perform a test run
     6)   Append data in the Created.rpt file to a master report file (Master.rpt).

Once these options are specified, MUM will add the user according to the 
criterion you have set.  These new features allowing you to manage individual 
users as well as users "en masse" and should substantially reduce your need to 
use other utilities (e.g. NetAdmin and NWAdmin) to supplement MUM.  These 
options are also saved in the massuser.ini file allowing you to customize MUM 
to your particular needs.

 

4.2  How MUM Adds Users from a List

Mass User Management uses a template to connect Novell NDS groups and 
restrictions to a particular user while adding or modifying users.  When adding 
or modifying from a list, templates are matched with a field in the text file 
representing the department identifier.  Templates allow you to define which 
NDS groups the user belongs to; it also allows you to specify volume 
restrictions, home directory locations, login scripts to use, and account 
restrictions, etc.  See Managing Templates for more information.

Mass User Management allows you to use a text file, similar to the format 
indicated in Table 1A, to generate accounts.  The text file is simply an ASCII 
file created from a database, spreadsheet or word processing program.  Tabs, 
commas or spaces are used to delineate categories.  MUM uses a previously 
defined template to connect Novell account restrictions to the department 
references in the text file.  


 

Table 1.  Database or Spreadsheet data:

Last Name First Name     Middle    Department (Template name)
Holmstead S.   Bruce     Development
Holmstead Shawn     Matthew   Development
McClellan Ron  A    Marketing
Crandal   John H.   Sales Group
Doe  Jane      Tech Support

Once you have created your ASCII file you have the following options when 
adding users.

     1)   Use a personalized user name algorithm or supply your own user name
     2)   Use a password algorithm or supply your own password
     3)   Define what to do if the account exists
     4)   Define which template file to use for the users restrictions
     5)   Actually add the user or perform a test run
     6)   Define the format of your ASCII file (e.g. tabs, commas or spaces)
     7)   Append data in the Created.rpt file to a master report file (Master.rpt).

When you are ready to perform the operation press OK and MUM will display 
the users as they are processed.  In addition, MUM will generate reports for 
users that were created, not created or modified during the adding run.  Any 
errors will be written to an error report log (ErrorLog.rpt).  You may view all 
these report files using the View Menu.

4.3  User name and Full Name Options

 

If you choose the "Full Name" option, MUM will check the full name field for 
every user in the context identified in the template to see if a matching full name 
exists.  If the full name exists, MUM will modify the account if you selected the 
"Apply Template" option.  Otherwise, an account will not be made for that user.  
If the full name doesn't exist, a unique user name will be generated using the 
current user name algorithm and the account will be added.  

All full names are generated from first, middle and last name text file fields.

If you choose the "User name" option, MUM will use data from the user name 
field (See Table Username in your text file for the user name.  If the user name 
already exists in the context identified by the template or if a user name is not 
found in the 5th field of the text file, the user will not be added.  If you selected 
the "Apply Template" option, however, the account will be modified.

4.4  Password Options

 

If you choose the "Same as User name" option, MUM will make the passwords 
identical to the user name with one exception.  If the user name is shorter than 
the required password length, extra random numbers will be added to the end of 
the password until the password is the same length as the required password 
length.  (i.e.  If the user name is LEEB and the required password length is six, 
the actual password might be LEEB56.)

If you choose the "Password Algorithm" option, MUM will generate a 
password using eight random alpha-numeric characters.  For example, the 
password could be something like AY7B9KH2.  This algorithm meets current 
Department of Defense (DOD) requirements for US Government installations.  
If the generated password is shorter than the minimum password length, random 
alpha-numeric characters will be added until the password is the correct length.  
For example, if the minimum password length is 10, the password might be 
L3GY20CPS1.

If you choose the "Password Supplied" option, MUM will take the supplied 
password from the 5th field (See Table 3)  (or the 6th field if you are also 
supplying user names) of the text file.  If the supplied password length is less 
than the required password length, the user will be rejected and an account will 
not be made for that user.

4.5  Account Exists Options

 

If you choose the "Don't Modify" option, MUM will not modify the user 
account if a duplicate full name or user name is found in the context specified 
by the template.  The users whose accounts already exist will appear in the 
Modified.rpt file to show that their accounts already exist (even though the 
account wasn't modified).

If you choose the "Apply Template" option, MUM will modify the user 
account if a duplicate full name or user name is found in the context specified 
by the template.  The users whose accounts already exist will appear in the 
Modified.rpt file to show that their accounts already exist.

When modifying user accounts, if a particular restriction of the existing account 
has a higher restriction than the template, MUM will leave the current 
restriction.  If the template is higher than the existing restriction, MUM will 
modify that restriction to match the template.  





For example, suppose:

1)   The user DOEJ already exists with the following restrictions (in part):
     No account expiration
     2 Concurrent Logins
     Disk restriction of 512 K on the SYS volume

2)   The template matching user DOEJ during the add run has the following 
restrictions (in part):
     Account expiration of 1/1/95
     No Limit to the number of concurrent logins
     Disk restriction of 2048 K on the SYS volume

Result:  User DOEJ will have the following restrictions (in part) after being 
modified:
     No account expiration (from #1)
     No Limit to the number of concurrent logins (from #2)
     Disk restriction of 2048 K on the SYS volume (from #2)

NOTE:
The algorithm used to modify accounts while adding is different than the 
algorithm used with the "Modify" menu items.  The "Modify" menu items do 
not compare restrictions, but force the account restrictions to be the restrictions 
you specify.  Thus, you can modify existing accounts in two different ways by 
either using the "Modify" menu items or by doing an Add Run and specifying 
the "Apply Template" option.

4.6  Type of Run Options--Adding

 

MUM will show you exactly the data it is working on and tell you if it 
encounters an error in the text file format.  This may go by quite rapidly, so you 
can view the error report log (ErrorLog.rpt) afterwards to see what error's were 
associated with which users.

If you choose the "Mock Run" option, MUM will run continuously and show 
you data it read for each user in the text file showing you the data read as well 
as the user name and password created or found.  If there is an error in the text 
file, MUM will tell you exactly what the error is so you may fix the problem.  
The Created.rpt, NotCreat.rpt and Modified.rpt reports will also be filled with 
data for the users in the text file, but accounts will NOT be created or modified 
for the users.

Note: The Mock Run does not verify information in the template.  The Mock 
Run only checks the input text file (exactly as the VTFILE.EXE utility).

If you choose the "Add New Users" option, MUM will run continuously and 
show you data it read for each user in the text file showing you the data read as 
well as the user name and password created or found.  If there is an error in the 
text file, MUM will tell you exactly what the error is so you may fix the 
problem.  The Created.rpt, NotCreat.rpt, and Modified.rpt reports will also be 
filled with data for the users in the text file, and accounts will be created and 
modified (if selected) for the users.

4.7  Text File Format for Adding Users

Text files utilized to add users should use either tabs, commas or spaces as 
delimiters and include at least the following fields (in this order):

     1)   Last Name
     2)   First Name
     3)   Middle Name
     4)   Department identifier
     5)   User name      -- optional
     6)   Password       -- optional
     7)   Extra Data          -- optional

The fields can be separated by tabs, commas or a number of spaces.  You can 
enter blank fields when delimiting with tabs or commas, but the field still needs 
to be there.  For example, if John Doe does not have a middle name and you are 
delimiting with commas, your text file could look like the following:

     Doe,John,,Template Name

If you use tabs instead of commas, make sure there are two tabs between "John" 
and "Template Name" as follows:

     Doe  John      Template Name

WARNING:

You CANNOT enter blank fields when delimiting with spaces.  MUM looks for 
at least the number of spaces you specify to separate fields.  If you have blank 
fields, MUM will end up using erroneous information when adding users.

Templates created using MUM need to be named exactly like the department 
identifier in the text file (see Table 1).  When MUM reads data from the text file 
for a user's department, it looks through the templates loaded and finds a 
matching department identifier.  If a match is not found, MUM will not create or 
modify the account but will put the user's information in the NotCreat.rpt report 
and put an error message in ErrorLog.rpt.

The adding function gives you the option of including a user name for each 
individual. If you want to specify the individual's user name , the 5th column 
should include the user name.

The adding function also gives you the option of including a password for each 
individual.  If you want to specify the individual's password , the 5th column 
should include the password.  If you want to specify the individual's user name 
and password , the 5th column should include the user name, and the 6th 
column should include the password.

If you have a data base that includes more fields than the ones required for 
MUM, you may include these after the standard 4 (or 6--depending on the user 
name/full name and password options) required fields.  The extra data (up to 
512 characters) will be stored and tacked on to the end of output reports but will 
not be used by MUM while generating accounts.

Checking the Text File for Errors

A small utility called VTFile (Verify Text File) is packaged with MUM to help 
managers verify whether the format of their text file is correct.  Just enter 
"vtfile" on the DOS prompt  to see the purpose and format of VTFile.  

The Mock Run option will also show you whether the format of the text file is 
correct.

4.8  Example of Adding Users 'en masse'

Suppose you are charged with managing accounts for all engineering students 
and faculty for a large university.  Each semester you receive an updated list of 
students from which you are to add accounts.  You need to provide different 
restrictions for different departments (See Table 2).  You are posed with the 
problem of:

     1)  Tying users to their correct department groups
     2)  Providing home directories corresponding to departments
     3)  Restricting volume use differently for different departments
     4)  Giving different login scripts for each department
     5)  Giving different account restrictions for each department
     6)  Giving accounts only to students that do not already have an account

You need to do all of this for a large number of students while maintaining all 
these changing accounts!

Table 2.  Requirements for users.

Department Listing  Groups
     Home Directory
     Login Script

Mechanical Engineering   DEVELOP, STUDENT
     USER:STUDENT\ME
     f:\usr\supervis\std.scr

Administration ADMIN, FACULTY
     FAC:ACCTS\ADMIN
     f:\usr\supervis\admin.scr

Sales Group    SALES, PRODUCT_GROUP
     USER:SALES
     f:\usr\supervis\sales.scr

101328 (Major Code) CHEME, GRADUATE, STUDENT
     USER:STUDENT\CHEME
     f:\usr\supervis\std.scr
     

Well, it's MUM to the rescue!  MUM will allow you to create templates to 
define different restrictions for your various group requirements.  Then it allows 
you to add the users using your list of students and faculty, while checking for 
existing accounts.  Later, if you want to change the restrictions for any of your 
groups, MUM will allow you to change them en masse.  You can also delete 
dynamically and generate reports of your users at any time.  Here's how the 
adding works.

MUM allows you to create a template in which you identify your different 
restrictions and requirements.  You need to make a template for each department 
group and name it exactly the same as your text file department listing.  For 
example, from Table 2 we see that we need to make a Mechanical Engineering, 
Administration, Sales Group and 101328 template.  Once the templates are 
generated and saved in a template file, you can add the accounts.  

When MUM reads in data, such as that listed in Table 1 (don't include the 
headings),  it searches the currently loaded template file to find a template 
matching the data in the department field.  Once found, MUM creates a user 
name (if not provided) and adds the user according to the given requirements.  If 
a matching template is not found, the user is not created and an error is 
generated in the ErrorLog.rpt report.

Figure 4.8.1:  Sample2.tmp contains the following templates:  101328, 
Administration, Mechanical Engineering and Sales Group.

 

For example, John Crandall, who is in the sales group, would be assigned to the 
Sales Group template.  The template would link John with the SALES and 
PRODUCT_GROUP groups; he would be given a home directory in the 
USER:SALES directory so that the path to his directory would be something 
like: f:\sales\CRANDALJ.  Similarly, Bruce and Shawn Holmstead would be 
assigned to the Mechanical Engineering template which would link them to ME 
and STUDENT groups.  Their directory paths would look like: 
g:\student\me\HOLMSTEB and g:\student\me\HOLMSTES respectively.

4.9  Personalizing a User name Algorithm

Overview of the User name Algorithm

Since many people like to use varying user name algorithms, we have provided 
a means to customize an algorithm for the creation of user names from a users 
first, middle and last name.


Defining a user name algorithm involves defining:
     1)   the number of characters to use from each name (referred to as name 
fragments)
     2)   the order of the name fragments
     3)   the name fragment replaced if a duplicate name is found (only the first 
character of the selected name fragment is replaced)

To aid in creating a user name algorithm, MUM displays what two sample users' 
user name would look like using the currently defined algorithm.  

The Next User name button will indicate what user name will be used if a 
duplicate user name is found on the system.  The Standard Algorithm button 
sets the user name algorithm to the algorithm used in previous versions of 
MUM.

Defining the Number of Characters in Each Name Fragment

Again, a name fragment is a portion of a given users first, middle and last name.

User names are composed of name fragments from the first, middle and last 
name of the user.  You may have a maximum of 8 characters in the user name, 
so you can decide how many characters of each name to use.

Defining the Order of Name Fragments

Next, you will need to decide what order the name fragments should appear in 
the user name.  Some people prefer the first name fragment at the first of the 
user name and some prefer it at the end.

Order the first, middle and last name fragments with values 1, 2 or 3.  You must 
order all fragments even if you do not intend to use a particular fragment.

Defining the Name Fragment to be Replaced

The Name to be Replaced field indicates which name fragment will be replaced 
if a duplicate user name is found on the system.  If the name fragment indicated 
is longer than one character, only the first character of the fragment will be 
replaced with a new character.

Using the Next User name button will help you get a feel for which character is 
being replaced.

4.10  Running Batch Files

Selecting the Run Batch Files menu item launches a DOS program that takes a 
Created.rpt file as input and executes any batch file associated with what 
department and matching template the user is in.  The batch file will begin in the 
users home directory.

You will need to specify two things:
     1)   identify the Created.rpt file
     2)   identify a drive letter MUM can use temporarily to map a drive to the 
users home directory.  If that drive is already mapped, the current 
mapping will be saved and restored after RunBatDS.exe is finished 
executing.

Note:  Make sure the drive letter specified for MUM to temporarily use is not 
the same drive letter as the one defined in the template identifying the location 
of the batch file.  For example, if you specified the batch file to be at 
f:\users\sales.bat, do NOT use drive F for MUM to temporarily map to the user's 
home directory.  The reason is that MUM maps the root drive to the home 
directory and other directories on that volume might not be accessible.

MUM needs a drive letter to use temporarily to map a drive in order to run the 
batch file and will restore the drive letter to it's original state when finished.  
MUM will map root the drive letter to the user's home directory.  If the home 
directory doesn't exist, MUM will generate and error and will not run the batch 
file.


Your batch file can use assume one input field: %1 for the user name.  A sample 
batch file could be as follows:

     REM Copy Windows files to the user's home directory
     md windows
     cd windows
     xcopy f:\users\setup\windows\*.* *.* /s
     
     REM For testing the batch file, 
     REM put in pause statements to view batch file output pause

     REM Set a user name variable
     SET USERNAME=%1
     

The RunBatDS.rpt report file contains output from the RunBatDS program, but 
does not include output from the actual batch file executed.  You can view the 
RunBatDS.rpt report file using the View menu. 






Part 5:  Deleting Users


5.1  Overview

Mass User Management allows system managers, with supervisory status, to 
delete users in five ways: by file, by group, by individual, by disabled account 
status and by last login status.  MUM will output three text files for you when 
you delete users.  It creates the Deleted.rpt, NotDelet.rpt and ErrorLog.rpt files.  
The Deleted.rpt file lists users that were deleted, the NotDelet.rpt lists users that 
were not deleted and the ErrorLog.rpt reports any errors encountered when 
deleting users.

To delete the user's Home Directory, use the "Delete Directories" option and 
specify the Deleted.rpt file to use as the source file containing the list of 
directories to be deleted.  If the headers and user names are still listed in the 
Deleted.rpt file when you run the "Delete Directories" option, MUM will ignore 
them.

WARNING

If you are not careful, you could destroy your system VERY quickly.  You will 
want to look at the Deleted.rpt file BEFORE running the "Delete Directories" 
option.  MUM will take the given directories and delete the given directory and 
it's tree structure.  MUM will not delete any of NetWares system directories 
(PUBLIC, MAIL, SYSTEM, or ETC).  MUM will delete any other directory.  
This option will delete hidden and read-only files and directories supplied.  

RECOMMENDATION

Back up your entire system before running the "Delete Directories" option.  This 
option is very capable of deleting NDS files and directories, hidden files, read-
only files etc.  Look through the Deleted.rpt file BEFORE running the "Delete 
Directories" option.

IMPORTANT

We recommend running DSRepair quarterly (or after adding or deleting large 
numbers of users) to ensure consistency of replicated DS databases.

5.2  Deleting an Individual User

When the option to delete an individual user is chosen, MUM will prompt you 
for a search criterion to identify the a particular user.  Since some systems have 
many thousands of users, we wanted to alleviate the need to unnecessarily 
display all of the users on your network.  As many of you know this becomes 
very tedious and time consuming.  Instead we will display only the users 
matching the search criterion you enter.  If you want to list all users enter the 
wild card character '*' for the search criterion.  If you want to list all the users 
beginning with B enter "B*" and press Search.  If you know the name of the 
user you wish to delete, you can also enter the user name in the "UserName" 
edit box.


When you have identified the user you wish to delete, press the delete button.  
You will then be given 'Are you sure' prompts to verify your choice.  The user's 
home directory will be saved in a file with the user name as the title.  For 
example, if you delete user DOEJ, the user's trustee directory assignments will 
be saved in a file called DOEJ.RPT.  Use the "Delete Directories" option on this 
file to delete the user's home directory.

5.3  Deleting Members of a Group

Deleting members of a group is as easy as selecting a group name.  MUM will 
generate a report in the Deleted.rpt file that lists the users deleted, and a file 
called NotDelet.rpt that lists users that could not be deleted.

This option supports both real and mock runs.  See Type of Run Options--
Deleting for more details.

5.4  Deleting Disabled Accounts

This option allows the system manager to scan and delete all disabled accounts 
on the network.  Using this option in conjunction with the Modify and Lists 
menus can help managers to identify accounts with certain criterion and disable 
them with the Modify options.  Managers can then use the "Delete Disabled 
Accounts" option to delete the unwanted accounts.

For example, if system managers wanted to delete all users who had not logged 
in for 6 months, they would use the Modify menu to identify users with old 
login dates and disable them.  Then they would use this option to delete those 
disabled accounts.

MUM will generate a report in the Deleted.rpt file that lists the users deleted, 
and a file called NotDelet.rpt that lists users that could not be deleted.

This option supports both real and mock runs.  See Type of Run Options--
Deleting for more details.

5.5  Deleting Expired Accounts

This option prompts you for a date and then searches the server for users with 
account expirations older than the date indicated.  When these accounts are 
found they are deleted.

NOTE:  Users with no expiration dates on their accounts are NOT deleted with 
this option.

MUM will generate a report in the Deleted.rpt file that lists the users deleted, 
and a file called NotDelet.rpt that lists users that could not be deleted.

This option supports both real and mock runs.  See Type of Run Options--
Deleting for more details.

5.6  Deleting Users using a File

To delete using a text file, Mass User Management only requires that the user 
name be listed first and be separated from all other fields by a tab.  All files 
generated by MUM can be used to delete users (ie. All *.rpt files as well as any 
file generated using the Modify or List menu options).  MUM will look for the 
first item on each line and assume it is the user name.  Table 3 illustrates how 
lists generated using MUM can also be used as delete lists.

Table 3.  Sample of data generated from the List Menu.  These lists can be used 
for deleting.

Data for Group: APPS
USERNAME  FULL NAME      ACCT EXP  ACCT DISAB
BRUCE     S. Bruce Holmstead  None Enabled   
SHAWN     Shawn Holmstead     None Enabled   
RON  Ron A McClellan     None Enabled   
JANE Jane Doe  None Enabled   

If you wish to use generated lists for deleting, you should delete the header on 
the file; however, it is not necessary.

If you select a real run, MUM will generate a Deleted.rpt and NotDelet.rpt.  A 
mock run will only generate Deleted.rpt and NotDelet.rpt files but not actually 
delete the user.  

For both types of run, the Deleted.rpt file lists users that were (or would have 
been) deleted along with any extra data that was included in the text file MUM 
read in.  It will also list the deleted users trustee directories.  The NotDelet.rpt 
file lists users that could not be deleted along with any extra data that was 
included in the text file used to delete.

5.7  Deleting Directories

To delete the user's Home Directory, use the "Delete Directories" option and 
specify the Deleted.rpt file to use as the source file containing the list of 
directories to be deleted.  If the headers are still listed in the Deleted.rpt file 
when you run the "Delete Directories" option, MUM will ignore them.

WARNING

If you are not careful, you could destroy your system VERY quickly.  You will 
want to look at the Deleted.rpt file BEFORE running the "Delete Directories" 
option.  MUM will take the given directories and delete the given directory and 
it's tree structure.  MUM will not delete any of NetWares system directories 
(PUBLIC, MAIL, SYSTEM, or ETC).  MUM will delete any other directory.  
This option will delete hidden and read-only files and directories supplied.  

RECOMMENDATION

Back up your entire system before running the "Delete Directories" option.  This 
option is very capable of deleting NDS files and directories, hidden files, read-
only files etc.  Look through the Deleted.rpt file BEFORE running the "Delete 
Directories" option.

IMPORTANT

We recommend running DSRepair quarterly (or after adding or deleting large 
numbers of users) to ensure consistency of replicated DS databases.

5.8  Type of Run Options--Deleting

MUM allows system managers to do a real or mock run for deleting users.  

If you choose the "Mock Run" option, MUM will run continuously through the 
users, showing you the user it is processing along with the user's home 
directory.  MUM will alert you of any errors it encounters.  A mock run will 
generate Deleted.rpt and NotDelet.rpt files indicating users that would have 
been deleted as well as users that could not be deleted.

If you choose the "Real Run" option, MUM will run continuously through the 
users, showing you the user it is processing along with the user's home 
directory.  MUM will alert you of any errors it encounters.  Any errors will 
appear in the Errorlog.rpt file, while all other information concerning users 
deleted and not deleted will be reported in the Deleted.rpt and NotDelet.rpt files.


Part 6:  Modifying User Restrictions


6.1  Overview

Mass User Management allows system managers to modify restriction for: an 
individual user, all users in a context, members of a certain group, users with old 
expiration dates, users with old login dates, users with disabled accounts, and 
users in a text file.  For all options, output may be displayed to the screen or 
saved to a file.  See User Restrictions that can be Modified for a detailed list of 
restrictions.  Any fields left blank will not be changed.

Instead of having to enter account restrictions each time you modify, you may 
select a template of restrictions and then customize those restrictions to fit your 
immediate need for modifying users.

Output files generated by the modify menu options are all delineated by tabs and 
can therefore be imported into any database, spreadsheet or word processing 
program.  This feature allows managers to closely integrate system database 
files with network users to generate graphs or reports on system usage.

6.2  User Restrictions that can be Modified

The Current Settings windows reflects a summary of the account restrictions for 
the current template.  To edit these restrictions choose the appropriate button in 
the Edit Settings section of the window.

Note: Any field left blank will not be modified.

Account Expiration Date:
     Enter the month, day and year you wish the account expiration date to be 
changed to or check the "No Expiration" box to make the accounts have no 
expiration date.  You can also enter the number of days before the account will 
expire, and MUM will determine the appropriate expiration date.  The "Days 
Before Account Expires" is not saved anywhere in NDS information -- it is only 
for convenience while running MUM.  Only the "Account Expiration Date" or 
"No Expiration" fields are saved in NDS information.

Enable/Disable/Remain Same Buttons:
     Check whether to enable or disable the account (default is to remain same).  
If you choose "Remain Same", the account status will remain the same as it is 
currently configured for each user.

Account Balance:
     Enter the amount to set the account balance to (-99,999,999 to 99,999,999).  
Make sure accounting is set up on the server before modifying the account 
balance.

Account Low Limit:
     Enter the amount to set as the account low limit (-99,999,999 to 
99,999,999) or check the "Unlimited" check box to allow unlimited credit.  
Make sure accounting is set up on the server before modifying the account low 
limit.

Add to Balance:
     Enter the amount to add to the user's current account balance (-99,999,999 
to 99,999,999).  Make sure accounting is set up on the server before modifying 
the account balance.

Change Password:
     You may change the password if you are modifying an individual user.  
Press the "Change  Password" button and then enter the new password.  Retype 
the password to make sure you entered the correct password.

Require Password:
     Check the "Require Password" check box to force the users to have a 
password.  If the users are not forced to have a password, they may still have a 
password however.

Minimum Password Length:
     Enter the minimum length of login passwords (1-20).

Unique Passwords Required:
     Check the "Unique Passwords Required" check box to force the users to 
supply a unique password when they change their password.

Require Periodic Change:
     Check the "Require Periodic Change" check box to force the users to 
supply a new password periodically.  The length of this period is defined in the 
"Days Between Change" edit box.

Days Between Change:
     Enter the number of days between forced password changes.  When you 
enter the number of days between changes, the password expiration date is 
automatically calculated for you.  You can un-check the "Require Periodic 
Change" check box to make the password never expire.

Password Expiration Date:
     Enter the month, day and year you wish the password to expire or un-check 
the "Require Periodic Change" box to make the password never expire.  The 
password expiration date does not have to match the "Days Between Change" 
edit box.  You can set the password to expire earlier or later than the "Days 
Between Change".  Once the password has expired, the "Days Between Change" 
will calculate the next password expiration date.

Maximum Connection:
     Enter the number of connections a user may simultaneously login (1-200) 
or check the "Unlimited" box to allow an unlimited number of connections.

Grace Logins Allowed:
     Enter the number of logins allowed (after the password has expired) to 
change the password before the account is disabled (1-20) or check the 
"Unlimited" box to allow unlimited logins after the password has expired.

Grace Logins Remaining:
     Enter the number of logins remaining to change the password (1 to Grace 
Logins Allowed).

Volume Restrictions:
     Highlight the volume name and press "Edit" to set the space restriction for 
that volume.  Indicate whether or not to limit space; if space is limited, indicate 
the limitation.  

Show Restrictions in Sub-contexts:
     If enabled, check the "Show Restrictions in Sub-contexts check box to 
show any volume restrictions for that user in all contexts below the current 
context.  By default this is unchecked.  Checking this option may take several 
minutes depending on the number of sub-contexts below the current context.


Groups Belonged To:
     The "Groups Belonged To" are shown on the left list box, and the other 
"Available Groups" are displayed on the right list box.  To make the users 
belong to a group displayed in the "Available Groups", either highlight the 
group in the "Available Groups" list box and press the "Insert" button or double 
click on the group.  To remove a group from the "Groups Belonged To", either 
highlight the group and press the "Delete" button or double click on the group.

Remove Other Groups Belonged To:
     Check the "Remove Other Groups Belonged To" check box to make the 
users only belong to the groups you specify.  If you do not check the "Remove 
Other Groups Belonged To" check box, the groups shown in the "Groups 
Belonged To" list box will be added to the user's list of groups belonged to.  For 
instance, if you want to make sure the users you are modifying are in the APPS 
group, double click on the APPS group in the "Available Groups" list box so the 
group is displayed in the "Groups Belonged To" list box.  By leaving the 
"Remove Other Groups Belonged To" check box unchecked, the users modified 
will belong to all groups they previously belonged to plus be added to the APPS 
group.

Create Group:
     MUM gives you the ability to create a new group on the fly.  Just press the 
"Create Group" button and enter the new group name.  The recently created 
group will then appear in the "Available Groups" list box.

6.3  Modifying an Individual User

When the option to modify an individual user is chosen, MUM will prompt you 
for a search criterion to identify the a particular user.  Since some systems have 
many thousands of users, we wanted to alleviate the need to unnecessarily 
display all of the users on your network.  As many of you know this becomes 
very tedious and time consuming.  Instead we will display only the users 
matching the search criterion you enter.  If you want to list all users enter the 
wild card character '*' for the search criterion.  If you know the name of the user 
you wish to modify, you can also enter the user name in the "UserName" edit 
box.

When this option is selected, managers are given a choice of which field they 
would like to change and whether to print to the screen or to a file.  Fields that 
are left blank will not be modified.  When OK is pressed, MUM will modify the 
user specified.


6.4  Modifying All Users in a Context

When this option is selected, managers are given a choice of which field they 
would like to change and whether to print to the screen or to a file.  Fields that 
are left blank will not be modified.  When OK is pressed, MUM will modify all 
user restrictions to those that are indicated.

Note:  The ADMIN user will not be modified.  The only way to modify the 
ADMIN user is to modify an individual user and select the ADMIN user.

6.5  Modifying Members of a Group

When this option is selected, managers are prompted for which group to modify.  
They are then taken to the standard modify dialog where they're given a choice 
of which field they would like to modify and whether to print to the screen or to 
a file.  Fields that are left blank will not be modified.  When OK is pressed, 
MUM will change user restrictions for the group indicated.

Note:  The ADMIN user will not be modified.  The only way to modify the 
ADMIN user is to modify an individual user and select the ADMIN user.



6.6  Modifying Users by Expiration Date

When this option is selected, managers may identify an expiration date to search 
for.  All accounts in the context with expiration dates older than the date 
indicated will be modified according to specifications identified in the "Enter 
New Restrictions" dialog.  Users with no expiration date will not be modified.  
Fields left blank in this dialog will not be modified.  When OK is pressed, MUM 
will modify user restrictions with expiration dates older than the date prompted 
for to the new restrictions.

Note:  The ADMIN user will not be modified.  The only way to modify the 
ADMIN user is to modify an individual user and select the ADMIN user.

6.7  Modifying Users by Login Date

When this option is selected, managers may identify a last login date to search 
for.  All accounts in the context with last login dates older than the date 
indicated will be modified according to specifications identified in the "Enter 
New Restrictions" dialog.  Users who have never logged in will be modified.  
Fields left blank in this dialog will not be modified.  When OK is pressed, MUM 
will change user restrictions with last login dates older than the date prompted 
for to the new restrictions.

Note:  The ADMIN user will not be modified.  The only way to modify the 
ADMIN user is to modify an individual user and select the ADMIN user.

6.8  Modifying Disabled User Accounts

When this option is selected, managers may modify all disabled accounts in the 
context.  Managers are then taken to the standard modify dialog where they're 
given a choice of which field they would like to change and whether to print to 
the screen or to a file.  Fields that are left blank will not be modified.  When OK 
is pressed, MUM will change user restrictions for the users in the text file 
indicated.

Note:  The ADMIN user will not be modified.  The only way to modify the 
ADMIN user is to modify an individual user and select the ADMIN user.

6.9  Modifying Users Listed in a File

When this option is selected, managers may identify a text file containing user 
names to be modified.  The text file must list each user name on a separate line.  
All list files generated using MUM may be used, as well as any of the report 
(*.rpt) files.  When the text file is selected, managers are then taken to the 
standard modify dialog where they're given a choice of which field they would 
like to change and whether to print to the screen or to a file.  Fields that are left 
blank will not be modified.  When OK is pressed, MUM will change user 
restrictions for the users in the text file indicated.


Part 7: Listing User Restrictions


7.1  Overview

Mass User Management allows system managers to generate restriction 
information for: an individual user, all users, members of a certain group, old 
expiration dates, old login dates, disabled accounts, and users in a text file.  For 
all options, output may be displayed to the screen or saved to a file.  See User 
Restrictions that can be Displayed for a detailed list of restrictions.

Output files generated by the lists menu options are all delineated by tabs and 
can therefore be imported into any database, spreadsheet or word processing 
program.  This feature allows managers to closely integrate system database 
files with network users to generate graphs or reports on system usage.

7.2  User Restrictions that can be Displayed

Press the "Select All Restrictions" button to easily check all check boxes.  Press 
the "Clear All Restrictions" button to easily un-check all check boxes.

Full Name:
     The users full name.

Account Expiration Date:
     The month, day and year the account expires.

Account Disabled/Enabled:
     Whether the account is enabled or disabled.

Account Balance--Low Limit:
     The account balance and low limit for the users.

Password Required:
     Whether the account is forced to have a password.

Password Expiration Date:
     The month, day and year the password expires.

Minimum Password Length:
     The minimum length of login passwords.

Days Between Password Change:
     The number of days before the password is forced to change.

Unique Passwords Required:
     Whether unique passwords are required when a user changes their 
password.

Maximum Connection:
     The number of connections a user may simultaneously login to.

Grace Logins Allowed:
     The number logins allowed (after the password expired) to change the 
password before the account is disabled.

Grace Logins Remaining:
     The number of logins remaining to change the password.

Volume Restrictions/Space in Use:
     The volume restrictions for each volume on the server as well as the disk 
space in use on each volume for the individual users.

Search Sub-contexts:
     Check this check box to have MUM search all sub-contexts under the 
current context for volume restrictions.  Searching sub-contexts could add 
substantial time to the list run depending on the number of sub-contexts below 
the current context.

Groups Belonged To:
     All of the groups the user belongs to.

 

7.3  Generating Reports for an Individual User

When the option to generate a report for an individual user is chosen, MUM will 
prompt you for a search criterion to identify the a particular user.  Since some 
systems have many thousands of users, we wanted to alleviate the need to 
unnecessarily display all of the users on your network.  As many of you know 
this becomes very tedious and time consuming.  Instead we will display only the 
users matching the search criterion you enter.  If you want to list all users enter 
the wild card character '*' for the search criterion.  If you know the name of the 
user you wish to view, you can also enter the user name in the "UserName" edit 
box.

When this option is selected, managers are shown the standard modify dialog.  
However, all buttons to modify the account are disabled.  The manager can only 
view the account restrictions for the selected user.

7.4  Generating Reports for All Users in a Context

When this option is selected, managers are given a choice of which field they 
would like to display and whether to print to the screen or to a file.  Restrictions 
that are not checked in the "Choose Restrictions" dialog will not be included.  
When OK is pressed, MUM will generate user restrictions for all users.

7.5  Generating Reports Lists for a Group of Users

When this option is selected, managers are prompted for a group.  They are then 
taken to the standard dialog where they are given a choice of which field they 
would like to display and whether to print to the screen or to a file.  Restrictions 
that are not checked in the "Choose Restrictions" dialog will not be included.  
When OK is pressed, MUM will change user restrictions for the group 
indicated.

7.6  Generating Reports by Expiration and Login Dates

When this option is selected, managers may identify an expiration date (or a 
login date) to search for.  All accounts in the context with expiration dates (or 
last login dates) older than the date indicated will be displayed according to 
specifications identified in the "Choose Restrictions" dialog.  Users with no 
expiration date will not be displayed.  However, users who have never logged in 
will be displayed.  Restrictions that are not checked in the "Choose Restrictions" 
dialog will not be included.  When OK is pressed, MUM will display user 
restrictions for users with expiration dates (or last login dates) older than the 
date prompted for.

7.7  Generating Reports for Disabled User Accounts

When this option is selected, managers may get a list of disabled accounts in the 
context.  Managers are taken to the standard dialog where they're given a choice 
of which field they would like to display and whether to print to the screen or to 
a file.  Restrictions that are not checked in the "Choose Restrictions" dialog will 
not be included.  When OK is pressed, MUM will generate user restrictions for 
the users listed in the text file indicated.

7.8  Generating Reports for Users Listed in a File

When this option is selected, managers may identify a text file containing user 
names to generate lists for.  The text file must list each user name on a separate 
line.  All list files generated using MUM may be used, as well as any of the 
report (*.rpt) files.  When the text file is selected, managers are then taken to the 
standard dialog where they're given a choice of which field they would like to 
display and whether to print to the screen or to a file.  Restrictions that are not 
checked in the "Choose Restrictions" dialog will not be included.  When OK is 
pressed, MUM will generate user restrictions for the users listed in the text file 
indicated.


Part 8:  Viewing Report Files

8.1  Overview

Mass User Management allows system managers to easily view the report files 
generated by MUM or any ASCII text file.  Below is a list of the files you can 
view with MUM and a short explanation of each file:

Users Created:
     Displays the Created.rpt file showing all users created during the last real or 
mock adding run.  This file contains the user name, last name, first name, 
middle name, department identifier, password, server name, and any extra data.

Users Not Created:
     Displays the NotCreat.rpt file showing all users not created during the last 
real or mock adding run.  View the "Error Report" to see why these users were 
not added.  This file contains the user name, last name, first name, middle name, 
department identifier, password, server name, and any extra data.

Users Modified during Add:
     Displays the Modified.rpt file showing all users whose accounts were 
modified during the last real or mock adding run.  View the "Error Report" to 
see if there were any errors modifying these accounts.  This file contains the 
user name, last name, first name, middle name, department identifier, password, 
server name, and any extra data.

Batch File Report:
     Displays the RunBatDS.rpt file showing the messages generated by 
RUNBATDS.EXE during the last batch file run.  The RunBatDS.rpt file does 
not show what the actual batch file did however, only status and error messages 
generated by RUNBATDS.EXE.  To view the output of the actual batch file, put 
pause messages in the batch file at key points so you can read the output.  Once 
the batch files are running the way you want them to, make sure to remove these 
pause messages to allow the batch files to run without waiting for you to press a 
key.

Users Deleted:
     Displays the Deleted.rpt file showing all users deleted and their home 
directories during the last real or mock deleting run.  This file contains the user 
name and that user's home directory.  Use the "Delete Directories" option to 
delete the user's home directory (and their files).

Users NOT Deleted:
     Displays the NotDelet.rpt file showing all users not deleted during the last 
real or mock deleting run.  This file contains the user name of the users not 
deleted.  View the "Error Report" to see why these users were not deleted.

Deleted Directories:
     Displays the DelDirs.rpt file showing all home directories (and their files) 
deleted during the last delete directories run.  View the "Error Report" to see if 
any errors occurred during the delete directories run.

Modify/List Report:
     Displays the General.rpt file containing the data generated during the last 
modify or list run.  A subsequent modify or list run will overwrite this file.  
View the "Error Report" to see if any errors occurred during the modify or list 
run.

Error Report:
     Displays the ErrorLog.rpt file containing any errors and a possible 
explanation that occurred any time during program execution.  This file is 
overwritten every time any kind of run is executed, so only the most recent error 
messages are displayed.  If an error occurred outside of a run (such as when 
creating a group or changing a password), you are generally given the option to 
view the error log.

A File:
     Displays any ASCII text file.  You are given a browse dialog to help you 
choose the file you would like to view.

8.2  Controls While Viewing Files

When viewing any files with MUM, you are given a standard set of controls.  In 
the bottom right corner of the dialog shows the current page out of the total 
number of pages (such as Page 3/5).  If there is more than one page, the 
following controls are available for use:

Button Controls:
Prev Takes you to the previous page.
Next Takes you to the next page.
Beg  Takes you to the first page.
End  Takes you to the last page.
Goto Gives you the option to go to any page you specify.




Part 9:  Getting Help


9.1  How to Get Help With MUM

If you have any questions about how MUM works, there are three ways you can 
get help:

1.   You can e-mail us at: techsupport@enmasse.com.  We generally try to 
answer all e-mail questions the same day.

2.  Visit our World Wide Web (WWW) site at http://www.enmasse.com/ to 
see answers to common problems.

3.   You can write to us at:

          Enmasse, LLC
          P.O. Box 50452
          Provo, UT 84605-0452

4.   You can call our technical support staff at:  (801) 763-8244.



Appendix:

10.1  Sample data files for adding

The following tables are from database or spreadsheet data:

Table 1A:  Standard fields required.

Last Name First Name     Middle    Department (Template name)
Holmstead S.   Bruce     Development
Holmstead Shawn     Matthew   Development
McClellan Ron  A    Marketing
Crandal   John H.   Sales Group
Doe  Jane      Tech Support

Table 2A:  Fields required for the username option.

Last Name First Name     Middle    Department     User name
Holmstead S.   Bruce     Development    bruce
Holmstead Shawn     Matthew   Development    shawn
McClellan Ron  A    Marketing ron
Crandal   John H.   Sales Group    john
Doe  Jane      Tech Support   jane

Table 3A:  Fields required for the fullname option and password supplied option 
combined.

Last Name First Name     Middle    Department     Password
Holmstead S.   Bruce     Development    bruce234
Holmstead Shawn     Matthew   Development    shawn234
McClellan Ron  A    Marketing ron234
Crandal   John H.   Sales Group    john234
Doe  Jane      Tech Support   jane234

Table 4A:  Fields required for the username option and password supplied 
option combined.

Last Name First Name     Middle    Department     User name Password
Holmstead S.   Bruce     Development    bruce     bruce234
Holmstead Shawn     Matthew   Development    shawn     shawn234
McClellan Ron  A    Marketing ron  ron234
Crandal   John H.   Sales Group    john john234
Doe  Jane      Tech Support   jane jane234


