Using ZENworks for Servers 3 Server Inventory

Another important component of ZENworks for Servers 3 server management is server inventory. ZENworks for Servers 3 uses inventory scan programs to scan and store hardware and software inventory of your managed servers. The following sections describe the inventory components and discuss how to scan server inventory and customize software scanning.

Understanding Server Inventory Components

To get the most out of ZENworks for Servers 3 server inventory, you need to understand the components that make up the inventory process and roles that inventory servers play in capturing and storing inventory data.

In a small network, one inventory server would be ample to collect, store, and provide access to the inventory data about servers. But in enterprise networks, the number of servers and the amount of inventory data that can be collected and managed becomes extremely complex. For that reason, ZENworks for Servers 3 implements a tree design to allow several inventory servers to be involved in accumulating and distributing the inventory data. The following is a list of the types of inventory servers and their roles in the inventory process:

  • Standalone server. The standalone server is used in small networks where only one server and database is needed for collecting and storing inventory data from the network. The standalone server collects the inventory data and stores it in a local database.

  • Root server. In an enterprise network, you need to implement several inventory servers to collect and store inventory data. The first inventory server you create is a root server that acts as the top-most level for the inventory tree. The root server must have an inventory database stored on it to store data collected from the other inventory servers below it in the tree.

  • Intermediate server. If you have a large network, you also need to create intermediate servers. The intermediate server collects data from servers below and passes that data to either another intermediate server above, or to the root server. An intermediate server can have an inventory database attached to it to store inventory information locally, but that is not required.

  • Leaf server. The leaf server is the bottom-most level of the tree. Leaf servers are responsible for collecting inventory data that has been scanned, and then passing that data up to the next level in the inventory tree. The leaf server can send data either to an intermediate server or the root server. It can also have an inventory database attached to it to store inventory information locally, but that is not required.

Now that you understand the types of inventory servers that are involved in the server inventory process, you need to understand the components that are involved. ZENworks for Servers 3 uses several different pieces to scan servers for inventory data, process that information, and then store it in the appropriate location. The following is a list of components that make up the inventory process:

  • Inventory scanners. Inventory scanners are agents that run on managed servers that are responsible for scanning the server's hardware and software. They collect the data each time they are run and store that data in a file.

  • Selector. The selector processes the data scanned by the inventory scanners and selects new data that should be added to the inventory database. It then places those scanned files into appropriate directories.

  • Sender and receiver. The sender and receiver are utilities that run on servers to transfer scanned files from an inventory server to the next level of server in the inventory tree.

  • Inventory storer. The inventory storer is a utility that runs on an inventory server with an inventory database attached. It is responsible for taking the inventory scan files that the server receives and storing the inventory data in the database.

  • Inventory database. The inventory database is an RDBMS maintained by Oracle or Sybase or a Microsoft SQL Server and acts as the repository for the hardware and software inventory data collected by the inventory scanners. You can access the data in the inventory database through management console reporting, as well as through user-customized database queries. (For more information about the inventory database, see Appendix A.)

Understanding the Scanning Process

Now that you understand the types of inventory servers and the software components that are involved in ZENworks for Servers 3 server inventory, it is helpful for you to understand the actual process using ZENworks for Servers 3 to scan, collect, and store inventory data.

The first thing that happens in the inventory process is that the inventory scanner agent is activated on a Windows or NetWare Server. The agent reads inventory policy settings (discussed later in this chapter) and uses those settings to scan the server. As the scanning agent runs, it collects data about the server's hardware and software and stores that data in .STR files on the server's local file system. The scan collector then transfers those files to the scan directory (\SCANDIR\) of the inventory server defined in the inventory policy.

After the inventory scanner places data in the scan directory, the selector begins to process the .STR files. The selector filters out everything but new inventory data, and then stores the new data in the enterprise merge directory (\ENTMERGEDIR\) to be transferred to a higher level and/or to the database directory (\DBDIR\) to be stored in the inventory database, if one is running on the server.

After files are stored in the enterprise merge directory, the sender zips up all the scan data files and sends them to a receiver running on another inventory server, which is defined in the roll-up policy (discussed later in this chapter).

The receiver opens the .ZIP files it receives from a sender and copies them to the enterprise merge directory (\ENTMERGEDIR\) to be transferred to a higher level and/or to the database directory (\DBDIR\) to be stored in the inventory database, if one is running on the server. On an intermediate server with an inventory database, for example, the files would be copied to both directories; however, on the root server the files would be copied to only the database directory.

After files are placed, the storer opens the .ZIP file, extracts the scan files to a temp directory (\DBDIR\TEMP\), and updates the inventory data with the data in the .STR files. After the database is updated, the administrator can view the new inventory data from the management console.

Setting Up Server Inventory

Now that you understand the components that are involved in the ZENworks Server Inventory process, you need to understand how to set up and configure the eDirectory objects that control inventory scanning. You use the management console to define the database types and locations in the inventory tree, as well as their synchronization and roll-up schedules. The following sections discuss the configuration changes you need to make at the management console to configure and customize server inventory.

