Installing Server Inventory on NetWare and Windows Servers

The ZfS 3 Server Inventory installation process, by default, assigns Standalone as the Inventory server role. The Standalone Server has the following characteristics:

To install ZfS Server Inventory in other deployment scenarios:

  1. Use top-down deployment for Inventory installation. Always begin the installation at the topmost level server and proceed with the next lower-level servers. For example, in an inventory setup with a Root Server and a Leaf Server, complete the inventory installation at the Root Server, and then run the installation for the Leaf Server. For more information on the role of servers, see Setting Up Server Inventory in Server Inventory in the Administration guide.

  2. After the Server Inventory installation, change the role of the Inventory server by configuring the Inventory Service object settings. For more information, see Setting Up Server Inventory in Server Inventory in the Administration guide.

Follow this sequence to install Server Inventory:

  1. Review the Readme, located on the ZENworks for Servers 3 program CD, for any last-minute information concerning installation.

  2. Select the Windows NT/2000 workstation or server where you will run the ZfS installation program.

    The recommended version of the Novell ClientTM must be installed on this workstation or server.

    IMPORTANT:  Make sure that ConsoleOne is not running on this workstation during the ZfS installation.

  3. Log into the eDirectory tree if you want to:

    Make sure that the eDirectory trees with servers where you want to install the Inventory server or the Inventory database components have the ZfS 3 schema extended.

  4. At the workstation, insert the ZENworks for Servers 3 program CD.

    The startup screen is displayed. If the startup screen is not automatically displayed after inserting the CD, run WINSETUP.EXE, located at the root of the CD.

    IMPORTANT:  If you copied the ZENworks for Servers 3 program CD structure to the installation workstation's hard drive, the path between the root of the hard drive and the first CD directory can contain only directory names that conform to the 8.3-character DOS file naming convention. If any long directory names exist in the path, the installation program will not work.

  5. To extend the schema on the target trees, click Schema Extensions > follow the prompts.

    If you have already extended the schema on the target tree, you need not extend it once again because the ZfS 3 schema extensions only need to be done once for a tree.

  6. Click New Installation > click Policy-Enabled Server Management.

  7. Read the license agreement > click Accept if you agree with the terms of the Software License Agreement > click Next.

  8. To perform a new installation, click New Installation > click Next.

    or

    To install from a saved installation configuration file, click Template Installation > browse for or enter the path and the filename > click Next.

  9. Select Server Inventory.

  10. Click Next to accept the defaults in the Installation Options page.

    NOTE:  If you want to independently install the ConsoleOne snap-ins, the Inventory Agent, or the Proxy Service, deselect Create eDirectory Objects.

  11. Browse for and select the tree where you are currently installing ZfS 3 Server Inventory > click Next.

  12. In the Server Selection for Inventory Services page, do the following:

    1. Click the Add Servers button > browse to the server objects and select them.

      NOTE:  In the Add Servers dialog box, you can list the servers by their eDirectory tree names or by Microsoft* Domain names. If you select the servers from the Microsoft Domain, you will be prompted to authenticate to the server.

      Make sure that the selected servers do not have the ZfD 3.x or earlier version components installed.

      This populates the selected server names to the Server Name column in the Server Selection for Inventory Services page.

      WARNING:  If you choose install on servers that are not residing in the tree selected in Step 11, but you have logged into this tree and chose to create eDirectory objects in Step 10, the installation program will create eDirectory objects in this tree also.

    2. To install ZfS 3 Server Inventory ConsoleOne snap-ins on the local machine, click the check box under ConsoleOne Snap-Ins column for the Local Machine.

      Local Machine refers to the Windows NT/2000 workstation or server you are using to perform the installation.

      If the local machine is a Windows NT/2000 workstation, you can install only the ZfS 3 Server Inventory ConsoleOne snap-ins. The other components will be unavailable.

      If the local machine is a Windows NT/2000 server with eDirectory installed, you can install the ZfS Inventory ConsoleOne snap-ins, the database, the Inventory Server, the Inventory Agent, and the Proxy Service.

      If the local machine is a Windows NT/2000 server without eDirectory, you can install the ZfS Inventory ConsoleOne snap-ins, the database, the Inventory Agent and the Proxy Service; however, the database objects will not be automatically created. To manually create the database objects, see Setting Up the Inventory Database for Sybase in Setting Up Server Inventory in Server Inventory in the Administration guide.

    3. For any server where you installed ConsoleOne, click the ConsoleOne Snap-Ins check box.

      To install the ConsoleOne snap-ins on all the servers, right-click anywhere in the ConsoleOne Snap-ins column and click Select All.

    4. Click the check box under the Database column for servers where you want to install the Inventory database to run on Sybase.

      To install the Inventory database on all the servers, right-click anywhere in the Database column and click Select All.

      NOTE:  If you want to use the Inventory database with an existing Oracle setup, do not select this option during the Server Inventory installation. Follow the steps in Setting Up the Inventory Database for Oracle in Setting Up Server Inventory in Server Inventory in the Administration guide.

    5. Click the check box under the Inventory Server column for the server where you want to run the Inventory services.

      To install the Inventory Server on all the servers, right-click anywhere in the Inventory Server column > click Select All.

    6. Click the check box under the Inventory Agent column for the servers that you want to inventory.

      To install the Inventory Agent on all the servers, right-click in the Inventory Agent column > click Select All.

    7. Click the check box under the Proxy Service column for the servers where you want to install and configure an XML Proxy server.

      If you want to send or roll up the scan data to an Inventory server that is across the firewall, you must configure a NetWare 5.1/6 or Windows NT/2000 server to run the XML Proxy service.

      To install the Proxy Service on all the servers, right-click in the Proxy Service column and click Select All.

    8. Click Next.

  13. In the Inventory Server Path Configuration page, do the following:

    1. Browse to add the path on the selected server where you want to install the Inventory server-side components.

      This path could be the same per platform for all target servers. For example, the defaults are SYS:\ZENWORKS for NetWare and C:\ZENWORKS for Windows.

      You can specify a different path for each server.

      NOTE:  Do not use spaces in the install path.

    2. If you have Novell Certificate Server installed and want to use the secure LDAP connection, click the Configure SSL check box to configure the Secure Socket Layer (SSL).

      By default, this option is selected.

    3. Browse to add the SSL certificate path on the selected server.

      To select a Trusted Root Certificate, you must first export it, either when you install Novell Certificate Server on a NetWare 5.1 or 6 server in the tree or by following the procedure below.

      If you have not yet exported the Trusted Root Certificate:

      • In ConsoleOne, right-click the SSL Certificate object (SSLCertificateDNS-server_name) > click Properties > click the Certificates tab > click the Trusted Root Certificate sub-option > click the Export button.
      • In the Export a Certificate dialog box, select the default settings by clicking the Export button.
      • Click Apply > Close.

      To select a certificate that was exported during the Novell Certificate Server installation:

      • Map a drive to SYS:\ volume of the NetWare server that the certificate was exported to.
      • Browse to and select the \PUBLIC\ROOTCERT.DER file.

      This certificate can be used for those servers in the tree using the organizational certificate authority created during Novell Certificate Server installation.

    4. Click Next.

  14. If you chose to install the Proxy service in Step 12.g, the XML Proxy Service configuration page will be displayed.

    1. Browse to add the path on the selected server where you want to install the XML Proxy service.

    2. Enter the port number of the XML Proxy service.

      You must enter a value between 0 and 65535.

      The firewall must allow XML RPC requests to the XML Proxy service on this port number to pass through. For more details on opening the port for a firewall, see the appropriate Firewall documentation.

    3. Click Next.

  15. To save the current installation configuration, click the Save the Following check box > enter a path and filename for the template file.

    You can use this template file to repeat the ZfS 3 Server Inventory again.

  16. Click Finish to begin the installation process.

  17. After installation, review the installation log file to ensure that all the selected components have been successfully installed.

    If you receive error messages during installation, see Installation Error Messages for more information.

  18. If necessary, rerun the Installation Wizard to install any components that failed to install.

  19. Click Exit to close the main installation program.

Before starting the Server Inventory service, you need to perform certain post-installation tasks. Continue with the tasks in Post-Installation Tasks .