Installing on NetWare 6.5

When installing Novell Nsure Audit on NetWare 6.5, we recommended that you follow these instructions to first install Nsure Audit 1.0 from your NetWare 6.5 Installation CD, then run the Nsure Audit 1.0.3 installation to upgrade to version 1.0.3 using the instructions in Installing on NetWare (Upgrading to Nsure Audit 1.0.3).

1. Start the NetWare 6.5 installation.

2. In the Choose a Pattern window, select the Novell Nsure Audit Starter Pack.

   • Select Pre-Configured Server > Novell Nsure Audit Starter Pack.

     or

   • Select Customized NetWare Server and mark the following components:
     • Apache2 Web Server and Tomcat4 Servlet Container
     • MySQL (if you want to configure the MySQL data store during installation)
     • Novell Nsure Audit Starter Pack
     • iManager 2.5

3. In the Summary window, review the products to be installed, then click Copy Files.

4. When the installation program displays the Component Selection window for the Novell Nsure Audit Starter Pack, select the program components you want to install.

   • Install Secure Logging Server: Installs the Secure Logging Server (lengine.nlm), the Multiple Directory Database (mdb.nlm), and the channel drivers (lgd*.nlm) to the current server. It also creates a Logging Server object in the Logging Services container.

     You need at least one Secure Logging Server in your network.

     • Autoconfigure MySQL: creates the MySQL Channel object in the Logging Services' Channel container and configures the Secure Logging Server to log events to the MySQL database. If you select this option, you must install MySQL with the NetWare 6.5 install. (See Step 2.)

       WARNING:  The MySQL Channel object is created with a default Expiration script that runs every night at midnight and automatically deletes every record older than 12 hours. This was done because the default events logged by the NetWare and eDirectory instrumentations quickly fill the database. To remove this setting, simply delete the script from the SQL Expiration Commands property in the MySQL Channel object and restart the Secure Logging Server. For more information, see My SQL Channel Object in the Novell Nsure Audit 1.0.3 Administration Guide.

   • Install Platform Agent installs and configures the Platform Agent (logevent.nlm), the Caching Module (lcache.nlm), and the NetWare and eDirectory instrumentations (auditNW.nlm and auditDS.nlm respectively).

     You must install the Platform Agent on every workstation or server that is running an application that logs events to Novell Nsure Audit. To enable NetWare and file system logging, the NetWare instrumentation must be installed and loaded on every server on which you want to log NetWare and file system events. To log eDirectory events, auditDS must be installed and loaded on one server per DS Replica.

     • Secure Logging Server Address is the IP address or host name of the Secure Logging Server that the Platform Agent connects to.

5. If you selected the Autoconfigure MySQL option, the installation program displays the Database Options window so you can define your MySQL data store.

   • MySQL Database Host: The IP Address or host name of the MySQL database server.
   • Port: Defines the port at which the Secure Logging Server connects to the database server. If this field is left blank, the Secure Logging Server uses the default MySQL port assignment, 3306.
   • DB Username: User account the Secure Logging Server uses to log in to the database. This account has all privileges to the default database and can log in from any IP address. The default username for the NetWare 6.5 data store is "auditusr."
   • DB User Password: Password the logging server uses to authenticate with the database. You must confirm this password. The default password for the NetWare 6.5 data store is "auditpwd."
   • Database Name: Name of the database to which the logging server writes events. The default database name is "naudit."
   • Table Name: Database table to which the logging server writes events. The default table is "log."

6. Follow the prompts to complete the rest of the NetWare 6.5 install. For more information, see the OES NetWare Installation Guide.

Upon completing the installation, you must restart the server or manually launch the installed components. For the program startup commands, see Commands and Utilities in the Novell Nsure Audit 1.0.3 Administration Guide.

Installing on NetWare (Upgrading to Nsure Audit 1.0.3)

1. On the NetWare server, insert, and if necessary, mount the NCL Server Components - CD 1, then launch NWConfig.

   • Load nwconfig.nlm at the server console.

2. In NWConfig, Select Product Options > Install a Product Not Listed.

