Documentation Errata 1
February 2009
Novell® ZENworks® 7.5 Asset Management documentation contains inconsistencies that are addressed in this errata. The corrections that have been found are listed below:
Beginning with Interim Release 9, Access Management 7.5 can accept an optional comma-delimited subnet list file for the Network Discovery task. You can't import a range of addresses; you can only import a list of individual subnets and individual addresses, in keeping with the Available Subnets list box on the Subnet tab of the Network Discovery Task dialog box. The import helps populate that list.
The Optional Fields can contain any data you want; they are included in anticipation that you might want to build a spreadsheet of addresses and subnets. If your spreadsheet contains something of interest (such as subnet descriptions), you can export the spreadsheet to a CSV file without stripping additional data. You can import the CSV file as long as the first columns are formatted correctly.
There is no error generated if this file does not exist. If the file exists, it must be named subnets.txt and must exist in the Manager's executable directory. The default location is C:\Program Files\Novell\Zenworks\Asset Managment\bin. The file should use the following format:
subnet1,mask1
subnet2,mask2
...
subnetX,maskX
For example:
199.12.64.0,255.255.255.0
Both the subnet and mask must be present in every line. The subnet and mask must consist of 4 octets each. The file can contain additional optional fields per line, but they must be separated from the subnet and mask by a comma, such as:
subnet,mask,OptionalField1,OptionalField2,...,OptionalField3
The maximum line length is 1024 characters. Only numeric values, periods, and commas are permitted before the optional second comma per line. Any characters are permitted after the second comma, and are completely ignored by the Network Discovery task.
This allows you to export a spreadsheet of subnets and masks in comma-separated-value format. The Network Discovery task automatically imports this file and uses it to populate the Available Subnets list on the Subnet tab on the Network Discovery Task dialog box.
On numeric page 43 of the Novell ZENworks Asset Management 7.5 Installation Guide, the use of UNC under the "Database Creation and Setup Tool" heading is unclear.
"4. In the Configure Oracle Temporary File dialog, specify where you want to create the TSCTEMP tablespace and click on the Next button. For Windows NT, enter a full path; for UNIX* or LINUX*, use UNC."
UNC stands for Universal or Uniform Naming Convention, which specifies a common syntax to describe the location of a network resource, such as printers, programs, directories, or files. The convention for UNIX or Linux is to use two forward slashes for a network resource or a single forward slash for a local resource. For example:
//ipaddress/directorypath/resource
smb://hostname/directorypath/resource
hostname:/directorypath/resource
On numeric page 260 of the Novell ZENworks Asset Management 7.5 User's Guide, under the "Defining a Proxy Server" heading, Step 4 states "Enter the port number of the proxy server." The proxy port field is not used and any port entered is ignored.
On numeric page 125 of the Novell ZENworks Asset Management 7.5 User's Guide, under the "Installing ZENworks Asset Management Collection Client Software" heading, the following feature does not exist:
Web Install - You can install collection client software from a web server on Windows systems. For more information, see Installing Client Applications from the Web.
On numeric page 131 of the Novell ZENworks Asset Management 7.5 Users Guide, all information under the "Installing Client Applications from the Web" heading is incorrect.
Other documentation references are included in the Novell ZENworks Asset Management 7.5 Help system.
On numeric page 15 of the Novell ZENworks Asset Management 7.5 Installation Guide, under the "System Requirements - Standalone Deployment" heading, only English versions of the supported operating systems are allowed for the Manager/Server installation.
On numeric page 55 of the Novell ZENworks Asset Management 7.5 Installation Guide, under the "Installing Client Applications" heading, all client platforms listed are 32-bit, unless otherwise noted.
On numeric page 344 of the Novell ZENworks Asset Management 7.5 User's Guide, the "NC_NetworkDiscOptions Table (Entity)" heading lists thread count options, but these options are no longer available. Also, the Collection Server edit window contains no thread count.
Some customers are confused between the features of ZENworks Asset Inventory and ZENworks Asset Management. ZENworks Asset Management contains all of the features of ZENworks Asset Inventory, plus Usage, Compliance, and Contract Management. In this respect, ZENworks Asset Management is a superset of ZENworks Asset Inventory.