Category : Network Files
Archive : MASSUSR2.ZIP
Filename : MASSUSER.HLP
Output of file : MASSUSER.HLP contained in archive : MASSUSR2.ZIP
ÿÿ ÿ¡ øûÿûÿûÿûÿûÿûÿû ûÿûÿûÿûÿûÿû ÿÿü ÿ ûøûÿûÿûÿûÿûÿûÿ ÿ ÿ ÿÿ ÿ¡ øûøûÿûÿûÿûÿûÿû ûÿûÿûÿûÿûÿû ÿÿü ÿ ûúûÿûÿûÿûÿûÿ
ÿÿü ÿ øúøûÿûÿûÿûÿû ûÿûÿûÿûÿûÿû ÿÿú ÿ ûúûøûÿûÿûÿûÿ ÿû ÿ ÿ ÿÿ ÿ¡ øûøûøûøûÿûÿûÿû ûÿûÿûÿûÿûÿû ÿÿû ÿ ÿÿ ÿ ÿûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿû ÿ ÿ ÿ ÿ ÿûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿû ÿÿ ÿ ûÿ ÿÿ ÿÿ ÿ¢ ÿ þúþúþúþúþúþúþúþúþúþúþú û ÿÿ ÿüúþú üúüþúüÿÿ ÿüüüþüüüüþüüúüüÿ ÿüüúüüüüúüüüüÌ ÿüüüüüüüþüüüüüüÎ ÿüüüüüüþüüüüüüü| ÿüüüüü üúüüüüüüüü| ÿüüüüü¢üþüüüüüüüüw ÿüüüüüüúüüüüüüÌ ÿüüüüüüüüüü ÿüüþüüüüüüü ÿüüþúüüüüúüüþüüÿ ÿüþúþ
üúþúüúþü ÿÿ« ÿ¡ û úþúþúþúþúþúþúþúþúþúþúþ ÿ ÿÿ ÿ ÿÿ ÿû ÿÿ ÿ¡ ûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿûÿ ÿÿ¿ ÿ ÿ !ÿ¿ / & ;) z4 ÿÿ
ÿÿÿÿbm0 |CTXOMAP ¥ |FONT µ |KWBTREE |KWDATA H |KWMAP y |SYSTEM þ |TOMAP Ø |TOPIC 4 |TTLBTREE ¹
TMP \ \ . \ .exe .cmd .bat .com ?* ./\ dG7DB>2ðBB2ÔAF2ÂBJ2æKN2 ÿÿÿÿÐC -
] ] EEE50 P 0PX 000WP `````` ppxxxx (null) ®" 7®"è2®"ì2®"ð2®"ô2®"ø2 e+000 010203040506070809101112M61xx ÿÿ ; Z x µ Ô ó 0Nmÿÿ : Y w ´ Ó ò /MlTZ PST PDT p p33t3,8SunMonTueWedThuFriSat JanFebMarAprMayJunJulAugSepOctNovDec 1#SNAN1#QNAN1#INF1#IND 1#SNAN1#QNAN1#INF1#IND 2 f$ à7yÃAC üÿÿÿÿÿÿþCÿÿÿÿÿÿï error: megasort: could not open %s.
error: Out of memory.
Out of memory.
Out of memory.
meg error: Out of memory.
w
Out of disk space. error: Out of me6 - l Ó°+,K }I( KàGáW
àG°áW5è ¤õ õ ÿÿÿÿ ÿÿÿÿ- - ! ÿÿ Introduction@ - @ ( " &K õ ÿ MASS USER MANAGEMENT 4
@ 4 * & &K ÿ (MUM) û ³ 4 û H b &K õ á3 ÿ Finally, there's a MUM to clean-up after you at work! by Bruce and Shawn Holmstead Holmstead Partners, Copyright (c) 1992. All Rights Reserved. Ordering Information ? â û ? ] &K á á á á á á$ á+ á1 ÿ Program Description and Changes in Version 1.2 Command Line/Batch File Usage Template Information Adding Users Deleting Users Modifying User Restrictions Generating Lists of User Restrictions List of Menus ( ? ( % &K õ ÿ 4 ( 4 ! Program DescriptionC 4 C + ( &K õ ÿ Program Description å ´ C å 1 4 &K ÿ Mass User Management (MUM) facilitates the management of four critical areas system managers frequently encounter. These include adding, deleting, updating and monitoring user accounts. You must be a SUPERVISOR equivalent for Mass User Management to function properly. Certain information in the bindery can only be accessed by a SUPERVISOR equivalent. Mass User Management will allow system managers to do the following: S å S C X &KPsH á á á$ ÿ 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. 2) Delete users from a text file listing usernames, a certain group, disabled accounts and expired accounts. 3) Modify user restrictions for all users, 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. v - S I d &KPsH á+ ák ¾ ÿ 4) Generate Lists of user restrictions for all users, 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. Changes in Version 1.2: 1) The password options have been expanded to allow supervisors to provide their own passwords while adding users. An additional password field can now be included in the text file used to add accounts. Previously, supervisors could only provide a username. See Password Options for more information. ì 1 4 &KPsH á! ÿ 2) Under the "Delete" menu, a menu item entitled "Delete Directories" was added to allow supervisors to delete ALL trustee directory assignments of users that were deleted using MUM. This option will delete the trustee directories, their files, and sub directories. Note that this option will delete all files including hidden and read only files in the Trustee Directories given. We recommend using caution when using this new option. See Deleting Directories for more information. N N @ R &KPsH á# á% ÿ 3) Under all deleting options, supervisors can now execute a mock deleting run. This can be used to get a listing of trustee directory assignments (since the deleting options generate a list of trustee directory assignments of the deleted users). See Type of Run Options--Deleting for more details. 4) Under all menu items on the "Modify" menu, supervisors can now modify user's account balance and low limit or add to the current account balance. See User Restrictions that can be Modified for more information. ¾ { N Ê C X &KPsH á% á, á, ÿ 5) Also under all menu items on the "Modify" menu, supervisors can now modify user's volume restrictions for any or all volumes. See User Restrictions that can be Modified for more information. 6) Under all menu items on the "Lists" menu, supervisors can now display] « user's current account balance and low limit. See User Restrictions that can be Displayed for more information. 7) Also under all menu items on the "Lists" menu, supervisors can now display user's current volume restrictions and current disk space in use for all volumes on the server. See User Restrictions that can be Displayed for more information. » Ê F ^ &KPsH ÿ 8) MassMode (MassUser's child program) has a completely new user interface that facilitates error checking and keeps supervisor's completely informed of MUM's progress. 9) Some general bug fixes involving file sharing between MassUser and MassMode . 10) Some general bug fixes involving displaying windows on the "Modify" and "Lists" menus. 11) Help buttons have been added to all dialog boxes to allow easy access to on-line help. % % " &K ÿ > % > ! G 0 1 Command Line-Batch File Usage ] > 6 > &K ÿ Command Line/Batch File Usage Mass User Management has the capability of performing various core functions in DOS mode. Descriptions of the command line arguments of MUM's child process, MassMode are detailed below. Command line arguments are listed for MUM's adding and deleting capabilities. Why MUM drops to DOS to perform operations: ñ © ý H b &KP s ÿ 1) One reason MUM drops into DOS to perform network operations is to allow system managers to add and delete users from a batch file. Managers who have their templates created and need to add or delete users on a regular basis can make the appropriate calls to MassMode without having to run MassUser each time. 2) Another reason MUM drops to DOS is so that it can be more backwards compatible with older versions of NetWare. Mass User Management uses Novell's utility MakeUser in a dynamic way to add users. Because the NetWare utility MakeUser is available with NetWareÙ l versions 2.11 and up, MassUser will provided needed service to more versions of NetWare. + ý + ' &KP s ÿ ù Å + ù 4 : &K ÿ MassMode format for ADDING USERS: MassMode can add users given the following command line arguments: a1 NONE filename accounts password run template_name Description of arguments: / È ù / g &K HÕ ÿ Argument Meaning a1 Adding code NONE Put any character into this field filename The name of the text file to add users from accounts Generate Accounts Option: 1 = Username option 0 = Full name option password Generate Password Option: 2 = Password Provided 1 = Same as Username 0 = Password Algorithm run Type of Run Option: 1 = Mock Run 0 = Real Run template_name Name of the template file to use to add users R * / R ( " &K HÕ ÿ NONE Put any character into this field T " R T 2 6 &K Õ ÿ Example: f:> massmode a1 0 students.add 1 1 0 winter.tmp NOTE: Mock runs will be automatically paused while in MassMode ; system managers can then choose to step through the run or allow it to run continuously. Real runs will not be paused unless a key is pressed while running. Ë T Ë 0 2 &K ÿ MassMode format for DELETING USERS: MassMode can delete users from several different username sources given the following command line arguments:  9 Ë ß ä &K ±çe=Í]í} ÿ Username Source d# group filename month day year run a file d1 NONE filename_d1 NONE NONE NONE run a group d2 group NONE NONE NONE NONE run disabled accounts d3 NONE NONE NONE NONE NONE run expired accounts d4 NONE NONE month day year run delete directories d5 NONE filename_d5 NONE NONE NONE NONE XXXXXXXXXXXXXXXXX- ( ß ( % &K Õ ÿ > ( > " &K ÿ Description of arguments: ( > ( % &K Õ ÿ µ q ( µ D Z &KPÕ/~HÕ ÿ Argument Meaning d# Deleting code group Group to use to delete from filename_d1 The name of the text file containing users to be deleted filename_d5 The text file (usually DELETED.RPT) containing paths of directories to be deleted. month The month to use for expired accounts day The day to use for expired accounts year The year to use for expired accounts ¯ x µ ¯ 7 @ &K HÕ ÿ run Type of Run Option: 1 = Mock Run 0 = Real Run (The default is Real Run if this field is left blank.) V * ¯ V , * &KPÕ/~HÕ ÿ NONE Put any character into this field f V f M l &K Õ ÿ Examples: Mock Runs f:> massmode d1 0 students.add 0 0 0 1 f:> massmode d2 faculty 0 0 0 0 1 f:> massmode d3 0 0 0 0 0 1 f:> massmode d4 0 0 12 31 91 1 f:> massmode d5 0 deleted.rpt 0 0 0 1 Real Runs f:> massmode d1 0 students.add f:> massmode d2 faculty f:> massmode d3 f:> massmode d4 0 0 12 31 91 NOTE: Mock runs will be automatically paused while in MassMode ; system managers can then choose to step through the run or allow it to run continuously. Real runs will not be paused unless a key is pressed while running. ( f ( % &K Õ ÿ - ( - !
Adding Users7 - 7 ' &K ÿ Adding Users æ 7 ) 7 @ &K à2 ÿ How MUM Adds Users: Mass User Management allows you to use a text file, similar to the format indicated in Table 1 , to generate accounts. The text file is just an ASCII file created from database, spreadsheet or word processing programs, and uses TABS to delineate categories. MUM uses a template to connect server groups and restrictions to the department references in the tex& F& â% t file. The template allows you to define which server groups the user belongs to; it allows you to specify volume restrictions, home directory locations, login scripts to use, and account restrictions. MUM uses the Novell utility MakeUser in a dynamic manner to actually add the users, so it is important that this utility be in your public folder. % ) % " &K ÿ s L % s ' &KP s ÿ NOTE: There are some programs that will not save tabs in an ASCII file. a : s a ' &KPÈ:H ÿ - Some of the editors that do NOT save tabs include: O & a O ) $ &KPs ÿ MS DOS 5.0 Editor and WordPerfect. d = O d ' &KPÈ:H ÿ - Some of the known programs that will save tabs include: X d ) $ &KPs ÿ Most spreadsheets and data base programs, Windows NotePad, WordPerfect's PEdit, etc. p C p - , &KPÈ:H á ÿ See Text File Format for Adding Users for more information. s F p s - , &K ÿ Table 1 . Database or Spreadsheet data: (delimiters are tabs) & s ^ &K رeÉ ÿ Last Name First Name Middle Department (Template name) Holmstead S. Bruce Mechanical Engineering Holmstead Shawn Matthew Mechanical Engineering Benzley Steve Administration McClellan Ron A CAEDM Faculty Doe John Henry Sales Group Doe Jane Sales Group Brown Mary Jane Marketing Group % % " &K ÿ ä % ; H &K ° á á á ÿ When you choose the Add Users from a List Option, you will be given username or full name options , password options and type of run options . When these are selected, indicate which text file to add from and press OK. ) È 5 a á á á á á á á ÿ Related Topics: Text File Format for Adding Users Creating Templates Examples o(. G/ â% f Adding Users Username and Full Name Options Password Options Type of Run Options Viewing Reports : 5 : ! Text File Format (Adding)¿ : ¿ > N &K à2 ÿ Text File Format for Adding Users: Text files utilized to add users should use tabs 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) Username -- optional 6) Password -- optional 7) Extra Data -- optional 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 users department, it looks through the templates loaded and finds a matching department identifier. If a match is not found MUM uses the first template in the list. 3 ¿ 3 % &K ÿ The adding function gives you the option of including a username for each individual. If you want to specify the individual's username, the 5th column should include the username. 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 username and password, the 5th column should include the username, and the 6th column should include the password. k 3 $ &K ÿ 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 username/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. l + ( &KP s ÿ A Note About Text File Format: Certain editors will not save tabs when files are saved as text files. a : m ' &KPÈ:H ÿ - Some of77 Î7 |0 the editors that do NOT save tabs include: O & m O ) $ &KPs ÿ MS DOS 5.0 Editor and WordPerfect. d = O d ' &KPÈ:H ÿ - Some of the known programs that will save tabs include: X d ) $ &KPs ÿ Most spreadsheets and data base programs, Windows NotePad, WordPerfect's PEdit, etc. + + ( " &KP!ã~ ÿ Z + Z : F &K ÿ 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. MUM v1.2 has been dramatically changed when you add users so that it now tells you exactly the data it is processing and tells you when it encounters an error in the text file format. Z Z < J &K á á á ÿ Related Topics: How MUM Adds Users Creating Templates Examples of Adding Users 2 2 ! ÿ Examples (Adding) c 2 ( " &K ÿ Examples of Adding Users: 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: l 1 4 &KP s ÿ -Tieing users to their correct department server groups -Providing home directories corresponding to departments -Restricting volume use differently for different departments -Giving different login scripts for each department -Giving different account restrictions for each department -Giving accounts only to students that do not already have an account ¾ Ê ) $ &K G> ä? <
ÿ You need to do all of this for a large number of students and while maintaining all these changing accounts! Table 2. Requirements for users. â Ê â ^ &K Õ©G ÿ Department Listing Server Groups Home Directory Login Script Mechanical Engineering ME, 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 2 â 2 - , &K ©Y ÿ Û 2 & &K ÿ Well, it's MUM to the rescue! MUM will allow you to created templates to define different restrictions for your various group requirements. Then it allows you to add the users using your list of students, 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. Ë ; H &K ÿ 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. Ü 7 @ &K à2 ÿ 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 username (if not provided) andÃD ÉF < adds the user according to the given requirements. If a matching template is not found, the first template entered is used as the default template. For example, Steve Benzley, who is in administration, would be assigned to the Administration template. The template would link Steve with the ADMIN and FACULTY server groups; he would be given a home directory in the FAC:ACCTS\ADMIN directory so that the path to his directory would be something like: f:\accts\admin\BENZLEYS. 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. ¡ c ¡ > N &K á á á ÿ Related Topics: How MUM Adds Users Text File Format for Adding Users Creating Templates 3 ¡ 3 ! Creating Templates â 3 - , &K ÿ Creating Templates MUM uses a template to connect server groups and restrictions to the department identifier in the text file. The MUM template allows you to define which server groups the user belongs to; it allows you to specify volume restrictions, home directory locations, login scripts to use, and account restrictions. MUM uses the Novell utility MakeUser in a dynamic manner to actually add the users, so it is important that this utility be in your public folder. l ) $ &K à2 ÿ For example, using the text file listed in Table 1 , you will need to make the following MUM templates: ¥ p ¥ 5 < &K ±eÉ ÿ Mechanical Engineering Administration CAEDM Faculty Sales Group Marketing Group (case is not important) i ¥ 7 @ &K á á ÿ Related Topics: Setting Account Restrictions using Templates Text File Format for Adding Users = = ! ¥ Setting Account Restrictions¯ = » ( " &K ¥O âO ¥O ÿ Setting Account Restrictions using Templates: You may set the following parameters for users assigned to the particular template:
Ë »
? P &KPù/~ù ÿ Account Information : Set the expiration date, account balance and account low limit (Make sure accounting is installed on your server before setting account balance and account low limit). Connection Information : Limit the number of connections the users can have. Password Information : If a password is required, set the length; indicate whether or not to require a unique password and indicate whether or not to force a periodic password change. Ý
@ R &KPù/~ù ÿ Groups Belonged To : Assign the users to groups currently existing on the server from which MUM is launched. The group must be in existence. All users will be added to the server group EVERYONE by default. Home Directory : Enter the volume and path for the base directory. The Home Directory will be the base directory plus the username. If the username is DOEJ and USR:STUDENT is indicated as the home directory, the real Home Directory will be: USR:STUDENT\DOEJ c 1 4 &KPù/~ù ÿ Volume Restrictions : Enter the volume name and indicate whether or not to limit space; if space is limited, indicate the limitation. Enter the exact title of the volume (ie. APPS). If a volume is not listed in Volume Restrictions, it will not be limited. For NetWare versions 2.xx, you cannot limit volumes individually; you can only enter the maximum disk space for all volumes collectively. If you are running NetWare versions 2.xx, MUM will take your volume restrictions from the SYS volume definition; if a SYS volume is not defined in the template, disk space will not be limited for any volumes. ' ó 3 4 : &KPù/~ù ÿ Login Script Path : Enter the path name and name of the login script file (ie. F:\USERS\SUPERVIS\login.scr ). ThÄT XW ¥O e login script file is an ASCII text file containing individual login script information for users assigned to the template. ¿ v 3 ¿ I d &K á á á á ÿ Related Topics: Creating Templates Username and Full Name Options Password Options Type of Run Options : ¿ : ! f Username/Fullname Options o : - , &K ÿ Username and Full Name Options: If you choose the " Full Name " option, MUM will check the full name field for every user on the network to see if a matching full name exists. If the full name exists, an account will not be made for that user. If the full name doesn't exist, a unique username will be generated and the account will be added. The generated username will usually be the first seven letters in the last name and the first initial of the first name. If the last name is shorter than seven letters, the username will include the entire last name. For example, Bruce Lee would have a username of LEEB. , ë , A T &K á á ÿ All full names are generated from first, middle and last name text file fields. Full names are converted to capital letters for comparison. If you choose the " Username " option, MUM will use data from the username field in your text file for the username. If the username already exists on the server or if a username is not found in the fifth field of the text file, the user will not be added. Related Topics: Creating Templates Setting Account Restrictions using Templates d . , d 6 > &K á á ÿ Password Options Type of Run Options 0 d 0 ! { PasswordOptionsË 0 × 5 < &K ÿ Password Options: If you choose the " Same as Username " option, MUM will make the passwords identical to the username with one exception. If the username is shorter than the required password length, extra "A" characters will be a°^ à^ °^ dded to the end of the password until the password is the same length as the required password length. (ie. If the username is LEEB and the required password length is six, the actual password will be LEEBAA.) If you choose the " Password Algorithm " option, MUM will generate up to an eight character password using the first four characters of the username and four random numbers. For example, if the username is HOLMSTES, the password will be essentially HOLM8324. If the username is shorter than four characters, the algorithm will use as the entire username plus four random numbers. For example, if the username is LEE, the password will be LEE1234 (4 random numbers). Ã × ? P &K á á ÿ If you choose the " Password Supplied " option, MUM will take the supplied password from the 5th field (or the 6th field if you are also supplying usernames) 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. This option is new to version 1.2. Related Topics: Creating Templates Setting Account Restrictions using Templates r < r 6 > &K á á ÿ Username and Full Name Options Type of Run Options < r < ! Type of Run Options--Adding X < 5 < &K ÿ Type of Run Options--Adding: Both run options have been dramatically changed in version 1.2. MUM will show you exactly the data it is working on and tell you if it encounters an error in the text file format. Pressing "O" for options, while in MUM's child process MassMode , will display the username, password and mode options you selected. It will also display the required fields for that particular operation. If you choose the " Mock Run " option, MUM will step through each user in the text file showing you the data read as well as the username and password created or found. If there is an error+e ge +e in the text file, MUM will tell you exactly what the error is so you may fix the problem. The created.rpt and notcreat.rpt reports will also be filled with data for the users in the text file, but accounts will NOT be created for the users. f < f * & &K ÿ If you choose the " Add New Users " option, MUM will run continuously and show you the data it read for each user as well as the username 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. If you want to step through each user in the text file, press a key to pause MUM's execution (once MUM has dropped to DOS). The created.rpt, notcreat.rpt, and makeuser.rpt reports will also be filled with data for the users in the text file, and accounts will be created for the users. Ô f Ô F ^ &K á á á á ÿ Related Topics: Creating Templates Setting Account Restrictions using Templates Username and Full Name Options Password Options 0 Ô 0 ! Created Reportsj > 0 j , * &K ÿ Viewing Created, Not Created and MakeUser Report Files: t H j , * &K ÿ The MakeUser.rpt report is the information given by Novell's utility MakeUser when users are added or deleted (a MakeUser.rpt report will NOT be made when using the "Mock Run" option) . When users are added, MUM allows you to view those users created and not created. The created.rpt and notcreat.rpt files are generated by MUM each time users are added or a mock run is preformed. System managers wanting to reuse data from the created.rpt should rename the report file before attempting to do another add run. An error will occur if the created.rpt file is selected to be used as the source text file for adding users since a new created.rpt is generated each add run. However, the created.rpt and notcreat.rpt files CAN be used for the Delete, Modify, or Ljl Ôl :l ists options; they can be renamed and then used for the Adding option. 5 5 ! :
Deleting Users IntroK
5 K > N &K á" á" á" ÿ Deleting Users Mass User Management allows system managers with supervisory status to delete users in four ways: by file, by group, by disabled account status and by last login status. MUM will output three text files for you when you delete users. It creates the MakeUser.rpt , Deleted.rpt and Notdelet.rpt files. The MakeUser.rpt file tells if users were actually deleted and reasons why they weren't. The Deleted.rpt file lists users that were deleted and the Notdelet.rpt lists users that were not deleted. é ¶ K é 3 8 &K ÿ To delete the user's Trustee Directory assignments, 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 usernames are still listed in the Deleted.rpt file when you run the "Delete Directories" option, MUM will ignore them. This option is new to version 1.2. 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, it's files, it's sub directories and their files. If the Deleted.rpt file gives the SYS: volume root directory as one of the Trustee Directory assignments to one of the deleted users, IT WILL DELETE THE ENTIRE SYS VOLUME. This option will delete hidden and read-only files and directories supplied (ie. BINDERY files, etc). 4 õ é @ ? P &K ÿ RECOMMENDATION: Back up your entire system before running the "Delete Directories" option. This option is very capable of deleting BINDERY files, hidden files, read-only files etc. Look through the Deleted.rpt file BEFORE running the "Delete DirectoriesÔr ½v Tp " option. IMPORTANT: Since Mass User Management uses Novell's utilitiy MakeUser to actually delete the accounts, and since MakeUser will not re-optimize your bindery, we recommend running Bindfix quarterly to clean up your bindery. ' @ ' $ &K ÿ ¦ l ' ¦ : F &K á á á ÿ Related Topics: Deleting Users using a File Deleting Members of a Group Deleting Disabled Accounts Ä ¦ Ä @ R &K á á! á# á" ÿ Deleting All Expired Accounts Deleting Directories Type of Run Options Viewing MakeUser, Deleted and Not Deleted Reports 5 Ä 5 ! Æ Deleting with a File ê 5 ) $ &K ÿ Deleting Users using a File: To delete using a text file, Mass User Management only requires that the username 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 username. Table 3 illustrates how lists generated using MUM can also be used as delete lists. h , * &K á- ÿ Table 3. Sample of data generated from the Generate Menu . These lists can be used for deleting. A A ) $ &K ©¥ ÿ Data for Group: CAEDM 0 ð A 0 @ R &K !Ñ© ÿ USERNAME FULL NAME ACCT EXP ACCT DISAB DUDE S. Bruce Holmstead None Enabled PUZZLED Shawn Holmstead None Enabled RON Ron A McClellan None Enabled SUPERVISOR CAEDM SUPERVISOR None Enabled SEB Steve Benzley None Enabled À 0
A T &K á" á" á" ÿ 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 , Notdelet.rpt and MakeUser.rpt files. A«} Û~ z mock run will only generate Deleted.rpt and Notdelet.rpt files since no calls will be made to MakeUser . 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. '
' $ &K ÿ N ' 3 8 &K á á ÿ Related Topics: Deleting Members of a Group Deleting Disabled Accounts Ä Ä @ R &K á á! á# á" ÿ Deleting All Expired Accounts Deleting Directories Type of Run Options Viewing MakeUser, Deleted and Not Deleted Reports 1 Ä 1 ! 9 Deleting a Groupà 1 à > N &K á" á" á# ÿ Deleting Members of a Group: Deleting members of a group is as easy as entering the group name. MUM will generate a report in the Delete.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 and is new to version 1.2. See Type of Run Options--Deleting for more details. N à 3 8 &K á á ÿ Related Topics: Deleting Users using a File Deleting Disabled Accounts Ä Ä @ R &K á á! á# á" ÿ Deleting All Expired Accounts Deleting Directories Type of Run Options Viewing MakeUser, Deleted and Not Deleted Reports ; Ä ; ! © Deleting Disabled Accounts¾ ; Ê 7 @ &K á) ÿ 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. ^ $ Ê ^ : F &K á" á" á# ÿ MUM will generate a report in the Delete.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 and is new to version 1.2. See Type of Run Options--Deleting for more details. O ^ 3 8 &K á á ÿ Related Topics: Deleting Users using a File Deleting Members of a Group Ä Ä @ R &K á á! á# á" ÿ Deleting All Expired Accounts Deleting Directories Type of Run Options Viewing MakeUser, Deleted and Not Deleted Reports : Ä : ! L ! Deleting Expired Accounts × : 9 D &K á" á" ÿ Deleting All Expired Accounts: This option prompts you for today's 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 Delete.rpt file that lists the users deleted, and a file called Notdelet.rpt that lists users that could not be deleted. ¯ ¯ , * &K á# ÿ This option supports both real and mock runs and is new to version 1.2. See Type of Run Options--Deleting for more details. ¦ l ¯ ¦ : F &K á á á ÿ Related Topics: Deleting Users using a File Deleting Members of a Group Deleting Disabled Accounts ¡ e ¦ < J &K á! á#/ Õ 6 á" ÿ Deleting Directories Type of Run Options Viewing MakeUser, Deleted and Not Deleted Reports 5 5 ! Ï " Deleting Directories Í 5 7 @ &K ÿ Deleting Directories: To delete the user's Trustee Directory assignments, 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 usernames are still listed in the Deleted.rpt file when you run the "Delete Directories" option, MUM will ignore them. This option is new to version 1.2. 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, it's files, it's sub directories and their files. If the Deleted.rpt file gives the SYS: volume root directory as one of the Trustee Directory assignments to one of the deleted users, IT WILL DELETE THE ENTIRE SYS VOLUME. This option will delete hidden and read-only files and directories supplied (ie. BINDERY files, etc). > > . . &K ÿ RECOMMENDATION: Back up your entire system before running the "Delete Directories" option. This option is very capable of deleting BINDERY files, hidden files, read-only files etc. Look through the Deleted.rpt file BEFORE running the "Delete Directories" option. ¨ m > ¨ ; H &K á á á ÿ Related Topics: Deleting Users using a File Deleting Members of a Group Deleting Disabled Accounts W ¨ 4 : &K á á" ÿ Deleting All Expired Accounts Viewing MakeUser, Deleted and Not Deleted Reports % % " &K ÿ / % / ! ¡ ! # Delete Reportsj > / , * &K ÿ Viewing Deleted, Not Deleted and MakeUser Report Files: XXXXXXXXXXXXXXXXXXXXXX Q ª x ª 2 6 &K ÿ The MakeUser.rpt report is generated from information given by Novell's utility MakeUser when users are added or deleted. When users are deleted, MUM allows you to view those users deleted and not deleted in the Deleted.rpt and Notdelet.rpt files respectively. System managers wanting to reuse data from the deleted.rpt should rename the report file before attempting to do delete run. An error will occur if the deleted.rpt file is selected to be used as the source text file for deleting users since a new deleted.rpt is generated each delete run. Also, the deleted.rpt will be deleted if an error occurs during the run. ' ª ' $ &K ÿ ¦ l ' ¦ : F &K á á á ÿ Related Topics: Deleting Users using a File Deleting Members of a Group Deleting Disabled Accounts o : ¦ o 5 < &K á á# ÿ Deleting All Expired Accounts Type of Run Options 7 o 7 ! = " $ Type of Run--Deleteing³ 7 ³ * & &K ÿ Type of Run Options--Deleting MUM has been recently updated to allow system managers to do a real or mock run for deleting users. Þ ³ ( " &K ÿ If you choose the " Mock Run " option, MUM will step through each user, showing you the user it is processing along with the user's trustee directories. MUM will alert you of any errors it encounters. You may press "C" to run continuously at any time; if you need to MUM to halt while processing users, just press any key. 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. Ë × 5 < &K ÿ 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 trustee directories. MUM will alert you of any errors it encounters. You may press anÜ â ò y key to pause the processing, and then if you wish to continue processing continuously press "C". A real run will first gather all the data for the users to be deleted and then it will make calls to MakeUser to delete the users. Any errors from MakeUser will appear in the MakeUser.rpt file, while all other information concerning users deleted and not deleted will be reported in the Deleted.rpt and Notdelet.rpt files. ¬ n × ¬ > N &K á á á ÿ Related Topics: Deleting Users using a File Deleting Members of a Group Deleting Disabled Accounts ¥ m ¬ ¥ 8 B &K á á! á" ÿ Deleting All Expired Accounts Deleting Directories Viewing MakeUser, Deleted and Not Deleted Reports % ¥ % " &K ÿ ; % ; ! ó # % Changing User Restrictions Ì ; 4 : &K á% ÿ Modifying User Restrictions Mass User Management allows system managers to modify restriction for: all users, members of a certain group, users with old expiration dates and users with old login dates. 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. 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. ' ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: M 8 Y G ` &K á& á' á( á) á* ÿ Modifying Restrictions for All Users Modifying Restrictions for a Group of Users Modifying Restrictions for Users with Old Expiration Dates Modifying Restrictions for Users with Old Login Dates Modifying Restrictions for Users Lis¦ ɦ /£ ted in a Text File A Y A !
$ & Restrictions that can be Changed _ A * & &K ÿ User Restrictions that can be Modified: (Note: Any field left blank will not be modified) O ? P &KPAç}A ÿ 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. Password Expiration Date : Enter the month, day and year you wish the password to expire or check the "No Expiration" box to make the password never expire. 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. Ê L j &KPAç}A ÿ Grace Logins Remaining : Enter the number of logins remaining to change the password (1 to Grace Logins Allowed). 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. Minimum Password Length : Enter the minimum length of login passwords (1-20). Days Between Pswd Change: Enter the number of days before password will change (1-365). c 1 4 &KPAç}A ÿ Enable/Disable Button : Check whether to enable or disable the account (default is to enable). ' ' $ &K ÿ ä ' & 6 > &KPAç}A ÿ 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. This is new to version 1.2. Account Low Limit : Enter the amount to set as the account low limit (-99,999,999 to 99,999,999) or check the "Unlimited" checkbox to allow unlimited credit. Make sure acco$® K® "¨ unting is set up on the server before modifying the account low limit. This is new to version 1.2. Q & : F &KPAç}A ÿ 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. This is new to version 1.2. Volume Restrictions : Enter the volume name and indicate whether or not to limit space; if space is limited, indicate the limitation. Enter the exact title of the volume (ie. APPS). If a volume is not listed in Volume Restrictions, it will not be modified. For NetWare versions 2.xx, you cannot limit volumes individually; you can only enter the maximum disk space for all volumes collectively. If you are running NetWare versions 2.xx, MUM will take your volume restrictions from the SYS volume definition; if a SYS volume is not defined in the template, disk space will not be modified. This is new to version 1.2. ' ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: M 8 M G ` &K á& á' á( á) á* ÿ Modifying Restrictions for All Users Modifying Restrictions for a Group of Users Modifying Restrictions for Users with Old Expiration Dates Modifying Restrictions for Users with Old Login Dates Modifying Restrictions for Users Listed in a Text File 4 M 4 ! q % ' Changing--All Userss I 4 s * & &K ÿ Modifying Restrictions for All Users: 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. 8 s 8 % &K ÿ Related Topics: T 8 2 6 &K á% á- ÿ User Restrictions that can be Modified Generating Restrictions for O· · ¨µ All Users 0 0 ! Î & ( Changing--GroupÙ 0 Ù , * &K ÿ Modifying Restrictions for a Group of Users: 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. : Ù : & &K ÿ Related Topics: Z : 1 4 &K á% á. ÿ User Restrictions that can be Modified Generating Restrictions for a Group of Users ; ; ! T ' ) Changing--Expiration Dates ÷ ; ) $ &K ÿ Modifying Restrictions for Users with Old Expiration Dates: When this option is selected, managers may identify an expiration date to search for. All accounts with expiration dates older than the date indicated will be modified according to specifications identified in the "Enter New Restrictions" dialog. 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. ' ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: i 8 1 4 &K á% á/ ÿ User Restrictions that can be Modified Generating Restrictions for Users with Old Expiration Dates 6 6 ! P ( * Changing--Login Dates ñ 6 & ) $ &K ÿ Modifying Restrictions for Users with Old Login Dates: When this option is selected, managers may identify a last login date to search for. All accounts with last login dates older than the date indicated will be modified according to specifications identified in the "Enter New Restrictions" dialog. Fields left blank in this dialog will not be modifie;¾ q¾ ;¾ d. When OK is pressed, MUM will change user restrictions with last login dates older than the date prompted for to the new restrictions. ' & ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: d 8 1 4 &K á% á/ ÿ User Restrictions that can be Modified Generating Restrictions for Users with Old Login Dates ; ; ! ô ) + Changing--from a Text File ;  ) $ &K ÿ Modifying Restrictions for Users Listed in a Text File: When this option is selected, managers may identify a text file containing usernames to be modified. The text file must list each username 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. '  ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: f 8 2 6 &K á% á0 ÿ User Restrictions that can be Modified Generating Restrictions for Users Listed in a Text File = = ! Ü * , Generating Restriction Listsâ ® = î 4 : &K á, ÿ Generating Lists of User Restrictions Mass User Management allows system managers to generate restriction information for: all users, for members of a certain group, for old expiration dates and for old login dates. 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 prÅ ¼Å Å ocessing program. This feature allows managers to closely integrate system database files with network users to generate graphs or reports on system usage. ' î ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: R 8 R G ` &K á- á. á/ á/ á0 ÿ Generating Restrictions for All Users Generating Restrictions for a Group of Users Generating Restrictions for Users with Old Expiration Dates Generating Restrictions for Users with Old Login Dates Generating Restrictions for Users Listed in a Text File C " R C ! + - Restrictions that can be DisplayedU - C U ( " &K ÿ User Restrictions that can be Displayed: ? å U ? Z &KPAç}A ÿ Full Name : The users full name. Account Expiration Date : The month, day and year the account expires. Password Expiration Date : The month, day and year the password expires. 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. Maximum Connection : The number of connections a user may simultaneously login to. Y ? Y U | &KPAç}A ÿ Minimum Password Length : The minimum length of login passwords. Days Between Pswd Change: The number of days before the password will change. Account Disabled : Whether the account is enabled or disabled. Vol. 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. This is new to version 1.2. Account Balance--Low Limit : The account balance and low limit for the users. This is new to version 1.2. , Y , ) $ &KPç} ÿ 8 , U % &K ÿ Related Topics: XXXXXXXXXXXXXXXXX·Ï Ð [Ê R U R G ` &K á- á. á/ á/ á0 ÿ Generating Restrictions for All Users Generating Restrictions for a Group of Users Generating Restrictions for Users with Old Expiration Dates Generating Restrictions for Users with Old Login Dates Generating Restrictions for Users Listed in a Text File 6 R 6 ! j , . Generating--All Users
Î 6
? P &K á, á& ÿ Generating Restriction Lists for All Users: 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. Related Topics: User Restrictions that can be Displayed Modifying Restrictions for All Users '
' $ &K ÿ 2 ' 2 ! ð - / Generating--Groupù Ì 2 ù - , &K ÿ Generating Restriction 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. 8 ù 8 % &K ÿ Related Topics: [ 8 2 6 &K á, á' ÿ User Restrictions that can be Displayed Modifying Restrictions for a Group of Users G & G ! . 0 Generating--Expiration And Login Dates e G ) $ &K ÿ Generating Restriction Lists for Users with Old Expiration Dates and Old Login Dates: When this option is selected, managers may identify an expiration date (or a login date) to search for. All accounts with expi¸Ö ÿÖ ¸Ö ration dates (or last login dates) older than the date indicated will be displayed according to specifications identified in the "Choose Restrictions" dialog. 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. ' ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: Û ¢ 8 Û 9 D &K á, á( á) ÿ User Restrictions that can be Displayed Modifying Restrictions for Users with Old Expiration Dates Modifying Restrictions for Users with Old Login Dates = Û = ! 1 / Generating--from a Text fileý Ô = ý ) $ &K ÿ Generating Restriction Lists for Users Listed in a Text File: When this option is selected, managers may identify a text file containing usernames to generate lists for. The text file must list each username 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. ' ý ' $ &K ÿ 8 ' 8 % &K ÿ Related Topics: f 8 2 6 &K á, á* ÿ User Restrictions that can be Displayed Modifying Restrictions for Users Listed in a Text File .
. ! 3 List of Menus; . ; ( " &K ÿ Lists of Menus 6
; 6 ) $ &KP s ÿ FILE MENU q 4 6 } = L &KPsùá á á ÿ New Templates Load Templatesmß £ß ß Edit Templates Q # } Q . . &KP s á3 ÿ ---- Ordering Information ---- 4 Q 4 + ( &KPsù ÿ Exit ) 4 ) & &KP s ÿ 8 ) 8 , * &KPsù ÿ ADD MENU E 8 E + ( &K ùá ÿ Add Users from a List - E - & &KP s ÿ ---- H - < J &K ùá á á ÿ View MakeUser Report View Users Created View Users NOT Created = = - , &KPsù ÿ DELETE MENU ´ t = ´ @ R &K Aá á á á ÿ Delete from a File Delete All Members of a Group Delete All Disabled Accounts Delete All Expired Accounts - ´ - & &KP s ÿ ---- ? - ? ( " &K á ÿ Delete Directories - ? - & &KP s ÿ ---- H - < J &K ùá" á" á" ÿ View MakeUser Report View Users Deleted View Users NOT Deleted % % " &K ÿ 7 % 7 ) $ &KPsù ÿ MODIFY MENU ½ u 7 ½ H b &K á& á' á( á) á* ÿ All Users Members of a Certain Group Expiration Date Older Than Last Login Date Older Than From a File 6
½ 6 ) $ &KPsù ÿ LISTS MENU · s 6 · D Z &K á- á. á/ á/ á0 ÿ All Users Members of a Certain Group Expiration Date Older Than Last Login Date Older Than From a File ( · ( ! % ÿÿÿÿÿÿÿÿTable 1m D ( m ) $ &K ÿ Table 1 . Database or Spreadsheet data: (delimiters are tabs) & m ^ &K رeÉ ÿ Last Name First Name Middle Department (Template name) Holmstead S. Bruce Mechanical Engineering Holmstead Shawn Matthew Mechanical Engineering Benzley Steve Administration McClellan Ron A CAEDM Faculty Doe John Henry Sales Group Doe Jane Sale8æ ¥æ æ s Group Brown Mary Jane Marketing Group 5 5 ! E
1 ÿÿ Ordering Information a 5 - , &K õ ÿ Ordering Information (Print this form using the Print Topic menu item under the File menu.) ³ ³ 2 6 &K(° ÿ Mass User Management is available on a per server licensing agreement with site licenses available. Company Information: < ³ < , * &K(° K ÿ Contact Name + < + ( " &K(° ÿ < + < , * &K(° K ÿ Company Name + < + ( " &K(° ÿ > + > , * &K(° K ÿ Street Address / > / , * &K(° Ñ© ÿ D / D 2 6 &K(° K Ñ© ÿ City State Zip + D + ( " &K(° ÿ @ + @ , * &K(° K ÿ Telephone Number + @ + ( " &K(° ÿ S $ + S / 0 &K(° K ÿ E-mail Address to send updates: D S D + ( &K(° ÿ Ordering Worksheet: F D F - , &K HÕ ÿ Individual Purchases: O F O 1 4 &K H!Aa ÿ Quantity Range Price Cost ¶ z O ¶ < J &K H!õa ÿ _______ 1 - 2 Copies $350.00 ea. __________ _______ Additional Copies $100.00 ea. __________ Sub Total __________ _ ¶ 0 2 &K Hõ ÿ Education Discount (2+ copies) - 20% __________ (Utah Residents add 6.25%) Tax __________ K K 4 : &K Hõa ÿ Total __________ q E K q , * &K HA ÿ If no sales tax: Tax Exemption No. _____________ Site License: + q + ( " &K(° ÿ W + c R v &K HAa ÿ Type of Institution Price Check One Education: Entire University $2100.00 __________ College in a University $1050.00 __________ (or small Acadíî ï 5è emy/University)* Business: Entire Company** $3000.00 __________ Company Department $1500.00 __________ + c + ( " &K(° ÿ K + K 1 4 &K H!õa ÿ Sub Total __________ Y - K Y , * &K Hõ ÿ (Utah Residents add 6.25%) Tax __________ K Y K 4 : &K Hõa ÿ Total __________ ` 6 K ` * & &K HA ÿ If no sales tax: Tax Exemption No. _____________ ý Ì ` ý 1 4 &K(° ÿ *Contact Holmstead Partners to see if you qualify **May be subject to division restrictions Note that the price for education reflects a 30% discount Department name to appear in license agreement: 4 ý 4 . . &K(à K ÿ + 4 + ( " &K(à ÿ J ! + J ) $ &K(° ÿ Send Check or Money Order to: v @ J v 6 > &K(° ! ÿ Holmstead Partners P.O. Box 50452 Provo, UT 84605-0452 Ô « v Ô ) $ &K(° ÿ - All prices may be subject to change without notification. - For information about site licenses (or any other questions) write to the above address or send E-mail to: + Ô + ( " &K(°± ÿ E + E + ( &K(° ! ÿ [email protected] % E % " ÿ ! % ! ! ÿÿÿÿÿÿÿÿÝ Ô â% |0 < K ¥O JY °^ +e :l Tp z T 6 Q ò /£ "¨ ¨µ ¸ çº ;¾ Á Å [Ê ^Ñ ÈÓ ¸Ö ÓÚ ß æ 5è zõ ð ç
X Helv ist of restrictTimes Any fields leSymbol k will not beHelvetica ! Changing £ d â% e ¥O f K g z h T i j 6 k l ¸ m çº n ;¾ o Á p ÈÓ q ¸Ö r ÓÚ s [Ê t "¨ u ò v 5è 1 ( |0 K JY °^ +e :l |0 |0 K K K ¥O ¥O JY JY °^ +e ò +e ò +e ò :l :l :l Q Tp z T 6 Q ò Tp z T 6 Q Q /£ "¨ ¨µ ¸ çº ;¾ Á ¨µ ¸ çº ;¾ Á Å [Ê ^Ñ ÈÓ ¸Ö ÓÚ ^Ñ ÈÓ ¸Ö ¸Ö ÓÚ ß ß æ 5è 5è / & ;) i24 G&WÂ& G ÿÿ - Ò- ÿÿÿÿAdding All Users--Changing Ô All Users--Generating Batch files--using to add Changing Restrictions ¸ Command line usage Created.rpt file h Creating Templates 8 Deleted.rpt files ° Deleting x Deleting Directories ¬ Deleting Users Description Disabled Accounts--Deleting ¤ Expiration Dates--Changing Ü Expiration Dates--Generating Expired Accounts--Deleting ¨ File--Deleting Format , Full Name options H Generating Restrictions è Group--Changing Ø Group--Deleting Group--Generating List of Menus Login Dates--Changing à Login Dates--Generating Makeuser.rpt file p Menus--List of Mock run P Notcreat.rpt file l Notdelet.rpt files ´ Ordering Information $ Password options L Real run X Registration Run options ` Setting restrictions < Table 1 Template restrictions @ Templates 0 Text file--Changing ä Text File--Generating Textfile ( Username options D Äuk¡ FÃ÷Á t ÷Á ué éè÷Á uéÇé»ÝÐëã.ÿ§ÝÐëã.ÿ§ ÝÐëã.ÿ§0÷Á u éPñ÷Á u¸ éöÁt3Àé @ú ë#º ë 3Ò»ë3Ò÷»¨ë3Ò»¨ë3Ò»hE ÐàÐà
D ÑàØ2u
2T
MD.ÿ'÷ÖèQ U
à ë÷ ë=¾Ð2òæè u
à ¾Üëê ¾è > .¥.¥.¥.¥.¥.¥ï î Ã> ;÷t ¥¥¥¥¥¥ï î Ãö tÅ2ÖxÁëÆßÆǹ ýó§ürðëóé~ÿ+Á|÷òÈ÷Ø÷Ø=C ~/URu½ 2Öy÷ÝM]} íxé`êÙ Û ß éURQ2ÖèÐÈØ3öî ötpþ| ítÊêÑËØ3ÀîwåtSr)þ|3
ÀtÌÄâÖñÍëßøÄ2äîwt(ÑåÑÒÑÑÑÓÑÐFuóëÎ÷Å? tÍ ÑèÑÛÑÞÑÚÑÝâôÎ÷ø÷Åÿ?tÍXx"L\|sÑßÑÛÑÙÑÚÑÝsÍ@ðé+L\|s3ö÷×÷Ó÷Ñ÷Ò÷ÝõÖÎÞþðé§ðXôPéUþ2òRÁ@P"ú3ÛëË Àt Òt÷âèÊU3í ÀtU Òt ÷âÈÚÕ D Àt Òt ÷âÈÚÕ X ÁP3É ÀtU Òt ÷âØêÑ D ÀtU Òt ÷âØêÑ D Àt Òt ÷âØêÑ X ÃP3Û Àt
÷eèÊÓ D ÀtU Òt ÷âèÊÓ D ÀtU Òt ÷âèÊÓ D Òt ÷âèÊÓ Õåÿ?X ÅP3íRD Àt
÷eÈÚÕ D ÀtU Òt ÷âÈÚÕ DU Òt ÷âÈÚÕ Q3ÉD Àt
÷eØêÑ / & ;) Lz _uîVHEÄFP ÿÿ $ <$ ÿÿÿÿ Introduction Program Description Command Line-Batch File Usage â% Adding Users |0 Text File Format (Adding) < Examples (Adding) K Creating Templates ¥O Setting Account Restrictions JY Username/Fullname Options °^ PasswordOptions +e Type of Run Options--Adding :l Created Reports Tp Deleting Users Intro z Deleting with a File T Deleting a Group Deleting Disabled Accounts 6 Deleting Expired Accounts Deleting Directories Q Delete Reports ò Type of Run--Deleteing /£ Changing User Restrictions "¨ Restrictions that can be Changed ¨µ Changing--All Users ¸ Changing--Group çº Changing--Expiration Dates ;¾ Changing--Login Dates Á Changing--from a Text File Å Generating Restriction Lists [Ê Restrictions that can be Displayed ^Ñ Generating--All Users ÈÓ Generating--Group ¸Ö Generating--Expiration And Login Dates ÓÚ Generating--from a Text file ß List of Menus æ Table 1 5è Ordering Information tFile a CreatingTemplates CreatingTemplates Creat ingTemplates Ordering r
AddingUsers ViewCreatedLists ViewCreatedLists ViewCreatedLists e DeletingUsersUsingAFile DeletingMembersOfAGroup DeletingDisabledAccounts E DeletingAllExpiredAccounts N DeletingUsers port s ViewDeletedLists ViewDeletedLists ViewDeletedLists ViewDeletedLists w! ChangingRestrictionsForAllUsers ' ChangingRestrictionsForAGroupOfUsers ChangingOldExpirationDates s ChangingOldLoginDates ChangingTextFile ÿ# GeneratingRestrictionsForAllUsers ) GeneratingRestrictionsForAGroupOfUsers n
GeneratingO ldExpirationAndLoginDates ' GeneratingOldExpirationAndLoginDates e GeneratingTextFile n9 . Database or Spreadsheet data: (delimiters are tabs)
First Name t Middle t Department (Template name) g Holmstead S. e Bruce Mechanical Engineering Holmstead Shawn Matthew Mechanical Engineering n Benzley Steve Administration S McClellan Ron A CAEDM Faculty Doe John a Henry
Sales Group Doe Jane \
Sales Group Brown Mary . Jane a
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/