1.2 Why Use ConsoleOne?

Novell is committed to ConsoleOne as a single management tool and is working hard to improve its capabilities and performance so you won't need legacy tools like NetWare Administrator. Following are some of the advantages of ConsoleOne over legacy tools. A few limitations are also listed after the advantages.

Advantage Explanation

Use on a Windows* computer or a NetWare server Manage the latest Novell products
Because ConsoleOne is Java-based, it can run on Windows, NetWare, Linux*, Solaris*, and Tru64 UNIX*. The legacy NetWare Administrator, NDS ManagerTM, and Schema Manager tools run only on Windows. ConsoleOne lets you manage the latest Novell products and enhancements, whereas NetWare Administrator and other legacy tools aren't being updated to do so. For example, you can administer DirXML, Single Sign-on, and Certificate Server only in ConsoleOne. If your tree is running NDS 8 and has containers with thousands of objects, browsing it in ConsoleOne is faster and more consistent. NetWare Administrator is slower opening large containers and is limited by available RAM. If a tree is running NDS eDirectory 8.5 or later and is configured for DNS federation, ConsoleOne lets you access contexts in that tree whether or not you are logged in to the tree. This allows you to treat multiple eDirectory trees as a single system for purposes of assigning rights and memberships. No legacy tool exposes this capability. See Section 2.1, Browsing and Finding Objects, on page 29.
Browse huge eDirectory trees
Access eDirectory resources through DNS federation

Advantage

Explanation
Create filtered eDirectory If your tree is running NDS eDirectory 8.5 or later, ConsoleOne lets you replicas create filtered replicas that contain only the objects and properties needed for synchronization with specific applications like PeopleSoft*. No legacy tool has this capability. See Section 7.2, Managing Replication, on page 78. Generate eDirectory reports Create all eDirectory object types ConsoleOne lets you generate reports on eDirectory objects, users, groups, and security. No legacy tool has these capabilities. See Generating Reports on page 89. ConsoleOne lets you create any object type defined in the schema of your eDirectory tree, including custom types you've added. NetWare Administrator can only create object types for which it has snap-ins. See Section 2.2, Creating and Manipulating Objects, on page 32. ConsoleOne lets you generically edit any object property defined in the schema of your eDirectory tree, including custom properties you've added. No legacy tool has this capability. ConsoleOne also lets you modify multiple objects of any class in a single operation, including files and folders on NetWare volumes. NetWare Administrator lets you do this only on User objects. See Section 2.2, Creating and Manipulating Objects, on page 32. ConsoleOne lets you define auxiliary classes and extend any eDirectory object with the properties defined in auxiliary classes. No legacy tool has this capability. See Section 6.2, Defining and Using Auxiliary Classes, on page 67. ConsoleOne lets you assign ASN.1 identifiers to object classes and attributes in the schema of your eDirectory tree. No legacy tool has this capability. See Section 6.1, Defining Custom Object Classes and Properties, on page 66. ConsoleOne lets you create roles in eDirectory so you can delegate administrative responsibilities. A role is a list of specific application functions that a person can perform. For an application function to be added to a role, it must exist as a task object in your eDirectory tree. For details, see Configuring Role-Based Administration on page 59.