3. Press F3 (F4 if you're using RCONSOLE) and specify the path to the directory where the installation program can find the install.ips file, which is located in the ncl_2_0_1:\nsureaudit\netware directory on the NCL Server Components - CD 1.

4. Select your install options. Each option is outlined in the following table. The third and fourth columns contain the recommended settings for a new installation and upgrade.

   Option	Description	New Install	Upgrade
   First-time Directory Install	Extends the Directory schema for Novell Nsure Audit version 1.0.3.	Yes	No
   Configure Server for Nsure Audit	Creates the Secure Logging Server object in Logging Services. It also creates a File Channel object in the Logging Services Channel container, and configures the Secure Logging Server to log events to the File channel.	Yes	No
   Nsure Audit Log Server Files	Installs the Novell Nsure Audit Secure Logging Server (lengine.nlm). The Secure Logging Server securely receives reported events, and is installed on only one server in your tree.	Yes	Yes
   Nsure Audit Instrumentation Files	Installs the NetWare Instrumentation (auditNW.nlm) and the eDirectory Instrumentation (auditDS.nlm). This instrumentation must be installed on any NetWare server that will report events.	Yes	Yes
   Nsure Audit Platform Agent Files	Installs the Novell Nsure Audit Platform Agent (logevent.nlm). The Platform Agent must be present on any NetWare server that will report events. If you are certain another instrumented application has previously installed the Nsure Audit 1.0.3 Platform Agent on this server, you can leave this unselected.	Yes	Yes
   Backup Files from Previous Versions	Makes a backup of existing Nsure Audit files to enable rollback.	No	Yes
   Directory Schema Update	Updates the Directory schema for Novell Nsure Audit version 1.0.3. NOTE:  You must scroll to see this option in nwconfig.	No	Yes

5. Press F10 to continue, then follow the on-screen instructions until you have completed the installation program.

If you selected First-time Directory Install or Directory Schema Update, enter the Directory administrator's login name and password to update the schema. This account must have admin rights to the root of the tree. If the admin object is not in the same context as the current server, you must enter the object's fully distinguished name (for example, .Admin.Accounts.Finance.YourCo).

If you selected Configure Server for Nsure Audit, you are prompted to provide a name for the Secure Logging Server object.

NOTE:  Do not overwrite newer files.

Upon completing the installation, you must restart the server or manually launch the installed components. For the program startup commands, see Commands and Utilities in the Novell Nsure Audit 1.0.3 Administration Guide.

Prerequisite Procedure

Before installing the Password Generation Service, you must first extend the eDirectory schema by doing the following:

1. From the NCL Server Components - CD 1, copy the passwordgenerationservice.sch file to a temporary location on the server's hard drive.

2. Rename the passwordgenerationservice.sch file to an 8.3 convention name. For example, pgsschem.sch.

3. From the NetWare server console, load NWCONFIG, then select Directory Options > Extend Schema.

4. Enter the username and password of a user with rights to extend the schema.

5. Enter the path to the renamed Password Generation Service schema file.

   This will update the schema. If the process completes successfully, you return to the Extend Schema screen.

Installation Procedure

To install the Password Generation Service:

CD: NCL Server Components - CD 1

Location: \passwordgenerationservice

NOTE:  You need to be authenticated as an Active Directory Domain Administrator on a Windows machine before running this install. When configuring the Password Generation Service, you must configure it to run as the same administrative user. If you change the Password Generation policy, ensure that you log in as the same administrative user.

1. Run setup.exe.

2. On the Welcome screen, click Next.

3. When you receive a reminder message about manually extending the eDirectory schema. Click OK to close the message.

   You already extended the schema in the previous section.

4. Specify the Password Generation Policy values.

   
   

   Make sure the policy does not contain conflicting rules.

   A conflicting policy would be as follows:

   Min Password Length = 10

   Max Password Length = 5

   IMPORTANT:  Your Password Generation policy must match your Active Directory password policy or you will receive Active Directory errors when Password Generation attempts to set the password.

5. Click OK > Finish.

Post-Install Procedure

After you have the Password Generation Service installed and running, you need to give the service rights to log on to the Active Directory Domain.

1. Click Start > Settings > Control Panel > Administrative Tools > Services.

2. Right-click PasswordGenerationService, then click Properties.

3. Click the LogOn tab.

4. Select This Account.

5. Click the browse button and select your Active Directory Domain/Administrator user.

6. Type the password, then retype the password where instructed to do so.

7. Click Apply, then click OK.

8. Restart the PasswordGenerationService.

   You have to restart the service before changes take effect.

9. (Optional) Check the passwordgen.log file in the \system32 directory to make sure the service was started correctly.

For information on using the Password Generation Service plug-in and command line utilities, see Using the Password Generation Service.