After installing the Novell ZENworks Server Management software to NetWare, Windows, Linux, and Solaris servers, there are tasks that cannot be automated within the installation processes that you should perform to complete the installation. The following sections give details about these tasks.
The first section contains tasks that should be done for all of the Server Management components. The other four sections are divided by component, and are listed by the components that can be installed.
Perform the necessary tasks in each of the following sections for the Server Management components you have installed:
The following tasks are specific to the Policy and Distribution Services component:
Restarting the Novell Servlet Gateway on NetWare 5.1 Servers
If you have a Novell Servlet Gateway running on a server where you installed Server Management, you need to restart the gateway’s Java process manually.
Creating the Policy and Distribution Database
To provide reporting capability for a Linux or Solaris Distributor server, follow these instructions to create a database on a NetWare or Windows server.
Configuring the Policy and Distribution Services Agents on Servers with Multiple Network Addresses
If a server where you have installed the Policy and Distribution Services agents has multiple network addresses on your network, follow these instructions.
Using Policy and Distribution Services
This section contains suggestions on what you can do next with Policy and Distribution Services.
The installation program stops all Java processes before installing ZENworks Server Management. After the Server Management installation is completed, the installation program attempts to automatically restart all of the Java applications that it had stopped before installing. Occasionally, there are Java process that the installation program cannot restart.
On NetWare 5.1 servers, the Novell Servlet Gateway application cannot be restarted automatically by the installation program. If you have this Java process running on a NetWare 5.1 server where you installed ZENworks, you need to restart it manually.
The Policy and Distribution database stores log messages for reporting purposes, detailing the successes and failures of Distribution processing and policy statuses. The database file currently cannot be created on a Linux or Solaris server. Therefore, if you want database logging by any Linux or Solaris Distributor or by the Policy/Package Agent, you must install the database on a NetWare or Windows server.
If you have not previously installed a database with a Database object in the eDirectory tree where the Linux or Solaris Distributor object resides, and you want database logging for the Linux and Solaris servers, perform the following procedure at a Windows installation machine:
If you have not already done so, log in to the eDirectory tree where the Distributor and Subscriber objects are created.
Insert the Novell ZENworks 7 Server Management with Support Pack 1 Program CD.
The initial installation program window appears. If it does not display automatically after inserting the CD, run winsetup.exe at the root of the CD.
Click , then select .
Accept the License Agreement, then click .
is selected by default.
Click .
is selected by default.
Click .
The and options are selected by default.
Click .
Select the eDirectory tree where you want to create the ZENworks Database object, click , then click .
In the Server Selection dialog box, click .
If the NetWare or Windows server where you want to create the Policy and Distribution database file has a corresponding eDirectory object, browse the eDirectory tree, then select the Server object.
or
For a Windows server in a Microsoft domain, in the drop-down list, click , expand the domain, then select the server.
Move the selected server from the list box into the list box, then click .
Back in the Server Selection dialog box, on the line for the selected server, mark the column, then click .
Fill in the fields:
Database path: Keep in mind that the Policy and Distribution database can become very large.
On NetWare, the default database path is sys:\zenworks. You should change the database path to use a volume other than sys:.
On Windows, the default database path is c:\zenworks. Whether this is an appropriate location depends on the size of the C: drive and the space available on other drives on the server.
Object name: The default object name is “ZENworks Database.” You can rename it if you plan to install multiple databases.
Container: Browse to and select the container object where you want the ZENworks Database object created. You could place it with other Tiered Electronic Distribution objects, or in the same container where the Server object resides.
Click .
The installation summary lists the server where the database file is installed and the eDirectory object that is created for it.
Click .
When the installation is complete, click to review what the installation program has done.
If the installation log file contains errors, you can print it for reference. To look up installation errors, see Section H.0, Installation Error Messages. Resolve the problem, then repeat the installation successfully.
Close the log file, then exit the installation program.
If a server where you have installed the Policy and Distribution Services agents has multiple network addresses on your network, some additional configuration is necessary before you start the agents. This situation arises when the server has one or both of the following characteristics:
Multiple NICs
Multiple DNS hostnames
Perform the following tasks as necessary:
To ensure that forward and reverse DNS lookups are successful, you need to edit a configuration file for each applicable server. The following steps apply to servers on all supported platforms:
Open the following file in a text editor:
Installation_path\zenworks\zfs‑startup.xml
Search for the following class:
<Class>com.novell.application.zenworks.ted.TED</Class>
Edit the following parameter that is listed under the class:
<Parameter Name="Hosts" />
If the parameter does not exist, create it and insert it in the parameter list.
Change it to include the DNS hostnames or IP addresses of your hosts. For example:
<Parameter Name="Hosts">192.68.1.203</Parameter>
Note the addition of the closing > character after the "Hosts" name and the closing </Parameter> code. Your DNS hostnames and IP addresses go between the codes as show above.
Do not list those that are bound to the server’s NIC card.
If you list more than one host, your list of DNS hostnames and IP addresses should be delimited by a semicolon (;). For example:
<Parameter Name="Hosts">192.68.1.203;192.68.1.204;server001.provo.novell.com</Parameter>
You can mix DNS hostnames and IP addresses in the list.
Save your changes, then close the file.
If you have multiple NICs, a server might not recognize the card that is used for your network access as the primary host card. To ensure that the correct NIC is recognized as the primary host:
In the text editor, open the following file:
Installation_path\zenworks\zfs‑startup.xml
Search for the following class:
<Class>com.novell.application.zenworks.ted.TED</Class>
Edit the following parameter that is listed under the class:
<Parameter Name="PrimaryHost" />
If the parameter does not exist, create it and insert it in the parameter list.
Change it to include the IP addresses of the proper NIC card. For example:
<Parameter Name="PrimaryHost">192.68.1.203</Parameter>
Note the addition of the closing > character after the "PrimaryHost" name and the closing </Parameter> code. The IP address goes between the codes as show above.
If the PrimaryHost parameter already has a DNS hostname, change it to the IP address.
Save your changes, then exit the text editor.
To take full advantage of Policy and Distribution Services, you can further configure your distribution system and server policies by doing the following:
Determining which Distributions you need, including server policies
Creating the Distributions and their related Channels
Determining whether other Distributors are needed
Installing the other Distributors
Creating a routing hierarchy for each Distributor
Configuring parent Subscribers where necessary
Associating Subscribers with Distribution Channels
Sending your Distributions
To do this, you need to understand Policy and Distribution Services, know what Distributions you need, and plan your distribution system. The degree of planning depends on the size and complexity of your network, and the size and frequency of your Distributions.
To understand Policy and Distribution Services, plan how to configure your distribution system, configure server policies, and create new Distributions, see Post-Installation Setup
in the Novell ZENworks 7 Server Management Administration Guide.
The following tasks are specific to the Server Inventory component. You must perform them in the order listed before starting the Server Inventory service on the Inventory server.
Server Inventory requires policy packages in the eDirectory tree that can hold the server policies that you can later configure and enable.
To determine which Policy Package objects to create, first determine which policies you need. For Server Inventory, you must create the following policy packages:
Service Location Package or Server Package
Distributed Server Package
To create Policy Package objects, do the following as applicable:
Policy packages are eDirectory objects that contain collections of policies grouped according to the object types. You should create an Organizational Unit (OU) for holding the policy packages.
Consider the following when determining where to place this OU:
Whether you have partitions in your tree
The 256-character limit in eDirectory for the full distinguished name
The search policy is used to locate the policy package
For Server Inventory, create two containers, one for Tiered Electronic Distribution objects and the other for the Server Inventory policy packages.
To create a container:
In ConsoleOne, right-click the container where you want the container for the policy packages placed.
IMPORTANT:If you have partitions that are accessed across a WAN, make sure that the Policy Package objects are in the same partition as the Server object so that the Policy/Package Agents loads. Also make sure that the Search policy does not require searching outside the partition where the Server object exists.
Click > > , then click .
Name the container (for example, Policies), then click .
Continue with Creating the Service Location Package.
or
Continue with Creating the Server Package.
You should do one or the other of these packages, as necessary.
The Service Location package is required to enable the Database Location policy and to associate the database object with the container under which the Inventory Service object is located.
Right-click the policy package’s container, then click > .
The Policy Package Wizard is displayed.
From the list, select , then click .
Specify a name for the Service Location Package.
Click , then click .
Continue with Creating the Server Package.
or
Continue with Creating the Distributed Server Package.
The Server package is required to enable the Database Location policy and to associate the database object with the Inventory Service object of the Inventory server.
IMPORTANT:If you chose to configure the Inventory Standalone Pre-Configuration settings during the installation, the Server Package is automatically created by the Installation program.
To create the Server Package:
Right-click the policy package’s container, then click > .
The Policy Package Wizard is displayed.
From the list, select , then click .
Specify a name for the Server Package.
Click , then click .
Continue with Creating the Distributed Server Package.
The Distributed Server package is required to distribute the Server Inventory policy among the inventoried servers.
Right-click the policy package’s container, then click > .
The Policy Package Wizard is displayed.
From the list, select , then click .
Specify a name for the Distributed Server Package.
Click , then click .
Continue with Creating and Configuring the Tiered Electronic Distribution Objects.
For Server Inventory, you must create and configure the following Tiered Electronic Distribution objects:
TED Distribution
TED Channel
For more information on how to create and configure the Tiered Electronic Distribution objects, see Tiered Electronic Distribution
in the Novell ZENworks 7 Server Management Administration Guide.
Continue with Configuring the Distribution Object for Server Inventory.
You must configure the Distribution object for distributing the Server Inventory policies.
From ConsoleOne, right-click the Distribution object, then click .
Click the tab.
Select from the drop-down list.
Click .
Select the Distributed Server package that has the Server Inventory policy.
Click the tab.
Modify the schedule.
Click , then click .
Continue with Configuring the Inventory Database Object on a NetWare Server.
If you install Sybase on a NetWare server that has CIFS as a default component, the server IP address or DNS name of the Inventory database_server_name object might not be configured correctly after the Sybase installation.
To configure the database object correctly:
Open ConsoleOne, then double-click the Inventory database object.
At the ZENworks Database page of the database object, enter the server IP address or DNS name of the server where the inventory database is installed.
Continue with Configuring the Policies on the Servers.
In a Standalone Server scenario, a single server acts as the Inventory server and also the database server. There is no requirement for roll-up of inventory data.
To know which policies should be configured for the Server Inventory that is deployed in a production environment, see Setting Up Server Inventory
in the Novell ZENworks 7 Server Management Administration Guide.
If you chose to install Inventory Server and Inventory Database (Sybase) during installation of Server Management, the Inventory Standalone Configuration dialog box was displayed. If you selected the check box in this dialog box, the installation program automatically created the Server Package, configured the Database Location policy within the Server Package, and started the Inventory Services. When the Server Management installation is complete, you need to create only the Server Inventory policy. However, if you did not choose the standalone option, then you must create both the Database Location and Server Inventory policies.
Perform the following applicable tasks to configure the policies:
The Database Location policy contains the location of the Inventory database. You can associate the Database object with a container under which the Inventory Service object is located through using the Service Location Package, or with an Inventory server through using the Server Package.
IMPORTANT:If you configure the Service Location Package and the Server Package, the Server Package settings override the Service Location Package settings.
To associate the Database object with a container under which the Inventory Service object is located:
In ConsoleOne, right-click the Service Location Package, then click to display the Policies page.
Select the check box under the column for the ZENworks Database policy.
Click to display the Inventory Management page.
Browse to the DN of the Inventory Database object (Inventory database_server_name), then click .
For a Sybase database, the database object is automatically created during the Server Inventory installation except if you are installing on a Windows 2000/2003 server without eDirectory installed. To manually create the database object, see Setting Up the Sybase Inventory Database
in the Novell ZENworks 7 Server Management Administration Guide.
For an Oracle database, you must create the database object and configure the object. For more information, see Setting Up the Oracle Inventory Database
in the Novell ZENworks 7 Server Management Administration Guide.
For a MS SQL database, you must configure the database object. For more information, see Setting Up the MS SQL Server 2000 or MS SQL Server 2005 Inventory Database
in the Novell ZENworks 7 Server Management Administration Guide.
Click .
Click the tab, then click .
Browse to select the container under which the Inventory Service object is located, then click .
Click , then click .
Continue with Configuring the Server Inventory Policy.
To associate the Database object with an Inventory server:
In ConsoleOne, right-click the Server Package, click to display the Policies page.
Select the check box under the column for the ZENworks Database policy.
Click to display the Inventory Management page.
Browse to and select the DN of the Inventory Database object (Inventory database_server_name), then click .
For a Sybase database, the database object is automatically created during the Server Inventory installation except if you are installing on a Windows 2000/2003 server without eDirectory installed. To manually create the database object, see Setting Up the Sybase Inventory Database
in the Novell ZENworks 7 Server Management Administration Guide.
For an Oracle database, you must create the database object and configure the object. For more information, see Setting Up the Oracle Inventory Database
in the Novell ZENworks 7 Server Management Administration Guide.
For a MS SQL database, you must configure the database object. For more information, see Setting Up the MS SQL Server 2000 or MS SQL Server 2005 Inventory Database
in the Novell ZENworks 7 Server Management Administration Guide.
Click .
Click the tab, then click .
Browse to select an Inventory server object, then click .
Click , then click .
Continue with Configuring the Server Inventory Policy.
The Server Inventory policy contains the IP address or the DNS name of the Inventory server to which the inventory data is sent. This policy also contains the inventory scanning schedule for the associated inventoried server. You must configure the Server Inventory policy for each inventoried server.
To configure the Server Inventory policy package:
In ConsoleOne, right-click a Distributed Server Package, then click to display the tab.
Click , then click or , depending on the operating system of the inventoried server.
Select the check box under the column for the Server Inventory policy.
Click to display the Server Inventory Policy page.
In the tab, configure the following settings:
Browse to select the DN of the Inventory Service object.
This setting specifies that the scanner sends the server scan data to this Inventory server.
Select the DNS name or the IP address of the Inventory server.
If the roll-up is to an Inventory server that is across the firewall, specify the IP address and the port number of the proxy server.
(Optional) Customize the Inventory scan for the inventoried servers:
To customize the hardware scan for the inventoried servers, click the tab and configure the following settings:
Enable DMI scan: Includes DMI scanning of Windows inventoried servers.
Enable WMI scan: Includes WMI scanning of Windows inventoried servers.
To customize the software scan for the inventoried servers on which Novell ZENworks for Servers 3.0 or ZENworks for Servers 3.0.2 is installed, click the tab and configure the following settings:
IMPORTANT:Do not configure the settings for the inventoried servers where ZENworks 7 Server Management is installed.
Enable software scan: Enables software scanning for the Windows inventoried servers associated with the Inventory policy. The scan program collects software information for the inventoried servers and stores it in the Inventory database.
Custom scan editor: Enables you to customize the list of application details to scan for at the Windows inventoried servers. The Inventory scanner scans for the details of the applications listed in the Custom Scan Editor.
For example, specify the following details in the Custom Scan Editor: Vendor Name=Microsoft; Product Name=Microsoft Office; Product Version=10.0; FileName=winword.exe; File Size=1 MB.
The Inventory scanner scans for the winword.exe file having a size of 1 MB on the inventoried servers. If the file is found, the scanner stores “Microsoft;Microsoft Office;10.0” for “winword.exe;1 MB” in the Inventory database.
Product identification number: Enables you to scan for the product identification number of the Microsoft applications installed on the inventoried servers.
Click the tab; if required, modify the settings of the following .ini files:
Asset information:
Scans for vendor-specific information from DMI. For more information on how to configure the Asset Information, see Scanning for Vendor-Specific Asset Information from DMI
in the Novell ZENworks 7 Server Management Administration Guide.
Zipped names:
Customizes the hardware scanning of Jaz* and Zip* drives. For more information, see Customizing the Hardware Scanning Information of Jaz and Zip Drive Vendors
in the Novell ZENworks 7 Server Management Administration Guide.
SWRules: Configure the SWRules file for the Windows inventoried servers on which Novell ZENworks for Servers 3.0 or ZENworks for Servers 3.0.2 is installed. Do not configure the settings for inventoried servers where ZENworks 7 Server Management is installed.
The option customizes the software scanning information of vendors and products. For more information, see Customizing the Software Inventory Information To Be Scanned For ZENworks for Servers 3.x Inventoried Servers
in the Novell ZENworks 7 Server Management Administration Guide.
HWRules:
Customizes the nominal size of monitors. For more information on how to configure the HWRules .ini file, see Customizing the Hardware Information for Monitor Size
in the Novell ZENworks 7 Server Management Administration Guide.
Click the tab.
Modify the schedule, click , then click .
In the Distributed Server Package property page, click the tab, then click .
Browse to add the Distribution object, then click .
Click , then click .
In ConsoleOne, right-click the Inventory Service object (Inventory Service_server_name), click , then click the tab.
Ensure that the check box is selected, then click .
This setting ensures that scanning is selected for the inventoried servers associated with the selected Inventory server.
Continue with Configuring the Distributor and the Subscriber Object.
To configure the Distributor and the Subscriber object, see Policy and Distribution Services
in the Novell ZENworks 7 Server Management Administration Guide.
If the inventoried servers are residing on a different eDirectory tree or on the Windows server that does not have eDirectory installed, you must create and configure an External Subscriber object for sending Distributions to Subscribers residing on inventoried servers in other trees. For more information on External Subscribers, see Policy and Distribution Services
in the Novell ZENworks 7 Server Management Administration Guide.
Continue with Installing the ODBC Drivers.
Before running the inventory reports, review the following:
Make sure that the appropriate ODBC client for Sybase, Oracle, or MS SQL is installed on the machine running ConsoleOne. The ODBC driver is automatically configured on the machine when you invoke the Inventory report.
To install the ODBC driver for the Sybase database:
In the Novell ZENworks 7 with Support Pack 1 Companion 2 CD, open the \database drivers directory.
Follow the instructions in the ODBCreadme.txt file in the \database drivers directory. The information helps you to set up the address of the Sybase database and verify that you can make a connection.
For Oracle, you must install the appropriate client for ODBC. For example, for Oracle 9i Inventory database, install the Oracle 9i client because Inventory reports are not compatible with either the older or the later version of the client.
For MS SQL, the client is available on all Microsoft Windows operating systems.
Make sure that at least MDAC 2.6 SP1 (Microsoft Data Access Component) is installed particularly on a Windows NT machine for running Crystal Reports. To check the version of MDAC on your box, click > > the tab pane. The minimum version required is 3.520.7326.0. If the version you have does not match the minimum requirement, you need to upgrade the ODBC core components by downloading from Microsoft Download Center.
If you need to start or stop the Inventory services, see Starting the Inventory Service.
If you need to start Samba, see Starting the Samba Service.
This section provides information on the following topics:
Table 6-1 Starting Inventory Services
After starting the Inventory service, make sure that the Inventory services are up and running. To list all services, enter ListSer * at the Inventory server console prompt. If the services are not up and running, check the Server Status log. For more information on the Server Status log, see Monitoring Server Inventory Using Status Logs
in the Novell ZENworks 7 Server Management Administration Guide.
Table 6-2 Stopping Inventory Services
If the Inventory server component is installed on a Linux machine, ensure that the Samba service is up and running by entering /etc/init.d/smb status at the Linux Inventory server console prompt.
If the service is not running, you must manually start the Samba service after the installation to enable the Inventory server to receive the inventory scans from the inventoried workstations. To manually start the Samba service, enter /etc/init.d/smb start at the Linux Inventory server console prompt.