ASG-TrackBird™ Installation Guide Version 3.3.1 Publication Number: TBZ0300-331 Publication Date: November 2005
The information contained herein is the confidential and proprietary information of Allen Systems Group, Inc. Unauthorized use of this information and disclosure to third parties is expressly prohibited. This technical publication may not be reproduced in whole or in part, by any means, without the express written consent of Allen Systems Group, Inc. Copyright © 2005 Allen Systems Group, Inc. All rights reserved. All names and products contained herein are the trademarks or registered trademarks of their respective holders. ASG Worldwide Headquarters Naples Florida USA | asg.com |
[email protected] 1333 Third Avenue South, Naples, Florida 34102 USA Tel: 239.435.2200 Fax: 239.263.3692 Toll Free: 800.932.5536 (USA only)
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v About this Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Publication Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi ASG Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Intelligent Support Portal (ISP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Telephone Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii ASG Documentation/Product Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 1:
Introduction to TrackBird Software Suite . . . . . . . . . . . . . . . . . . . . . . . 1 TrackBird Technology Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 TrackBird Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Software Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 5 5 6 6 7 7 7 8
Downloading ASG-TrackBird from the ISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 2:
Installing TrackBird Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Installing TrackBird Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum Required Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrackBird Server Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 13 14 21
Installing TrackBird IP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum Required Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the TrackBird IP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Primary or Secondary Web Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Choosing a Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Configurations when Using IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22 22 22 29 30 36
Installing TrackBird Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 i
ASG-TrackBird Installation Guide
Chapter 3:
SQL Server and Oracle Database Creation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . The Wizard at a Glance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating an SQL Server Database for TrackBird . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Oracle Database for TrackBird . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49 49 50 54
Updating to TrackBird 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from 2.2 to 3.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from 3.x to 3.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58 58 58 59 62
Installing the PC Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Operating System Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Chapter 4:
Operating Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter Settings for the Inventory Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differences in the Collection Procedure Depending on the Platform. . . . . . . . . . . . . . . Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67 68 68 69
Installing TrackBird Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Installation Using TrackBird Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Installation Using an Internet Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Installation as a Standalone Inventory Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Installation Using the TrackBird Client Installation Wizard . . . . . . . . . . . . . . . . Client Installation via IP Using a Login Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Installation via a Shared Directory Using a Login Script . . . . . . . . . . . . . . . . . .
69 70 71 71 74 77 82
Situation Following Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Executable Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component Files (IP only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NETBIRD.CFG Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTOEXEC.BAT Launch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STARTUP.CMD Launch File for OS/2 Warp 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WIN.INI System File Under Windows 3.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows 9x, NT, 2000, XP, and 2003 Registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83 83 84 84 84 85 90 91 91 91
Mac OS X and Mac OS Classic Client Installation . . . . . . . . . . . . . . . 93 Mac OS X Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Web Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Macintosh OS X Client Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creation of End User’s Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk Image Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Disk Image on the TrackBird IP Server . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Macintosh Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94 95 97 99 99
Mac OS Classic Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 ii
Contents
Deploying the Mac OS Classic Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Chapter 5:
PDA Clients Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Palm OS Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Palm Desktop Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Deploying the Palm OS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 How TrackBird Palm OS Client Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Palm OS Version 3.5 or later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Palm OS Prior to Version 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Windows CE Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Deploying a Windows CE Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Chapter 6:
UNIX Clients Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 AIX Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying the AIX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify AIX Client installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation folder on client workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing an AIX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
115 115 117 117 118
HP/UX Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying the HP/UX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify HP/UX Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Folder on Client Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the HP/UX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119 119 121 121 122
Linux Client Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying Linux Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the Linux Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Folder on Client Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the Linux Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
123 123 124 125 126
Solaris Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying the Solaris Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Solaris Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Folder on Client Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial Number Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a Solaris Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126 126 128 129 129 130
Launching a Collection Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Customizing your UNIX Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collection Agent Startup Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collection Agent Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installed Packages Detection (Solaris Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
130 131 131 132
iii
ASG-TrackBird Installation Guide
Chapter 7:
Installing the SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Installing the SNMP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
iv
Preface
This ASG-TrackBird Installation Guide provides an overview of the ASG-TrackBird (herein called TrackBird) suite and installation instructions. TrackBird helps you to control and manage your IT assets.
About this Publication This publication consists of these chapters: •
Chapter 1, “Introduction to TrackBird Software Suite,” presents an overview of each product that encompasses the TrackBird suite and describes the software’s architecture and special features.
•
Chapter 2, “Installing TrackBird Servers,” provides installation information for installing and upgrading the TrackBird servers.
•
Chapter 3, “Installing the PC Collectors,” provides instructions for installing the PC collectors.
•
Chapter 4, “Mac OS X and Mac OS Classic Client Installation,” includes preinstallation requirements and installation instructions for Mac OS X and Mac OS Classic clients.
•
Chapter 5, “PDA Clients Installation,” provides instructions for installing TrackBird on a PDF.
•
Chapter 6, “UNIX Clients Installation,” provides instructions for installing TrackBird on UNIX platforms including: AIX, Solaris, HP/UX, and Linux.
•
Chapter 7, “Installing the SNMP Collector,” discusses installing the TrackBird SNMP Collector.
v
ASG-TrackBird Installation Guide
Related Publications The documentation library for ASG-TrackBird consists of these publications (where nn represents the product version number): •
ASG-TrackBird Reference Guide (TBD0400-nn) details the complete TrackBird suite of products. Includes user and administrator information for each TrackBird module.
Note:
To obtain a specific version of a publication, contact ASG Customer Support.
Publication Conventions ASG uses these conventions in technical publications: Convention
Represents
ALL CAPITALS
Directory, path, file, dataset, member, database, program, command, and parameter names.
Initial Capitals on Each Word
Window, field, field group, check box, button, panel (or screen), option names, and names of keys. A plus sign (+) is inserted for key combinations (e.g., Alt+Tab).
lowercase italic monospace
Information that you provide according to your particular situation. For example, you would replace filename with the actual name of the file.
Monospace
Characters you must type exactly as they are shown. Code, JCL, file listings, or command/statement syntax. Also used for denoting brief examples in a paragraph.
vi
Vertical Separator Bar ( | ) with underline
Options available with the default value underlined (e.g., Y|N).
Underline
Denotes a cursor-selectable field or line.
bold (exclusively for UNIX and some Macintosh input)
Identifies commands, field names, program names, file names, directory names, and any other items that are predefined by the system.
Preface
ASG Customer Support ASG provides support throughout the world to resolve questions or problems regarding installation, operation, or use of our products. ASG provides all levels of support during normal business hours and emergency support during non-business hours. ASG Third-party Support. ASG provides software products that run in a number of third-party vendor environments. Support for all non-ASG products is the responsibility of the respective vendor. In the event a vendor discontinues support for a hardware and/or software product, ASG cannot be held responsible for problems arising from the use of that unsupported version.
Intelligent Support Portal (ISP) Online product support is available at: http://www.asg.com/support/support.asp via the ASG Intelligent Support Portal (ISP) at: http://isp.asg.com. This is the logon information for ISP online support: Customer ID = NNNNNNNNN Password = XXXXXXXXXX where: NNNNNNNNN is your customer ID supplied by ASG Product Distribution. XXXXXXXXXX is your unique password supplied by ASG Product Distribution. The ASG-Intelligent Support Portal User's Guide provides instructions on how to use the ISP and is located on the ASG Customer Support web page.
vii
ASG-TrackBird Installation Guide
Telephone Support To expedite response time, have this information ready: •
Product name, version number, and release number
•
List of any fixes currently applied
•
Any alphanumeric error codes or messages written precisely as displayed
•
A description of the specific steps that immediately preceded the problem
•
Verify whether you received an ASG Service Pack or cumulative service tape for this product. It may include information to help you resolve questions regarding installation of this ASG product. The Service Pack instructions are in a text file on the distribution media included with the Service Pack. You can access the latest software corrections and Service Packs via the ISP.
•
The severity code (ASG Customer Support uses an escalated severity system to prioritize service to our clients. The severity codes and their meanings are listed in the following table.)
Severity Codes and Expected Support Response Times
viii
Severity
Meaning
Expected Support Response Time
1
Production down, critical situation
Within 30 minutes
2
Major component of product disabled
Within 2 hours
3
Problem with the product, but customer has work-around solution
Within 4 hours
4
"How-to" questions and enhancement requests Within 4 hours
Preface
The Americas Phone
Fax
E-mail
United States and Canada
800.354.3578
1.239.213.3721
[email protected]
Mexico
001.800.514.9156
1.239.213.3721
[email protected]
Europe, Middle East, and Africa (EMEA) During normal business hours, ASG recommends calling the Central Support number first (except in South Africa). Phone
Fax
E-mail
Central Support
00.800.3544.3578
44.1727.812018
[email protected]
English
44.1727.736305
44.1727.812018
[email protected]
French
33.141.028590
33.141.028589
[email protected]
German
49.89.45716.200
49.89.45716.400
[email protected]
Italian
39.0290450025
[email protected]
Dutch
31.30.600.4026
[email protected]
Spanish
34.917.628.509
South Africa
800.201.423
34.917.628.530
[email protected] [email protected]
Asia Pacific (APAC) Phone
Fax
E-mail
Central Support
61.3.9645.8500
61.3.9645.8077
[email protected]
Australia
800.637.947
61.3.9645.8077
[email protected]
Hong Kong
800.96.2800
Japan
81.3.5326.3684
81.3.5326.3001
[email protected]
Singapore
65.6332.2922
65.224.8516
[email protected]
[email protected]
All Other Countries (Also for any non-working numbers) All other countries
Phone
Fax
E-mail
1.239.435.2201
1.239.213.3721
[email protected]
ix
ASG-TrackBird Installation Guide
If you receive a voice mail message, follow the instructions to report a production-down or critical problem. Leave a detailed message including your name and phone number. An ASG Customer Support representative will be paged and will return your call as soon as possible. Have available the information described previously when the ASG Customer Support representative contacts you.
ASG Documentation/Product Enhancements Submit all product and documentation suggestions to ASG’s product management team at http://www.asg.com/asp/emailproductsuggestions.asp. If you do not have access to the web, FAX your suggestions to product management at (239) 263-3692. Include your name, company, work phone, e-mail ID, and the name of the ASG product you are using. For documentation suggestions, include the publication number located on the publication’s front cover.
x
Chapter 1:Introduction
to TrackBird Software Suite
1
The TrackBird software suite developed by ASG helps you to control and manage your IT assets. The TrackBird suite of solutions acts within four complementary areas and is composed of seven modules: •
The TrackBird Inventory module performs the hardware and software audit of your workstations (Windows, Macs, and Linux) and servers whereas the TrackBird SNMP module audits all active SNMP-compliant devices on your network (switches, hubs, print servers, and routers). The TrackBird Reporting module allows you to export the gathered data into comprehensible reports for external analysis.
•
The TrackBird Monitoring module allows you to monitor the actual rate of use of all installed applications within your network structure and to better adapt your license purchases and maintenance contract negotiations in the long term.
•
The TrackBird Policy module translates your internal IT Policies to the desktop management and discovers all abnormal procedures. TrackBird allows you to monitor modifications on your workstations and be proactive to any unauthorized actions. Furthermore, TrackBird Gateway enables you to export the data generated by the other modules of the TrackBird suite into third-party applications such as Help Desk, Remote, ESD, or general asset management applications.
•
The TrackBird Software Distribution enables you to manage your IT infrastructure more efficiently while remaining virtually invisible to the user.
•
The TrackBird Web module enables you to visualize your data via queries and reports with a Web browser from any station on your network.
1
ASG-TrackBird Installation Guide
Figure 1 • TrackBird software suite
TrackBird Technology Architecture TrackBird is based on a 3-tier architecture: •
Inventory clients (or collectors)
•
Inventory servers
•
Data extraction and analysis tools
Inventory clients are installed remotely on the workstations and run on various platforms (DOS, Windows 3.x through XP, Mac OS 7.6.1 (via AppleShare), Mac OS 8.1 through 9.2.2 (via AppleShare or TCP/IP), Mac OS X (versions 10.0 through 10.2.6 via TCP/IP), OS/2 2.11 through Warp 4.5, AIX 4.3 or later, HP/UX 10.2 or later, Solaris 5.8 & 5.9, Linux Red Hat 7.1 through 9.0, Mandrake 8.2, Suse 8.1, 9.0 and 9.1, Windows CE and Palm OS) to collect the necessary inventory information. The collected data is then sent to inventory servers responsible for either managing wide area network (WAN) links into a centralized web server or handling exchanges with the database (inventory information and options, new collector versions, hardware and software repository information, etc.).
2
1 Introduction to TrackBird Software Suite
Once installed the collector is totally independent and can easily be managed remotely. The standard inventory tool is complemented by an SNMP inventory tool used to collect information on all SNMP (Simple Network Management Protocol) agents on a network, such as routers, printing servers, network printers, manageable hubs, standard UNIX systems, and nodes equipped with an SNMP agent. Once it is recorded in the database, the information can be accessed by a number of complementary tools: •
TrackBird Server, as the primary interface for performing database and repository administration tasks. It is also used by the user to run queries in the database in the following two modes: —
List queries, which correspond to the standard querying mode. The user selects a set of inventory criteria together with a set of filtering or grouping options. The query result can then be exported to Excel, Access or any other type of database;
—
Tree queries, a unique TrackBird feature for quickly and simply displaying inventory results. In a few clicks, the user can organize and define the structure of the inventoried assets and quickly access key inventory information in an itemized list.
•
TrackBird Reporting, see the ASG-TrackBird Reference Guide for details.
•
TrackBird Monitoring, see the ASG-TrackBird Reference Guide for details.
•
TrackBird Gateway, see the ASG-TrackBird Reference Guide for details.
TrackBird workstations can intercommunicate worldwide via the HTTP protocol, meaning that organizations can obtain a daily log of the software and hardware configurations of all TrackBird workstations, including those in subsidiaries abroad, if they wish. Each client workstation performs its own data collection and sends the inventory results to its parent server which in turn communicates the information to the primary server, regardless of its location, via the Internet Protocol.
3
ASG-TrackBird Installation Guide
Figure 2 • Global architecture illustrating all possible technologies
Primary Server. This workstation is the company’s main TrackBird network server. The TrackBird IP Administration interface is installed on this workstation. All options concerning client collector points on the TrackBird network are managed through this interface, regardless of the collectors’ geographical location. Secondary Server. Once you have defined a primary server, you can create secondary servers. A secondary server acts as a relay between workstations linked to it and the primary server. As the TrackBird IP interface is not installed on secondary servers, they cannot be used for workstation administration. A secondary server acts only as the parent server for the servers and workstations linked to it. Client Workstation. A client workstation is a workstation whose inventory information you want to collect. It must be linked to a server (primary or secondary) and is installed after the server. (See “Installing TrackBird Clients” on page 69.) HTTP Transfer. HTTP is the Internet data transfer protocol standard used to send the inventory results to the primary server via an IP address.
4
1 Introduction to TrackBird Software Suite
TrackBird Features TrackBird Inventory TrackBird Inventory is a multi-platform data collector tool that builds and maintains complete inventories of IT hardware and software completely automatically, for both networked and stand-alone workstations. The tool can be set up with collection options customizing it to each company’s needs (assets for inventory, frequency, upgrades, etc.). The collection point for stand-alone workstations is simply installed on a diskette. For improved inventory results and rapid notification of changes, the collector can be configured to produce regular reports. The collected data can be fully integrated into an existing database to provide detailed descriptions of IT assets and precise user profiles. Key features and benefits of TrackBird Inventory: •
A totally reliable solution using a recognition method based on PCI, Plug & Play, DMI, WMI and BIOS System Management standards
•
Inventory of standard and in-house installed software
•
Automatic inventory (network) or manual inventory (diskette)
•
Supplied with a comprehensive software reference library
•
Automatic detection of new software versions/releases
•
Easy to install and implement while also offering enhanced performance and reliability
•
Suitability for all types of IT assets (all sizes, multiple locations and vendors, etc.)
•
Multi-platform solution supporting multiple native databases
•
Secure function access through user profile administration
•
User-friendly interface with fully customizable query and report options
TrackBird SNMP TrackBird SNMP is used to collect information from a network’s SNMP (Simple Network Management Protocol) agents on network devices such as routers, printing servers, network printers, manageable hubs, standard UNIX systems and nodes equipped with an SNMP agent. TrackBird SNMP also provides detailed configuration details of these components. TrackBird SNMP is the ideal tie-in with an IT inventory solution such as TrackBird Inventory, as the SNMP protocol is used by a large number of manufacturers of network peripherals for remote control and administration of devices.
5
ASG-TrackBird Installation Guide
Key features and benefits of TrackBird SNMP: •
Private Management Information Base (MIB) updates using an integrated import module
•
Network-wide data collection
•
Automatic inventory launch
•
Customizable collection options
•
Comprehensive collection of exact configuration details of all active nodes on the network
TrackBird Reporting TrackBird Reporting is a tool used to generate reports from queries run on a TrackBird database. Queries are SQL-based and are developed using a simple, drag-and-drop interface that makes it easy to design and build SQL queries. This module is run from the TrackBird Repository Explorer, from the Start menu. Key features and benefits of TrackBird Reporting: •
Highly user-friendly interface
•
Predefined reports available
•
Reports can be produced in Word (RTF), HTML, PDF and Excel formats
•
Complementary tool to TrackBird Inventory, TrackBird Monitoring, TrackBird Policy and TrackBird SNMP
TrackBird Monitoring TrackBird Monitoring enables organizations to monitor the utilization of their software. It is a powerful tool for viewing software utilization rates based on predefined criteria such as frequency, number of executions and total time of use, either per workstation, per department or for the entire organization. Key features and benefits of TrackBird Monitoring:
6
•
Multi-platform solution with a native multi-base interface
•
Easy integration in multi-site environments
•
Automatic distribution of the solution on the network
•
Information collected on stand-alone workstations can be consolidated with network data
•
User-friendly solution with customizable interface
•
Automatic detection of new software versions and proprietary applications
1 Introduction to TrackBird Software Suite
•
Built-in software knowledge base containing over 5,000 references (that can be filtered by product, editor, location and/or type of workstation)
TrackBird Policy TrackBird Policy is a management module enabling IT managers within an organization to automatically set up and define rules in line with global corporate policy. TrackBird Administrator can for instance maintain a library of authorized software within the company and ensure that no unauthorized software is installed or run by users across the enterprise. This feature, which is managed at server level, is totally transparent to the end-user. Key features and benefits of TrackBird Policy: •
Automatic alert generation system (e.g. for applications outside the company standards, etc.)
•
Comparison of installed applications with the customer’s original version
•
Anti-virus manager (installed version, definition file, comparison with the latest version, etc.)
TrackBird Gateway TrackBird Gateway is a powerful, fully customizable tool used for information and data exchanges with asset management, help desk or ERP applications. TrackBird Gateway is certified by the leading software vendors including AssetCenter (Peregrine), Service Center (Peregrine), Tivoli, Microsoft SMS, Qualiparc (PS’Soft), Actima (Staff & Line), Kim’Parc (Kimoce) as well as many others. Key features and benefits of TrackBird Gateway: •
Total security through integrity control mechanisms;
•
Two-way data exchanges with third-party products, including repository, directory or location information;
•
Native support of Oracle and SQL Server databases.
TrackBird Software Distribution The TrackBird Software Distribution module offers a simple and effective solution to software and content deployment in enterprises with large distributed communities of users. Tightly integrated with the other TrackBird modules, TrackBird Software Distribution enables you to manage your IT infrastructure more efficiently while remaining virtually invisible to the user.
7
ASG-TrackBird Installation Guide
Key features and benefits of TrackBird Software Distribution: •
Installing software on each TrackBird clients (Windows)
•
MSI, InstallShield and Wise setup program supported
•
Customizable distributions available
TrackBird Web TrackBird Web allows you to view your queries and reports on any computer with web access using a web browser. Key features and benefits of TrackBird Web: •
Predefined queries and reports available
•
Intuitive graphical user interface (GUI)
Downloading ASG-TrackBird from the ISP To download your installer from ASG’s ISP Note:
ASG encourages you to visit the Intelligent Support Portal (ISP): http://www.asg.com/support/support.asp. The ISP allows you to verify whether any product or documentation revisions, new maintenance, or service packs apply to this product release.
8
1
Open your Web-browser.
2
Access www.asg.com or enter http://cust.asg.com/_xKwave/ISP/ISPframes.aspx and skip to step 4 on page 9.
1 Introduction to TrackBird Software Suite
3
Select Intelligent Support Portal from the Support drop-down menu.
The Intelligent Support Portal page appears.
4
Click Log in from the left panel. 9
ASG-TrackBird Installation Guide
The Intelligent Support Portal Login page appears in the right panel.
5
Complete all the fields listed and click Login. A menu will appear to allow specific support actions.
6
10
From the left panel tree, select Downloads ` Product ` Install Package.
1 Introduction to TrackBird Software Suite
A list of products your site is authorized to download will appear. 7
Select the product name from the list.
8
Click OK. You will be prompted to accept the License Agreement.
9
Scroll to the bottom and select YES, I accept the terms.
10
Click OK. A specialized product download page for the product media will display.
11
Click the install instructions link to review installation information.
12
Click the ASG product name link to download the *.ZIP file.
13
Save the *.ZIP file to your hard disk or a network location.
11
ASG-TrackBird Installation Guide
12
Chapter 2:Installing
2
TrackBird Servers
Installation of the TrackBird suite consists of installing the TrackBird Server(s) and then installing the collection point on each workstation.
Installing TrackBird Server Minimum Required Configuration TrackBird Server operation does not require many computer resources or a dedicated workstation or server, as the TrackBird Server application requires few CPU and memory resources to run queries. The console, on the other hand, should have a high-performance network connection and sufficient display resources to take full advantage of the 32-bit interface. The database used with the TrackBird Server application may however require considerable resources to operate correctly. That is why it is generally more important to upgrade the server on which the database is installed, taking into account the number of users likely to access the base to use its data. We will therefore distinguish here between the console and the database server, making a further distinction between the different types of databases. If TrackBird Server and the database are installed on the same machine, their individual hardware requirements must be added together. Hardware Requirements System Requirements Database Server
• Pentium IV, 1 GHz
• 512 MB RAM (For further information and other • 50 MB free disk space + N x operating systems, see 300 KB (where N is the the requirements of the number of inventoried respective editors.) workstations) + DAT drive
• Windows NT 4 SP6, 2000, XP, or 2003 • SQL 6.5 Service Pack 5a or later Or • Oracle 7.2 or later Or • Interbase (provided with installation)
13
ASG-TrackBird Installation Guide
Hardware Requirements System Requirements Administration Console
• Pentium IV 1 GHz • 512 Mb RAM • 350 MB available disk space
• Windows NT 4 SP6, 2000, XP, or 2003 • 800 x 600 video minimum • Network card
Installation Process To install TrackBird servers 1
Insert the TrackBird installer compact disc (CD) into the CD-ROM drive. The Auto run displays.
14
2
Click Install TrackBird.
3
Choose a setup language (English or French).
4
Click OK.
2 Installing TrackBird Servers
The Welcome screen displays.
5
Click Next. The License Agreement screen displays.
6
Carefully read the license contract and accept the terms in order to install the TrackBird software. Click Yes to accept the terms and continue the installation. Or
If you do not accept the terms, click No to end the installation process.
15
ASG-TrackBird Installation Guide
The User Information screen displays.
7
Accept the DEMO company name and demonstration license serial number (valid for 30 days for use with 80 workstations) Or
Enter your name, your company name, and the license serial number supplied with the TrackBird software. 8
Click Next. The Registration information screen displays.
9
16
Click Next.
2 Installing TrackBird Servers
The Choose Destination Location screen display.
10
Accept the default TrackBird installation directory (C:\PROGRAM FILES\ASG\TRACKBIRD SERVER) or specify an alternative directory in which to install the TrackBird application. Note:
A TrackBird installation comprises two parts: TrackBird Server and InterBase. The latter is always installed in the C:\PROGRAM FILES\BORLAND\INTERBASE directory and requires approximately 10 MB of available disk space. 11
Click Next. The Setup Type screen displays.
17
ASG-TrackBird Installation Guide
12
Select the type of installation you require. •
The Typical installation, after which the computer must be restarted, is suitable for product evaluation.
•
A Custom installation, which should be used if the product is being set up for intensive use, is described below to present all the different elements of product installation.
•
A Compact installation installs only the TrackBird Server program files, help files, InterBase database and the TrackBird Wizards. By selecting Custom installation, you can define in detail how TrackBird is to be set up, selecting which modules and components are to be installed.
The table below provides information on the various elements of the installation. Files Program files
These files are for TrackBird Server. Their installation is essential for administration of the software and the database and so cannot be unselected.
Databases
Empty database
Interbase database containing no inventory data. It can be used as a reference database for the creation of your personalized database. Its installation is recommended.
Demo database
This Interbase database contains a set of sample workstations and network devices and demonstrates the quality of the information collected by TrackBird, as well as the processing possibilities and the queries that can be carried out on the data.
French
This option installs the French version of the online help.
English
This option installs the English version of the online help.
Help files
18
Explanation
Interface editor
TrackBird Designer is an accessory component of TrackBird enabling administrators who wish to have users fill out the inventory data directly on each workstation (following technical servicing, for example) to create a data input interface containing all data entry fields and the control objects required by them. Examples supplied with this component are displayed if this component is installed.
SNMP Client installation
The SNMP client is a configurable collector used to inventory active network devices that use SNMP. Install this component if you have acquired the necessary software license.
2 Installing TrackBird Servers
Files
Explanation
DB Express
This Borland product is used by TrackBird Server for native communication with the various supported databases (SQL, Oracle, etc.).
Wizards
Wizards are provided to help to set up and implement TrackBird throughout your computer system. Installation of all wizards is therefore highly recommended, even if they may not all seem useful right away. Their usefulness will be explained later.
Note:
TrackBird may be set up in US English or French. The selected language is applied throughout the server module. 13
When you have selected the appropriate installation type and options, click Next. The Select Program Folder screen displays.
19
ASG-TrackBird Installation Guide
14
Select the appropriate program folder and click Next to display a summary of all the above information.
15
Click Next to complete the installation. The Setup Status screen displays while TrackBird installs.
20
2 Installing TrackBird Servers
The installer displays a screen indicating the installation is complete.
16
Select Yes. I want to restart my computer now.
17
Click Finish.
TrackBird Server Registration To use TrackBird Server, the license must be registered using the registration program. This program is run either during the installation process or by running the TrackBird Register program.
To register TrackBird Server 1
Select the Windows Start menu ` Programs ` TrackBird Suite ` TrackBird Register.
2
Click Register. An Information dialog displays registration information. If your license has expired and a new one is required, enter your company name and the license key in the corresponding fields and click Register. 21
ASG-TrackBird Installation Guide
3
Click Cancel to exit the application.
Installing TrackBird IP Server Minimum Required Configuration The minimum configuration required depends on whether you are installing TrackBird IP Server or a TrackBird client. Details of both types of configurations are as follows: •
•
TrackBird IP Server —
Windows NT 4.0 SP5 or later
—
Internet Explorer 4.01 or later
Workstation clients —
Workstation clients
—
Windows 95, 98, Me
—
Windows NT 4.0, 2000, XP
—
OS/2 Warp 4
—
Mac OS 7.6.1 to 9.2.2 (AppleShare mode)
—
Mac OS 8.1 or later (TCP/IP mode)
—
Mac OS X (TCP/IP mode)
—
Linux (RedHat 7.1 or later, or Mandrake 8.0 or later, Suse 8.1 or later)
—
AIX 4.3 or later
—
HP/UX 10.2 or later
—
Solaris 5.8 and 5.9
Installing the TrackBird IP Server The TrackBird IP Server InstallShield Wizard displays a series of screens that guides you through the installation process. If you are not used to installing programs in this way, you can install TrackBird IP Server without studying the information displayed in the screens, simply by clicking Next in each stage of the process.
22
2 Installing TrackBird Servers
To install the TrackBird IP server 1
Insert the TrackBird installer CD into your computer’s CD-ROM drive. Or
If the installer Autorun program does not display, double-click the AUTORUN.EXE file on the CD. The Autorun program displays the installation screen for the different TrackBird products.
2
Click Install TrackBird IP. The first screen welcomes you to the TrackBird IP Server InstallShield Wizard. You are now ready to complete a series of steps to set up the TrackBird IP server.
3
Click Next. 23
ASG-TrackBird Installation Guide
The TrackBird IP Server user license agreement.
4
Read the license agreement terms carefully and accept them by clicking Yes to continue the installation and display the next screen (User Information). Or
If you do not accept the user license agreement’s terms, click No to cancel installation of the TrackBird IP Server software. The User information screen displays
5
Enter your name, your company’s name and the TrackBird IP Server software’s serial number. You can either accept the DEMO company name and demonstration license serial number (valid for 30 days for use with 80 workstations) or enter your name, your company name, and the license serial number supplied with the TrackBird software.
24
2 Installing TrackBird Servers
If you already have a TrackBird Server license agreement and the TrackBird Server software is installed on your computer, the information is copied from the information supplied when the existing version of TrackBird Server was installed. When you have entered the appropriate information 6
Click Next to display the Choose Destination Location screen.
7
Specify where you want to install the TrackBird IP Server files. This installation of the TrackBird IP Server software will then be installed in this folder. By default, the InstallShield Wizard is configured to install the TrackBird IP Server software in the C:\PROGRAM FILES\ASG\TRACKBIRD IP SERVER folder on your hard disk. Or
If you want to install TrackBird IP Server into different folder (other then the default) click Browse and specify where you want to install the TrackBird IP Server software. 8
Click Next to display the Server Type screen.
25
ASG-TrackBird Installation Guide
9
Specify whether you are installing a primary or a secondary TrackBird server. ‘The Primary Server option is selected by default. The primary server is the main server in your TrackBird IP Server system. You must install this workstation first. Note:
Do not confuse the TrackBird primary server with your corporate network’s main server. You can install the TrackBird primary server on any workstation connected to your network. This workstation will act as the main server for all client workstations connected to the TrackBird system, and contains all files needed to configure and update the client workstations via the IP protocol. TrackBird IP Administration, TrackBird IP Server’s interface, is also installed on this workstation. For details of how to use this interface, see the ASG-TrackBird Reference Guide for details. The primary server is therefore essential to use of TrackBird IP Server and must always be the first workstation installed. If you want to install a secondary TrackBird IP server, you must run this installation process again on that workstation, selecting the Secondary Server option in this screen during installation. A secondary server is a workstation that is linked to the primary server. This server acts as a relay and is used particularly in installations on several sites. For example, a primary server might be installed in a company in New York and give instructions to a secondary server installed in a subsidiary in Chicago. See “Primary or Secondary Web Server Settings” on page 29 for more details. 10 26
Click Next.
2 Installing TrackBird Servers
11
Specify which web server will be used by the TrackBird IP Server. See “Choosing a Web Server” on page 30.
12
Upon completing instructions for the web server, specify in which Web folder the TrackBird IP Server software is to be installed and used. The Web folder corresponds to the folder that notably contains all files needed for future client workstation installations or updates. It is also used as a relay when each client workstation’s information is collected.
The Web alias refers (points) to this Web folder. The Web folder corresponds to the physical folder linked to the TrackBird virtual folder. This address refers to the physical folder: http://[Workstation name or IP address]:[Port]/[Alias name]
By default, the InstallShield Wizard is configured to create the Web folder C:\PROGRAM FILES\ASG\TRACKBIRD IP SERVER\VIRTUALDIR. 27
ASG-TrackBird Installation Guide
If you do not want to use the default folder as the Web folder, click Browse and then specify which folder you want by selecting the Web folder or typing its name in the Choose Folder dialog, then click OK to return to the TrackBird IP Server InstallShield Wizard screen. 13
Click Next to display the final screen in the installation process.
14
Specify the program folder by accepting the default name, TrackBird Suite, selecting an alternative existing name in the Existing Folders list or typing a new name in the Program Folders box. This is the name that will be displayed in the workstation’s Programs menu when you open the Windows Start menu.
15
Click Next to display a confirmation screen detailing the selected installation options.
16
Check that the correct installation options have been selected, if necessary clicking Back to change options then clicking Next to return through the installation screens, then click Next in the confirmation screen to begin installing the TrackBird IP Server software. The InstallShield Wizard displays a screen showing how installation of the files needed by TrackBird IP Server is progressing. This screen shows which files are being copied, together with the full path to the destination folder. Note:
Should you want to halt the installation, click Cancel. The Cancel button displays at all stages of the installation, in each screen shown by the TrackBird IP Server InstallShield Wizard. Clicking Cancel displays a message asking whether you really want to exit the installation process. 28
2 Installing TrackBird Servers
17
•
To return to the screen last displayed by the TrackBird IP Server InstallShield Wizard, click No.
•
To cancel all steps performed since the TrackBird IP Server installation process began and halt the installation, click Yes.
If manual configurations are required, you may see the screen below. Click Next.
Once all of the files have been copied onto the workstation, the TrackBird IP Server InstallShield Wizard proposes to restart the computer. 18
Restart the computer. If you choose to restart the computer later you cannot use TrackBird IP Server until after you restart the computer. This is because TrackBird IP Server will not function optimally until the computer has restarted.
19
Click Finish to complete installation of TrackBird IP Server.
Primary or Secondary Web Server Settings To install a secondary server on a workstation, you must know certain information about the parent server to which the workstation is linked. The parent server is the server that gives instructions to the secondary server. It can be a primary or secondary server but must in all cases have already been installed using the TrackBird IP Server InstallShield Wizard. You must know the following information when installing a secondary trackBird IP server.
29
ASG-TrackBird Installation Guide
Parent Server’s IP Address Each computer is identified by a number separated by points into four groups of up to three digits (for example, 255.255.255.255). This number is called an Internet Protocol address or more commonly the “IP address”. This number is used by computers to communicate via the Internet. If you know this address, specify it in the Parent Server IP Address field. Or
If you do not know the IP address, ask your network administrator for the IP address of the workstation to which you want to link your secondary server.
Alias Name The web server’s alias name is a name allocated to a virtual folder on the web server that is accessed using the Internet to obtain information, scripts, HTML pages, etc. For TrackBird IP Server, this is the name that was allocated to the parent server when it was installed. It is used in all data transfers needed for the TrackBird IP Server to function. At this stage of the installation process, you must know this alias name. All this is explained in detail in the rest of the installation process.
Port Used to Access the Parent Server By default, port 80 is used for HTTP data transfers. Note:
For more information on the server types, see “TrackBird Technology Architecture” on page 2.
Choosing a Web Server The most widely used commercially available web servers are Microsoft’s Internet Information Services (IIS) and Apache Server. TrackBird IP Server can therefore use either server types; however you can install an alternative server if you wish. See “Using an Alternative Web Server on the Workstation” on page 36 for details. It uses one of these servers to perform all file transfers. For Apache Server instructions see “Apache Web Server” on page 33. 30
2 Installing TrackBird Servers
IIS Web Server By default, the Internet Information Services (Microsoft) option is selected on the TrackBird IP Server InstallShield Wizard screen (see step 10 on page 26).
To install TrackBird IP Server with IIS as the web server 1
Select the Internet Information Services (Microsoft) option and then click Next. Clicking Install IIS has the same result as double-clicking the Add/Remove Programs icon and then double-clicking the Add/Remove Windows Components icon in the Windows Control Panel. However, if you choose to install IIS using the Control Panel in this way you must run the TrackBird IP Server InstallShield Wizard again so that it detects that IIS is installed. Note:
As the following installation procedure to install IIS does not work with Windows NT 4.0, if Windows NT 4.0 is installed a message displays telling you to use the Windows NT 4.0 Option Pack to install IIS. 2
Click Install IIS. When the Windows Components Wizard window opens, check the Internet Information Services (IIS) option and then click Next to install the software.
3
When IIS has been installed, close the Windows Components Wizard window to return to the TrackBird IP Server InstallShield Wizard and continue with the TrackBird IP Server software installation process. The Internet Information Services (Microsoft) option is now activated and the Install IIS button no longer displays. If this is not the case then wait a few seconds while the InstallShield Wizard detects that IIS is installed.
4
The InstallShield Wizard asks you to specify which web site you want to use TrackBird IP Server on. You must also specify the virtual folder name, called the alias.
31
ASG-TrackBird Installation Guide
a
Alias Name. The alias is the name of a folder that is called a virtual folder because it only consists of a name when it is created; the folder is not created physically on the workstation’s hard disk. Instead, it refers (hence the name “alias”) to the physical folder created on the hard disk during the server installation process in step 12 on page 27. This alias can be seen in ‘Internet Information Services’, on the Web site specified during the installation process. It is used to access this site via the Internet by specifying the following: http://[Workstation name or IP address]/[Alias name]/
where: Workstation name or IP address is the workstation name or IP address of the TrackBird primary server queried. This address accesses the TrackBird primary server’s physical folder via the Internet Alias name is where the TrackBird primary server has the alias. It is therefore essential to create this virtual folder on the IIS server so that the clients and server can intercommunicate. The TrackBird IP Server InstallShield Wizard proposes the virtual folder name (Alias name) TrackBird. You can change this if you wish. b
Web Site. Internet Information Services (IIS) enable you to choose on which site you want the virtual folder to appear. This is why the TrackBird IP Server InstallShield Wizard proposes a drop-down list, Web site, listing all web sites available on your IIS server. If IIS is already installed on the workstation, several sites may be displayed in the list. If you have just installed it there will only be one site, called Default Web Site.
32
2 Installing TrackBird Servers
The default IIS server used is Default Web Site. The default name allocated to the virtual folder is TrackBird. If the virtual folder already exists, the following message is displayed; select Yes to confirm that you want to replace the existing TrackBird virtual folder, or select No to cancel its replacement and then type a different name in the Alias Name box.
Note:
If you want to use a web site that does not already exist, you must first create it in IIS and then refresh the Web site and Web alias page. 5
When you have defined the Alias name and web site, click Next to display the next screen in the installation process, described in step 12 on page 27.
Apache Web Server If IIS is not installed on the workstation., the Apache Server option is proposed by default and the InstallShield Wizard displays an Install IIS button. This button enables you to install Microsoft’s IIS during the TrackBird IP Server installation process. If you click Next to specify that TrackBird IP Server will use Apache Server software, the InstallShield Wizard displays the next screen in the installation process (see step 10 on page 26). If IIS is not installed on the workstation, the Internet Information Services (Microsoft) option is deactivated and an Install IIS button displays beside it. Regardless of whether or not you have a version of the Apache Server software currently installed on the workstation, the TrackBird IP Server InstallShield Wizard displays one of two different screens depending on whether IIS is installed on the workstation.
If Apache and IIS is not Currently Installed on the Workstation If IIS is not installed on the workstation, the Apache Server option is selected by default, the Internet Information Services (Microsoft) option is deactivated and an Install IIS button displays beside it. `
To continue installing the TrackBird IP Server software with Apache as the web server, click Next to display the next screen in the installation process, described in “Port and Web Alias” on page 34. 33
ASG-TrackBird Installation Guide
If IIS is installed on the Workstation. If “Internet Information Services” is installed on the workstation, the Internet Information Services (Microsoft) option is selected by default. `
To continue installing TrackBird IP Server with Apache as the web server, select the Apache Server option and then click Next to display the next screen in the installation process (“Port and Web Alias” on page 34.).
If Apache is Already Installed on the Workstation If a version of Apache is already installed on the workstation, the TrackBird IP Server InstallShield Wizard displays the following message when you click Next.
This is because TrackBird IP Server is installed with a specific version of the Apache software for TrackBird products. The TrackBird IP Server will use the ApacheTrackBird service. The version already installed on the workstation will not be modified in any way. You can therefore install Apache without worrying about the version already installed on the workstation. Click OK to continue the installation process.
Port and Web Alias The next screen asks you to specify which port is used to access the Apache server you are installing and the name of the virtual folder, called the alias.
Alias Name The alias name is the name of a folder that is called a “virtual” folder because it only consists of a name when it is created; the folder is not created physically on the workstation’s hard disk. Instead, it refers (hence the name “alias”) to the physical folder created on the hard disk during the server installation process. This alias can be seen in the Apache configuration file. It is used to access this site via the Internet by specifying the following: http://[Workstation name or IP address]:[Port]/[Alias name]/
34
2 Installing TrackBird Servers
where: Workstation name or IP address is the workstation name or IP address of the TrackBird primary server queried. Port is the port number used for HTTP data transfers. The workstation name or IP address accesses the TrackBird primary server’s physical folder via the Internet, where the TrackBird primary server has the alias Alias name. It is therefore essential to create this virtual folder on the Apache server so that the clients and server can communicate. The TrackBird IP Server InstallShield Wizard proposes the virtual folder name (Alias name) TrackBird. You can change this if you wish. The TrackBird IP Server InstallShield Wizard displays one of two different screens concerning the port, depending on whether or not “Internet Information Services” is installed on the workstation. If IIS is not Installed on the Workstation. By default, port 80 is specified for HTTP transfers. The TrackBird IP Server InstallShield Wizard displays the following screen.
Click Next to display the next screen in the installation process (see step 12 on page 27). If IIS is Installed on the Workstation. As IIS uses port 80 by default, the TrackBird IP Server InstallShield Wizard proposes port 8080 as this is an easy number to remember. The InstallShield Wizard displays the following screen.
35
ASG-TrackBird Installation Guide
If you wish, you can allocate port 80 to the Apache Server even if “Internet Information Services” already uses this port. Ask your network administrator for more information on which ports are used by your system. Click Next to display the next screen in the installation process, see step 12 on page 27.
Using an Alternative Web Server on the Workstation The choice of whether to use IIS, Apache, or an alternative web server is a purely personal one. TrackBird IP Server works in the same way regardless of which of these servers you choose. Choose whichever suits you best. To use web server software other than Apache and IIS, select the Other server (manual configuration) radio button and then click Next to display the next screen in the installation process, described in step 12 on page 27. Note:
If you choose to use web server software other than Apache and IIS, you must configure the alternative web server for TrackBird IP Server use.
Manual Configurations when Using IIS With IIS Version 4 and Version 5 You must configure the Error 404 page which displays an error message in the event of a page not found and which also allows the migration of TrackBird client 3.x to 3.3. v331
If you are using IIS Version 6.0, see “With IIS Version 6” on page 38. 36
2 Installing TrackBird Servers
To configure custom error (IIS Version 4 and 5) 1
In the Computer Management window, choose Services and Applications ` Internet Informations Services ` Web Sites ` Default Web Site ` TrackBird.
2
Right-click TrackBird and choose Properties, the following window appears:
3
Click the Custom Errors tab.
4
Select Error 404 and click Edit.
37
ASG-TrackBird Installation Guide
5
Choose URL in the Message Type drop-down list.
6
In the URL field, type the path: /trackbird/scripts/tb_404.cgi.
7
Click OK to apply the change.
8
Click OK again to validate the change.
With IIS Version 6 You must add a Web Service Extension and customize the error 404 page in order to allow the migration of the TrackBird 3.x clients to 3.3. v331
If you are using IIS Version 4 or 5, see “With IIS Version 4 and Version 5” on page 36.
To add the Web Service Extension
38
1
In the Computer Management window, choose Services and Applications ` Internet Informations Services ` Web Service Extensions
2
To add a new Web Service Extension, choose one of the two following methods: •
Right-click then choose Add as new Web Service Extension.
•
Choose Add as new Web Service extension... in the right panel’s tree view.
2 Installing TrackBird Servers
v331
The New Web Service Extension window appears.
3
Enter TrackBird in to the Extension name field.
4
To add TrackBird CGI scripts, click Add...
39
ASG-TrackBird Installation Guide
40
5
Click Browse and select the folder C:\PROGRAM FILES\ASG\TRACKBIRD IP SERVER\VIRTUALDIR\SCRIPTS.
6
Change the field Files to All files (*.*) to see the CGI scripts appear.
7
Choose the first script and click Open, the script is added to the Required files list. Repeat this operation in order to add the six other scripts.
8
Select the Set extension status to Allowed check box.
9
Click OK to validate these additions.
2 Installing TrackBird Servers
The Web Service Extension is added to the existing Web Service Extensions.
To configure Error 404 (IIS Version 6) 1
In the Computer Management window, choose Services and Applications ` Internet Informations Services ` Web Sites ` Default Web Site ` TrackBird.
2
Right-click TrackBird and choose Properties, the following window appears:
41
ASG-TrackBird Installation Guide
42
3
Click the Custom Errors tab.
4
Select Error 404 and click Edit.
2 Installing TrackBird Servers
5
Choose URL from the Message type drop-down list.
6
In the URL field, type the path: /trackbird/scripts/tb_404.cgi.
7
Click OK to apply the changes.
8
Click OK again to validate the changes.
Installing TrackBird Web TrackBird Web does not require many computer resources or a dedicated workstation or server. ASG recommends these minimum configuration requirements: IIS 5 or above and access to a Web browser. Note:
You must download the ZIP installer for your product before completing the steps below. For instruction on retrieving your product’s installer ZIP file, see “Downloading ASG-TrackBird from the ISP” on page 8.
To install TrackBird Web 1
For Full licensed copy: a
Unzip the TBN330.ZIP or if the ZIP was expanded to a CD, insert the installer CD.
b
Double-click the AUTORUN.EXE
Or
For Evaluation copy, unzip the TBN330_EVAL.ZIP and double-click TRACKBIRDSUITE.EXE. It will extract files in C:\PROGRAM FILES\TRACKBIRD INVENTORY SUITE SETUP. The Autorun displays. 43
ASG-TrackBird Installation Guide
2
Click Install TrackBird Web. The first screen welcomes you to the TrackBird Web InstallShield Wizard. You are now ready to complete a series of steps to set up TrackBird Web.
3
Click Next. The TrackBird Web user license agreement.
44
2 Installing TrackBird Servers
4
Read the license agreement terms carefully and accept them by clicking Yes to continue the installation and display the next screen (Choose Destination). Or
If you do not accept the user license agreement's terms, click No to cancel installation of the TrackBird Web software. The Choose Destination Location screen displays.
45
ASG-TrackBird Installation Guide
5
Specify where you want to install the TrackBird Web files. This installation of the TrackBird Web software will then be installed in this folder. By default, the InstallShield Wizard is configured to install the TrackBird Web software in the C:\PROGRAM FILES\ASG\TRACKBIRD WEB folder on your hard disk. Or
If you want to install TrackBird Web into a different folder (other then the default), click Browse and specify where you want to install the TrackBird Web software.
46
2 Installing TrackBird Servers
6
Click Next to complete the installation. The Setup Status screen displays while TrackBird installs.
7
Click Finish.
47
ASG-TrackBird Installation Guide
8
48
Now you can access TrackBird Web from any workstation by typing this URL: http://IPAddressTrackBirdWeb/tbweb.
2 Installing TrackBird Servers
SQL Server and Oracle Database Creation Wizard The Wizard at a Glance The purpose of this Wizard is to make it easier to perform the various steps required to create a functional Microsoft SQL Server or Oracle database for TrackBird Server by grouping the steps in a single module. It takes care of: •
Creating the Data unit or the TableSpace
•
The database itself
•
Transferring the reference data
49
ASG-TrackBird Installation Guide
The Wizard may therefore be used by both users with little knowledge of SQL Server or Oracle and database administrators who wish to quickly create a TrackBird database via a “remote administrator” workstation but do not have SQL administration tools available (notably the enterprise manager). To run the Wizard, click the Windows Start button and then select Programs. Select TrackBird Suite. In the Wizards subgroup, select SQL Server and Oracle Database Creation Wizard.
Generating an SQL Server Database for TrackBird The information required to generate an operational TrackBird database is entered in 4 steps. 1
Define the DB Express alias that will be used for database generation.
2
Create a unit and empty database.
3
Select the reference database for migration.
4
Generate the SQL database.
Step 1: Define the DB Express Alias Click Next in the SQL Server And Oracle Database Creation Wizard’s welcome screen to display the first step.
50
2 Installing TrackBird Servers
Select or define the target DB Express alias. This alias will be used to provide a link between TrackBird Server and the target database under SQL. Note:
Avoid defining an alias name containing special characters and spaces, as this may cause problems for the SQL language used during migration. It is preferable to use a name such as the one shown in the picture. In the Database Type drop list, select SQL Server. In the Server Name box, type the name of the server hosting the SQL database (and/or its IP address). In the Administrator Login and Administrator Password boxes, type the account login/password combination used to manage the database (e.g. sa). To check that the database parameters, administrator login and administrator password are correct, click Test Connection. If the database connection fails, check the database connection parameters and the workstation configuration. If the parameters seem correct, try replacing the name of the SQL server with its IP address. Some network configurations may interfere with the distribution of names (DNS). If the database connection is functioning correctly, click Next to display the following screen in the SQL database installation procedure.
51
ASG-TrackBird Installation Guide
Step 2: Create the Empty Database
The account entered in the previous step is used to authorize creation of the SQL database and the associated tables. Name the target database to be created on the SQL server, by clicking then entering its name, size and location details.
and
Note:
Ensure you do not use the name of an existing database as this may result in irreparable damage. The size and location of the database are two very important factors that must not be ignored. If you have any doubts, you should contact your SQL administrator. The TrackBird SQL database will require approximately 20 MB of disk space for the 52
2 Installing TrackBird Servers
reference tables, and an inventoried node occupies approximately 300 KB in the database. The size of a database for 10,000 workstations will therefore be approximately 20*1,024+10,000*300 = 3,200,480 KB (i.e. 3 GB). Note:
The address of the specified unit (.DAT) corresponds to a location on the SQL server, not on your workstation. The path must therefore comply with all requirements concerning use of the SQL server. If you have any doubts, you should contact your administrator. Click OK to begin database generation on the SQL server, and then click Next to display the following screen.
Step 3: Select the Reference Database
Before you generate the tables in the SQL database, you must specify which reference database will be used for migration. If you are migrating the TrackBird database, this is the TrackBird database. If you have already used the product for some time, this is the database to which you regularly connect. You must select one of the options displayed below the reference database name. •
Transfer only Structure. Select this option if TrackBird is being set up for the first time and no data has yet been imported or entered in the database.
•
Transfer Structure and Data. Select this option if data has already been imported and additional information has been entered directly into the database (administrative fields, etc.).
Click Next to begin TrackBird database generation and then specify whether TrackBird Server is to be run at the end of the procedure in order to check the database structure.
53
ASG-TrackBird Installation Guide
Step 4: Generate the Database The database is now created. The tables are identical to those in the reference database defined in the previous step and, if the corresponding option was selected, the data in the reference database is also transferred. If the data is transferred, this step may take some time. Performing this operation directly on the SQL server wherever possible is therefore recommended, by installing a copy of TrackBird Server and the Wizard on the server together with a copy of the reference database if this is not the database installed by default.
Creating an Oracle Database for TrackBird Note:
Before you create the Oracle database, the SQL Net Client must be already installed on the workstation and an Oracle alias must have been defined for the server that will host the TrackBird database. In this example, we will use the alias Oracle_Server.
Step 1: Define the DB Express Alias To define the DB Express alias 1
54
Select or define the target DB Express alias in the Wizard. This alias will be used to provide a link between TrackBird Server and the target database under Oracle (TrackBird_ORA).
2 Installing TrackBird Servers
Note:
Avoid defining an alias name containing special characters and spaces, as this may cause problems for the SQL language used during migration. It is preferable to use a name such as the one shown in the picture. Unlike the configuration used for SQL Server, the server name corresponds in this case to the alias set up using the SQL Net EASY Configuration tool (e.g. Oracle_Server). Click Next. After confirming that the alias has been created in DB Express, the Wizard performs a connection test. If the test fails, check the parameters in the previous window and the workstation configuration. If the parameters seem correct, try changing the generated alias’s type (Named Pipes, TCP/IP, etc.). Some network configurations may interfere with the distribution of names (DNS).
Step 2: Create the Empty Database The account entered in the previous step is used to authorize creation of the Oracle database and the associated tables.
Click New to create a new TrackBird database administrator in the following dialog.
55
ASG-TrackBird Installation Guide
In this dialog, the requested name and password correspond to the account used to access TrackBird in the current database. If database migration is performed immediately after TrackBird is installed and set up, note that the name is Admin and the password is admin. Oracle, however, requires that a password be set up when a user is created. Select a password that is simple and easy to remember because if it is lost, it is impossible to access the TrackBird database under Oracle. If the user that you wish to create already exists on the Oracle server, do not check the Create administrator option. This user will become the default user. You must also name the TableSpace that will be created on the Oracle server. Ensure you do not use the name of an existing database as this may result in irreparable damage. For the sake of consistency, however, you may use the same name as that of the alias created in the previous step, i.e. TrackBird_ORA. To define the TableSpace, click the icon to the right of the drop list and enter the required arguments in the following dialog.
Note:
The location specified in this dialog corresponds to a path on the Oracle server, not on the workstation. To avoid affecting the organization of the Oracle server, which is set up by the administrator, asking the administrator for potential locations for the future TrackBird database is recommended. This will also ensure that all data is correctly saved.
56
2 Installing TrackBird Servers
The TrackBird_ORA database will occupy approximately 20 MB for the reference tables, and an inventoried workstation occupies approximately 300 KB in the database. The size of a database for 10,000 workstations will therefore be approximately 20*1024+10,000*300 = 3,204,800 KB (i.e. 3 GB). For Oracle migrations, you must also create a temporary TableSpace used by TrackBird and Oracle to store data, notably during database transactions. To define the TableSpace, click the icon to the right of the corresponding drop list and enter the required information in the dialog. Note:
Again for the sake of consistency, the TableSpace may be called TrackBird_ORA_TMP. Setting up the temporary TableSpace in the same directory as the main TableSpace is not recommended. Note also that although you must indicate the size, a size of 500 MB is more than sufficient for the previous example of 10,000 workstations.
Step 3: Select the Reference Database
Before you generate the tables in the Oracle database, you must indicate which reference database should be used for migration. For TrackBird, this is certainly the TrackBird database. If you have already used the product for some time, it is the database to which you regularly connect. You must select one of the following two options below the reference database name. •
Transfer only Structure. Select this option if TrackBird is being set up for the first time and no data has yet been imported or entered in the database.
57
ASG-TrackBird Installation Guide
•
Transfer Structure and Data. Select this option if data has already been imported and additional information has been entered directly into the database (administrative fields, etc.).
Click Next to begin database generation and then specify whether TrackBird Server is to be run at the end of the procedure in order to check the database structure.
Step 4: Generate the Database The database is now being created. The tables will be identical to those in the reference database defined in the previous step and, if the corresponding option was selected, the data in the reference database is also transferred. If the data is transferred, this step may take some time. ASG recommends performing this operation directly on the Oracle server wherever possible, by installing a copy of TrackBird Server and the Wizard on the server together with a copy of the reference database if this is not the database installed by default. Of course, this is possible only on a Windows NT server.
Updating to TrackBird 3.3 Introduction In this section, we will present the steps involved in updating from an existing TrackBird database to Version 3.3. This operation is only for clients who are already using TrackBird. Before going any further, you should carefully read the entire section below regarding prerequisites in order to protect and recover your entire work environment and not irretrievably lose data from the old database. Finally, it is essential that the following prerequisites be carried out precisely and all operations be completed before beginning the update procedure.
Update Prerequisites Backing up the Existing Database Before any other action, whichever type of DBMS is used for the TrackBird database (Interbase, SQL Server or Oracle), it is essential to make a backup of the entire database so that, should any problems arise during the update procedure, the database can be restored.
58
2 Installing TrackBird Servers
The database backup should be kept for some time following the update so that it is possible to revert to that version of the database should it be difficult to operate the new TrackBird database or data be lost during the update process. The source database backup may be used later to retrieve the lost information following update processing. Lastly, testing retrieval of the database backup data to check database integrity before starting the update procedure is recommended. The database can be backed up in the following ways.
Direct Backup In this case, the data is backed up onto a tape and the upgrade is based on the current database. This solution is simple but the data can be retrieved only by overwriting the current database should a problem occur.
Backup and Restore under Another Name This solution is safer because it is used to work on the backup database while leaving the source database available. It can also be used to check that the source database’s data can be safely retrieved. In this method, you must firstly back up the source database and then restore it under another name. The result is: •
The name of the database unit changes, if it is an SQL database;
•
The name of the TableSpace changes, if it is an Oracle database;
•
The name of the directory containing the database changes, if it is an Interbase database.
Upgrading from 2.2 to 3.3 Complete the following procedure to upgrade TrackBird from Version 2.2 to 3.3. (ASG recommends upgrading to a new computer to improve TrackBird performance.)
To upgrade from 2.2 to 3.3 1
Save Your Database •
If you use a Paradox database, save files in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DATA and save the files in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DBCONNECTIONS\*.*. Or
•
If you use an Oracle database, make a dump and save the files in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DBCONNECTIONS\*.*. 59
ASG-TrackBird Installation Guide
Or •
If you use an SQL Server database, make a backup and save the files in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DBCONNECTIONS\*.*.
2
Download the new version.
3
Invoke the new TrackBird Server Version 3.3 installer.
4
Install TrackBird Server, TrackBird IP Server and TrackBird Web (only with IIS) on a new computer.
5
Configure TrackBird IP with the same parameters as the old TrackBird IP. For example, keep the installation folder to C:/NETBIRD; keep the web server alias as netbird, etc. In each collection points, go to Update options tab and choose the appropriate options for your TrackBird clients.
6
Upgrade the database. In order to simplify the process, ASG recommends using another workstation where TrackBird 2.2 and 3.3 will be installed. TrackBird database Version 2.2 needs BDE driver and TrackBird Version 3.3 needs DBExpress driver. Database alias 2.2 will be linked to the production database. By default, database alias 3.3 is linked to Interbase database. If you want to use an Oracle or SQL Server database, first you have to create it with Oracle & SQL Server creation wizard. Before upgrading the database, you have to stop Agent IP Version 2.2 to stop automatic import of collection files in the production database to avoid database corruption.
7
Start the Database migration wizard.
8
Choose migrate version 2 into 3 option.
9
For source database, choose database alias 2.2, for destination database, choose your Oracle or SQL Server database alias 3.3.
10
Restart Agent IP Version 2.2.
11
Update on some TrackBird clients. Before the complete migration to the new TrackBird Server, some tests are made on TrackBird clients to check if TrackBird clients will be updated.
60
2 Installing TrackBird Servers
Steps for Testing: a
On the TrackBird clients, edit the file NETBIRD.CFG (folder C:/NETBIRD/DATA) and change the SERVERPATH field to enter the TrackBird Server 3.3 IP address.
b
Stop TrackBird Agent on TrackBird clients. Open the MS-DOS command and type c:/netbird/bin: agentnt.exe /unload (for Windows NT clients).
c
Check that TrackBird Agent is not running in Task Manager. Then you can launch it. The client is updated when in C:/NETBIRD/BIN, the binaries are with the date of the day.
Note:
If the new TrackBird Server 3.3 is a Windows 2003 server with IIS 6, your TrackBird clients must be updated to the last version 2.2.9 before upgrading to version 3.3. Or, you can use Apache (last version 2.2.9 not mandatory) to upgrade to version 3.3 and then restart IIS 6 when the upgrade is done. 12
Migrate to the new TrackBird Server 3.3. After all the tests, you are now ready to migrate to the new TrackBird Server 3.3 for all TrackBird clients. Stop TrackBird 2.2 and change the IP address of the new TrackBird Server 3.3 in order to have the same address as the old one so the TrackBird clients can be updated without any changes on them. Note:
TrackBird clients will be updated automatically and all at the same time. TrackBird is now upgraded to the new version. To check if all clients are up-to-date: a
Open TrackBird IP Administration; in collection options, choose folder options tab
b
Click the plus sign (+) to add a new entry
c
In Folder column, enter the installation folder (C:/NETBIRD/BIN)
d
In Filter column, enter AGENTNT.EXE for Windows NT clients.
e
Save configuration.
61
ASG-TrackBird Installation Guide
f
During the next collection, TrackBird clients will add information about agentnt.exe in the collection files. Then in TrackBird Server, for each workstation, you can check in Software\File item that an entry appears for AGENTNT.EXE so you can check the size and the creation date.
You can do a simple list query to see all workstations which are not already upgraded. In this list query, you add features: •
CPU\Collection information\outputfile
•
Software\File\Name with criterion = AGENTNT.EXE
•
Software\File\Creation date with criterion less than the < date of the migration. All workstations with an AGENTNT.EXE older than the migration date are not up-to-date.
Upgrading from 3.x to 3.3 Complete the following procedure to upgrade TrackBird from a previous release.
To upgrade TrackBird 1
Save TrackBird IP Server configuration. If you added new groups, collection points, or secondary servers in TrackBird IP Administration, you need to save your IP configuration. Make a copy of the folder C:\PROGRAM FILES\ASG\TRACKBIRD IP SERVER\DATA.
2
3
62
Save your database. •
If you use an Interbase database, save the file C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DATA\TRACKBIRD.GDB
•
If you use an Oracle database, make a dump and save the files in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DBCONNECTIONS\*.*.
•
If you use an SQL Server database, make a backup and save the files in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DBCONNECTIONS\*.*.
Uninstall TrackBird Server, TrackBird IP Server, and TrackBird Web. a
To uninstall TrackBird Server, open Control Panel, choose Add or Remove Programs and choose TrackBird Server. At the end of the uninstallation click No, I will restart my computer later.
b
To uninstall TrackBird IP Server, open Control Panel, choose Add or Remove Programs and choose TrackBird IP Server. At the end of the uninstallation click Yes, I want to restart my computer.
2 Installing TrackBird Servers
c
To uninstall TrackBird Web, open Control Panel, choose Add or Remove Programs and choose TrackBird Web.
d
Ensure the folder C:\PROGRAM FILES\ASG is deleted.
4
Download the new version.
5
Install TrackBird Server, TrackBird IP Server and TrackBird Web. a
Unzip the file downloaded.
b
Launch the TRACKBIRDSUITE.EXE file and unpack it to a convenient location. The Autorun application will launch on completion.
c
From the Autorun application, click Install TrackBird. The defaults should suffice for most installations
d
—
Enter your license code
—
At the end of the installation click No, I will restart my computer later.
From the Autorun application, click Install TrackBird IP. The defaults should suffice for most installations —
e
At the end of the installation click Yes, I want to restart my computer now.
From the Autorun application, click Install TrackBird Web. The defaults should suffice for most installations
Note:
Microsoft IIS is required for TrackBird Web. 6
7
Copy your old IP configuration (step 1 on page 62). a
Open Computer Management window, choose Services node. Stop Inventory IP Agent service.
b
Copy the saved files C:\ PROGRAM FILES\ASG\TRACKBIRD IP SERVER\DATA\*.* in the new folder C:\PROGRAM FILES\ASG\TRACKBIRD IP SERVER\DATA.
c
Open TrackBird IP Administration; check that all your groups, collection points, primary server and secondary servers are well configured. All parameters in collection options are not saved in the data folder so you have to configure them then save the configuration.
Add an alias to the new database.
63
ASG-TrackBird Installation Guide
a
If you use an Interbase database: —
Rename TRACKBIRD.GDB file in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DATA FOLDER IN TRACKBIRD_REFERENCE.GDB. This database will be the reference database.
—
Copy your saved database TRACKBIRD.GDB file in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DATA folder. The default alias opens your saved database. You have to add an alias to the reference database.
—
Launch TrackBird Server, in the login window, click the pen icon.
—
Click Add Alias, give a name to the alias, e.g., trackbird reference and ensure Interbase is selected for the database type.
—
Click Next, in the new window, Local should be selected; in the database path, click the folder and browse your computer to C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DATA.
—
Choose TRACKBIRD_REFERENCE.GDB, click Next. In the next window, the user is sysdba and the password is masterkey.
— b
Click OK to create the alias.
If you use an Oracle database: —
Copy the saved files DBXCONNECTIONS.INI and DBXDRIVERS.INI in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DBCONNECTIONS folder. In the file DBXCONNECTIONS.INI, you have the alias to the Oracle database.
64
—
You have to add an alias to the reference database. Launch TrackBird Server, in the login window, click the pen icon.
—
Click Add Alias, give a name to the alias, e.g., trackbird reference and ensure Oracle is selected for the database type.
—
Click Next, in the new window, Local should be selected; in database path, click the folder and browse your computer to the C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DATA folder and choose TRACKBIRD_REFERENCE.GDB.
—
Click Next. In the next window, the user is sysdba and the password is masterkey.
—
Click OK to create the alias.
2 Installing TrackBird Servers
c
If you use an SQL Server database: —
Copy the saved files DBXCONNECTIONS.INI and DBXDRIVERS.INI in C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DBCONNECTIONS folder. In the file DBXCONNECTIONS.INI, you have the alias to the SQL Server database.
8
9
—
You have to add an alias to the reference database. Launch TrackBird Server, in the login window, click the pen icon.
—
Click Add Alias, give a name to the alias, e.g., trackbird reference and ensure SQL Server is selected for the database type.
—
Click Next, in the new window, Local should be selected; in database path, click the folder and browse your computer to C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\DATA.
—
Choose TRACKBIRD_REFERENCE.GDB, click Next. In the next window, the user is sysdba and the password is masterkey.
—
Click OK to create the alias.
Upgrade the database: a
Launch Database Migration Wizard (Start ` Programs ` Trackbird Suite ` Wizards) and follow the wizard.
b
Choose the upgrade version 3 option. For information, the database source is the reference database, choose Trackbird Reference alias and the destination database is your old database.
Restart Agent IP Service. Open TrackBird IP Administration, at the bottom of the window, right-click IP Agent and choose Start IP Agent. Note:
To check if all clients are up-to-date: a
Open TrackBird IP Administration; in collection options, choose folder options tab.
b
Click the plus sign (+) icon to add a new entry.
c
In Folder column enter the installation folder (C:/TRACKBIRD/BIN).
d
In Filter column enter AGENTNT.EXE for Windows NT clients.
e
Save configuration.
65
ASG-TrackBird Installation Guide
During the next collection, TrackBird clients will add information about AGENTNT.EXE in the collection files. f
In TrackBird Server, for each workstation, you can check in Software\File item that an entry appears for AGENTNT.EXE so you can verify the size and the creation date.
g
You can do a simple list query to see all workstations which are not already upgraded. In this list query, you add features: —
CPU\Collection information\outputfile
—
Software\File\Name with criterion = AGENTNT.EXE
—
Software\File\Creation date with criterion less than ( 5.2
Mac OS X only
Macintosh OS X Client Installation The installation process for Macintosh clients is separate from the main installation as it needs to access specific Macintosh resources to configure the installation process. The following sections describe how to deploy TrackBird for Macintosh OS X. For earlier version of MacOS, refer to the original TrackBird documentation
To install the TrackBird client on a Macintosh running Macintosh OS 10.x
94
1
Create an end user's installer (on a Macintosh). For details see “Creation of End User’s Installer” on page 95.
2
Put the end user's installer on your PC where TrackBird IP Server is running.
3
Download the end user's installer with a web browser and launch it for each computer.
4 Mac OS X and Mac OS Classic Client Installation
Creation of End User’s Installer To create an end user installer 1
Locate the disk image file named Trackbird_macx_installer.dmg in this folder: C:\Program Files\ASG\Trackbird Server\Installer\MAC OS X\
2
Copy this disk image file to your hard disk.
3
Double-click it's icon to mount the disk image. The Trackbird_macx_installer window displays showing the application tbinstmacx_admin.
4
Copy the tbinstmacx_admin application to your hard disk.
5
Unmount the disk image Trackbird_macx_installer and delete the disk image file Trackbird_macx_installer.dmg.
6
Double-click the tbinstmacx_admin application icon to open the TrackBird installer.
7
Enter your administrator information (name and password).
8
Enter the parameters needed to connect to TrackBird IP Server: a
Enter the TCP/IP number of the server where TrackBird Admin IP is running (e.g., 192.168.42.4). 95
ASG-TrackBird Installation Guide
b
Enter the port of the web server (usually 80 for IIS and 8080 for Apache). Port number 80 is used in this procedure.
c
Alias to TrackBird on the web server (IIS or Apache). For example, trackbird is used in the procedure.
This information (encrypted in the end user installer) is used to install the TrackBird components. If you setup an Administrator account on each computer with the same parameters you entered, your end users will not be prompted for an Administrator password during the installation process. Or
If you do not have the same account on each client computer, you may leave these fields blank. Your end users will then have to authenticate themselves as an Administrator of the client computer. 9
Test the parameters you entered in step 8 by clicking Install. The end user's installer launches.
A window showing the installation steps appears. At the end of the installation, the end user's installer automatically quits and launches the TrackBird client in order to collect the information on this Macintosh. This information is automatically sent to the TrackBird IP Server and imported into the TrackBird Server. 10
If this installation is successful, click Create. You are prompted for a location to save your end user's installer (named nbinstmacx).
You are ready to complete the next step: create a disk image containing your end user's installer and install this disk image on your TrackBird IP Server.
96
4 Mac OS X and Mac OS Classic Client Installation
Disk Image Creation Complete the following procedure to create a disk image (.dmg file) containing the TrackBird installer. Note:
To create the disk image the Disk Copy application will be used. This application differs on Macintosh OS 10.2 with earlier version of Macintosh OS X.
To create a disk image for Macintosh OS Version 10.2 and later 1
Create a folder named TrackBird Installer on the Desktop.
2
Copy the TrackBird Installer (nbinstmacx) to the TrackBird Installer folder on the Desktop.
3
Open the Disk Copy application (found in /Applications/Utilities).
4
Select New ` Image. Or
Select File ` Volume. 5
Navigate to and select the TrackBird Installer folder on the Desktop.
6
Click Image.
7
When prompted, enter these parameters:
8
a
Save as parameter = trackbird_macx_installer
b
Where parameter = Desktop
c
Image Format parameter = compressed
d
Encryption parameter = none
Click Save and wait for the process to end. A disk image named trackbird_macx_installer.dmg is now on the Desktop.
9
If you plan to use internet-enabled disk image (only available on Macintosh OS 10.2.3 or later), complete these steps. a
Open the Terminal application (found in /Applications/Utilities).
b
Set the internet-enabled flag, enter this command in the Terminal window: 97
ASG-TrackBird Installation Guide
hdiutil internet-enable -yes ~/Desktop/trackbird_macx_installer.dmg
where ~ is a shortcut that references your complete home directory path.
To create a disk image for Macintosh OS Version 10.1
98
1
Open the Disk Copy application (found in /Applications/Utilities).
2
Choose Image ` New Blank Image.
3
When prompted, enter these parameters: a
Save as parameter = trackbird_macx_installer_NonCompressed
b
Where parameter = Desktop
c
Volume Name parameter = TrackBird Installer
d
Size parameter = 5 MB
e
Format parameter = Mac OS Extended
f
Encryption parameter = none
4
Click Create.
5
Drag and Drop (copy) the TrackBird Installer (nbinstmacx) to the mounted disk image (/Volume/TrackBird Installer).
6
Unmount the disk image deleting the disk image icon to the trash or by using the pop-up menu command Eject.
7
Switch back to the Disk Copy application;
8
Choose Image ` Convert Image.
9
When asked for a disk image, select the trackbird_macx_installer_NonCompressed.dmg you created in step 3.
10
Click Convert.
11
When prompted, enter these parameters: a
Save as parameter = trackbird_macx_installer
b
Where parameter = Desktop
4 Mac OS X and Mac OS Classic Client Installation
12
c
Image Format parameter = compressed
d
Encryption parameter = none
Click Convert and wait for the converting process to end.
Installing the Disk Image on the TrackBird IP Server Copy the file Trackbird_macx_installer.dmg to your PC where you have TrackBird IP server running in C:\Program Files\ASG\TrackBird IP Server\VirtualDir\files\install
Installing a Macintosh Client The following sections describe using an internet-enabled disk image. ASG recommends this solution for Macintosh OS Version 10.2.3 or later with Apple's Safari web browser. Internet-enabled disk image should not be used on system earlier than Macintosh OS Version 10.2.3. The installation is done using your TrackBird IP Server as an installation URL on each Macintosh workstation. The URL used will be in this form: http://192.168.42.4:80/trackbird/
where: •
192.168.42.4 is the TCP/IP number of the PC where the TrackBird IP server is running.
•
80 is the port number of the web server. Note:
You may omit the :80 for IIS but need to enter :8080 for Apache), •
trackbird is the IIS alias (or Apache folder).
99
ASG-TrackBird Installation Guide
Macintosh OS Version 10.2.3 or later In order to use the internet-enabled disk image (starting with Macintosh OS 10.2.3), ASG recommends using Apple's web browser Safari (http://www.apple.com/safari/). On Macintosh without Safari installed, you may also use Microsoft's Internet Explorer but the procedure is longer.
To use an internet-enabled disk image with an Apple's Safari web browser 1
Launch Safari and enter your TrackBird IP server URL.
2
In Safari, choose Window ` Downloads to see the different installations steps and locate the TrackBird Installer icon (nbinstmacx). On your desktop, you will found the TrackBird Installer (named nbinstmacx).
3
Double-click the TrackBird installer (file nbinstmacx on your Desktop). The client is installed and the first collect is carried out automatically.
4
Put the file nbinstmacx in the Trash folder. Note:
The disk image Trackbird_macx_installer.dmg is sent to the Trash folder. The internet-enabled option is disabled by Safari; you may not use this disk image again (with the internet-enabled feature)
To use an internet-enabled disk image with an Internet Explorer
100
1
Launch Internet Explorer and enter your TrackBird IP server URL. The disk image file Trackbird_macx_installer.dmg is downloaded to your client Macintosh.
2
Double-click the Trackbird_macx_installer.dmg disk image. On your desktop, you will find the TrackBird Installer (named nbinstmacx).
3
Double-click the TrackBird installer (file nbinstmacx on your desktop). The client is installed and the first collect is carried out automatically.
4
Put the file nbinstmacx in the Trash folder.
4 Mac OS X and Mac OS Classic Client Installation
Macintosh OS X Earlier Versions As the internet-enabled disk image are only supported with Macintosh OS 10.2.3 or later, the installation process changes. Also, using an Internet Explorer web browser or Apple's Safari may not run on your older system (Safari requires Macintosh OS X version 10.2 Jaguar or later). Note:
The procedure is also valid if you choose not to use an internet-enabled disk image.
To use an internet-enable disk image with earlier versions of Macintosh OS X 1
Launch Internet Explorer and enter your TrackBird IP server URL. The disk image file Trackbird_macx_installer.dmg is downloaded to your client Macintosh.
2
Double-click the Trackbird_macx_installer.dmg disk image to mount the disk image with Apple's Disk Copy application.
3
Locate the volume TrackBird Installer on your Desktop, open its window to see the TrackBird Installer (named nbinstmacx).
4
Double-click the TrackBird installer (file nbinstmacx on your TrackBird Installer volume). The client is installed and the first collect is carried out automatically.
5
Unmount the disk image by selecting the TrackBird Installer volume and choosing Eject from the pop-up menu.
6
Put the file Trackbird_macx_installer.dmg in the Trash folder.
Mac OS Classic Client Installation The installation process for Macintosh clients is separate from the main installation as it needs to access some specific Macintosh resources to configure the installation process. This section includes instructions to perform a TrackBird deployment for Macintosh OS Classic. Installing the TrackBird client on a Macintosh running Macintosh OS Version 7 or 9 involves these basic steps: •
Configure and package the TrackBird agent installer on 1 MacOS workstation and put this installer on the PC where TrackBird IP (the data collection and agent distribution point) is running.
•
For each computer, you have to download the end user's installer with a web browser and launch it. 101
ASG-TrackBird Installation Guide
To install the TrackBird client on a Macintosh running Macintosh OS Classic 1
Locate the Mac OS Classic TCPIP Installer.sit.hqx file, which is found in the MacOS Classic folder in the TrackBird Server Installer folder. By default it is located in C:\Program Files\ASG\TrackBird Server\Installer.
2
Copy this file, using the network or by USB drive (recommended) to the desktop of one of your Mac OS Classic workstations.
3
Using StuffIt, decompress TCPIP Installer.sit.hqx. A folder named TCP_IP Installer folder will be created. Inside this folder there will be a file named 192.168.42.4$trackbird$_80.
4
Create a new folder named tbinstmac on your desktop.
5
Copy the installer (192.168.42.4$trackbird$_80) to this folder.
6
Rename the installer to nnn.nnn.nnn.nnn$alias$_xxxx. Where: nnn.nnn.nnn.nnn is the IP address of the TrackBird IP Server. alias is the IIS or Apache alias of the virtual directory where TrackBird IP Server is installed (by default trackbird) xxxx is the TCP/IP port of the web server where TrackBird IP Server is installed. For example, if my TrackBird server is at 10.31.12.151 with the default alias and port (under IIS), the file is renamed 10.31.12.151$trackbird$_80. Under Apache, it will likely be 10.31.12.151$trackbird$_8080, because of the alternate port configuration.
7
Use DropStuff (or StuffIt) to compress (make a self-extracting archive) and binhex the folder tbinstmac. This will create a file named tbinstmac.sea.hqx.
8
Copy this file to your PC server into the folder (by default C:\Program Files\ASG\TrackBird IP Server\VirtualDir\files\install). This folder already contains the PC installer named nbinst32.exe. Note:
Adjust the above path location if you did not use the default install path.
102
4 Mac OS X and Mac OS Classic Client Installation
Deploying the Mac OS Classic Agents The agents are deployed by launching a web browser on the client Mac OS Classic workstation and downloading the agent installer via the TrackBird IP Server URL.
To deploy the agents 1
Using a standard web browser, open the TrackBird IP Server URL. The URL depends on your installation parameters. The address should be in this format: http://nnn.nnn.nnn.nnn:xxxx/alias where: nnn.nnn.nnn.nnn is the IP address of the TrackBird IP Server. xxxx is the TCP/IP port of the web server where TrackBird IP Server is installed. alias is the IIS or Apache alias of the virtual directory where TrackBird IP Server is installed (by default trackbird). For example, if my TrackBird server is at 10.31.12.151 with the default alias and port (under IIS), the URL will likely be http://10.31.12.151:80/trackbird. Under Apache, it will likely be http://10.31.12.151:8080/trackbird. The installer will be downloaded to the Macintosh. If your Internet Explorer options are configured appropriately, this file will be de-binhexed and uncompressed automatically. If this is not the case, use Stuffit Expander to decompress manually.
2
Double-click the installer (i.e., 10.31.12.151$trackbird$_80) in the tbinstmac folder. The client installs and a collection launches automatically, and, once the collection finishes, you may view the results on the TrackBird Server console.
103
ASG-TrackBird Installation Guide
104
Chapter 5:PDA
5
Clients Installation
Palm OS Client Installation Check that you have already installed: •
TrackBird client for Windows Version on client workstation.
•
Palm HotSync application is installed on the client workstation. You can download Palm Desktop software 4.1 for Windows at URL: http://www.palmone.com/us/support/downloads/win_desktop.html
Palm Desktop Requirements Palm Desktop Version 4.1 for Windows requires: •
Handheld: Palm Tungsten series, Palm Zire series, Palm i700 series, Palm m500 series, Palm m100 series, Palm VII series, Palm V series, Palm III series, PalmPilot handhelds.
•
Desktop Pentium class PC running Windows 98, Windows NT 4, Windows 2000, Windows ME, or Windows XP.
•
8 MB RAM minimum (ASG recommends16 MB).
•
50 MB available hard disk space.
•
Video resolution 640x480 and 256 colors (ASG recommends 800x600).
•
One available USB port if used with Palm USB Universal Cradle or PalmConnect USB Kit Or
•
One open serial port if used with Palm Serial HotSync Cradle or PalmConnect Serial Kit.
105
ASG-TrackBird Installation Guide
Deploying the Palm OS Client Palm OS Collector Automatic Installation To automatically install the Palm OS collector, you must have selected the option "Collector automatic installation for mobile devices" in the Windows options tab of the TrackBird IP Administration interface. Windows client agent (AGENTNT.EXE for Windows NT, Windows 2000, and Windows XP or AGENT32.EXE for Windows 95, Windows 98, and Windows ME) located in the C:\TBCLIENT\BIN folder detects automatically when HotSync software is running. Windows client agent downloads Palm OS client package from TrackBird IP Server (primary or secondary server). This package is decompressed and TBPALM_INSTALL.EXE and PALMDLLSHIM.DLL are copied to C:\TBCLIENT\BIN. Palm OS client components are installed on HotSync folder and HotSync registry is updated. TrackBird Palm OS client TRACKBIRD.PRC is installed during the next synchronization with the Palm.
Palm OS Collector Automatic Uninstallation Palm OS Client is uninstalled when Windows client will be uninstalled. See “TrackBird IP Administration” in the ASG-TrackBird Reference Guide for instructions on uninstalling a Windows client.
Palm OS Collector Manual Installation To manually install the Palm OS Collector 1
Copy TBPALM_INSTALL.EXE and PALMDLLSHIM.DLL library in C:\TBCLIENT\BIN. You can find these 2 files in the C:\PROGRAM FILES\ASG\TRACKBIRD SERVER\PDA\PALMOS\BIN folder.
2
Double-click TBPALM_INSTALL.EXE. A C:\TBCLIENT\BIN\PALM folder is created and contains:
106
—
3 dynamic libraries used for installing Palm OS client with HotSync application: CONDMGR.DLL, HSAPI.DLL, INSTAIDE.DLL
—
A TB_CONDUIT.DLL conduit to synchronize collection information between your Palm PDA and TrackBird Server
5 PDA Clients Installation
— 3
TRACKBIRD.PRC, TrackBird client. Is installed via HotSync on your Palm during the next synchronization.
Synchronize your Palm PDA with your workstation.
Palm OS client is now installed.
To check collection data in your Palm 1
Click the TrackBird icon on your Palm.
2
Select Refresh Data from the Options menu. A collection of your Palm is done.
3
Choose a category in menu to see information.
Figure 3 • TrackBird Palm OS interface
To ensure TrackBird Server is collecting information from your Palm, check your HotSync configuration on your workstation.
107
ASG-TrackBird Installation Guide
To check your HotSync configuration
108
1
Choose Custom on HotSync menu.
2
Choose TrackBird to configure conduit.
5 PDA Clients Installation
3
Choose Handheld overwrites Desktop to retrieve information from Palm to TrackBird Server.
4
Synchronize your Palm. Collection file will be sent to TrackBird IP Server and it will be imported into the TrackBird Server.
Palm OS Collector Manual Uninstallation To manually uninstall the Palm OS Collector 1
Choose Start ` Run.
2
Enter cmd and click OK. An MS-DOS command window opens.
3
Go to C:\TBCLIENT\BIN and type :tbpalm_install.exe /UNINSTALL. The folder C:\TBCLIENT\BIN\PALM is deleted. HotSync registry is modified.
4
Delete TBPALM_INSTALL.EXE and PALMDLLSHIM.DLL from the C:\TBCLIENT\BIN folder.
109
ASG-TrackBird Installation Guide
How TrackBird Palm OS Client Works Palm OS Version 3.5 or later During synchronization between your Palm and your workstation, TrackBird client detects this event. If collection information is not up-to-date, a collection is launched. Data synchronization is then realized by the TB_CONDUIT.DLL.
Palm OS Prior to Version 3.5 During synchronization between your Palm and your workstation, the TB_CONDUIT.DLL invokes the TrackBird client to run a collection. Data synchronization is then realized by the TB_CONDUIT.DLL. 1
TB_CONDUIT.DLL conduit creates an XXX.NBP in C:\TBCLIENT\DATA Windows client folder. Windows client detects the NBP file and does the following: •
Moves the XXX.NBP file to the C:\TBCLIENT\DATA\TPV_PDA folder
•
Converts NBP file to NBC file
•
Creates a compressed package (XXX.NBR) and sends this file to TrackBird IP Server where it is imported to TrackBird Server.
1. The output file name depends on Palm OS version and model. If it exists, ROM serial number is used, if not a number base on installation date and hour is used.
110
5 PDA Clients Installation
Windows CE Client Installation This version is tested for Pocket PC 2000 and 2002 with Windows CE 3.0 operating system. Microsoft ActiveSync software must be installed on each client workstation where a Pocket PC will be connected to work with TrackBird client. You can download this software at one of these URLs: •
For Pocket PC 2002: —
ActiveSync 3.7:
http://www.microsoft.com/windowsmobile/resources/downloads/pocketpc/activesy nc37.mspx •
For Pocket PC 2000: —
ActiveSync 3.6:
http://www.microsoft.com/technet/treeview/default.asp?url=technet/prodtechnol/w ce/downloads/acsync36.asp —
ActiveSync 3.1:
http://www.microsoft.com/technet/treeview/default.asp?url=technet/prodtechnol/d ownloads/handheldpe/default.mspx
Deploying a Windows CE Client To automatically install the Windows CE collector, you must have selected the option "Collector automatic installation for mobile devices" in the Windows options tab of the TrackBird IP Administration interface. Deploying the TrackBird client is a simple task. The executable, TBPOCKETPC_INSTALL.EXE, is present in the BIN folder on the TrackBird client when ActiveSync software is installed.
How Windows Agent Works Client agent (AGENTNT.EXE in BIN client folder) automatically detects if Microsoft ActiveSync software is installed and loaded (process in Task Manager) on TrackBird client. Client agent automatically extracts the TBPOCKETPC_INSTALL.EXE application in the BIN folder.
111
ASG-TrackBird Installation Guide
Launch the TBPOCKETPC_INSTALL application to create a Pocket PC folder in C:\TBCLIENT\BIN. This application configures ActiveSync to install TrackBird client (TBCE_CLIENT.EXE) during the next synchronization. Note:
If ActiveSync software is uninstalled, client agent deletes the TBPOCKETPC_INSTALL.EXE application.
How the TrackBird Client Works HotSync Registration The Client agent records the TBCE_CLIENT.EXE application in an entry in the Registry of TrackBird Client to be launch automatically by ActiveSync software at the next 1
synchronization .
Libraries downloaded If a Pocket PC is physically connected to TrackBird client, a collection is realized. The TBPOCKETPC_INSTALL.EXE application extracts these 3 libraries in the BIN client folder on the workstation: •
TBCE_PLATFORM.DLL
•
TBCE_DETECT.DLL
•
TBCE_COMPAQ.DLL
2
These libraries are adapted for different platforms (Pocket PC 2000, 2002) and different processor types (ARM, MIPS, SH3, and SH4). They are downloaded to the Pocket PC Windows folder and then deleted from the workstation.
Data Collection The TBCE_CLIENT.EXE application collects and created an XXX.NBP file in the workstation DATA folder.
Data Send to TrackBird IP Server Client agent detects an NBP file and creates a collection file in TrackBird format (NBC and NBX file). A package (NBR file) is created from NBC and NBX files and then sent to TrackBird IP Server. Client agent moves all Pocket PC files in DATA\TPV_PDA to the client sub-folder.
1. This entry is created during the first launch (typically during the installation) or in case of TBPOCKETPC_INSTALL.EXE is moved. 2. TBCE_COMPAQ.DLL library is only extracted and downloaded on Compaq iPaq H3600. It allows to collect more specific features.
112
5 PDA Clients Installation
Automatically Import in TrackBird Server The collection file is automatically imported in to TrackBird Server.
113
ASG-TrackBird Installation Guide
114
Chapter 6:UNIX
6
Clients Installation
AIX Client Installation AIX client was tested on AIX Version 4.3 and 5. AIX client is compatible with Version 4.3 or later.
Deploying the AIX Client Configuring the TrackBird IP Server After installing TrackBird IP Server, you must configure the TrackBird IP Administration tool to indicate client’s installation path. Click the collection point which corresponds to your AIX workstations, then modify the AIX Clients field in the Installation folder tab, save configuration. By default, the folder value is /usr/local/tbclient/
Installing from a Web Browser Open your web browser on a client workstation and enter a URL using this format: http://AddressIPServer:Port/Alias/
where: AddressIPServer is your TrackBird IP Server. Port is by default 80 or 8080. Alias is trackbird. For example, the URL could be: http://192.168.2.2:80/trackbird/ Save the file to your client workstation.
Installing without a Web Browser If you do not have a web browser, copy c:\Program Files\ASG\TrackBird IP Server\VirtualDir\files\install\tbinstaix on your client workstation. 115
ASG-TrackBird Installation Guide
Note:
Download the file in binary mode if you are using file transfer protocol (FTP).
Common Installation Change the file execution mode, type the following command: •
If you use a web browser, enter: chmod u+x tbinstaix_AdressIP\$Alias_trackbird\$_portNumber Note:
Ensure you type a back slash (\) before a dollar sign ($) so that the dollar sign ($) is not interpreted by the shell. •
If you do not use a web browser, enter: chmod u+x tbinstaix
Two syntaxes to launch the installer: ./tbinstaix –server=IPAddress [-port=portNumber] [-alias=aliasName] [-installPath=pathname]
where: server is the server name and is mandatory. port is by default using 80. alias is by default trackbird. installPath is by default /usr/local/tbclient (the value in TrackBird IP Administration, Installation folder tab). ./tbinstaix__IPAddress\$alias\$_portNumber,
For example: ./tbinstaix_ 192.168.42.4\$trackbird\$_80 Note:
You must be an administrator (super user) to install TrackBird client. Use the su command.
116
6 UNIX Clients Installation
Verify AIX Client installation After installation, you can check that TrackBird daemon is running by typing the following command: ps –cef | grep tbiaix
To start or stop TrackBird daemon manually, a script has been created in /etc/rc.d/rc2.d/ folder. To stop daemon, type: /etc/rc.d/rc2.d/trackbird stop To start daemon, type: /etc/rc.d/rc2.d/trackbird start This daemon automatically starts and stops at each logon and logout. The system launches symbolic links: /etc/rc.d/rc2.d/K99trackbird to stop the process and /etc/rc.d/rc2.d/S99trackbird to start the process.
Installation folder on client workstation The /usr/local/tbclient directory contains these files: Subdirectory Filename Name bin
Description
Contains all executables tbaaix
Agent executing inventory collection tbcaix
tbuaix
Automatically updates the client workstation
tbcaix
Hardware and software inventory collection client
tbiaix
Daemon that regularly executes the “tbaaix” application
memconf
Perl script to have information about memory banks. This script is launched by tbcaix
117
ASG-TrackBird Installation Guide
Subdirectory Filename Name components
data
Description
Contains all components used in collecting information on the Linux workstation nbopt
Package containing the collection option settings
nblng
Package containing the language settings
nbkb
Package containing the knowledge base files
nbaix
package containing the collector, daemon and AIX agent update
nbinst
Package containing files used when first installing the TrackBird client
*.kb
Knowledge base files
*.nb*
Collection files
netbird.cfg
The configuration file containing information on the collection options
Removing an AIX Client To remove AIX client and all its components on the client workstation, you have to stop daemon tbiaix by typing this command: /etc/rc.d/rc2.d/trackbird stop
Then you must delete trackbird script and client folder: rm rm rm rm
/etc/rc.d/rc2.d/trackbird /etc/rc.d/rc2.d/K99trackbird /etc/rc.d/rc2.d/S99trackbird –rf /usr/local/tbclient
Note:
You must be an administrator (super user). Use the su command.
118
6 UNIX Clients Installation
HP/UX Client Installation HP/UX client has been tested on HP/UX Version 10.2, 11.0, and 11.i.
Deploying the HP/UX Client TrackBird IP Server Configuration After installing TrackBird IP Server, you must configure the TrackBird IP Administration tool to indicate client’s installation path. Click the collection point which corresponds to your HP/UX workstations, then modify the HP/UX Clients field in Installation folder tab, and save the configuration. By default, the folder value is /usr/local/tbclient/
Installing with a Web Browser Open your web browser on a client workstation and enter a URL using this format: http://AddressIPServer:Port/Alias/
where: AddressIPServer is your TrackBird IP Server. Port is by default 80 or 8080 Alias is trackbird. For example, the URL could be: http://192.168.2.2:80/trackbird/ Save the file to your client workstation.
Installing without a Web Browser If you do not have a web browser, copy c:\Program Files\ASG\TrackBird IP Server\VirtualDir\files\install\tbinsthpux on your client workstation. Note:
Download the file in binary mode if you are using an FTP server.
119
ASG-TrackBird Installation Guide
Common Installation Change the file execution mode, type the following command: •
If you use a web browser, enter: chmod u+x tbinsthpux_AdressIP\$Alias_trackbird\$_portNumber Note:
Ensure you type a back slash (\) before a dollar sign ($) so that the dollar sign ($) is not interpreted by the shell. •
If you do not use a web browser, enter: chmod u+x tbinsthpux
Two syntaxes to launch the installer: ./tbinsthpux –server=IPAddress [-port=portNumber] [-alias=aliasName] [-installPath=pathname]
where: server is the server name and is mandatory. port is by default using 80. alias is by default trackbird. installPath is by default /usr/local/tbclient (the value in TrackBird IP Administration, Installation folder tab). ./tbinsthpux__IPAddress\$alias\$_portNumber,
For example: ./tbinsthpux_ 192.168.42.4\$trackbird\$_80 Note:
You must be an administrator (super user) to install TrackBird client. Use the su command.
120
6 UNIX Clients Installation
Verify HP/UX Client Installation After installation, you can check that TrackBird daemon is running by typing this command: ps –cef | grep tbihpux
To start or stop TrackBird daemon manually, a script has been created in the /etc/init.d/ folder. To stop daemon, type: /sbin/init.d/trackbird stop To start daemon, type: /sbin/init.d/trackbird start This daemon automatically starts and stops at each logon and logout. The system launches symbolic links: /etc/rc1.d/K99trackbird to stop the process and /etc/rc2.d/S99trackbird to start the process.
Installation Folder on Client Workstation The /usr/local/tbclient directory contains these files: Subdirectory Name
Filename
bin
Contains all executables
Description
tbahpux
Agent executing inventory collection tbchpux
tbuhpux
Automatically updates the client workstation
tbchpux
Hardware and software inventory collection client
tbihpux
Daemon that regularly executes the tbahpux application
memconf
Perl script perl to have information about memory banks. This script is launched by tbchpux
121
ASG-TrackBird Installation Guide
Subdirectory Name components
data
Filename
Description
Contains all components used in collecting information on the Linux workstation nbopt
Package containing the collection option settings
nblng
Package containing the language settings
nbkb
Package containing the knowledge base files
nbhpux
Package containing the collector, daemon and HP/UX agent update
nbinst
Package containing files used when first installing the TrackBird client
*.kb
Knowledge base files
*.nb*
Collection files
netbird.cfg
The configuration file containing information on the collection options
Removing the HP/UX Client To remove HP/UX client and all its components on client workstation, you have to stop daemon tbihpux by typing the following command: /sbin/init.d/trackbird stop
Then you have to delete trackbird script and client folder. rm rm rm rm
/sbin/init.d/trackbird /etc/rc1.d/K99trackbird /etc/rc2.d/S99trackbird –rf /usr/local/tbclient
Note:
You must be an administrator (super user). Use the su command.
122
6 UNIX Clients Installation
Linux Client Installation The Linux client was tested on: •
Red Hat Linux 7.1, 7.2, 7.3, and 8.0
•
Mandrake Linux 8.2
•
Suse 8.2, 9.0
Deploying Linux Client TrackBird IP Server Configuration After installing TrackBird IP Server, you must configure the TrackBird IP Administration tool to indicate the client’s installation path. Click the collection point which corresponds to your Linux workstations, then modify the Linux Clients field in the Installation folder tab, and save the configuration. By default, the folder value is /usr/local/tbclient/
Installing with a Web Browser Open your web browser on a client workstation and enter a URL using this format: http://AddressIPServer:Port/Alias/
where: AddressIPServer is your TrackBird IP Server. Port is by default 80 or 8080. Alias is trackbird. For example, the URL could be: http://192.168.2.2:80/trackbird/ Save the file to your client workstation.
Installing without a Web Browser If you do not have a web browser, copy c:\Program Files\ASG\TrackBird IP Server\VirtualDir\files\install\tbinstlinux on your client workstation. Download the file in binary mode if you are using file transfer protocol (FTP).
123
ASG-TrackBird Installation Guide
Common Installation •
If you use a web browser, enter: chmod u+x tbinstlinux_AdressIP\$Alias_trackbird\$_portNumber Note:
Ensure you type a back slash (\) before a dollar sign ($) so that the dollar sign ($) is not interpreted by the shell. •
If you do not use a web browser, enter: chmod u+x tbinstlinux
Two syntaxes to launch the installer: ./tbinstlinux –server=IPAddress [-port=portNumber] [-alias=aliasName] [-installPath=pathname]
where: server is the server name and is mandatory. port is by default using 80. alias is by default trackbird. installPath is by default /usr/local/tbclient (the value in TrackBird IP Administration, Installation folder tab). ./tbinstlinux__IPAddress\$alias\$_portNumber,
For example: ./tbinstlinux_ 192.168.42.4\$trackbird\$_80 Note:
You must be an administrator (super user) to install TrackBird client. Use the su command.
Verifying the Linux Client Installation After installation, you can check that TrackBird daemon is running by typing this command: ps axuw | grep tbilinux
To start or stop TrackBird daemon manually, a script has been created in the /etc/init.d/ folder. 124
6 UNIX Clients Installation
To stop daemon, type: /etc/init.d/trackbird stop To start daemon, type: /etc/init.d/trackbird start This daemon is automatically start and stop at each logon and logout.
Installation Folder on Client Workstation The /usr/local/tbclient directory contains the following files: Subdirectory Name
Filename
bin
Contains all executables
components
data
Description
tbalinux
Agent executing inventory collection tbcaix
tbulinux
Automatically updates the client workstation
tbclinux
Hardware and software inventory collection client
tbilinux
Daemon that regularly executes the “tbaaix” application
Contains all components used in collecting information on the Linux workstation nbopt
Package containing the collection option settings
nblng
Package containing the language settings
nbkb
Package containing the knowledge base files
nblinux
Package containing the collector, daemon and AIX agent update
nbinst
Package containing files used when first installing the TrackBird client
*.kb
Knowledge base files
*.nb*
Collection files
netbird.cfg
The configuration file containing information on the collection options
By default, the client installs 2 libraries (libdetect and libdmidecode) in /usr/local/lib
125
ASG-TrackBird Installation Guide
The library libdetect needs the support files that are located in /usr/local/share/detect The dynamic linker configuration file (/etc/ld.so.conf) is modified to add the entry /usr/local/lib (This path indicates the libdetect and libdmidecode libraries locations). The installer then runs the command /sbin/ldconfig to update the dynamic linker configuration.
Removing the Linux Client To remove Linux client and all its components on client workstation, you have to stop daemon tbilinux by typing the following command: /etc/init.d/trackbird stop
Then you have to delete trackbird script and client folder. rm /etc/init.d/trackbird rm –rf /usr/local/tbclient Note:
You must be an administrator (super user). Use the su command.
Solaris Client Installation Solaris client was tested on Solaris 8 and 9.
Deploying the Solaris Collector TrackBird IP Server Configuration After installing TrackBird IP Server, you must configure the TrackBird IP Administration tool to indicate client’s installation path. Click the collection point which corresponds to your Solaris workstations, then modify the Solaris Clients field in the Installation folder tab, and save the configuration. By default, the folder is /usr/local/tbclient/.
Installation Using a Web Browser Open your web browser on a client workstation and enter the following URL: http://AddressIPServer:Port/Alias/ 126
6 UNIX Clients Installation
where: AddressIPServer is your TrackBird IP Server. Port is by default 80 or 8080. Alias is trackbird. For example, the URL could be: http://192.168.2.2:80/trackbird/
Save the file in your client workstation.
Installing without a Web Browser If you do not have a web browser, copy c:\Program Files\ASG\TrackBird IP Server\VirtualDir\files\install\tbinstsolaris on your client workstation. Note:
Download the file in binary mode if you are using an FTP server.
Common Installation Change the file execution mode, type the following command: •
If you use a web browser, enter: chmod u+x tbinstsolaris_AdressIP\$Alias_trackbird\$_portNumber Note:
Ensure you type a back slash (\) before a dollar sign ($) so that the dollar sign ($) is not interpreted by the shell. •
If you do not use a web browser, enter: chmod u+x tbinstsolaris
Two syntaxes to launch the installer: ./tbinstsolaris –server=IPAddress [-port=portNumber] [-alias=aliasName] [-installPath=pathname]
127
ASG-TrackBird Installation Guide
where: server is the server name and is mandatory. port is by default using 80. alias is by default trackbird. installPath is by default /usr/local/tbclient (the value in TrackBird IP Administration, Installation folder tab). ./tbinstsolaris__IPAddress\$alias\$_portNumber,
For example: ./tbinstsolaris_ 192.168.42.4\$trackbird\$_80 Note:
You must be an administrator (super user) to install TrackBird client. Use the su command.
Verifying Solaris Client Installation After installation, you can check that TrackBird daemon is running by typing the following command: ps –cef | grep tbisolaris
To start or stop TrackBird daemon manually, a script has been created in /etc/init.d/ folder. To stop daemon, type: /etc/init.d/trackbird stop To start daemon, type: /etc/init.d/trackbird start This daemon automatically starts and stops at each logon and logout. The system launches symbolic links: /etc/rc1.d/K99trackbird to stop the process and /etc/rc2.d/S99trackbird to start the process.
128
6 UNIX Clients Installation
Installation Folder on Client Workstation The /usr/local/tbclient directory contains the following files: Subdirectory Filename Name bin
components
data
Description
Contains all executables tbasolaris
Agent executing inventory collection tbcsolaris
tbusolaris
Automatically updates the client workstation
tbcsolaris
Hardware and software inventory collection client
tbisolaris
Daemon that regularly executes the tbasolaris application
memconf
Perl script perl to have information about memory banks. This script is launched by tbcsolaris
Contains all components used in collecting information on the Linux workstation nbopt
Package containing the collection option settings
nblng
Package containing the language settings
nbkb
Package containing the knowledge base files
nbsolaris
Package containing the collector, daemon and Solaris agent update
nbinst
Package containing files used when first installing the TrackBird client
*.kb
Knowledge base files
*.nb*
Collection files
netbird.cfg
The configuration file containing information on the collection options
Serial Number Detection If a file serial_number.txt is in the tbclient/data folder, its first line will be used as the serial number for the model.
129
ASG-TrackBird Installation Guide
Removing a Solaris Client To remove Solaris client and all its components on client workstation, you have to stop daemon tbisolaris by typing the following command: /etc/init.d/trackbird stop
Then you have to delete trackbird script and client folder. rm rm rm rm
/etc/init.d/trackbird /etc/rc1.d/K99trackbird /etc/rc2.d/S99trackbird –rf /usr/local/tbclient
Note:
You must be an administrator (super user) to install TrackBird client. Use the su command.
Launching a Collection Manually The collection tool supports a -now command line parameter. This parameter will allow the collection process to be executed without using the existing scheduling restrictions. In order to work properly, it will need to be run with system administrator privileges as some detection needs it. For example, the following command line will start the inventory on the Solaris platform: su /usr/local/tbclient/bin/tbcsolaris –now
Replace by tbcaix for AIX platforms, tbchpux for HP/UX platforms.
Customizing your UNIX Client Configuration It may be necessary to have a custom TrackBird configuration on each UNIX (AIX, HP/UX, Solaris) workstation. Currently, the configuration is set in the TrackBird IP Administration tool and is global to a group. Configuration options are downloaded by the inventory client and stored in the netbird.cfg file (located in the data folder).
130
6 UNIX Clients Installation
You can use the localopt.cfg file to override netbird.cfg file options. The options will have the same format as in netbird.cfg file and the inventory client process looks in the localopt.cfg file first. If the option is not set in that file it obtains it from the netbird.cfg. Therefore, you can overwrite any option set in netbird.cfg.
Collection Agent Startup Time To avoid having the collection running at the same time on each UNIX server, a collection startup time will be added to the configuration file localopt.cfg in the data folder. In this file, in the section [Agent] this option will be called StartupTime and will have a military time format (24 hours format). This option will use the local time of the UNIX station. For example: [Agent] StartupTime=0930
In the above example, the collection will not start before 9:30 A.M.
Collection Agent Priority An option in the localopt.cfg file allows the system administrator to change the collection process execution priority. This priority will be set in the [Agent] section and will be called Priority. Its value will be in the range of - 20 to 20. Negative values will cause more favorable scheduling (and less priority for other processes). The same priority will be applied to the agent and the collector. For example: [Agent] Priority =20
131
ASG-TrackBird Installation Guide
Installed Packages Detection (Solaris Only) You can filter the installed packages based on their installation date. If a section [Methodes] contains a key FilterPackageActive with a value 1, the installed packages will be filtered based on their installation date. If the key does not exist or has a 0 value, the installed packages are not filtered. Only newer packages than the date indicated will be collected using the key FilterPackageDate (indicated with the format DD/MM/YYYY like in the netbird.cfg file). Note:
If the FilterPackageDate key is empty, the system installation date is used as a reference. This filters out any packages installed the same day on the system. For example: [Methodes] FilterPackageActive =1 FilterPackageDate = Or [Methodes] FilterPackageActive =1 FilterPackageDate = 30/01/2004
132
7
Chapter 7:
Installing the SNMP Collector
Installation of SNMP Collector consists in the following two stages: •
Installing the SNMP Collector software
•
Configuring the SNMP Collector software before inventory collection
Both stages of installing the SNMP Collector are described below.
Installing the SNMP Client After installing TrackBird Server, an SNMP subgroup should display in your TrackBird Suite program group. If the subgroup does not exist complete the following procedure.
To install the SNMP client 1
Rerun the TrackBird installation and then select Custom installation
2
Deselect all options except the SNMP Collector installation and then executing the installation.
3
Run the Install SNMP Client file The Choose Setup Language dialog displays.
133
ASG-TrackBird Installation Guide
4
Select a language and then click OK. The License Agreement dialog displays.
5
Click Yes to accept the terms of the license agreement. The Choose Destination Location dialog displays.
6
134
Specify the directory in which you wish to install the Collector
7 Installing the SNMP Collector
7
Click Next The Select Program Folder dialog displays.
8
Select a Program Group, which may be the same as the TrackBird group.
9
Click Next to begin the SNMP client installation.
135
ASG-TrackBird Installation Guide
136
Index
A Administration console minimum requirements 14 AIX client 115 Alias Name field 30 Installing IIS 32 Alias Name field, TrackBird IP Server installation 30 Alias Name field, TrackBird IP Server installation (Apache Web server) 34 AUTOEXEC.BAT client launch file 90 B Browser.kb file 85 C ChangeServerPath parameter, NETBIRD.CFG 87 Client Installation Wizard Display Progress option 79 Distribution Point field 80 Edit Results option 79 Exclusion Ranges field 79 Folder field 81 Install Inventorist Interface option 81 Notify Users option 79 Recover Unknown Software option 79 Use Computer Name As Output File option 81 Client interface executable files 84 Client Workstation definition 4 CLIENTPATH parameter, NETBIRD.CFG 86 Collection Diskette Generator 72 Compact installation 18 Company field installing TrackBird Server 24 Component files, TrackBird clients 84 Configuration minimum requirements 13 Configuration file NETBIRD.CFG 85 Configuration, minimum required 13 conventions page vi Custom installation 18 customizing UNIX client configuration 130
D Data files, TrackBird clients 84 Database server minimum requirements 13 DB Express definition 19 Definitions Alias name 32 primary server 26 Secondary server 26 DELAIS parameter, NETBIRD.CFG 88 detecting installed packages (Solaris) 132 Display Progress option, Client Installation Wizard 79 Distribution Point field, Client Installation Wizard 80 DOS TrackBird client launch file 91 DOS executable files 83 downloading installer 8 E Edit Results option, Client Installation Wizard 79 error 404 IIS Version 6 41 error page 404 IIS Version 4 and 5 36 EXCLUDE parameter, NETBIRD.CFG 89 Exclusion Ranges field, Client Installation Wizard 79 Executable files client interface 84 DOS 83 OS/2 84 Windows 3.x 83 Windows 9x 83 Windows NT, 2000 and XP 83 Executable files, TrackBird clients 83 F Features TrackBird Gateway 7 TrackBird Inventory 5 TrackBird Monitoring 6 TrackBird Policy 7 137
ASG-TrackBird Installation Guide
TrackBird Reporting 6 TrackBird SNMP 5 Folder field, Client Installation Wizard 81 FOLLOWCOMPUTERNAME parameter, NETBIRD.CFG 87 FORCE_NO_INTERFACE parameter, NETBIRD.CFG 88 ForceRASConnection parameter, NETBIRD.CFG 87 FREQUENCE parameter, NETBIRD.CFG 88 G G_000121.kb file 85 Generating SQL Server database for TrackBird 50 GETFOLDERx parameter, NETBIRD.CFG 90 GROUPIP_NAME parameter, NETBIRD.CFG 86 H HP/UX client 119 HTTP Transfer definition 4 Hw.kb file 85 I IDPC parameter, NETBIRD.CFG 86 IIS Version 4 and 5 36 IIS Version 6 38 INCONNUS parameter, NETBIRD.CFG 90 Install Inventorist Interface option, Client Installation Wizard 81 install.bat file 82 Installation TrackBird Server 13 Installation Folder, TrackBird IP Server installation 25 Installation prerequisites inventory clients 69 Installation process 14 Installation program folder 20 Installation type Compact 18 Custom 18 Typical 18 Installing IIS Alias Name field 32 standalone TrackBird clients 71 TrackBird client from collection diskettes 73
138
TrackBird clients using the TrackBird Client Installation Wizard 74 TrackBird clients via a shared directory 77 TrackBird clients via a Web Server 74 TrackBird clients via IP using a login script 77 TrackBird clients via shared directory using a login script 82 TrackBird inventory clients 69 installing SNMP client 133 Installing IIS Web Site field 32 Installing PC collectors 67 Installing the TrackBird suite 13 Installing TrackBird IP Server Alias Name field 30 Alias Name field (Apache Web server) 34 Installation Folder 25 Port field 30 Port field (Apache Web server) 35 Server type 25 Web Site field (IIS Web server) 31 installing TrackBird IP server 23 Installing TrackBird IP Server, license agreement 24 Installing TrackBird Server Alias Name field 30 Parent Server’s IP Address field 30 Port field 30 INSTALLPDA 88 Intelligent Support Portal (ISP) 9 INTERFC parameter, NETBIRD.CFG 87 InterfProgramInterval parameter, NETBIRD.CFG 89 InterfProgramUnit parameter, NETBIRD.CFG 89 Internet browser using to install TrackBird clients 71 Inventory clients differences in collection procedure 68 installation prerequisites 69 K KEY parameter, NETBIRD.CFG 88 Knowledge base files 84 Browser.kb 85 G_000121.kb 85 G_000122.kb 85 Hw.kb 85 Logs.kb 85 Logs.kbx 85
Index
Logslinux.kb 85 Logsmac.kb 85 Modeles.kb 85 Rep.kb 85 Sysrep.kb 85 L LAST parameter, NETBIRD.CFG 85 LastInterf parameter, NETBIRD.CFG 86 LastLog parameter, NETBIRD.CFG 86 Launch files DOS client 91 OS/2 client 91 Windows 3.x client 91 LAUNCH parameter, NETBIRD.CFG 87 license agreement, TrackBird IP Server installation 24 Linux client 123 Login script using to install TrackBird clients via IP 77 using to install TrackBird clients via shared directory 82 LOGINVAR parameter, NETBIRD.CFG 90 Logs.kb file 85 Logs.kbx file 85 Logslinux.kb file 85 Logsmac.kb file 85 M Mac OS Classic deploying agents 103 installing TrackBird client 102 Macintosh clients prerequisites 93 Macintosh OS X client installation 94 Minimum required configuration 13 Modeles.kb file 85 N Name field installing TrackBird Server 24 nbinstip.bat file 77 NETBIRD.CFG file 85 NETBIRD.CFG parameters ChangeServerPath 87 CLIENTPATH 86 DELAIS 88 EXCLUDE 89 FOLLOWCOMPUTERNAME 87 FORCE_NO_INTERFACE 88 ForceRASConnection 87
FREQUENCE 88 GETFOLDERx 90 GROUPIP_NAME 86 IDPC 86 INCONNUS 90 INTERFC 87 InterfProgramInterval 89 InterfProgramUnit 89 KEY 88 LAST 85 LastInterf 86 LastLog 86 LAUNCH 87 LOGINVAR 90 ONLY_NEW 87 OUTPUTLONGNAME 85 OUTPUTNAME 85 OutputNamePrefixGroup 86 OutputNamePrefixPtColl 86 OutputNamePrefixServer 86 PRINT 87 PROGRAMINTERVAL 89 PROGRAMMODE 89 PROGRAMUNIT 89 PTCOLLIP_NAME 86 SERVERPATH 86 SetStationName 87 SETTARGETFOLDERx 90 SoftProgramInterval 89 SoftProgramUnit 89 USER 88 WARN 87 Notify User option, Client Installation Wizard 79 O ONLY_NEW parameter, NETBIRD.CFG 87 Operating System compatibility, PC collectors 67 OS/2 executable files 84 OUTPUTLONGNAME parameter, NETBIRD.CFG 85 OUTPUTNAME parameter, NETBIRD.CFG 85 OutputNamePrefixGroup parameter, NETBIRD.CFG 86 OutputNamePrefixPtColl parameter, NETBIRD.CFG 86 OutputNamePrefixServer parameter, NETBIRD.CFG 86
139
ASG-TrackBird Installation Guide
P Palm Desktop requirements 105 Parameters inventory clients 68 Parent server port 30 Parent server’s IP address 30 Parent Server’s IP Address field 30 PC collectors installing 67 operating principles 67 Operating System compatibility 67 PC inventory client parameter settings 68 Port 30 Port field 30 Port field, TrackBird IP Server installation 30 Port field, TrackBird IP Server installation (Apache Web server) 35 Primary Server definition 4 Primary server definition 26 Primary Server option button installing TrackBird Server 26 PRINT parameter, NETBIRD.CFG 87 PROGRAMINTERVAL parameter, NETBIRD.CFG 89 PROGRAMMODE parameter, NETBIRD.CFG 89 PROGRAMUNIT parameter, NETBIRD.CFG 89 PTCOLLIP_NAME parameter, NETBIRD.CFG 86 R Recover Unknown Software option, Client Installation Wizard 79 Registration TrackBird server 21 Registration program 21 Registry key (Windows 9x, NT, 2000, XP) 91 Rep.kb file 85 S Scripts nbinstip.bat 77 Secondary Server definition 4 Secondary server definition 26 Secondary Server option button
140
installing TrackBird Server 26 Serial Number field installing TrackBird Server 24 Server type, TrackBird IP Server installation 25 SERVERPATH parameter, NETBIRD.CFG 86 SetStationName parameter, NETBIRD.CFG 87 SETTARGETFOLDERx parameter, NETBIRD.CFG 90 Shared directory using to install TrackBird clients 77 SNMP Client definition 18 SNMP Collector 133 SoftProgramInterval parameter, NETBIRD.CFG 89 SoftProgramUnit parameter, NETBIRD.CFG 89 Solaris detecting installed packages 132 Solaris client 126 SQL Server and Oracle Database Creation Wizard 49 SQL Server and Oracle Database Creation Wizard, Step 1 (Oracle) 54 SQL Server and Oracle Database Creation Wizard, Step 1 (SQL Server) 50 SQL Server and Oracle Database Creation Wizard, Step 2 (Oracle) 55 SQL Server and Oracle Database Creation Wizard, Step 2 (SQL Server) 52 SQL Server and Oracle Database Creation Wizard, Step 3 (Oracle) 57 SQL Server and Oracle Database Creation Wizard, Step 3 (SQL Server) 53 SQL Server and Oracle Database Creation Wizard, Step 4 (Oracle) 58 SQL Server and Oracle Database Creation Wizard, Step 4 (SQL Server) 54 SQL Server database, generating for TrackBird 50 startup time UNIX server collection 131 STARTUP.CMD launch file 91 Step 1 SQL Server and Oracle Database Creation Wizard (Oracle) 54 SQL Server and Oracle Database Creation Wizard (SQL Server) 50 Step 2
Index
SQL Server and Oracle Database Creation Wizard (Oracle) 55 SQL Server and Oracle Database Creation Wizard (SQL Server) 52 Step 3 SQL Server and Oracle Database Creation Wizard (Oracle) 57 SQL Server and Oracle Database Creation Wizard (SQL Server) 53 Step 4 SQL Server and Oracle Database Creation Wizard (Oracle) 58 SQL Server and Oracle Database Creation Wizard (SQL Server) 54 Sysrep.kb file 85 T TrackBird features 5 TrackBird client Mac OS Classic 102 TrackBird Client Installation Wizard using to install TrackBird clients 74 TrackBird clients AUTOEXEC.BAT launch file 90 component files 84 data files 84 DOS launch file 91 executable files 83 installing 69 installing as a standalone tool 71 installing using an Internet browser 71 installing using TrackBird Explorer 70 knowledge base files 84 Windows 3.X client launch file 91 TrackBird databases definition 18 TrackBird Explorer using to install TrackBird clients 70 TrackBird Gateway features 7 TrackBird help files definition 18 TrackBird interface editor definition 18 TrackBird Inventory features 5 TrackBird IP Server installation user information 24
TrackBird Monitoring features 6 TrackBird Policy features 7 TrackBird program files definition 18 TrackBird Reporting features 6 TrackBird Server 3.0 update prerequisites 58 updating to 58 TrackBird Server installation 13 TrackBird Server registration 21 TrackBird SNMP features 5 TrackBird Software Distribution 7 Typical installation 18 U UNIX
configuring TrackBird client 130 Updating to TrackBird Server 3.0 58 TrackBird Server 3.0 prerequisites 58 Use Computer Name As Output File option, Client Installation Wizard 81 User information, TrackBird IP Server installation 24 USER parameter, NETBIRD.CFG 88 W WARN parameter, NETBIRD.CFG 87 Web Server using to install TrackBird clients 74 Web Server option buttons installing TrackBird Server 27 Web Service Extension adding 38 Web site definition 32 Web Site field, TrackBird IP Server installation (IIS Web server) 31 WebSSLActivated 88 WebSSLPort 88 WIN.INI system file 91 Windows 2000 executable files 83 Registry key 91 Windows 3.x client launch file 91 executable files 83 Windows 9x executable files 83
141
ASG-TrackBird Installation Guide
Registry key 91 Windows NT executable files 83 Registry key 91 Windows XP executable files 83 Registry key 91 Wizards definition 19 SQL Server and Oracle Database Creation 49
142
ASG Worldwide Headquarters Naples Florida USA | asg.com
CD Contents