Configuring the Inventory Service Object

The first object you need to configure for server inventory is the inventory service. You must create an inventory service object for each server on which you install ZENworks for Servers 3. The inventory service object defines which role that server plays during the server inventory process. (The inventory service object can be created automatically during the installation of ZENworks for Servers.)

To configure the inventory service object for an inventory server, right-click the inventory service object in ConsoleOne and select Properties. Then select Inventory Service Object Properties from the drop-down list of the Inventory Server Object tab, as shown in Figure 12.14.

Figure 12.14. Inventory service object properties of an inventory service object of a ZENworks for Servers 3 inventory server.

graphics/12fig14.jpg

From the Inventory Service Object Properties panel, you can configure the following items of the inventory server:

  • Inventory Server Role. Select the role of the server (Standalone, Root, Intermediate, or Leaf) from the drop-down list. Then you need to define whether it has a database connected by selecting the Connected to Database box (Intermediate and Leaf only). You also need to specify whether machines are connected to this service (Root and Intermediate only).

  • Discard Scan Data Time. Defines a date and time to discard all scan data and start with a fresh copy.

  • Scan Directory Path. Defines the location on the inventory server where the scan data files are to be stored when a scan is run.

  • Enable Scan of Machines. Enables you to temporarily disable scanning of machines. This option is useful if you need to reduce server or network traffic for troubleshooting or performance reasons.

ZENworks for Servers 3 enables you to configure the synchronization schedule to synchronize servers being inventoried with the inventory server with which they are associated. To configure the synchronization schedule for an inventory server, right-click the inventory service object in ConsoleOne and select Properties. Then select Inventory Server Sync Schedule from the drop-down list of the Inventory Server Object tab, as shown in Figure 12.15.

Figure 12.15. Inventory Server Sync Schedule panel of an inventory service object of a ZENworks for Servers 3 inventory server.

graphics/12fig15.gif

From the Inventory Server Sync Schedule panel, you can configure the following synchronization options for the inventory server:

  • Schedule Type. Determines whether the synchronization is a daily, weekly, or monthly type, or whether it should use the policy package to determine its schedule.

  • Days Active. Enables you to specify, by clicking the day's button, which days the schedule will be active. This is useful for performance reasons. If no changes occur over the weekend, for example, but you are performing network-intensive backups, then you would not select Saturday and Sunday.

  • Start and End Time. Enables you to specify the start and stop time for inventory to occur. This enables you to control what times during the day inventory can run. By setting the stop time to 8:00 a.m., for example, you could have inventory stop at 8:00 a.m. before users begin logging on to the network.

  • Random Dispatch Time. Enables you to have ZENworks randomly start the synchronization between the start and end times.

  • Repeat. Enables you to have ZENworks repeat the synchronization at the specified interval. This can be extremely useful if you are watching software inventory that changes frequently.

Configuring the Distributed Server Inventory Policy

After configuring the inventory service object, you need to configure server inventory policy for distributed server packages that you want to use to collect and distribute inventory data. The server inventory policy enables you to configure which inventory service the servers associated with this package are to use. It also allows you to enable and configure hardware and software scanning.

To configure the server inventory policy for a distributed server package, right-click the package and select Properties from the drop-down menu. Then select the Policies tab for the operating system you want to configure. ZENworks for Servers 3 enables you to select NetWare, Windows, Linux, Solaris, or General to configure for all those operating systems. Next, enable the server inventory policy by checking the box next to it. Finally, select the server inventory policy and click the Properties button to bring up the Server Inventory Policy Properties window. The following sections discuss how to configure the server inventory policy from this window.

Configuring the Inventory Service for the Server

The first step in configuring the server inventory policy is to configure which inventory service the servers associated with this policy are to use. Select the General tab in the Server Inventory Policy panel, as shown in Figure 12.16, and configure the following settings:

  • Inventory Server Object DN. Use the Browse button to navigate through the eDirectory tree and locate the inventory service policy, the correct roll-up schedules, and locations configured for servers associated with this distributed server package.

  • Server IP Address/DNS Name. After selecting the inventory server object, you need to select the IP address or DNS name to use for connecting to the inventory database. Make certain that you select the correct name or address or the inventory servers will be unable to connect to the inventory service database.

  • Proxy Server Configuration. Leave Proxy Server Configuration alone; you do not need to configure it for server inventory.

Figure 12.16. General panel of the NetWare Inventory Server Policy for a distributed server package.

graphics/12fig16.gif

Configuring Hardware Scan

If you are configuring an inventory server policy for Windows, then you need to configure hardware scanning by selecting the Hardware Scan tab and setting the following options:

  • Enable DMI Scan. Enables ZENworks to collect hardware inventory data from Windows NT/2000 workstations by using the Desktop Management Interface (DMI) 2.0 specification. (DMI drivers are usually available through the vendor of the hardware platform.)

  • Enable WMI Scan. Enables ZENworks for Servers 3 to collect hardware inventory data from Windows NT/2000 workstations by using the Web-based Management Interface (WMI) 1.5 specification. (WMI drivers are included in the Windows system.)