1.3.1 Accessibility Usage
To enable the new ConsoleOne accessibility feature, complete the following procedure: 1 Install Java Access Bridge. The Java Access Bridge exposes the Java Accessibility API in a Windows DLL so that Windows Assistive Technologies can interact with Java applications that use the Java Accessibility API. To set up the Java Access Bridge for use with ConsoleOne, complete the following steps: 1a Download the Java Access Bridge from the Java Access Bridge Website (http:// java.sun.com/products/accessbridge).
1b Unpack the Java Access Bridge into the C:\AccessBridge-1_2 directory and enter the following: C:\AccessBridge-1_2\installer\Install For more information on installing and configuring the Java Access Bridge, see the Java Access Bridge readme (http://java.sun.com/products/accessbridge/README.txt). 2 Place a copy of the C:\AccessBridge-1_2\installer\installerFiles\accessibility.properties file in the ConsoleOne_installation_path\JRE\LIB folder. By default, this folder is at C:\NOVELL\CONSOLEONE\1.2\JRE\LIB.
1.4 Snap-Ins from Other Products
If you installed or will install a product that includes ConsoleOne snap-ins and you want to retain those snap-ins in this release of ConsoleOne, make sure those snap-ins are installed in the same place as this release of ConsoleOne. The following are some points to consider: ConsoleOne 1.2 snap-ins are compatible with this release of ConsoleOne, but ConsoleOne 1.1 snap-ins aren't. If your product provides only ConsoleOne 1.1 snap-ins, you might want to install this release of ConsoleOne in a different place than ConsoleOne 1.1. By default, ConsoleOne 1.1 is installed on the NetWare server in sys:\public\mgmt\console1. Novell products typically install ConsoleOne snap-ins on the SYS volume of a NetWare server. For example, NDS 8 installs the snap-in for LDAP in sys:\public\mgmt\consoleone\1.2. If you install this release of ConsoleOne on the SYS volume of a NetWare server, it overwrites ConsoleOne 1.2x and disables ConsoleOne 1.1. However, existing ConsoleOne 1.2 snap-ins are retained. If you install this release of ConsoleOne locally on a workstation hard disk, other products such as eDirectory might not be able to find the right place to add snap-ins to the installation. In such a case, it is up to you to move any snap-ins from other products into the new installation. On NetWare, move the snap-in to sys\public\mgmt\consoleone\1.2. On Windows, move the snap-ins to c:\novell\consoleone\1.2. On UNIX, move the snap-ins to /usr/ConsoleOne/bin/ConsoleOne. To see a list of registered ConsoleOne snap-ins installed on your ConsoleOne machine, click Help > About Snap-ins. Click the name of an individual snap-in to view the version number. Updated Novell product snap-ins can be downloaded from the Novell Product Downloads Site (http://download.novell.com).

Installing ConsoleOne on NetWare 1 Bring down Java and any Java applications that are running on the server, including the server GUI. You can do this by entering JAVA -EXIT at the console prompt. 2 Have all users who are currently running ConsoleOne remotely through a connection to the server exit their ConsoleOne sessions. 3 At a Windows workstation, map a drive letter to the root of the server's SYS volume. 4 At the same workstation, insert the CD that contains ConsoleOne, or go to the Novell Free Downloads site (http://download.novell.com). 5 Browse the CD or Web site until you find the available ConsoleOne packages > select the package for Windows/NetWare.
TIP: If you are using a CD that runs an installation program and you see an option to install just ConsoleOne, choose that option and skip to Step 8. 6 If you are using the Web site, download and unzip the ConsoleOne files to a temporary area. If you are using a CD, skip this step. 7 Run the installation executable file (setup.exe or consoleone.exe). 8 Follow the instructions on the screen to complete the installation. When you are prompted for the location to install to, select the drive that is mapped to the root of the server's SYS volume. IMPORTANT: You must select a drive that is mapped to a letter, not a UNC path. Starting ConsoleOne on NetWare To start ConsoleOne locally on a NetWare server, enter C1START at the console prompt. To start ConsoleOne remotely from a Windows computer with a drive mapped to the NetWare server, see Starting ConsoleOne on Windows on page 19. For help with navigating and performing basic tasks in ConsoleOne, see Administration Basics on page 29. If you encounter problems starting or using ConsoleOne, see Troubleshooting on page 99.

1.5.3 Linux

You can install and run ConsoleOne locally on a Linux computer. You can also run it from another computer through an X terminal (remote) session, if that computer has an X windowing subsystem. System Requirements for Linux IMPORTANT: For ConsoleOne v1.3.6d onwards, if the Linux Kernel version installed in your system is 2.6, the Java runtime environment (JRE) that is included in the ConsoleOne installation package will not be installed. For Kernel version 2.4, you can choose to install JRE or not.

4 In Name, enter a name for the new object. If it's an eDirectory object, be sure to follow proper naming conventions. See Naming Conventions (http://www.novell.com/documentation/edir871/edir871/data/ a2iiidp.html#a2iiie9) in the Novell eDirectory Administration Guide for details. 5 Specify any other information requested in the dialog box. Click Help for details. (If you are using generic editors, no details are available.) 6 Click OK.
2.2.2 Modifying an Object's Properties
1 Right-click the object > click Properties. 2 Edit the property pages you want. Click Help for details on specific properties. See Section 2.3, Editing Object Properties, on page 34 for general information on using property pages. 3 Click OK.
2.2.3 Modifying Multiple Objects Simultaneously
1 Select the objects using one of the following methods: In the right pane, Shift+click or Ctrl+click multiple objects of the same type Click a group or template object to modify its members Click a container to modify the objects it contains 2 Click File > Properties of Multiple Objects. 3 If you selected a container in Step 1, in the dialog box double-click the object type that you want to modify; otherwise, skip this step. 4 On the Objects to Modify page, make sure only the objects that you want to modify are listed. Add and delete objects as needed. 5 On the other property pages, specify the property values to set for all the selected objects. Click Help for details on specific properties.
IMPORTANT: See Section 2.3, Editing Object Properties, on page 34 for differences in how property pages work when editing multiple objects. 6 Click OK.

2.2.4 Renaming an Object

1 Right-click the object > click Rename. 2 In New Name, enter the new name. If it's an eDirectory object, be sure to following proper naming conventions. See Naming Conventions (http://www.novell.com/documentation/edir871/edir871/data/ a2iiidp.html#a2iiie9) in the Novell eDirectory Administration Guide for details. 3 Click Save Old Name if you want to save the old name of the object. The old name is stored in the Other Name field of the object's General Identification property page. 4 Click OK.

2.2.5 Moving Objects

1 In the right pane, Shift+click or Ctrl+click the objects to select them. TIP: You can't move a container object unless it's a partition root. For details, see Section 7.1, Managing Partitions, on page 73. 2 Right-click your selection > click Move. 3 Click the browse button next to the Destination field > select the container to move the objects to > click OK. 4 If you want to create an alias in the old location for each object being moved, select Create an Alias for All Objects Being Moved. This allows any operations that are dependent on the old location to continue uninterrupted until you can update those operations to reflect the new location. 5 Click OK.

3.1.1 Creating a User Object
1 Right-click the container that you want to create the User object in > click New > click User. 2 Fill in the New User dialog box. Click Help for details. 2a To apply a template during creation of the user object, select Use Template. 2b To set additional user properties during creation of the user object, select Define Additional Properties. 3 Click OK. 4 If the Set Password dialog box appears, set the user's login password > click OK. IMPORTANT: If this dialog box appears and you cancel it, an eDirectory password (objectkey pair) wont be created for the user account and the user wont be able to log in unless you set up some other means of authentication, such as an NMASTM password. You can set an eDirectory password later on the Password Restrictions property page of the User object. If you
leave the password blank and click OK, the User object is created with a blank (null) eDirectory password and the user can log in without entering a password.
3.1.2 Creating a User Template
1 Right-click the container that you want to create the Template object in > click New > click Object. 2 Under Class, select Template > click OK. 3 Fill in the New Template dialog box. Click Help for details. 3a To clone an existing Template or User object, select Use Template or User. 3b To set template properties immediately after creating the Template object, select Define Additional Properties. After clicking OK, you'll see property pages that look similar to those of a User object. Help is available on all the property pages. 4 Click OK.
3.2 Setting Up Optional Account Features
After creating a User object, you can optionally set up the users network computing environment, implement extra login security features, and set up an accounting of the user's NetWare server usage. In This Section Setting Up a User's Network Computing Environment on page 42 Setting Up Extra Login Security for a User on page 42 Setting Up an Accounting of a User's NetWare Server Usage on page 43
3.2.1 Setting Up a User's Network Computing Environment
1 Right-click the User or Template object that you want to set up the network computing environment for > click Properties. Use a Template object if you haven't created the User object yet. 2 On the General tab, select the Environment page. 3 Fill in the property page. Click Help for details. 4 Click OK.
3.2.2 Setting Up Extra Login Security for a User

1 Right-click the User or Template object that you want to set up login security for > click Properties. Use a Template object if you haven't created the User object yet. 2 On the Restrictions tab, fill in the property pages you want.
Click Help for details on any page.

Page Use to

Password Restrictions Address Restrictions Time Restrictions
Set up a login password. Restrict the locations the user can log in from. Restrict the times when the user can be logged in. If the user will log in remotely, see Section 3.4, Login Time Restrictions for Remote Users, on page 44. Limit the number of concurrent login sessions. Set a login expiration and lockout date.

Login Restrictions

3 Click OK. 4 To set up intruder detection for all the User objects in a container: 4a Right-click the container > click Properties. 4b On the General tab, select the Intruder Detection page. 4c Fill in the property page. Click Help for details. 4d Click OK.
3.2.3 Setting Up an Accounting of a User's NetWare Server Usage
1 Right-click the User or Template object that you want to set up the accounting for > click Properties. Use a Template object if you haven't created the User object yet. 2 On the Restrictions tab, select the Account Balance page. 3 Fill in the property page. Click Help for details. 4 Click OK. 5 Use NetWare Administrator to set up one or more NetWare servers to charge for network services. See the NetWare Administrator online help for details.
3.3 Setting Up Login Scripts
A login script is a list of commands that executes when a user logs in. It is typically used to connect the user to network resources like files and printers. Login scripts execute on the users workstation in the following order: 1. Container login script 2. Profile login script 3. User login script
During login, if the system doesn't find any of these login scripts, it skips to the next one in the list. If none are found, the system executes a default script that maps a search drive to the SYS:PUBLIC folder on the users default server. The default server is set on the Environment property page of the user object. In This Section Creating a Login Script on page 44 Assigning a Profile to a User on page 44
3.3.1 Creating a Login Script
1 Right-click the object that you want to create the login script on > click Properties.
To Have the Login Script Apply To Create It On
One user only One or more users that haven't been created yet All the users in a container A set of users in one or more containers
The User object A Template object The container object A Profile object
2 On the Login Script page, enter the login script commands you want. See Novell Client for Windows > Login Script Commands and Variables (http:// www.novell.com/documentation/lg/noclienu/index.html) for details. 3 Click OK. 4 If you created the login script on a profile object, assign the profile to the users you want as explained below.

Controlling Access to Novell eDirectory by Resource on page 51 Controlling Access to Novell eDirectory by Trustee on page 51
4.1.1 Controlling Access to the NetWare File System by Resource
1 Right-click the resource (file, folder, or volume) that you want to control access to > click Properties. NOTE: Select a volume or folder to control access to all the resources below it. 2 On the Trustees page, edit the list of trustees and their rights assignments as needed. For descriptions of the individual access rights, see Section 4.5, About NetWare Rights, on page 55. 2a To add an object as a trustee, click Add Trustee > select the object > click OK > under Access Rights, assign the trustee's rights. 2b To modify a trustee's rights assignment, select the trustee > under Access Rights, modify the rights assignment as needed. 2c To remove an object as a trustee, select the object > click Delete Trustee > Yes. The deleted trustee will no longer have explicit rights to the file or folder but might still have effective rights through inheritance or security equivalence. 3 Click OK.
4.1.2 Controlling Access to the NetWare File System by Trustee
1 Right-click the trustee (the object that possesses, or will possess, the rights) > select Properties. 2 On the Rights to Files and Folders page, click Show > select the NetWare volume containing the file system that you want to control access to > click OK. The Files and Folders list is filled in with any files and folders that the trustee currently has rights assignments to on the selected volume. 3 Edit the rights assignments as needed. For descriptions of the individual rights, see Section 4.5, About NetWare Rights, on page 55. 3a To add a rights assignment, click Add > select the file or folder to control access to > click OK > under Rights, assign the trustee's rights. 3b To modify a rights assignment, select the file or folder to control access to > under Rights, modify the trustee's rights as needed. 3c To remove a rights assignment, select the file or folder to control access to > click Delete > Yes. The trustee will no longer have explicit rights to the file or folder but might still have effective rights through inheritance or security equivalence. 4 Repeat Step 2 and Step 3 as needed to edit the trustee's rights assignments on other NetWare volumes. 5 Click OK.
4.1.3 Controlling Access to Novell eDirectory by Resource
1 Right-click the eDirectory resource (object) that you want to control access to > click Trustees of This Object. NOTE: Choose a container to control access to all the objects below it. 2 Edit the list of trustees and their rights assignments as needed. Click Help for details. 2a To modify a trustee's rights assignment, select the trustee > click Assigned Rights > modify the rights assignment as needed > click OK. 2b To add an object as a trustee, click Add Trustee > select the object > click OK > assign the trustee's rights > click OK. When creating or modifying a rights assignment (in the Rights Assigned To dialog box), you can grant or deny access to the object as a whole, to all the properties of the object, and to individual properties. Click Help in the dialog box for details. 2c To remove an object as a trustee, select the object > click Delete Trustee > Yes. The deleted trustee will no longer have explicit rights to the object or its properties but might still have effective rights through inheritance or security equivalence. 3 Click OK.

4.5.3 How NetWare Calculates Effective Rights
A user's effective rights are calculated by NetWare each time the user tries to access a file or folder on a NetWare volume. You can view a user's effective rights to any file or folder as explained in Section 4.4, Viewing Effective Rights, on page 54. Following is the process used by NetWare to calculate effective rights. This process is similar to, but not the same as, the process used by eDirectory to calculate users' effective rights to eDirectory objects and properties. For information on that process, see eDirectory Rights (http://www.novell.com/documentation/edir871/edir871/data/ fbachifb.html#fbachifb) in the Novell eDirectory Administration Guide. 1. Checks whether the user effectively has the Supervisor right to the NetWare server where the target file or folder resides. (eDirectory supplies this information to NetWare.) If so, the user effectively has all rights in the file system of the server, and the rest of this process is skipped. If not, continues with the next step. 2. Determines which eDirectory objects the user is security equivalent to. (eDirectory supplies this information to NetWare.) 3. Descends to the next level in the file system along the path to the target file or folder. TIP: The next level below the NetWare server is the root folder of the volume. 4. Checks whether the user, or any of the objects that the user is security equivalent to, is assigned the Supervisor right at the current level. If so, the user effectively has all rights from this level down in the file system, and the rest of this process is skipped.
If not, continues with the next step. 5. Does the following for the user and each object that the user is security equivalent to: a. Checks whether the user (or object) is assigned any non-Supervisor rights at the current level. If so, sets the effective rights of the user (or object) to the rights specified in the assignment and skips to Step 6. If not, continues with the next substep. b. Removes from the current effective rights any rights that are blocked by an inheritance filter at the current level. 6. If the current level of the file system is the target file or folder, the user's final effective rights are the sum of his or her current effective rights and the current effective rights of each object that the user is security equivalent to. If the target file or folder hasn't been reached yet, returns to Step 3.
Configuring Role-Based Administration

administration applications. They are organized into one or more RBS modules, which are containers that correspond to the different functional modules of the application. TIP: If your organization has developed a custom administration application that uses RBS objects, you can create the RBS objects for it manually as explained in Section 5.4, Creating RBS Objects for Custom Applications, on page 61. In This Section Creating an RBS Role Object on page 60 Specifying the Tasks That RBS Roles Can Perform on page 60
5.2.1 Creating an RBS Role Object
1 Right-click the container that you want to create the RBS role object in > click New > click Object. 2 Under Class, select RBS:Role > click OK. 3 Enter a name for the new RBS role object. Be sure to follow proper eDirectory naming conventions. See Naming Conventions (http:// www.novell.com/documentation/edir871/edir871/data/a2iiidp.html#a2iiie9) in the Novell eDirectory Administration Guide. Example: Password Administrator Role 4 Click OK.
5.2.2 Specifying the Tasks That RBS Roles Can Perform
1 Right-click an RBS role or RBS task object > click Properties. RBS task objects are located only in RBS module containers. 2 On the Role Based Services tab, make the associations you want: For an RBS role, select the Role Content page > edit the list of tasks that the role can perform. For an RBS task, select the Member Of page > edit the list of roles that can perform the task. 3 Click OK.
5.3 Assigning RBS Role Membership and Scope
Once you have defined the RBS roles needed in your organization, you can assign the membership of each role. In doing so, you specify the scope in which each member can exercise the functions of the role. Depending on the administration application associated with the role functions, the scope is specified either as a context in the eDirectory tree or as an object that represents some other (noneDirectory) kind of scope.
TIP: If an administration application defines scope in non-eDirectory terms, it will extend the schema of your eDirectory tree to include the needed scope object class. You can then create scope objects as explained in Creating an Object That Represents a Non-eDirectory Scope on page 63. 1 Right-click either the RBS role object or the object that represents the users who you want to assign as role members > click Properties. You can assign users as role members individually or in groups, organizations, or organizational units. However, if you want each user to exercise the role within a different scope, you must assign role memberships individually. 2 On the Role Based Services tab, assign the role memberships you want: For an RBS role object, select the Members of Role page > edit the list of members and their scopes as needed. Click Help for details. For a user, group, organization, or organizational unit object, select the Assigned Roles page > edit the list of role memberships and scopes as needed. Click Help for details. If you want a single role membership to have multiple, non-overlapping scopes (such as two different branches of the eDirectory tree), you must list that role membership multiple times, each with a different scope. 3 Click OK.

Auxiliary Class Is Listed? Action
Select it > click Remove Extension > Yes. This deletes all the properties added by the auxiliary class except for any that the object already had innately.
Cancel the dialog box. You'll have to delete the auxiliary class from each object one at a time. See Deleting Auxiliary Properties from an Object on page 69.
6.3 Deleting Unused Classes and Properties
You can delete unused classes and properties (attributes) that aren't part of the base schema of your eDirectory tree. We recommend that you only delete classes that you've defined and that you're sure aren't being used. ConsoleOne only prevents you from deleting classes that are currently being used in locally replicated partitions. In This Section Deleting a Property from the Schema on page 70 Deleting a Class from the Schema on page 70
6.3.1 Deleting a Property from the Schema
1 Click anywhere in the eDirectory tree whose schema you want to modify. 2 Click Tools > Schema Manager. 3 On the Attributes tab, select the property > click Delete > click Yes.
6.3.2 Deleting a Class from the Schema
1 Click anywhere in the eDirectory tree whose schema you want to modify.
2 Click Tools > Schema Manager. 3 On the Classes tab, select the class > click Delete > click Yes.
Partitioning and Replicating Novell eDirectory
A partition is a subdivision of your Novell eDirectoryTM tree that can be stored and replicated as an independent unit across multiple servers. If your tree is large or spans WAN links, you can partition and replicate it to improve network performance and fault tolerance. For details, see Replicas (http://www.novell.com/documentation/edir871/edir871/data/fbaecheh.html#fbaecheh) and Partitions (http://www.novell.com/documentation/edir871/edir871/data/fbachabc.html#fbachabc) in the Novell eDirectory Administration Guide. To perform partition and replication operations, you need the Supervisor right to the part of the eDirectory tree that you will partition or replicate. In your tree, the containers that have an icon next to them mark the points where the tree is partitioned. (Each of these containers is the root of a partition.) At such points, you can open a special view in the right pane (illustrated below) to see and configure the replicas of the partition. You can also access similar views from server objects in the tree.
Figure 7-1 Partition and Replica View
In This Chapter Section 7.1, Managing Partitions, on page 73 Section 7.2, Managing Replication, on page 78 Section 7.3, About Replica States, on page 80

Trustee Assignments

Name of resource (eDirectory object) that the trustee assignment controls access to, list of trustees (objects holding rights to the resource) and their assigned rights. Username, other (unofficial) names for the user, whether a login password is required, whether the user can change his or her own password, minimum password length, whether the last eight passwords must be unique, maximum number of days a password can be used, number of grace logins allowed, number of grace logins remaining, password expiration date and time. Name of user who hasn't logged in for at least 90 days, other (unofficial) names for the user, last login date and time. Name of user whose password has expired, other (unofficial) names for the user, password expiration date and time, last login date and time. Name of user who is logged in from multiple workstations, other (unofficial) names for the user, number of workstations the user is logged in from, network addresses of the workstations.
User Password Requirements
Users Not Logged In Users with Expired Passwords
Users with Multiple Workstation Logins
9.1.3 eDirectory User and Group Reports
This report catalog contains report forms that let you generate reports on the users, groups, and organizational roles in your eDirectory tree. The following table describes user and group reports:

User Contact List

Username, first name, last name, telephone number, Internet e-mail address, postal address
Duplicate Common User Names Group Membership Organizational Roles User Information User Login Scripts
Name of duplicate user, number of users so named, first and last name of each user, context of each user Group name, general information about the group (owner, description, location, department, and organization), list of members of the group Organizational role name, description, list of occupants, list of other objects that are explicitly security equivalent to the organizational role Username, first name, last name, employee ID, description, location, department Username, other (unofficial) names for the user, description of the user, content of the user's login script

9.2 Setting Up Reporting

The reporting setup you need depends on the kind of reports you want to generate, as summarized in the table below. Steps for completing the reporting setup are given after the table. IMPORTANT: Reporting works only if you run ConsoleOne on a Windows computer with 128 MB of RAM. It doesn't work if you run ConsoleOne on NetWare, Linux, Solaris, or Tru64. In addition, the eDirectory tree you are reporting on must contain a NetWare volume to install the report catalog files on. If your eDirectory tree doesn't contain a NetWare server, you can't set up reporting in ConsoleOne.

9.4 Designing Custom Reports
To design custom reports, you must complete the general reporting setup (see Section 9.2, Setting Up Reporting, on page 92), and then add the JReport Designer tool (purchased separately) to the ConsoleOne installation that you will use to design reports. You can then create your own custom report catalogs and report forms. In This Section Adding JReport Designer to Your ConsoleOne Installation on page 96 Creating a Custom Report Catalog on page 97 Creating or Modifying Report Forms on page 97
9.4.1 Adding JReport Designer to Your ConsoleOne Installation
1 From the Windows computer where ConsoleOne is installed, or from a Windows computer with a drive mapped to the NetWare server where ConsoleOne is installed, start a Web browser and go to the Novell ConsoleOne site (http://www.novell.com/products/consoles). 2 Locate and click the JReport Designer for ConsoleOne link. This should take you to a Jinfonet Web site where you can download a package called JReport Designer for Novell Reporting Services. This package is designed to integrate the JReport Designer tool with your ConsoleOne installation. If you can't find the JReport Designer link on the ConsoleOne site, check the site again later. At the time of this publishing, the availability date for JReport Designer hasn't been finalized. 3 Follow the instructions on the Jinfonet Web site to download and run the JReport Designer for Novell Reporting Services setup program (DESIGNER.EXE or SETUP.EXE).
4 Follow the prompts to complete the setup. When you are prompted for the installation directory, choose the location of your ConsoleOne installation. By default, this is:
Local Drive Network Drive C:\NOVELL\CONSOLEONE\1.2 SYS:PUBLIC\MGMT\CONSOLEONE\1.2
9.4.2 Creating a Custom Report Catalog
1 Right-click the container that you want to create the Report Catalog object in > click New > click Object. 2 Under Class, select Report Catalog > click OK. 3 In Name, enter a name for the new report catalog object. Be sure to follow proper eDirectory naming conventions. (See Naming Conventions (http:// www.novell.com/documentation/edir871/edir871/data/a2iiidp.html#a2iiie9) in the Novell eDirectory Administration Guide.) Example: Custom XYZ Reports 4 Select the location to store the files associated with the report catalog, and select the data source to be used by the report catalog. Click Help for details. 5 Click OK. 6 In the Add Table dialog box, select the database tables that your report forms will query > click Add. Repeat this action as needed. If you are using the Novell-defined NDS Reporting data source, most of the database tables correspond to eDirectory object classes. 7 Click Done in the Add Table dialog box. 8 Create the catalog's report forms as explained below.

9.4.3 Creating or Modifying Report Forms
1 Right-click the report catalog object that contains (or will contain) the report forms > click Properties. 2 On the Forms page, create and modify the report forms you want. Click Help for details. Clicking New or Open on the Forms page starts the JReport Designer tool. For information on using that tool, see the JReport User's Guide (http://www.jinfonet.com/docs.htm).

Troubleshooting

Use to Get
This chapter gives solutions to problems you might encounter when setting up or using ConsoleOne. If this information doesn't solve your problem, you can try the following contacts:

Contact

Novell Support site (http://support.novell.com) or the vendor you purchased the software from 1-800-NETWARE Novell Product Downloads site (http:// download.novell.com)
Free technical support Direct, charged Novell technical support ConsoleOne updates
In This Chapter Section 10.1, ConsoleOne Malfunctions or Won't Start, on page 100 Section 10.2, Performance Is Sluggish, on page 100 Section 10.3, I Need a Completely Local Installation, on page 101 Section 10.4, Can't Find the eDirectory Tree That I Want to Log In To, on page 101 Section 10.5, Newly Created User Can't Log In, on page 101 Section 10.6, Can't Create Volume or Directory Map Object, on page 101 Section 10.7, Can't Abort Partition Operation, on page 102 Section 10.8, Problems Generating a Report, on page 102 Section 10.9, Field or Option is Disabled, on page 102 Section 10.10, Known Quirks and Limitations, on page 102 Section 10.11, ConsoleOne 1.3.4 Errors, on page 104 Section 10.12, Authentication and Password Modification Errors in ConsoleOne 1.3.6, on page 104 Section 10.13, Menu Keyboard Navigation Indicators Are Not Displayed, on page 105 Section 10.14, Creating Objects Using ALT+255 Displays a Question Mark (?) Character in ConsoleOne 1.3.6, on page 105 Section 10.15, Login Fails from Windows Workstation, on page 105 Section 10.16, Role Based Services Saves the Page Even if You Cancel the Property Book, on page 105 Section 10.17, Unable to Delete Custom Attributes in the Other Tab of a User, on page 105 Section 10.18, The Add and Delete Option Remains Disabled after Applying Changes on Other Property Book Page, on page 105 Section 10.19, The Splash Screen that Shows the Snapins Loading Does Not Get Displayed While Starting ConsoleOne, on page 106 Section 10.20, ConsoleOne Import/Export functionality Failing on Solaris, on page 106
10.1 ConsoleOne Malfunctions or Won't Start

Possible Cause Solution

You are starting ConsoleOne Make sure you have the system requirements and drive mappings on a Windows computer that specified for Windows on page 18. doesn't have the required drive mapping or Novell client software. You are starting ConsoleOne on a NetWare server that doesn't have NJCL 2 installed properly. You are starting ConsoleOne on a Linux or Solaris computer that doesn't have the correct Java runtime environment (JRE). Remove the \NJCLV2 folder from SYS:JAVA on your server and reinstall ConsoleOne. This installs a new copy of NJCL 2 on your server so that ConsoleOne will work. If you chose not to install the JRE during installation of ConsoleOne and your existing JRE is not the one noted in System Requirements for Linux on page 21 or System Requirements for Solaris on page 23, you might want to add the bundled JRE to your ConsoleOne installation (type c1-install -c jre at the system prompt, applicable to Consoleone 1.3.6f or lower). For Consoleone 1.3.6h or higher, type Linux : rpm -ivh NOVLc1Linuxjre-1.4.2-13.i386.rpm Solaris : pkgadd -vd NOVLc1jre.pkg If you are sure you want to run with a different JRE, then set the JRE_HOME or C1_JRE_HOME environment variable to the location of that JRE. ConsoleOne determines which JRE to use as follows: If C1_JRE_HOME is specified, that JRE is used. If the JRE bundled with ConsoleOne is installed, that JRE is used. If JRE_HOME is specified, that JRE is used. Otherwise, ConsoleOne displays an error message and quits. You are starting ConsoleOne remotely through an X terminal session on a computer that doesn't have an X windowing subsystem. If ConsoleOne is installed on a Linux or Solaris computer and you are trying to run it remotely through an X terminal session, the computer where you are running the terminal session must have an X windowing subsystem installed or it won't work. The X terminal session must be configured to permit transmissions from the remote host and to use the local X windowing subsystem for display.

novdocx (en) 6 April 2007

ConsoleOne 1.3.6h

September 2007

1 Overview

ConsoleOne is a Java utility that lets you manage Novell eDirectory objects, schema, partitions, replicas, and NetWare server resources. Additional capabilities are added to ConsoleOne if you install other Novell products. For example, if you install eDirectory, LDAP management capabilities are added.

2 Installation

ConsoleOne is typically installed as part of a larger product, such as Novell eDirectory or NetWare. If this release of ConsoleOne hasn't been installed by a larger product, you can install it using the procedure below for your platform.

2.1 Windows

Prerequisites Novell Client Version 4.91 Novell Client Version 4.91 SP3 or above is recommended You can install and run ConsoleOne locally on a Windows workstation or server, or you can install it remotely on a NetWare or Windows server and run it through a mapped or shared drive pointing to that server. If you install locally on a workstation, other Novell products such as Novell eDirectory might not be able to add needed snap-ins to your installation. For this reason, we recommend a server installation. 2.1.1 Installing ConsoleOne on Windows Use this procedure to install ConsoleOne locally on a Windows server or workstation. To install ConsoleOne remotely on a NetWare server, see NetWare on page 2. 1 If a previous version of ConsoleOne is running on the Windows computer, exit it. 2 Insert the CD that contains ConsoleOne, or go to the Novell Product Downloads Site (http:// download.novell.com) 3 Browse the CD or Web site until you find the available ConsoleOne packages > select the package for Windows/NetWare. TIP: If you are using a CD that runs an installation program and you see an option to install just ConsoleOne, choose that option and skip to Step If you are using the Web site, download and unzip the ConsoleOne files to a temporary area. If you are using a CD, skip this step. 5 Run the installation executable file (setup.exe or consoleone.exe).
6 Follow the instructions on the screen to complete the installation. TIP: If you are installing on a Windows server and you will run ConsoleOne remotely through drive sharing, don't forget to share the folder where you install ConsoleOne. Some Novell products require that this share be established before running the installation program.

2.2 NetWare

If you install ConsoleOne on a NetWare server, you can run it locally on that server or remotely on a Windows computer with a drive mapped to that server. Installing ConsoleOne on a NetWare server also allows other Novell products such as eDirectory to add needed snap-ins to your installation. 2.2.1 Installing ConsoleOne on NetWare 1 Bring down Java and any Java applications that are running on the server, including the server GUI. You can do this by entering JAVA -EXIT at the console prompt. 2 Have all users who are currently running ConsoleOne remotely through a connection to the server exit their ConsoleOne sessions. 3 At a Windows workstation, map a drive letter to the root of the server's SYS volume. 4 At the same workstation, insert the CD that contains ConsoleOne, or go to the Novell Free Downloads site (http://download.novell.com) 5 Browse the CD or Web site until you find the available ConsoleOne packages > select the package for Windows/NetWare. TIP: If you are using a CD that runs an installation program and you see an option to install just ConsoleOne, choose that option and skip to Step If you are using the Web site, download and unzip the ConsoleOne files to a temporary area. If you are using a CD, skip this step. 7 Run the installation executable file (setup.exe or consoleone.exe). 8 Follow the instructions on the screen to complete the installation. When you are prompted for the location to install to, select the drive that is mapped to the root of the server's SYS volume. IMPORTANT: You must select a drive that is mapped to a letter, not a UNC path.

2.3 Linux

You can install and run ConsoleOne locally on a Linux computer. You can also run it from another computer through an X terminal (remote) session, if that computer has an X windowing subsystem. 2.3.1 Installing ConsoleOne on Linux 1 If previous versions of ConsoleOne and eDirectory are running on the Linux computer, shut them down and uninstall them completely from the system (remove all the associated files). 2 Insert the CD that contains ConsoleOne, or go to the Novell Free Downloads site (http:// download.novell.com)

3 Locate the ConsoleOne installation program (the c1-install file) on the CD or by downloading it from the Web site as follows:
Source CD Web site Steps to Locate the c1-install File Change to the ConsoleOne/Linux directory. Click Management > ConsoleOne for Linux. Follow the instructions on the Web site to download the ConsoleOne package (the c1linux.tar file). Unpack the file you just downloaded (type tar xf c1linux.tar at the system prompt). Change to the ConsoleOne/Linux directory that was created by unpacking the download file.
4 Run the ConsoleOne installation program (type c1-install at the system prompt). 5 Follow the prompts to complete the installation. IMPORTANT: This release of ConsoleOne for Linux has been tested only on the Sun 1.4.2_13 Java runtime environment (JRE). This JRE is included in the ConsoleOne installation package in case you don't have it. If you do have it and it's already installed, select No when you are prompted whether to install it. After ConsoleOne is installed, you can uninstall it at any time by entering the c1-uninstall command at the system prompt. For a log of ConsoleOne installation or uninstallation results, see the corresponding log file created in the /var directory.

2.4 Solaris

You can install and run ConsoleOne locally on a Solaris computer. You can also run it from another computer through an X terminal (remote) session, if that computer has an X windowing subsystem. 2.4.1 Installing ConsoleOne on Solaris 1 If previous versions of ConsoleOne and eDirectory are running on the Solaris computer, shut them down and uninstall them completely from the system (remove all the associated files). 2 Insert the CD that contains ConsoleOne, or go to the Novell Free Downloads site (http:// download.novell.com) 3 Locate the ConsoleOne installation program (the c1-install file) on the CD or by downloading it from the Web site as follows:
Source CD Steps to Locate the c1-install File Change to the ConsoleOne/Solaris directory.

Web site

Click Management > ConsoleOne for Solaris. Follow the instructions on the Web site to download the ConsoleOne package (the c1sol.tar file). Unpack the file you just downloaded (type tar xf c1sol.tar at the system prompt). Change to the ConsoleOne/Solaris directory that was created by unpacking the download file.
4 Run the ConsoleOne installation program (type c1-install at the system prompt). 5 Follow the prompts to complete the installation. IMPORTANT: This release of ConsoleOne for Solaris has been tested only on the Sun 1.4.2_13 Java runtime environment (JRE). This JRE is included in the ConsoleOne installation package in case you don't have it. If you do have it and it's already installed, select No when you are prompted whether to install it. After ConsoleOne is installed, you can uninstall it at any time by entering the c1-uninstall command at the system prompt. For a log of ConsoleOne installation or uninstallation results, see the corresponding log file created in the /var directory.

2.5 Tru64 UNIX

You can install and run ConsoleOne locally on a Tru64 UNIX computer. You can also run it from another computer through an X terminal (remote) session, if that computer has an X windowing subsystem. 2.5.1 Installing ConsoleOne on TruIf previous versions of ConsoleOne and eDirectory are running on the Tru64 UNIX computer, shut them down and uninstall them completely from the system (remove all the associated files). 2 Insert the CD that contains ConsoleOne, or go to the Novell Free Downloads site (http:// download.novell.com) 3 Locate the ConsoleOne installation program (the c1-install file) on the CD or by downloading it from the Web site as follows:
Source CD Web site Steps to Locate the c1-install File Change to the ConsoleOne/Tru64 directory. Click Management > ConsoleOne for Tru64. Follow the instructions on the Web site to download the ConsoleOne package (the c1tru64.tar file). Unpack the file you just downloaded (type tar xf c1tru64.tar at the system prompt). Change to the ConsoleOne/Tru64 directory that was created by unpacking the download file.
4 Run the ConsoleOne installation program (type c1-install at the system prompt). 5 Follow the prompts to complete the installation. IMPORTANT: This release of ConsoleOne for Tru64 UNIX has been tested only on the Compaq* 1.2.2 Java runtime environment (JRE). This JRE is included in the ConsoleOne installation package in case you don't have it. If you do have it and it's already installed, select No when you are prompted whether to install it. After ConsoleOne is installed, you can uninstall it at any time by entering the c1-uninstall command at the system prompt. For a log of ConsoleOne installation or uninstallation results, see the corresponding log file created in the /var directory.

3 Known Issues

The following are the known issues and suggested workarounds: Role Based Services saves the page even if you cancel the property book. This happens when you add a role and define the scope for it, and then do other operations. To resolve this, you need to delete the role before you exit from the properties page. Else, the role will be saved. Unable to delete custom attributes in the Other tab of a user. To resolve this, grant supervisor entry right to the Other tab. Add and Delete option remains disabled after applying changes on Other property book page. Work around: Select the node, that is the attribute you are adding, for example, Mailbox Location before applying the changes. ConsoleOne on Windows uses Jndi for directory naming operation. If you give a name where a backslash (\) appears more than one time, e.g \\\\.test.novell. ConsoleOne fails to work correctly if the RDN of an object ends with a" \" since Jndi recognizes only one backslash " \" as an escape character and ignores the rest appearing in the name. This is a limitation of the language and not ConsoleOne. Work around: It will efficiently work with iManager since iManager uses JClient. Use iManager instead of ConsoleOne. Older ConsoleOne versions break nds utilities. If you install any version of ConsoleOne prior to ConsoleOne 1.3.6h on an OES2 server, many utilities do not function properly. For example, the following error message displays for ndsrepair: ndsrepair: symbol lookup error: ndsrepair: undefined symbol: compute_paths To resolve this issue, uninstall the older versions of ConsoleOne and install ConsoleOne 1.3.6h or above.

4 Documentation

For additional information on ConsoleOne, refer to ConsoleOne User Guide (http:// www.novell.com/documentation/consol13/index.html).
5 Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. A trademark symbol (, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.

6 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not use, export, or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Patents: U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903; 5,633,931; 5,652,859; 5,671,414;5,677,851; 5,692,129; 5,701,459; 5,717,912; 5,758,069; 5,758,344; 5,781,724; 5,781,724; 5,781,733; 5,784,560; 5,787,439; 5,818,936; 5,828,882;5,832,274; 5,832,275; 5,832,483; 5,832,487; 5,850,565; 5,859,978; 5,870,561; 5,870,739; 5,873,079; 5,878,415; 5,878,434; 5,884,304; 5,893,116;5,893,118; 5,903,650; 5,903,720; 5,905,860; 5,910,803; 5,913,025; 5,913,209; 5,915,253; 5,925,108; 5,933,503; 5,933,826; 5,946,002; 5,946,467;5,950,198; 5,956,718; 5,956,745; 5,964,872; 5,974,474; 5,983,223; 5,983,234; 5,987,471; 5,991,771; 5,991,810; 6,002,398; 6,014,667; 6,015,132;6,016,499; 6,029,247; 6,047,289; 6,052,724; 6,061,743; 6,065,017; 6,094,672; 6,098,090; 6,105,062; 6,105,132; 6,115,039; 6,119,122; 6,144,959;6,151,688; 6,157,925; 6,167,393; 6,173,289; 6,192,365; 6,216,123; 6,219,652; 6,229,809. Patents Pending. Novell is a registered trademark of Novell, Inc. in the United States and other countries. SUSE is a registered trademark of SUSE AG, a Novell business. All third-party trademarks are the property of their respective owners.