NDSCount v MT-1.10 ================== (Feb 16, 1997) DISCLAIMER ---------- THIS PRODUCT IS SUPPLIED "AS IS". THE AUTHOR DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF MERCHANTABILITY AND OF FITNESS FOR ANY PURPOSE. THE AUTHOR ASSUMES NO LIABILITY FOR DAMAGES, DIRECT OR CONSEQUENTIAL, WHICH MAY RESULT FROM THE USE OF THIS PRODUCT. Introduction ------------ NDSCount is a DOS command-line utility that scans your NDS schema and reports on the different object classes that are defined. If extensions, such as NetWare Connect, have been installed, they too will be reported. For each object class, an object count is given. This is useful if you are wondering how many user and container objects you have in your tree. If you generate a report file, the names of the objects are listed. Notes ----- 1. The names of the classes are schema dependent. Therefore, you need to be careful when specifying the class name if you are looking for a specific class name. A complete list of the "base" class name is listed in a later section of this documentation. 2. To make it easier to read, any embedded blanks in the class names are replaced by an underscore. This is simply for display purposes. 3. By default, NDSCount only looks at the current name context. If you wish to report on the subtree on the number of object, use the "-s" switch. If you wish a report on the whole tree, make sure you first change your context to [Root] before running NDSCount. 4. Note that not all class names will have an object in the NDS. Some classes are used by other classes (as Super Classes). For example, you will find a class named Person, but there is no NDS object called Person. Instead, the class Person is used by the class Organizational Person, which is in turn used by User. This is also true for, for example, Partition. 5. The order in which the class name information returned by the API calls is not alphabetical. Rather, it is based on the order in which the class is defined into the schema. Therefore, any schema extension will be listed by NDSCount last. Using this knowledge, NDSCount "assumes" the class "Volume" is the last base class defined in the NetWare 4.1 schema (as it is the last one listed). And any other classes listed after Volume is considered as extensions. If your network was upgraded from NetWare 4.0x to 4.1, for example, some of the newer base class name in NetWare 4.1 is added to the end of the list (ie not in the same order if you have installed a brand new NetWare 4.1 network). In these cases, the newer object classes (such as Messaging Server) will be considered as "extensions" as they appear after the class Volume. 6. NDSCount will only count the objects that your logged in id has the right to "see". Installing NDSCount ------------------- No special installation steps or program need to be used. Simply copy NDSCount to SYS:PUBLIC of your servers. You must have the Unicode files for the country code and code page that your workstation use available in the respective NLS directories, for example, SYS:PUBLIC\NLS. Should you install NDSCount into a different directory, you may need a search path to the directory where the unicode files are located. Running NDSCount ---------------- You can run NDSCount with the following command-line parameters: NDSCOUNT [-a] [-c] [-n] [-r] [-s] where "-a" specifies the report file will be appended to, if one exists. It has no effect unless the "-r" switch is also specified. "-c" specifies continuous scroll on display. Otherwise, pause at the end of each displayed screen. "-n ClassName" specifies the target class name. This is the class of which you wish to determine the number of objects it has. The use of wild card (i.e. "*") is not allowed. "-r" specifies that a report file should be generated. This is helpful when you wish to have a list of the object names for each of the classes. "-s" specifies searching of the subtree. This will cause the utility to recursively search the lower containers for a name match to the target class. Note: None of the above parameters are case sensitive. ---- Configuring NDSCount -------------------- n/a Schema Class Names of NetWare 4.10 ---------------------------------- The following is a list of the base schema class names as shipped with NetWare 4.10: Messaging_Server Message_Routing_Group External_Entity List AFP_Server Bindery_Queue Top Alias Bindery_Object Computer Country Device Directory_Map Group Locality NCP_Server Organization Organizational_Person Organizational_Role Organizational_Unit Partition Person Printer Print_Server Profile Queue Resource Server Unknown User Volume Registration ------------ This version of NDSCount is full-functional shareware. The -s and the -c command-line options are disabled in this trial version. You are granted a 30-day license to evaluate NDSCount. Should you like to continue using NDSCount after 30 days, a registered version is available for $25US. This will be a NETWORK license, limited to ONE NDS TREE. This license does not allow you to resell NDSCount or to include it as part of another software package or service contract. You can register NDSCount via CompuServe: !GO SWREG. If you can not register via CompuServe, you can FAX a Purchase Order to +1(905) 886-2534. Please make sure you either include your tree name information on the FAX or send a follow up email. Canadian orders is $34.00 CDN plus GST. All other countries, please remit in US funds. Special agreements for service providers are available. Although the license does not grant you the right to resell the program (i.e. for a profit; but you can charge the customer a service charge for your time). If you are a service provider, you can register copies on behave of your customers (by providing your customer's mailing information -- this is used only for tracking purposes). At the same time, we ask you to send us a separate email indicating that you are registering on behave of your customer and inciate in this email if further software upgrade (free or for a charge) be send to you or the customer directly, and an email address for that purpose. Other Information ----------------- NDSCount is written in C using Microsoft C optimizing compiler and Novell's Client SDK v1.0e. Some string manipulating routines are from the CXL library. Revision History ---------------- Oct 08, 1995. Version MT-1.00, released code. Feb 16, 1997. Version MT-1.10, released. Added tree name check.