Configuring Software Scan

Next you need to configure software scanning. Enable software scanning by checking the box next to the Enable Software Scan option, and then clicking the Custom Scan Editor button to bring up the Custom Scan Editor window (see Figure 12.17).

Figure 12.17. Custom Scan Editor window for software scanning in the server inventory policy for a distributed server package.

graphics/12fig17.gif

If you are configuring a server inventory policy for Windows, then you also have the option to enable ZENworks to scan for product identification numbers of applications that are installed on inventoried Windows NT/2000 Servers. The product identification number can be extremely useful in sorting and organizing inventory software reports.

From the Custom Scan Editor window, you can create a list of software that ZENworks for Servers 3 will scan for on servers during the inventory process. The Custom Scan Editor provides you with a powerful tool to optimize software scanning for your network. Use the Custom Scan Editor to specify the vender, product name, product version, filename, and file size of the software for which you want to scan on servers. This enables you to selectively inventory only software that is important to track, reducing the size of inventory reports as well as network and server utilization.

Configuring the Configuration Editor

After you enable and configure software scanning, you can modify the INI file that ZENworks for Servers 3 uses when reporting software inventory by selecting the Configuration Editor tab, as shown in Figure 12.18. From the Configuration Editor tab, you can edit the SWRules file by clicking the Set Default button to open the default file, and then modifying the entries. This enables you to modify what information ZENworks includes when you create inventory reports.

Figure 12.18. Configuration Editor panel of the server inventory policy for a distributed server package.

graphics/12fig18.gif

If you are modifying the server inventory policy for Windows, then the Configuration Editor tab will have a drop-down arrow enabling you to modify the entry's INI files for Zipped Names. This modification enables you to specify the manufacturers of software that is being used to zip files, as well as the identifiers that they are using for the zipped files.

If you are modifying the server inventory policy for Windows, you can also modify the entries in the INI file for Asset Information. You can specify the DMI classnames and attributes for things such as a server model, model number, serial number, and computer type.

Configuring the Service Location Package

The next step in configuring server inventory is to define the inventory database for the service location package object and associate the database object with the inventory service object. This step tells ZENworks which inventory server to use for objects associated with the service location package. Follow these steps to configure the service location package from within ConsoleOne:

  1. Create and/or select the service location package.

  2. Right-click the service location package object and select Properties from the pop-up menu; then select the NetWare or Windows Policies tab.

  3. Enable the ZENworks database policy by checking the box next to it. Click the Properties button to open the Database Properties window.

  4. Select the Inventory Management Tab; then click the Browse button to find the inventory database object you want to use for the service location. Click OK.

  5. When you return to the Properties page for the service location package, select the Associations tab.

  6. Click the Browse button and select the container that stores the inventory service object you want to associate with the inventory database you defined for the service location package. Click OK.

  7. Click Apply to configure the service location package.

Configuring the Roll-Up Policy

After configuring the service location package, you need to configure the roll-up policy if this inventory server is a leaf or intermediate server. The roll-up policy controls the flow of scanned data through the inventory tree by determining the next inventory location and schedule-to-roll scan data collected by the current inventory server. Follow these steps to configure the roll-up policy for an inventory server in ConsoleOne:

  1. Create and/or select the server package object that is associated with the inventory server.

  2. Right-click the server package object and select Properties from the pop-up menu; then select the NetWare or Windows Policies tab.

  3. Enable the roll-up policy by checking the box next to it. Click the Properties button to open the roll-up policies window, as shown in Figure 12.19.

    Figure 12.19. Roll-Up Policy panel of the server inventory policy for a distributed server package.

    graphics/12fig19.gif

  4. Click the Browse button and navigate to the inventory service object of the intermediate or root server to which you want this server to roll-up scan data. Click OK.

  5. Select the IP address of the next level inventory server.

  6. Select the Roll-Up Schedule tab and configure the schedule of when to roll scan data collected by this server up to the next level. You need to keep in mind the synchronization schedule defined for the inventory server when configuring the roll-up schedule so that there are no conflicts and there is minimal lag time. If the inventory synchronization, for example, runs only monthly, then you want the roll-up to occur after the synchronization is complete to avoid a one-month latency of information being rolled up in the tree. (See the "Configuring the Inventory Service Object" section and Figure 12.15, earlier in this chapter, for more information about the schedule page.)

  7. Click the OK button to return to the Server Package Properties page.

  8. Select the Associations tab and click the Add button.

  9. Browse to the inventory server object you want to associate with this server package. Click OK twice to return to the Server Package Properties page.

  10. Click the Apply button to configure the roll-up policy.



Novell's ZENworks for Servers 3. Administrator's Handbook
Novell's ZENworks for Servers 3. Administrator's Handbook
ISBN: 789729865
EAN: N/A
Year: 2003
Pages: 137

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net