Administrators Guide

HP OpenView Desktop Administrator

Manufacturing Part Number: J4734-90000

October 1999

United States
© Copyright 1999 Hewlett-Packard Company
Legal Notices
Hewlett-Packard makes no warranty of any kind with regard to this
manual, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be held liable for errors contained herein or direct, indirect,
special, incidental or consequential damages in connection with the
furnishing, performance, or use of this material.
Warranty. A copy of the specific warranty terms applicable to your
Hewlett- Packard product and replacement parts can be obtained from
your local Sales and Service Office.
Restricted Rights Legend. All rights are reserved. No part of this
document may be photocopied, reproduced, or translated to another
language without the prior written consent of Hewlett-Packard
Company. The information contained in this document is subject to
change without notice.
Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013
for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the
Commercial Computer Software Restricted Rights clause at FAR 52.227-
19 for other agencies.
HEWLETT-PACKARD COMPANY
3404 E. Harmony Road
Fort Collins, CO 80525 U.S.A.
Use of this manual and flexible disk(s), tape cartridge(s), or CD-ROM(s)
supplied for this pack is restricted to this product only. Additional copies
of the programs may be made for security and back-up purposes only.
Resale of the programs in their present form or with alterations, is
expressly prohibited.
Copyright Notices. ©copyright 1983-99 Hewlett-Packard Company, all
rights reserved.
Reproduction, adaptation, or translation of this document without prior
written permission is prohibited, except as allowed under the copyright
laws.

2
Trademark Notices
OpenViewΠis a trademark of Hewlett-Packard Company.
NetWare® is a U.S. registered trademark of Novell, Inc.
Microsoft® is a U.S. registered trademark of Microsoft Corporation.
Windows NT® is a U.S. registered trademark of Microsoft Corporation.
Windows® and MS Windows® are U.S. registered trademarks of
Microsoft Corporation.
SOLID Embedded EngineΠis a trademark of Solid Information
Technology Ltd.
Other product names mentioned in this manual may be trademarks or
registered trademarks of their respective companies and are hereby
acknowledged.

3
4
 Contents

1. About DTA Administration

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
When should you use this guide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
How to obtain deployment training and assistance . . . . . . . . . . . . . . .15
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

2. Desktop Administrator overview

Year 2000 compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
What’s new in DTA 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Easy maintenance with the SmartDeploy agent . . . . . . . . . . . . . . . . .21
Industry-standard relational database support . . . . . . . . . . . . . . . . . .21
Snapshot software distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Application publishing and subscription capability . . . . . . . . . . . . . . .21
New Inventory category and field override. . . . . . . . . . . . . . . . . . . . . .22
Improved usability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
DTA architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Relational database support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Data replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
DTA applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Software Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Integration with other products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
HP OpenView Network Node Manager
for Windows NT25
HP OpenView IT/Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
HP OpenView Asset Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

5
 Contents

HP TopTools Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
pcANYWHERE (Symantec Corporation). . . . . . . . . . . . . . . . . . . . . . . 25

3. Resource requirements
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Network software requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Network protocol support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Database connection requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Microsoft SQL Server Client requirements . . . . . . . . . . . . . . . . . . . . . 30
Microsoft SQL Server preparation requirements . . . . . . . . . . . . . . . . 31
Component requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Storage requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Account requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
User authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Required accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Windows NT accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4. About DTA sites

Site components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Database support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Site trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Types of sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
DTA server function configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Data replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Transaction files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6
 Contents

5. Managing data
Displaying network information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Changing displayed data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Sorting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Querying data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Copying a field value from a viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Grouping information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Summarizing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Printing the contents of a viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Exporting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Exporting data to other file formats . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Exporting data using ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Working at another site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

6. Maintaining sites
Controlling replication activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Data scanning schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Transfer schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Transfer method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Modifying replication schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Controlling the order of data replication to multiple Satellite sites .106
Modifying and monitoring sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Changing the communication mode of a site . . . . . . . . . . . . . . . . . . .108
Revising site information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Specifying the correct NOS for the site server . . . . . . . . . . . . . . . . . .109
Specifying servers to be managed . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Specifying revised database server information. . . . . . . . . . . . . . . . .113
Changing the way DTA identifies the database server . . . . . . . . . . .114

7
 Contents

Viewing management server information. . . . . . . . . . . . . . . . . . . . . . . 117

Viewing site server location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Repositioning a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Merging DTA 5.0 site trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Merging trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Splitting a site tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Deleting sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Renewing expired DTA accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Launching a program remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Installing an additional Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Moving managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Adding an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

7. Managing the SmartDeploy agent

SmartDeploy agent features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
SmartDeploy agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Configuring the SmartDeploy agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
SmartDeploy agent configuration pages . . . . . . . . . . . . . . . . . . . . . . 142
Configuration page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Controlling managers and application agents . . . . . . . . . . . . . . . . . . . 149
Controlling agents on managed computers . . . . . . . . . . . . . . . . . . . . 149
Controlling managers and agents on the management server. . . . . 152
Setting schedules for the application agents . . . . . . . . . . . . . . . . . . . . 155
Setting schedules for DTA Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Switching the way SmartDeploy agent runs . . . . . . . . . . . . . . . . . . . . 163

8
 Contents

SmartDeploy agent problems and solutions . . . . . . . . . . . . . . . . . . . . .165

Installed program does not appear . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Fails to launch error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

8. Adding a site
Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Adding a child site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
Before adding a child site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Performing a remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Performing a CD installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Running the SmartDeploy agent wizard at Primary sites. . . . . . . . .192
SmartDeploy agent configuration at Satellite sites . . . . . . . . . . . . . .197
Setting up managed computers to launch agents . . . . . . . . . . . . . . . . .198
Login scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
User policy files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Windows NT Domain environments with Domain logins . . . . . . . . .199
Windows NT Domain environments with local logins . . . . . . . . . . . .200
Windows NT Workgroup environments . . . . . . . . . . . . . . . . . . . . . . .201
NetWare NDS and Bindery environments . . . . . . . . . . . . . . . . . . . . .201
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
Using the log file method to install the SmartDeploy agent
to selected computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
Using RSI to install the SmartDeploy agent to selected computers 204

A. Removing DTA
Removing agents from managed computers . . . . . . . . . . . . . . . . . . . . .215
Removing DTA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

9
 Contents

B. Command-line switches
Agent switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Manager switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

C. Tools and Utilities

APPIMPRT.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
DTACLEAN.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
DTACPI.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
NACCESS.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
OAREDIT.EXE (Object Address Resolution) . . . . . . . . . . . . . . . . . . . . 235
SDLDMP32.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
SERVCTRL.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
SOLCON.EXE (SOLID Remote Control) . . . . . . . . . . . . . . . . . . . . . . . 238
SOLSQL.EXE (SOLID SQL Editor) . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
TFILEAGE.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
TFILECHK.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
TFILEDMP.EXE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

D. SOLID database maintenance

Scheduling the backup of SOLID database files . . . . . . . . . . . . . . . . . 248
Scheduled backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Generic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Restoring backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Correcting a failed backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Database Support Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
When to use Database Support Installer. . . . . . . . . . . . . . . . . . . . . . 256

10
Contents

Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
Running the installer (DTA Database Support Installer) . . . . . . . . .257
OS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
Component Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
ODBC Manager 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
SOLID 3.0 Client (SOLID ODBC Driver) . . . . . . . . . . . . . . . . . . . . . .259
SOLID Server 3.0 (SOLID Embedded Engine DBMS). . . . . . . . . . . .259
Moving a SOLID database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
Deleting a SOLID database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263

11
Contents

12
1 About DTA Administration

13
 About DTA Administration
About this guide

About this guide

HP OpenView Desktop Administrator (DTA) 5.0 provides an integrated
set of desktop management applications to help you effectively manage
the workstations and servers in your environment. These applications let
you administer desktops across Windows NT and Novell NetWare
operating systems. You choose the DTA applications you need to perform
specific management tasks.
This guide provides information that enables system administrators to
manage data generated from the Inventory and Software Distribution
applications, maintain DTA sites and the bundled SOLID database,
manage the SmartDeploy agent, and add a child site to a DTA site tree.

When should you use this guide?

This guide assumes that DTA 5.0 sites have been installed and deployed
throughout your production environment. You use this guide to help you
administer and maintain the product after it has been rolled out to your
network by an HP approved implementation partner or someone in your
organization who has been trained on DTA deployment.

CAUTION Upgrading from DTA 4.x to 5.0 needs as much careful planning and
preparation as a new DTA 5.0 deployment. Because upgrading to DTA
5.0 requires database conversion, and could cause changes in site tree
design, site configurations, and system resources, do not attempt to
perform an upgrade without obtaining an HP approved implementation
partner or the information contained in the Deploying DTA Solutions
training course. See the section “How to obtain deployment training and
assistance” on page 15 for more information. Upgrading without the
proper information and training could result in data loss, agent conflicts,
and an overall decrease in productivity in your networking environment.

14 Chapter 1
 About DTA Administration
About this guide

Use this Administrators Guide in conjunction with the other guides

provided with DTA:

• Software Distribution Guide—Explains how to use the DTA Software

Distribution application. Includes information on configuring the
application, creating and distributing jobs, creating job actions, and
using the snapshot and subscription features. A print version of this
guide comes with the product and a PDF version is located in the
HPDTA\CONSOLE\DOCS directory of the CD.
• Inventory Guide—Describes how to use the DTA Inventory
application. Includes information on changing default settings, and
collecting hardware and software inventory data. A print version of
this guide comes with the product and a PDF version is located in the
HPDTA\CONSOLE\DOCS directory of the CD.
• HP Applications Integration Guide—Contains information and
instructions on how DTA integrates with other HP applications. A
PDF version of this guide is located in the
HPDTA\CONSOLE\DOCS directory of the CD.

How to obtain deployment training and assistance

For information on the three-day Deploying DTA Solutions course and
other DTA courses:
• Visit the HP Education Center web site,
http://www.education.hp.com
• In the U.S., call 1-800-472-5277 (1-800-HP-CLASS)
• In Canada, call 1-800-563-5089.
A list of HP approved implementation partners is available on the HP
OpenView web site at:
http://www.openview.hp.com/products/dta/partners

Chapter 1 15
About DTA Administration
About this guide

Chapter overview
A brief description of each chapter in this guide is provided below.

Chapter 2: Desktop Administrator overview

Contains an overview of what’s new in DTA 5.0, and summaries of each
of the components and applications of DTA, including integrated
applications.

Chapter 3: Resource requirements

Lists system and account requirements for DTA.

Chapter 4: About DTA sites

Introduces the concept of single sites, site trees, and site hierarchies.
Also describes the available DTA directory structure configurations for
server hardware at a site, and basic data replication operations within
and between sites.

Chapter 5: Managing data

Includes information and instructions on working with data from the
Console, including displaying, querying, grouping, and exporting data, as
well as scoping to other sites.

Chapter 6: Maintaining sites

Provides various site maintenance information and configuration
procedures that may be required post-installation. These procedures
include changing replication schedules, identifying servers for software
distribution or inventory, modifying sites, merging site trees, splitting
site trees, and installing additional Consoles.

Chapter 7: Managing the SmartDeploy agent

Includes post-installation configuration instructions for the
SmartDeploy agent, including scheduling. Also includes instructions for
stopping, starting, and removing the agents and managers.

Chapter 8: Adding a site

Includes instructions for adding a child Primary or Satellite site by
remote or CD installation methods.

16 Chapter 1
 About DTA Administration
About this guide

Appendix A: Removing Desktop Administrator

Provides instructions for removing Desktop Administrator agents and
software.

Appendix B: Command-line switches

Lists command-line switches for the SmartDeploy agent and application
agents.

Appendix C: Tools and utilities

Lists the tools and utilities available with DTA.

Appendix D: SOLID database maintenance

Provides instructions on backing up, restoring, and maintaining the
bundled SOLID database.

Chapter 1 17
 About DTA Administration
Contact Information

Contact Information
Technical Support Technical support information can be found on the HP OpenView World
Wide Web site at:
http://www.hp.com/openview/support.html
________________________________

Documentation Your comments on and suggestions for the documentation help us

Feedback understand your needs and better meet them.
You can provide feedback about documentation via the HP
documentation site at:
http://ovweb.external.hp.com/lpe/doc_serv
Or you can email comments to: ovdoc@fc.hp.com
________________________________

Training For information on current HP OpenView training available, see the HP

Information OpenView World Wide Web site at:
http://openview.hp.com
Follow the links for Training to obtain information about scheduled
classes, training at customer sites, and class registration.

18 Chapter 1
2 Desktop Administrator
overview

19
Desktop Administrator overview
Year 2000 compliance

Year 2000 compliance

Desktop Administrator 5.0 is year 2000 compliant, as defined by the
Hewlett-Packard Standard for Compliance.
As defined by the Standard, a “Compliant” product accurately processes
date data (including, but not limited to: calculating, comparing, and
sequencing dates), from, into, and between the twentieth and
twenty-first centuries, the years 1999 and 2000, and leap year
calculations, when used in accordance with its product documentation,
and provided all other products used in combination with the product
properly exchange data with it.
Your underlying hardware and OS software must be year 2000 compliant
for Desktop Admnistrator to operate in accordance with this Standard.

20 Chapter 2
 Desktop Administrator overview
What’s new in DTA 5.0

What’s new in DTA 5.0

DTA 5.0 comes with a host of improvements and new features that are
described below.

Easy maintenance with the SmartDeploy agent

SmartDeploy agent technology makes DTA installation and maintenance
simpler, easier, and more reliable. The agent schedules, controls, and
upgrades all other DTA agents, and can be configured to reduce network
impact. A SmartDeploy wizard provides easy-to-follow steps to guide you
though the agent installation process.

Industry-standard relational database support

DTA supports existing Microsoft SQL Server 6.5 (SP5) and 7.0
installations and ships with a bundled version of SOLID Embedded
Engine 3.0 for Windows NT.

Snapshot software distribution

DTA Snapshot technology provides administrators with a quick and
simple way to install complex applications. Snapshot lets you capture
modifications you make to a “reference” computer and create a script file
of the actions associated with those modifications. You can then use the
script file to create a distribution job that installs an application on a
recipient computer. See the Software Distribution Guide for details.

Application publishing and subscription capability

Using the model of a publisher-subscriber relationship, DTA subscription
services lets administrators make applications and data files available to
the user community, allowing those users to customize their individual
desktop environments. See the Software Distribution Guide for details.

Chapter 2 21
Desktop Administrator overview
What’s new in DTA 5.0

New Inventory category and field override

The Inventory application now lets you override any existing fields
scanned by Inventory with your own custom fields. The Inventory
application also includes a new inventory category, Network Adapters.
See the Inventory Guide for details.

Improved usability
Setup and Remote Install wizards are more intuitive and easier to use.
The Remote Install wizard now incorporates DTA manager installation.

22 Chapter 2
 Desktop Administrator overview
DTA architecture

DTA architecture
DTA provides a common architecture that the applications use to work
together. This architecture include elements described below.

Console
From a single location, lets you perform tasks and view information that
DTA generates about your managed desktops. You can also use the
Console to configure various parts of DTA, such as the SmartDeploy
agent and DTA applications.

Communications
Provides network access and reliable data transfer over Microsoft
Windows and Novell NetWare operating systems and protocols.

Relational database support

Provides ODBC support for industry standard relational database
management systems including MicroSoft SQL Server. Ships with a
bundled version of SOLID 3.0 Embedded Engine.

Data replication
Replicates desktop management information from site to site according
to schedules you set.

Chapter 2 23
Desktop Administrator overview
DTA applications

DTA applications
DTA includes applications that collect data and perform administrative
tasks on the computers in your network.

Inventory
Performs hardware and software inventories of PC computers on your
network.

Software Distribution
Installs software and updates configuration or other files on PC
computers.
The DTA CD contains online guides that explain how to configure and
use these applications. The PDF versions of these guides are located in
the HPDTA\CONSOLE\DOCS directory.

24 Chapter 2
 Desktop Administrator overview
Integration with other products

Integration with other products

DTA can work with several other products available from
Hewlett-Packard. You can find integration information and instructions
for the HP products in the HP Applications Integration Guide. A PDF
version of this guide is located in the HPDTA\CONSOLE\DOCS
directory.

HP OpenView Network Node Manager

for Windows NT
DTA provides an integration component for Network Node Manager for
Windows NT (NNMNT) 6.0 that lets you launch DTA from NNM and lets
you access NNM from the DTA Console.

HP OpenView IT/Operations
DTA (on Windows NT 4.0) integrates with IT/Operation 4.x and 5.x. To
use these management applications together, you install, configure, and
customize the DTA/ITO Integration package. The package includes ITO
Integration templates.

HP OpenView Asset Manager

DTA includes a program that lets you export the DTA hardware and
software inventory records from the DTA database to a format you can
import into ITSM Asset Manager 5.6.

HP TopTools Web
DTA integrates with TopTools Web 4.1 to provide more information on
DMI or SNMP compliant computers.

pcANYWHERE (Symantec Corporation)

DTA provides a remote control solution with Symantec pcANYWHERE
9.0 for HP OpenView Desktop Administrator to allow you to control a PC
from the Console over a network connection. A version of DTA with
pcANYWHERE bundled on the CD is available from Hewlett-Packard.

Chapter 2 25
Desktop Administrator overview
Integration with other products

26 Chapter 2
3 Resource requirements

27
 Resource requirements
System requirements

System requirements
This section lists the types of network and communication software that
are supported by DTA. It also details the minimum hardware and
software requirements.

NOTE DTA site architecture and usage model will determine exact server and
client memory and disk requirements.
All Operating Systems and Network Operating Systems must include all
Year 2000 updates from the original vendor.

Network software requirements

DTA runs on Microsoft Windows NT and Novell NetWare networks. You
can use existing users, groups, and domains with DTA applications for
any part of your environment.
At Primary sites, DTA must run under one of the following network
operating systems:

• Microsoft Windows NT Server 4.0 (SP4 or SP5)

• Novell NetWare 4.11 or 4.2 in both NDS and bindery mode (IPX
compatibility mode).
• Novell NetWare 5.0 in both IP/IPX and bindery mode (IPX and IP
compatibility mode).
At Satellite sites, DTA can support any file server running the following
network operating systems:

• Microsoft Windows NT Server 3.51 (SP5)

• Microsoft Windows NT Server 4.0 (SP4 or SP5)
• Novell NetWare 3.2 (bindery mode)
• Novell NetWare 4.11 or 4.2 in both NDS and bindery mode (IPX
compatibility mode).
• Novell NetWare 5.0 in both IP/IPX and bindery mode (IPX and IP
compatibility mode).

28 Chapter 3
 Resource requirements
System requirements

Network protocol support

For communications between agents and managers, DTA supports the
following network protocols:
• TCP/IP
• IPX/SPX.
For replicating and moving data between sites, DTA supports the
following network protocols:
• Direct mapping (uses the underlying network protocol)
• TCP/IP
• FTP.
For communications between managers and supported relational
databases, DTA supports the TCP/IP network protocol.
Some databases do not support TCP/IP. See the “Database connection
requirements” below for more information.

Connection speed requirement

The minimum connection speed DTA must have to connect to managed
computers or remote sites is 56 kbps (kilobits per second).

Database connection requirements

DTA managers can access the following databases under the indicated
protocols:

• SOLID Embedded Engine 3.0 (Windows NT 4.0): TCP/IP

• Microsoft SQL Server 6.5 (SP5): TCP/IP
• Microsoft SQL Server 7.0 (Windows NT only): TCP/IP
You can store your relational database on the same server as other DTA
software or on a separate server. In Windows NT network environments,
DTA is set by default to connect to the database by using the computer
name of the server where the database resides. However, you can also
configure DTA to connect to the database through the static server IP
address instead.

Chapter 3 29
Resource requirements
System requirements

For best performance, DTA recommends that your database

management system (DBMS) reside on the same server as DTA, or at
least the same server as the \MANAGERS subdirectory, which is where
the DTA managers reside. For more information on where DTA directory
structures can be installed, see “DTA server function configurations” on
page 53.

ODBC requirements
To connect to existing relational databases or to install the bundled
SOLID 3.0 database, DTA requires that the server where the database
resides run ODBC manager version 3.5 or higher.
If you run DTA Setup without any ODBC manager, Setup automatically
installs the 3.5 version. If you have an outdated OBDC manager
installed, DTA installation will fail unless you first update your ODBC
manager. For information on installing or upgrading ODBC manager to
version 3.5, see “Database Support Installer” on page 255.
Depending on the database you are using, the following drivers must also
be installed and set up on the server where your database resides:

• SOLID 3.0 for NT ODBC driver (installed by DTA)

• Microsoft SQL Server 6.5 ODBC driver+9
• Microsoft SQL Server 7. 0 ODBC driver

Microsoft SQL Server Client requirements

If you use DTA with Microsoft SQL Server, you must install the
Microsoft SQL Server ODBC driver for version 3.7 on the management
server and on any computer on which the Console runs.
The Microsoft SQL Server ODBC driver for version 3.7 is included in the
SQL Server 7.0 and Server 6.5 (SP5) DBMS Software.

30 Chapter 3
 Resource requirements
System requirements

Microsoft SQL Server preparation requirements

If you are planning to use Microsoft SQL Server 6.5 or 7.0 with DTA, you
must first prepare the DBMS before running DTA Setup.

Microsoft SQL Server 6.5

Before starting the DTA Setup program make sure you have done the
following:

• Upgraded Microsoft SQL Server to SP5 or later

• Set up a separate data device (recommended but not required). The
initial size depends on how many initial nodes you plan to support
and how much inventory you intend to gather.
• Set up a database on the device.
• If two or more DTA sites share the same SQL Server 6.5 DBMS,
created a new account with SQL Server authentication. DTA does not
support Windows NT authentication. This account (newly created in
most cases) must use a database that is designated only for the DTA
site being installed. (A new account points to MASTER by default)
The account must also be made the DBO (database owner) to ensure
the corrrect read/write permissions.
• Tested the new acccount with ISQL_W tool (or equivalent tool),
located in the SQL Server 6.5 program group.
The account you set up is your DBMS account. You will specify it during
site installation in the DTA Setup program’s Database User Access
Account panel.

Chapter 3 31
Resource requirements
System requirements

Microsoft SQL Server 7.0

Before starting the DTA Setup program, make sure you have done the
following:
• Set up a new database for each planned DTA site. You can use the
same Microsoft SQL Server DBMS.
• If two or more DTA sites share the same SQL Server 7.0 DBMS,
created a new account with SQL Server authentication. DTA does not
support Windows NT authentification. This account (newly created in
most cases) must use a database that is designated only for the DTA
site being installed. (A new account points to MASTER by default.)
The account must also be made the DBO (database owner) to ensure
the correct read/write permissions.
• Tested the new account with the Query Analyzer tool (or equivalent
tool), located in the SQL Server 7.0 program group.
The account you set up is your DBMS account. You will specify it during
site installation in the DTA Setup program’s Database User Access
Account panel.

Component requirements
The computers that run DTA components must meet certain minimum
hardware requirements. These requirements are described in the
following sections.
In general, the specifications below allow you to run DTA and the
computer OS, with some computer usage left over for other applications
and processes. Nevertheless, you should take into account the memory
requirements of all the applications you plan to run on the system, as
many require considerable memory and may not run well with DTA
unless you add more memory.

Install computer requirements

Ideally, you should run DTA Setup from the DTA management server,
that is, on the server on which you plan to store the DTA managers.
(When you run DTA Setup, the program assumes the computer it is
running on is the management server, unless you specify otherwise.)

32 Chapter 3
 Resource requirements
System requirements

If you cannot install DTA from the management server, a good

alternative is the DTA site server (the server that stores the \AGENTS,
\CONSOLE, and \DATA directories). If neither the management server
or site server are possible, then run DTA Setup from a computer that has
the following installed on it:

• Microsoft Windows NT 4.0 (SP4 or higher)

• CD-ROM drive
• 10 MB free disk space
• 64MB RAM.

Console minimum requirements

A computer running the Console must meet the following minimum
requirements:

• Windows NT 4.0 (SP4 or higher)

• 64 MB of RAM without managers (with managers, see “Management
server minimum requirements” on page 34); for Consoles where
Software Distribution snapshot files are created, 128 MB of RAM
• Pentium II class CPU recommended.
Typically, you run the Console from the management server. By default,
DTA installs the Console there. However, you can also install and run
the Console on any NT 4.0 (SP4 or higher) managed computer. For
instructions on installing a Console to another NT 4.0 computer, see
“Installing an additional Console” on page 132.

Chapter 3 33
 Resource requirements
System requirements

SIF file import requirements

Table 3-1 lists the minimum RAM requirements which apply if you
import snapshot information files (SIF).
Table 3-1 Minimum requirements for SIF file import

RAM Number of install Number of uninstall

actions in a SIF job actions in a SIF job

64 MB 16000 16000

128 MB 24000 24000

256 MB 24000 24000

Page file size should be double the memory size.

For more information on SIF file size see the Software Distribution
Guide.

Management server minimum requirements

The computer on which you install the managers is called the
management server. Where possible, DTA recommends that you use the
management server as the install computer
If your management server is installed in a centralized configuration,
that is, if all DTA server functions (database, site, and manager) are
installed on the same server, then the following minimum requirements
apply for that server:

• Microsoft Windows NT Server (SP4 or SP5)

• Server-class 266 MHz Pentium II or faster processor
• CD-ROM drive
• 8 GB or greater disk space (based on usage)
• 256 MB RAM for bundled SOLID database (384 MB recommended)
• 384 MB RAM for MS SQL Server 7.0 (512 MB RAM recommended
with 192 MB allocated for SQL Server 7.0).

34 Chapter 3
 Resource requirements
System requirements

For other configurations, the following minimum requirements apply:

• Microsoft Windows NT Server 4.0 (SP4 or SP5)

• Server-class 266 MHz Pentium II or faster processor
• CD-ROM drive
• 8GB or greater disk space (based on usage)
• For 500 nodes or less, 256 MB RAM
• For 500 or more nodes, 512 MB RAM.
All requirements are based on the following assumptions:

• All DTA applications are installed, using about 80 MB of disk space

• The management server is dedicated to DTA only
• Software Distribution jobs run a few times a week
• Inventory frequency: 500 transaction files per week; 2,500 inventory
records per 24-hour period
• Inventory transaction file size: .AOT is 70 KB or less; .INT is 12 KB
or less.

Netware environments If you use NetWare as your network

operating system, the Novell 4.6 Client software must be installed on the
management server.

Chapter 3 35
 Resource requirements
System requirements

Agent requirements
Agents can run on workstations with a range of hardware and operating
systems. Table 3-2 identifies general system requirements for PC-based
agents.
Table 3-2 Agent system requirements

Agent Operating systems Memory

Inventory Windows 9.x 16 MB

Windows NT 4.0 32 MB
Windows 2000 Professional 48 MB

Software Distribution Windows 9.x 16 MB

Windows NT 4.0 32 MB
Windows 2000 Professional 48 MB

SmartDeploy Windows 9.x 16 MB

Windows NT 4.0 64 MB
Windows 2000 Professional 48 MB

Managed computer requirements

DTA can manage workstations that run Microsoft Windows 9x, NT 4.0,
or 2000 Professional operating software.
Managed computers running Microsoft Windows 95 software must have
either SP1or OSR2 installed on them.

NetWare environments If you use NetWare as your network

operating system, the following NetWare client software must be
installed on each managed computer:

• Novell 3.1 Client or Microsoft Windows 9x

• Novell 4.6 Client for Microsoft Windows NT 4.0
• Novell 4.7 Client for Microsoft Windows 2000 Professional (Beta
version. For updates to the 4.7 Client, see the Novell website.)

36 Chapter 3
 Resource requirements
System requirements

Storage requirements
The amount of disk space required to store DTA components varies,
depending on the applications you install. Table 3-3 lists the amount of
disk space required to store each DTA component or application before
you begin populating the database.
Table 3-3 Storage Requirements

Component Required disk space (in MB)

Core files 16 MB

Inventory 2 MB

Software Distribution 3 MB

Online Documentation 17 MB

For each site you install, DTA creates four directories in which to store
components and data. In addition, the management server has a
\MANAGERS directory, and each managed computer has an \HPDTA
directory (if you don’t change the default share).

Primary and Satellite site disk space requirements

At a Primary site, the file server you use as the site server must have at
least 105 MB of disk space for DTA directory storage. (This number will
change as you use DTA.)
At a Satellite site, the site server must have at least 30 MB of disk space
for DTA directory storage.
The amount of disk space required to store databases varies, depending
on your DBMS, the size and scope of your site tree, the number and type
of applications you install, and the amount and type of data you want to
store. See Chapter 4, “About DTA sites,” on page 43 for more information
about estimating database size.

Chapter 3 37
 Resource requirements
System requirements

Table 3-4 lists the disk space required for each directory.
Table 3-4 Directory space requirements

Directory Space required (in MB)

HPDTA\AGENTS 8 MB

HPDTA\CONSOLE 89 MB
HPDTA\DATA* 1 MB

HPDTA\DATA with pcANYWHERE* 17 mb

HPDTA\MANAGERS (management 16.1 MB

server)

HPDTA\AGENTS on each managed 8 MB

computer*

\SOLID* 6 MB

* As data records are created and transferred, these directories will

fluctuate in size significantly. Therefore, the specifications in the table
above refer only to newly installed directories.

38 Chapter 3
 Resource requirements
Account requirements

Account requirements
Besides the hardware and software requirements described above, there
are other aspects of your network environment that you should consider
when you use DTA.

User authentication
Be sure that you identify the personnel who understand and control user
authentication for your company’s network environment. It is best to
have at least one team member who:

• Understands the current network security scheme

• Has the ability to write and modify login scripts or policy files for your
networked computers.
Be aware that the DBMS accounts you set up automatically grant write
access to the database DTA uses.
There is also a read-only account that is automatically created during
DTA Setup. The read-only account has the following user name and
password.
User name: DTAUSER
Password: HPDTA
This account provides read-only access to the SOLID database.

Required accounts
DTA requires a number of database, Windows NT, and if necessary,
Novell NetWare accounts at each DTA installation (site). It requires
them so it can install and access various server directories across your
networking environment.These accounts are set up before the first DTA
site is installed.
In general, you can use a Domain Administrator account for any
Windows NT accounts that DTA requires. In Windows NT Workgroup
environments where servers and managed computers are not part of a
Windows NT domain, you can use a local administrator account.

Chapter 3 39
Resource requirements
Account requirements

In environments where your site server runs NetWare 4.x or 5.x, you can
typically use an admin account or an account that has security equal to
one. For NetWare 3.x servers, the account must be a supervisor account
or have security equivalent to one.
The accounts are described below.

Logon account (Windows NT)

The account you use to log onto the install computer when you perform
DTA Setup. This account provides access to the management server and,
if you are installing the bundled version of SOLID 3.0 for Windows NT,
the database server too.
The account of the user who is currently logged onto the management
server or database server must have administrative rights to those
servers.
Although DTA does not prompt you for this account, if it is not set up or
does not have administrative rights, the DTA Setup program will fail.
You can use either the Domain Administrator account (if the
management server or database server is part of a domain) or a local
administrative account for the servers.
The current logged-on user account is required only at Primary sites.

DTA site server account (Windows NT or NetWare)

This account provides access to the DTA site server where the various
DTA files are stored in the \CONSOLE, \AGENTS, and \DATA
directories.
If your site server runs NetWare, this account is the same as your
NetWare account. If your site server runs Windows NT Server, this
account can be either the Domain Administrator account (if it’s part of a
domain) or a local administrative account for the server.
You are prompted for this account in DTA Setup or when you add a site
in the Smart Deploy agent wizard.
The DTA site server account is required at both Primary and Satellite
sites.

40 Chapter 3
 Resource requirements
Account requirements

DBMS user account (Database)

This account lets DTA access your database management system. The
DTA managers and Console require it to access your database server.
If you are installing the bundled version of SOLID 3.0 for Windows NT,
DTA creates this account for you. For existing databases, you must
supply the existing database account for your DBMS.
You are prompted for this account in DTA Setup and when you add a
site.
The DBMS user account is required only at Primary sites.

NOTE For Microsoft SQL Server, supply the SQL Server database user account
(SQL Server authentication).

Managers account (Windows NT)

This account is the NT System Service account for the DTA managers. It
allows DTA managers, which are NT System Services, to run on the
management server.
The Managers account requires all privileges that are necessary to run
an NT System Service. You can use either the Domain Administrator
account (if the management server is part of a domain) or a local
administrative account for the management server.

NOTE If you plan to deploy the SmartDeploy agents to specific, targeted

workstations (rather than globally, to all workstations), then the user
name and password that you use for the Managers account must be for a
Domain Administrator. If you use a local administrator user name and
password for the Managers account, DTA will not be able to deploy the
SmartDeploy agent to those targeted computers.

DTA prompts you for the managers account during DTA Setup or when
you add a site.
The Managers account is required only at Primary sites.

Chapter 3 41
Resource requirements
Account requirements

SmartDeploy agent account (Windows NT)

This account is required only if you configure the SmartDeploy agent to
run as an NT System Service from the local disk of managed computers.
The account provides access to managed computers. If the managed
computers belong to an NT domain, you can use a Domain Administrator
account. However, if the managed computers belong to an NT Workgroup
environment, you must use a local administrative account.
If you do use a local administrative account, you must make sure that all
managed computers have one common user ID and password assigned to
them. The SmartDeploy agent will not be able to run from the local disk
of managed computers unless those computers have been synchronized
with a common user ID and password.
DTA prompts you for the SmartDeploy agent account during Smart
Deploy agent configuration, which you access either through the
SmartDeploy wizard or the Console.
The SmartDeploy agent account is required at both Primary and
Satellite sites.

Windows NT accounts
As long as you follow the guidelines described under each account above,
you can use a combination of user names and passwords to deploy DTA.
For example, you can use a local administrative user name and password
to install a DTA site and then use a Domain adminisrator user name and
password to install the SmartDeploy agent.

42 Chapter 3
4 About DTA sites

43
About DTA sites
Site components

Site components
This section describes the different DTA components that work together
in a site.

Console
The Console provides an integrated interface from which you can:

• Configure the SmartDeploy agent or run the SmartDeploy agent

wizard
• Perform administrative tasks on computers in each site, for example,
create distribution jobs or perform inventories
• View and print the data the applications generate
• Configure how applications run
• Configure and install sites.
You run the Console on the computer on which it is stored, or from the
network. The computer storing or running the Console must run
Windows NT 4.0 (SP4 or higher) software. DTA installs the Console to
the management server by default, although you can use a Console
installation program to install and run it on another computer. See
“Installing an additional Console” on page 132 for more information on
the Console install program.

Database support
DTA supports MS SQL Server 6.5 (SP5)and 7.0. It ships with SOLID 3.0
for Windows NT.
These databases contain DTA tables, or data records, that store
information about the particular DTA application or component that
generates them.

44 Chapter 4
 About DTA sites
Site components

For example, the Inventory application stores information in various

tables about the computer hardware and software in your network. The
Software Distribution application uses particular tables to store
distribution jobs and historical logs about the jobs. Configuration and
installation information about sites are stored in other tables. DTA also
provides known software applications and vendors in an applications
table and a vendors table, respectively.
For the MS SQL Server DBMS, DTA builds the required DTA tables in
an MS SQL database during DTA installation. You must have already
created and set up the MS SQL database prior to installing DTA,
otherwise the DTA tables will not install.
For the bundled version of SOLID 3.0, DTA builds the required DTA
tables during install to a single SOLID database. (It is not recommended
that this database be used for any application other than DTA.)

Managers
Managers are installed and run on computer running Windows NT 4.0
Server (SP4 or higher) software. See Chapter 3, “Resource
requirements,” on page 27 for other specific requirements.
The computer on which DTA installs the managers is called the
management server (formerly called the management computer in DTA
4.x). DTA installs the managers in a \MANAGERS subdirectory under
the \HPDTA directory (\HPDTA\MANAGERS). The term management
server refers to a this set of files, which handle the management
functions of DTA. Therefore, a management server does not necessarily
have to be a separate piece of server hardware. Depending on the server
hardware configuration at a site, it can be the same computer as the one
on which the other DTA components are installed, or it can be a separate
computer within the site. See “DTA server function configurations” on
page 53 for more information.
The DTA managers and their functions are described below.
Site manager
Inserts data generated by agents to the database and replicates data
between sites. It sends any events it generates to the Windows NT Event
Viewer.

Chapter 4 45
About DTA sites
Site components

DTA manager
Using a Winsock connection, DTA manager sends jobs to targeted
workstations by way of Software Distribution agents. It receives requests
from Software Distribution agents for jobs, reads the database for them,
and delivers those jobs to the agents running on the workstations. The
agents then run the jobs.
For more information on the DTA manager, see the Software Distribution
Guide.

Running managers
Because managers run as NT System Services, they can run on servers
even when an end-user is not logged onto the network.
Both Site manager and DTA manager are controlled by the SmartDeploy
agent. The SmartDeploy agent can start, stop, schedule, upgrade, and
remove the managers, according to your instructions.
DTA installs both managers to the same management server. You cannot
install one manager on one server and the other elsewhere. Also, you can
only install one instance of DTA manager and Site manager.

Agents
Agents run on workstations to perform tasks and gather data. The
agents and their functions are described below.
Smart Deploy agent
Installs the DTA Inventory and Software Distribution agents during
DTA Setup. Can also schedule, remove, update, start, and stop both
managers and agents.
Inventory agents
Collect hardware and software information from computers.
Software Distribution agents
Check for pending distribution jobs and execute them on targeted
managed computers.

46 Chapter 4
 About DTA sites
Site components

Server Distribution agent

(Formerly the Server Distribution manager in DTA 4.x.). Receives
distribution jobs and executes them on targeted servers. The Server
Distribution agent is stored and runs from the management server. See
the Software Distribution Guide for more information on the types of jobs
you can distribute to servers using this agent.
Server Inventory agent
(Formerly the Server Inventory manager in DTA 4.x.). Gathers software
information about servers, volumes, and network shares. The Server
Inventory agent is stored and runs from the management server. See the
Inventory Guide for more information on the types of inventory scans
this agent can perform on servers.

Storing and running agents

You configure how and where agents run through the SmartDeploy
agent, which controls the other DTA agents. DTA provides a
configuration wizard for the SmartDeploy agent during installation.
After installation (and if necessary), you can change the agent
configuration or schedule through the Console. See Chapter 7,
“Managing the SmartDeploy agent,” on page 139 for more information on
configuring the SmartDeploy agent.
By default, DTA stores and runs the agents on workstations, but you can
also store and run them from the server.
Storing the agents on workstations reduces login time and network
traffic. It also reduces the opportunity for problems such as packet loss to
occur.
You may also want to store an agent on workstations if you want
workstations to have the functionality the agent provides, even when the
network is down. For example, if you want to continue taking inventory
on the applications run by end-users when the server is unavailable, you
can store the SmartDeploy agent on workstations.
If you choose to run agents on the local disks of workstations, you also
have the option of running them as NT System Services on any
workstations running Windows NT. Agents running as NT System
Services assume the same access rights as the account used for login by
the NT System Service. Services may therefore have control over certain
operations on NT workstations that otherwise may not be available when
the agents run as executable applications. Also, end-users do not have to
be logged onto their workstations for the agents to work.

Chapter 4 47
 About DTA sites
Site components

Be aware, however, that because NT System Services run perpetually,

there will be times when no user is logged on, making it impossible for
the Service to send messages to the currently logged off user.

NOTE In cases where agents are running as Services, Software Distribution has
a job-level flag to indicate if the user must be logged on for the job to
work. In such cases, the job will wait until a valid user has logged onto
the workstation. However, if you are running Inventory as a Service and
you specify user prompts, the inventory scan will suspend indefinitely if
no user is logged onto the computer.

Following is a list of the ways the SmartDeploy agent sets up the agents
to run:

• Windows 9x—Adds agents to the registry Run key.

• Windows NT 4.0—Adds agents to the registry Run key, or installs
them as NT System Services. Installing agents as NT System
Services allows agents to run regardless of whether end-users have
logged their computers onto the network.
• Windows 2000 Professional—Adds agents to the registry Run key, or
installs them as NT System Services. Installing agents as NT System
Services allows agents to run regardless of whether end-users have
logged their computers onto the network.

How DTA installs the SmartDeploy agent

After the SmartDeploy agent wizard guides you through selecting the
installation and running options for the SmartDeploy agent, the
SmartDeploy agent takes care of installing all other DTA agents.
Initially, DTA installs the SmartDeploy agent executable, SAGENT.EXE,
to the site server \\HPDTA\AGENTS directory, along with the
SmartDeploy agent configuration file, SAGENT.INI, and other DTA
agent files. The configuration file contains the installation and running
options you specified in the wizard. Among the options you configure is
the location of the SmartDeploy agent. You can store and run it from the
site server, or locally, on each managed computer at the site.

48 Chapter 4
 About DTA sites
Site components

When you modify the login scripts or policy files of workstations to

include the path to the SmartDeploy agent executable, they become DTA
managed computers. They can be managed by DTA because they now
have the pathname to the SmartDeploy agent and therefore can launch
it.
The first time an end-user logs a managed computer onto the network,
the computer uses the site server pathname to the SmartDeploy agent to
launch and run it. Once the SmartDeploy agent runs, however, it reads
its configuration file for your wizard instructions. If you have chosen the
default setting to store and run the SmartDeploy agent from the local
hard disks of computers, the SmartDeploy agent will copy itself to the
Windows install directory (for example, C:\WINDOWS) of every
managed computer when the end-user logs in. After it installs to the
local hard disk of the computers, it copies the contents of the site server
\HPDTA\AGENTS directory to local hard disks of each managed
computer at the site, launches itself, and ceases running from the site
server.
Each managed computer then has a copy of the SmartDeploy agent
executable file, its configuration file, and the other agent files.
The next time the end-user logs the computer onto the network, the
computer uses the local pathname to the SmartDeploy agent executable
to launch it and the other application agents.
For every logon thereafter, the SmartDeploy agent, whether stored on
the site server or on the hard disks of managed computers, reads its local
configuration file for new configuration and running instructions and
carries them out. You can set how often the SmartDeploy agent polls for
new instructions through the Console. For more information, see
Chapter 7, “Managing the SmartDeploy agent,” on page 139.

Chapter 4 49
About DTA sites
Site trees

Site trees
You can implement DTA as a series of sites arranged in a configuration
called a site tree. A site tree contains sites placed in a logical hierarchy,
with a central site at the top. A site tree provides added control over your
network by letting you view data from different locations in the site tree
and perform tasks on specific parts of the network.

Types of sites
Since not all parts of your network require the same level of
administration, DTA provides two types of sites you can specify.
Primary site
Every implementation must have at least one Primary site, which
includes the Console, DBMS, managers, and agents. Each Primary site
must have a site server, on which DTA applications and other
components run, and a management server, on which the managers are
installed. Managers process data for the computers within the site. It
also must have a database server, on which the DBMS is installed.
Site servers, management servers, and database servers represent
functions of DTA rather than actual pieces of hardware. Therefore, they
can physically reside on a single server, or on three separate servers, or
in several different configurations on two servers. Available
configurations are discussed in “DTA server function configurations” on
page 53.
Each Primary site also manages any Satellite sites that are immediately
below it and on the same branch of the site tree. Such a Primary site is
called a managing site.
Sites that are single installations (are not part of a site tree) must be
Primary sites.
Satellite site
Satellite sites have a site server, but no management server. Instead,
managers run on the management computer at the closest Primary site
above the Satellite site. Data generated within the site is viewed through
the Console at a Primary site above it in the tree and rolled up to the
database server at the managing site.

50 Chapter 4
 About DTA sites
Site trees

Generally, sites with a small number of users or an intermittent or

disconnected network connection should be designated as Satellite sites.
You can install a Satellite site in connected or disconnected
communication mode. The difference is that, in connected mode, the
managed computers at the Satellite site use a Winsock connection to the
DTA Software Distribution management processes. For optimal
performance, it is recommended that you install Satellite sites across a
WAN link in disconnected communication mode, as Satellite sites
running in a connected mode typically require significant processing
power.
Satellite sites do not have local network administrators.
Table 4-1 lists the characteristics of each site type.
Table 4-1 Site type characteristics

Site type Requires a local Requires a Has a Requires a

administrator? management Console? database
server? server?

Primary Yes Yes Yes Yes

Satellite No No No No

Site tree relationships

The structure of your site tree affects the scope of the tasks you can
perform and the amount of data you can view at each site. The following
terms define positions within a site tree:

• central site—The site at the top of the tree. From the central site, you
can see data and perform tasks for every site in the tree. The central
site must be a Primary site.
• parent site—A site that sends data to and receives data from at least
one other site below it. A parent site can have many child sites. It can
also be a child site to a site above it in the site tree.
• child site—A site that receives data from and replicates data to a site
above it. A child site can have only one parent site. It can also be a
parent site to a site below it in the site tree.
• managing site—A Primary site that stores and runs managers for one
or more Satellite child sites.

Chapter 4 51
 About DTA sites
Site trees

Figure 4-1 illustrates how site relationships are defined by their relative
positions in the site tree. Site 002 (Hong Kong) is both a child site of site
000 (Tokyo) and a parent site of site 010 (Los Angeles) and site 020 (New
York).

Figure 4-1 Tree relationships

The managing site for a Satellite site is its closest Primary parent site. In
the figure above, site 000, the Primary central site, is the managing site
for Satellite child sites 001 (San Francisco) and 003 (Seattle). It is also
the parent site of 002, but not its managing site, because 002 is a
Primary site too. However, site 002 is a managing site for Satellite sites
010 and 020.
Table 4-2 outlines the possible relationships between sites of various
types.
Table 4-2 Site types and relationships

Site type Parent sites can be ... Child sites can be...

Primary Primary Primary, Satellite

Satellite Primary None

52 Chapter 4
 About DTA sites
Site trees

DTA server function configurations

Depending on the NOSs used in your network environment, the amount
of server disk space available, and whether you require a dedicated
database server, you can store and run DTA components in a number of
different directory configurations. These are described in the following
sections.
A DTA server function configuration is a grouping of a management
server, site server, and database server. The terms management server,
site server, and database server are functional only; they represent the
directory structure that DTA installs to the hardware you specify.
Server function configurations apply to Primary sites only, as Satellite
sites require only a site server.
The management server directory structure that DTA installs is:
\\Server\volume\HPDTA
\MANAGERS
The site server directory structure is:
\\Server\volume\HPDTA
\AGENTS
\CONSOLE
\DATA
The database server directory structure is that of your existing DBMS, or
for the bundled version of SOLID 3.0, it is:
\\Server\volume\HPDTA
\SOLID
The Console runs on the management server by default, but you can also
run it from the site server. To run it on any other Windows NT 4.0
computer, you must use the Console installation program. For more
information on installing the Console, see “Installing an additional
Console” on page 132.
Each site contains a site configuration database table, which stores the
site configuration information for the entire site tree. This database table
is synchronized through replication.

Chapter 4 53
 About DTA sites
Site trees

See Chapter 3, “Resource requirements,” on page 27 for complete

information about DTA minimum system requirements for server
hardware.

Centralized configuration
A centralized configuration (illustrated in Figure 4-2) has a single file
server that functions as both management server for the site and as the
site server that stores DTA applications and executable files. All
computers managed by the site, which are referred to as managed
computers, are connected to this file server.

Figure 4-2 Centralized configuration

A centralized configuration provides the best performance for DTA.

You can use a centralized configuration if your environment contains a
file server that:
• Runs Windows NT 4.0 Server software
• Has sufficient disk space, memory, and power to store your DBMS,
DTA applications and executable files, and to run managers
• Is accessible to all computers (workstations and servers) that are part
of the site.

54 Chapter 4
 About DTA sites
Site trees

The DTA Setup program provides an option for a Typical installation,

which installs DTA under a centralized configuration like the one shown
above. You might choose a Typical installation if you are installing the
bundled version of SOLID 3.0 DBMS and have a Windows NT file server
with enough capacity to run the site server, management server, and
database server functions of DTA. However, you do not have to select the
Typical installation to install a centralized configuration. In fact, it may
be preferable to install a centralized configuration using the Custom
option, which lets you specify the site, management, and database server
paths individually. The following are two reasons why you may want to
use the Custom option instead to install a centralized configuration:
• If you want to obtain optimal performance with the SOLID DBMS,
the best way to do it is to install the \DATA directory on a separate
hard drive than the \SOLID directory. The only way you can do this is
through the Custom option, which lets you specify different paths,
and therefore hard drives, for the site server and database server.
• If you plan to use Microsoft SQL Server as your DBMS, the best way
to obtain optimal performance with DTA is to run SQL Server on a
server with two processors. If you have set up SQL Server to run this
way, you can use the Custom option to install DTA to the
dual-processor server under a centralized configuration
Even though all site components are installed on a single server, you
must use universal naming conventions (UNCs). If you specify a disk
drive letter, the agents look on the corresponding drive of the managed
workstation where they are running. Thus, the agents will not be able to
find the database on the server.

To configure DTA to use UNCs

Step 1. Create a directory to be shared on the file server.

Step 2. Share the newly created directory.

Step 3. Map a drive to the directory.

Step 4. Install the software to the mapped drive that contains the directory.

Chapter 4 55
 About DTA sites
Site trees

Separate database server

A separate database server configuration (illustrated in Figure 4-3) is a
two-server configuration, with the Windows NT database server
separated from a file server that stores the management and site server
functions of DTA.

Figure 4-3 Separate Windows NT database server

If you are using Microsoft SQL Server with DTA, this is the second best
server configuration. The first is a centralized configuration where DTA
and SQL Server are installed on a single, dual-processor server.
If you are using the bundled SOLID database, DTA performance under
this configuration, although not quite as high as with a centralized
configuration, still exceeds that which you would receive under any of
the configurations described in later sections.
You can use a separate database server configuration if your
environment has these characteristics:

• Runs under the Windows NT NOS

• Requires a dedicated server for your DBMS
• Contains a file server with sufficient disk space, power, and memory
for storing and running DTA managers, applications and executable
files (and most likely the Console).

56 Chapter 4
 About DTA sites
Site trees

For management server and site server requirements, see Chapter 3,

“Resource requirements,” on page 27.

Separate management server

A separate management server configuration (illustrated in Figure 4-4)
has the management function separated from the other DTA functions.
The management server is a separate server, while the site server and
database server share a single file server.

Figure 4-4 Separate management server configuration

This configuration under-performs those that were described in the

previous sections because the DTA Site manager must move, read, and
write transaction files across the network more often to write to the
database.
You can use a separate management server configuration if your
environment has these characteristics:

• Runs under the Windows NT NOS

• Does not require a dedicated server for your DBMS

Chapter 4 57
 About DTA sites
Site trees

• Contains a file server with sufficient disk space, power, and memory
for storing and running DTA managers, applications, executable files,
and the DBMS
• Does not have a single file server powerful enough to run all the
functions of DTA.
For management server requirements, see Chapter 3, “Resource
requirements,” on page 27.

Separate site server

A separate site server configuration (illustrated in Figure 4-5) is a
two-server configuration with the site server separated from the
management server and database server. The management server and
database server are stored on the same file server.

Figure 4-5 Separate site server configuration

This configuration gives you the best performance in NetWare

environments. In Windows NT environments, the performance is better
than the “separate management server” configuration, but worse than
the “centralized” or “separate database server” configurations. However,
its performance still exceeds the distributed configuration.

58 Chapter 4
 About DTA sites
Site trees

You can use a separate site server configuration if your environment has
these characteristics:

• Runs under the Windows NT or Novell NetWare NOSs

• Does not require a dedicated server for your DBMS
• Contains a file server with sufficient disk space, power, and memory
for storing the management function of DTA and the DBMS (and
most likely the Console)
• Does not have a single file server powerful enough to run all the
functions of DTA.
For management server requirements, see Chapter 3, “Resource
requirements,” on page 27.

Distributed configuration
A distributed configuration (illustrated in Figure 4-6) has all DTA
functions stored on separate servers.

Figure 4-6 Distributed configuration

Chapter 4 59
About DTA sites
Site trees

This configuration offers the least performance of all the configurations

previously described. You can use a distributed configuration if your
environment has these characteristics:

• Runs under any of the following NOSs: NetWare or NT

• Requires a dedicated server for the DBMS
• Does not contain a file server with sufficient disk space, memory, or
power to use in any of the other configurations.
For management server requirements, see Chapter 3, “Resource
requirements,” on page 27.

60 Chapter 4
 About DTA sites
Data replication

Data replication
Replication is the process of copying new and changed data at one site
and moving it to another. This is the way that DTA synchronizes the
databases at different sites. This section provides an overview to DTA
replication and data transfer.

Data transfer
During replication, data moves in one of two directions: up the tree
(roll-up) or down the tree (fan-out). Figure 4-7 shows the types of data
that move up and down a site tree, depending on which DTA application
you are using, or if you have made changes to the properties of the site
tree, such as adding or deleting a site.

Figure 4-7 Data flow

Chapter 4 61
 About DTA sites
Data replication

The following classes of data roll up the tree:

• Data collected by Inventory tests (scans)

• Log data stored in the various Software Distribution logs
• Application and vendor records
• Site information, that is, data that describes the hierarchical
structure of the entire site tree, and any Console site configuration
changes (such as replication schedule changes).
The following classes of data fan out:

• Software distribution jobs

• Application and vendor records
• Site information.
Site information and application and vendor records are the only types of
data that travel both up and down a site tree, because they are the only
type of information that must be synchronized at every site in a tree. If
you make changes at a site (for example, adding a site to the tree), those
changes are replicated to all other sites in the tree, both above and below
the changed site.
Distribution jobs go only to their recipients at child sites, so the fan-out is
selective. However, log data about jobs that have run (distribution logs)
only rolls up the tree to update the parent sites.
Table 4-3 shows the direction each class of data moves in the site tree
during replication.
Table 4-3 Data category by direction of movement

Data that rolls up Data that fans out

Site information Site information

Hardware inventory Software Distribution jobs

Software inventory
Application information Application Information

Vendor information Vendor information

Software Distribution log

62 Chapter 4
 About DTA sites
Data replication

Transaction files
DTA replicates data with transaction files. A transaction file (sometimes
called a T-file) is like a container or envelope that DTA agents and
managers use to package data and move it from one place to another.
There are two basic kinds of transaction files:

• Agent transaction files—Files created by agents at the originating

site and inserted (despooled) into the appropriate databases at that
same site. This is called intra-site data transfer.
• Site manager transaction files—Files created at the originating site,
then transferred to and despooled at the destination site, all by Site
manager. This is called inter-site data transfer.
Before a transaction file can be despooled or transferred to another site,
it is placed in a temporary storage location, that is, an inbox or an
outbox. A site inbox is a directory that contains incoming transaction
files. A site outbox is a directory that contains transaction files scheduled
for transfer to other sites.

Agent transaction files

The job of an agent transaction file is to get data from its place of origin,
the managed computer, and put it in a site inbox (In the case of Software
Distribution log data, DTA manager puts the data in the site inbox). Site
manager can then take the data from the inbox and insert it into the
database at that site.
Each agent transaction file carries an extension that identifies the type
of data it contains:

• .DLD—Contains Distribution log data and is created by Software

Distribution agents.
• .AOT—Contains software inventory data, and application and vendor
data. Created by Inventory agents.
• .INT—Contains hardware inventory, prompts, and tracked-files data
and is created by Inventory agents.
• .BMT—Contains basic workstation information that DTA collects
separately when the Inventory application has not been installed.
DTA does not generate a separate .BMT file if the Inventory
application is installed; basic workstation information is instead
included in the .INT file.

Chapter 4 63
About DTA sites
Data replication

In the case of Primary sites, agent transaction files begin and end at
their originating site; that is, Site manager does not transfer them to
other sites. Rather, it inserts the records packaged by them into the
database for the site.
At Satellite sites, because they do not have a database, Site manager
transfers the agents transaction files to the managing (Primary) site,
where it then inserts the records packaged by them into the database.

Site manager transaction files

Where agent transaction files are created by the agents at a site to
process information within that site, site manager transaction files are
created by Site manager for replication to other sites. That is, the job of
the Site manager transaction file is to transfer data from the originating
site to the destination site or sites (inter-site data transfer).
You can identify Site manager transaction files by their extension (which
also tells you their direction of travel) as follows:

• .RTF—Moves up the site tree, from child to parent site; can contain
site tree information, Inventory scans, Distribution log data, and
application and vendor information.
• .NTF—Moves down the site tree, from parent to child site; can
contain site tree information, distribution jobs, and application and
vendor records.
Site manager transaction files always begin at the originating site and
end at the destination site or sites. The Site manager at the originating
site scans the database—according to the replication schedules you
set—and packages any data that is flagged for other sites in an .RTF or
.NTF transaction file. The type of transaction file depends on the position
of the destination site with respect to the originating site in the
hierarchy of the site tree.

64 Chapter 4
 About DTA sites
Data replication

Site manager transaction files always begin with the three-character site
ID of the originating site. For example, if Site manager scans inventory
database records at Site 001 for data that is flagged to be rolled up the
site tree, it creates a transaction file with the extension .RTF, and the
first three characters are 001, as follows:
001xxxxx.RTF
where xxxxx indicates the count for the transaction file. Each site
maintains a counter for transaction files created at the site. The counter
characters are alphanumeric, from 0 to Z.

NOTE Agent transaction files do not contain the originating site ID as part of
their filenames. They are processed at a single site, so there is no need to
identify an originating site.

Chapter 4 65
About DTA sites
Data replication

66 Chapter 4
5 Managing data

67
 Managing data
Displaying network information

Displaying network information

From the Browse menu, you can view information that DTA applications
generate or use. You can choose the type of information you want to view
and customize the information displays. The DTA Console lets you
perform a variety of tasks, such as viewing, adding, grouping, querying,
exporting, sorting, printing, and deleting the information.
Figure 5-1 shows the Console.

Figure 5-1 DTA Console

Using the Browse menu items, you can display the DTA viewers, which
contain information for any site or group in your networking
environment. These viewers (and the information they display) are
available depending on the DTA applications you installed.

68 Chapter 5
 Managing data
Displaying network information

Most viewers display a divided window (viewer) like the Computers

viewer shown in Figure 5-2. The left pane of the viewer displays a list of
sites and groups, and the right pane displays the data associated with
site or group selected in the left pane. You can create groups, and you can
specify which fields (column headings) are displayed in the right pane.
To display information in a viewer, choose the viewer from the Console
Browse menu or toolbar. For example, if you choose COMPUTERS, DTA
displays a viewer similar to the one below.

Figure 5-2 Computers viewer

data
column
groups
heads
(you can
create
custom
groups)

Chapter 5 69
 Managing data
Displaying network information

To change the display in all DTA viewers

Step 1. Choose a DTA viewer from the Console Browse menu or from the toolbar.

Step 2. Select STYLES from the View menu and select the Table tab.

Figure 5-3 Table tab

Step 3. Check or uncheck table viewer options and click OK.

• If you want to be able to select one data cell at a time (or a block of
cells), rather than an entire row, check Use Spreadsheet Style
Selection.

• To number the rows in the view, check Row Numbers.

• To place lines between the rows and columns, check Gridlines.

• To show which fields (column headings) are indexed in the database,

check Mark Indexed Fields With An Asterisk.

70 Chapter 5
 Managing data
Displaying network information

To change the display in a specific viewer

Step 1. To open the dialog that lets you change the display, do one of the
following:

• Click the right mouse button within the right pane of the viewer and
then choose VIEW STYLE to display table view options.

• Choose STYLES from the Console View menu, and then select the
Table tab to select table view options.
Depending on the method you chose, the Table View Options dialog
displays. (If you chose from the Console View menu, you see a property
page instead.)

Figure 5-4 Table View Options dialog box

Step 2. Check or uncheck table viewer options and click OK.

• If you want to select one data cell at a time (or a block of cells), rather
than an entire row, check Use Spreadsheet Style Selection.

• To number the rows in the view, check Row Numbers.

• To place lines between the rows and columns, check Gridlines.

• To show which fields (column headings) are indexed in the database,
check Mark Indexed Fields With An Asterisk.

Chapter 5 71
 Managing data
Displaying network information

To change the font for specific text displayed (such as column heads)
in all DTA viewers

Step 1. Choose a DTA viewer from the Console Browse menu or from the toolbar.

Step 2. Select STYLES from the View menu.

Figure 5-5 Font tab

Step 3. Select the type of displayed information for you want to change the font.

Step 4. Click FONT.

Step 5. Select the font, font style, and size and click OK.
Step 6. Click Apply to save the changes.

Step 7. Repeat Steps 3 through 6 as necessary.

Step 8. When done, Click OK.

72 Chapter 5
 Managing data
Displaying network information

To change the font for all data displayed in a specific viewer

Step 1. Choose a DTA viewer from the Console Browse menu or toolbar.

Step 2. Right-click anywhere in the viewer and select FONT.

Figure 5-6 Font dialog box

Step 3. Select the font, font style, and size and click OK.

To change the displayed color of Software Distribution log data

Step 1. Choose SOFTWARE DISTRIBUTION from the Console Browse menu or

Distribute from the toolbar.
Step 2. Select STYLES from the View menu.

Chapter 5 73
 Managing data
Displaying network information

Step 3. Click the Color tab.

Figure 5-7 Color tab

Step 4. Select the type of message you want to display in color:

• Informational: Those jobs that have successfully run, or are pending.

• Minor: Those jobs that have run with minor errors.

• Major: Those jobs that have run with major errors.

• Critical: Those jobs that have run with critical errors.

Step 5. Select a color from the panel on the right.

Step 6. Click Apply.

Step 7. Repeat Steps 1 through 3 as necessary.

Step 8. Click OK when done.

74 Chapter 5
 Managing data
Displaying network information

Changing displayed data

You can change the data columns displayed for a particular group in the
viewer. You can also change the properties of the objects included in the
viewer.

To modify the fields in a viewer

Step 1. Select the group you want to view in the left pane of the viewer.
Step 2. Do one of the following:

• Right-click the right pane of the viewer and choose FIELDS.

• Choose the DATA submenu from the View menu and then choose
FIELDS.

Figure 5-8 Field Definition dialog box

Step 3. To add a field to the viewer, do the following:

a. Select a category from the Categories list box.

b. Select a field from the Fields list box.

c. Click Add to add the field to the list of selected fields.

Chapter 5 75
 Managing data
Displaying network information

Step 4. To delete fields from the viewer, do the following:

a. Select the field you want to delete from the Selected Fields list box.

b. Click Delete to delete the field from the viewer.

c. To delete all the fields from the viewer, click Clear All.

Step 5. To reorder the fields in the viewer, do the following:

a. In the Selected Fields list box, select the field you want to move and
drag it to the place you want it to be.

b. Repeat this step for each field you want to move.

Step 6. Click OK when you finish modifying the viewer.

To modify object properties

Step 1. Select the group you want to view in the left pane of the viewer.

Step 2. Select the object (row) you want to modify in the right pane of the viewer.
Step 3. Double-click the object or right-click in the right pane and choose
PROPERTIES from the menu.

76 Chapter 5
 Managing data
Displaying network information

The displayed property page depends on the type of object you chose. For
example, if you select a computer from the Computers viewer, DTA
displays the a property page similar to the following one.

Figure 5-9 Object property page

Step 4. Make any changes as necessary or available.

Step 5. When finished, click OK.

Sorting data
You can sort data in a viewer by the values in the viewer fields (that is,
the columns). Depending on the type of data in a column, you can sort
the data alphabetically, numerically, or chronologically.
You have two choices for data sorting: ascending order and descending
order. When you re-sort the data in one column, the entries in the other
columns are also reordered to maintain the integrity of each row.

Chapter 5 77
 Managing data
Displaying network information

To re-sort data in a column

Step 1. To sort a column in ascending order, double-click the column.

The rows in the viewer display in ascending order for the selected field.
Step 2. To sort a column in descending order, hold down the Shift key and
double-click the column heading.

The rows in the viewer display in descending order for the selected field.

To re-sort data from a dialog

Step 1. Choose a viewer from the Console Browse menu or toolbar.

Step 2. Do one of the following:

• Right-click anywhere in the right pane of the viewer and select Sort.

• Select DATA from the Console Viewer menu and then choose Sort.

Figure 5-10 Sort dialog box

Step 3. Select the field (column head) by which to sort in the viewer.

Step 4. Select the sort order.

The rows in the viewer display in ascending or descending order for the
selected field, according to your selection.

78 Chapter 5
 Managing data
Displaying network information

Querying data
You can query any field that displays in a viewer. You can create a query
to select information for a report or to selectively view database
information.

NOTE Indexed fields provide the quickest queries. DTA indexed fields have an
asterisk by them.

To query on a viewer

Step 1. Choose a viewer from the Console Browse menu or toolbar.

Step 2. Do one of the following:

• Right-click anywhere in the right pane of the viewer and select

QUERY.

• Select the Query button from the Console toolbar.

• Select DATA from the Console Viewer menu and then choose Query

Figure 5-11 Query definition dialog box

Step 3. Select a category from the Categories drop-down list box.

Chapter 5 79
 Managing data
Displaying network information

Step 4. Enter or select a Query Name.

Step 5. Select a field from the Fields list box.

Step 6. Specify the operator.

Step 7. Enter the value for which you are querying. It does not have to be
case-sensitive.

Step 8. If you want more relational expressions in the query, click AND or OR
and repeat steps 6 through 8.

• AND joins two relational expressions, making both true.

• OR joins two relational expressions, making one or the other, but not
both, true.
Step 9. To save a query for reuse, click Save. To delete the query, click Delete.

Step 10. If necessary, do any of the following:

• Select Replace to replace the currently displayed description with the

current value.

• Select Remove to remove the selected condition from the condition

list.

• Select Clear All to remove all conditions from the description list,
whether selected or not.

• Select Group to group more than one condition. Select the conditions
and select group. The conditions are grouped with parenthesis.

• Check Show Categories to prepend the category name in front of the

field in the condition.

Step 11. Click OK.

80 Chapter 5
 Managing data
Copying a field value from a viewer

Copying a field value from a viewer

You can copy a specific field value from one of the Console viewers so that
you don’t have to enter it again into the Value text box in the Query
Definition dialog.

To copy a field value

Step 1. Open the viewer you want and right-click on the record containing the
value you want to copy.

Step 2. Select VIEW STYLES or TABLE VIEW OPTIONS, depending on what you see
in the menu.

Step 3. Check the option, Use Spreadsheet Style Selection in the Table View
Options dialog box.

Step 4. Click OK to return to the viewer.

Step 5. Right-click the field value you want to copy and select COPY from the
menu.

Step 6. Click the Query button on the Console toolbar to display the Query
Definition dialog. You can also right-click the right pane of the viewer or
select DATA from the Console View menu.

Step 7. Place the cursor over the Value text box and right-click it.

Step 8. Select PASTE from the menu to paste the value into the box.

Chapter 5 81
 Managing data
Grouping information

Grouping information
You can group information with other information that has similar
attributes. For example, you can create a group of workstations that run
on the same network operating system. You can create two types of
groups: dynamic and static.

• Dynamic groups use a database query to search for specific types of

information. This database filter collects objects that have the
attributes you specify. Each time you access the group, and each time
you refresh the display, DTA dynamically recreates the group based
on the most recent data in the database.
Use this type of group when you want updated information each time
you view the group. For example, you might create a dynamic group of
all computers that have Pentium as their CPU Type.
• Static groups contain a fixed set of objects, which you choose. A static
group does not use a database filter to place objects in a group.
Use this type of group when you want to define a group in which the
objects change only if you modify the group. For example, you might
create a static group of computers that are assigned to your staff
members.

To create a group

Step 1. Choose a viewer from the Console Browse menu. This example uses
COMPUTERS.

Step 2. Right-click in the left pane of the viewer to display the New Group menu,
or select the Console File menu.

Step 3. Choose NEW GROUP from the menu.

82 Chapter 5
 Managing data
Grouping information

Figure 5-12 New Group dialog box

Step 4. Enter the name of the group in the Group Name text box.
Step 5. Enter a description of the group in the Description text box.

Chapter 5 83
 Managing data
Grouping information

Step 6. If you are creating a static group, skip to step 7. If you are creating a
dynamic group, do the following:

a. Select Dynamic.

b. Click Edit Group.

Figure 5-13 Query Definition dialog box

c. Specify the query that defines the dynamic group.

You do this by selecting a Field and an Operator and entering a Value.

You can use AND and OR to string query elements together. When
you click Add, the values you have selected and entered appear in the
Description text box.

d. When you finish specifying the query, click OK, and skip to Step 8.

84 Chapter 5
 Managing data
Grouping information

Step 7. If you are creating a static group, do the following:

a. Select Static.

b. Click Edit Group.

Figure 5-14 Static Group Definition dialog box

c. From the Select From list box, select the objects you want in the
group and click Add.

d. When you finish adding objects, click OK to return to the <New>

dialog.

Step 8. Click Field View if you want to modify the default list of fields displayed
in the viewer for the group.
Step 9. From the Fields list box, select any fields (column headings) you want to
display in the viewer and click Add.

From the Selected Fields list box, select any fields you want to remove
from the viewer and click Delete if necessary.

Step 10. When you finish, click OK.

Step 11. On the General page, click OK again to complete the operation.

Chapter 5 85
 Managing data
Grouping information

NOTE You can modify the fields shown in the group view at any time by
right-clicking in the right side of the viewer and selecting Fields from the
displayed menu.

To add or delete an object in a static group

Step 1. In the viewer, select the group you want to modify from the list in the left
pane.

Step 2. Double-click the group name or right-click in the right pane and select
PROPERTIES from the menu.

Step 3. Click Edit Group.

Figure 5-15 Static Group Definition dialog box

Step 4. Do one of the following:

• To add an object to the group, select an object in the Select From list
box and click Add.

• To delete an object from the group, select an object in the Selected

Items list box and click Remove.

86 Chapter 5
 Managing data
Grouping information

Step 5. Click OK.

Step 6. Click OK again.

A dynamic group is a filter for a query process, so instead of adding or

deleting them, you can change them. You can change the contents of a
dynamic group by changing the variables in the Query Definition dialog
box.

To delete a group

Step 1. In the viewer, select the group you want to delete from the list in the left
pane.
Step 2. Press Delete.

Step 3. Click OK.

Summarizing data
You can view or print a summary of the data displayed in any column in
a viewer.

To summarize column data

Step 1. Choose a viewer from the Console Browse menu.

Step 2. If you haven’t already done so, specify spreadsheet style selection:

a. Right-click in the right side of the viewer and select VIEW STYLES. You
can also select STYLES from the Console View menu, and then select
the Table tab.

b. Select the Use Spreadsheet Style Selection option and click OK.

Step 3. Within the view, double-click a column heading.

Chapter 5 87
 Managing data
Grouping information

Step 4. Choose DATA from the Console View menu, and then SUMMARY from the
Data submenu.

Figure 5-16 Summary window

The Summary window displays each type of entry that appears in the
column you selected. Next to the entry type is the number of times that
entry type occurs in the current view.

Step 5. If you want to print the summary, click Print.

Printing the contents of a viewer

You can use the Print command to print the contents of a viewer. Before
you print a view, you may want to delete unnecessary columns, sort the
database based on one of its columns, or select a range of rows to print.

88 Chapter 5
 Managing data
Grouping information

To print a viewer

Step 1. Display the viewer you want to print by choosing it from the Console
Browse menu or toolbar.

Step 2. Choose PRINT from the File menu.

Figure 5-17 Print dialog box

Step 3. Do any of the following as necessary:

• If you don’t want the header to be the name of the viewer, enter a
different name in the Header text box.

• Check the options you want to include when printing.

• Click Printer to change the printer setup.

• Click Page to change the page setup.

Step 4. Click OK to print the view.

Chapter 5 89
 Managing data
Exporting data

Exporting data
You may want to export data to other applications or to another file
format. You can do this by copying data using the Export command.

Exporting data to other file formats

You can save information that DTA displays in a viewer in the following
formats:

• .TXT—Text
• .CSV—Comma-separated values
• .DIF—Data Interchange Format
• .DBF—dBASE III
• .WKS—Lotus 1-2-3.

To save data to other file formats

Step 1. Choose an item from the Console Browse menu or toolbar.

Step 2. Sort the rows in the viewer as you want them to display in the new
format.

Step 3. If you do not want to export the entire database, select the data you want
to export.

Step 4. Choose EXPORT from the File menu.

Step 5. Choose FILE from the Export submenu.

Step 6. To change the export location, select a drive and directory from the
Directories list box.

Step 7. Select the desired file format from the Type drop-down list.
Step 8. Enter a filename in the File Name list box.

Step 9. If you want to export only the data you selected in a previous step, check
Export Selected Records Only.

Step 10. Click OK.

90 Chapter 5
 Managing data
Exporting data

Exporting data using ODBC

You can use the Export ODBC (Open Database Connectivity) menu
option to export the data displayed in DTA viewers to applications that
are compliant with ODBC 3.5.
The advantage of exporting through ODBC, rather than simply
exporting to another file format is that it preserves your view
information, including the data types.
Be aware, however, that you can only export a DTA viewer to a single
table in a target database. For example, if a DTA viewer displays data
from multiple database tables, you can only export the viewer to one
table in a database.
DTA has been tested with the following database management systems
(DBMSs):

• MS SQL server
• MS Access
• SOLID 3.0 for Windows NT.
Other ODBC data sources may also work with DTA.

To export data to ODBC format

Step 1. Make sure the destination DBMS is installed and that its ODBC option
has been enabled.

Step 2. If you have not already done so, create a destination database using the
database management tools provided with the DBMS.

Step 3. If you haven’t already done so, run the 32-bit ODBC administrator in the
Control Panel and add a Data Source Name (DSN) that specifies your
database and driver.
Windows creates database information that combines the information
about the database engine, driver, and database you have created into an
entry in the ODBC.INI file.

Make a note of the DSN you entered in this step. You will use this name
in a later step.

Step 4. Open the DTA Console for the site.

Chapter 5 91
 Managing data
Exporting data

Step 5. From the Console Browse menu or toolbar, select the viewer you want to
use for selecting records to export.

Step 6. Sort the records in the viewer as you want them to display in the new
format.

Step 7. If you do not want to export the entire database, select the data you want
to export.

Step 8. Choose Export from the File menu, and then ODBC from the submenu.
Step 9. Enter the data source name (DSN) in the Destination Data Source Name
text box or click Browse to select a DSN.

Step 10. Enter a database name in the Destination Database Name text box. Use
an extension that matches your chosen database format, if one is
required.

Step 11. Enter a unique table name in the Destination Table Name text box.
Step 12. Click the Advanced tab.

Step 13. Choose an export mode (ASCII or Raw).

• Click Standard Export Mode (ASCII) to export all the fields as ASCII
text.

• Click Advanced Export Mode (Raw) if you want the export utility to
attempt to match the source data types to the destination data types,
and if you want to preserve date fields.

• Click Save Destination Data As Defaults to make the current

destination data source name and destination database name the
new defaults.

• Click Export Selected Records Only to export only the data you
selected in the viewer.
Step 14. Click OK to export to the ODBC destination.

Real-time access through ODBC

DTA also allows real-time, read-write and read-only access to its
database by external, ODBC-compliant front-end applications, such as
Microsoft Access. The steps required to access DTA data depend on the
third-party application you are using.

92 Chapter 5
 Managing data
Working at another site

Working at another site

Usually, the position of a site in the site tree determines the range of the
tasks you can perform and the data you can view from the Console. In
the Figure 5-18, for example, from the Console at site 002 (Hong Kong),
you can see data about or perform tasks for computers at sites 002, 010,
and 020, but not sites 000, 001, or 003.

Figure 5-18 Viewing site data

If you want to perform tasks or view data at a site other than the one you
are currently logged onto, you can scope to it. In order to scope from a
child site to a parent Primary site, you must provide the DBMS account
for that site. You can use the read-only account created at DTA Setup.
However, if you scope from a parent Primary to a child site, you do not
need to provide an account password for the DBMS account.
For example, in Figure 5-18 if your home site is site 002 (Hong Kong) but
you want to create a distribution job for a computer at site 003 (Seattle),
you perform the steps in the following procedure to scope to site 003.

Chapter 5 93
 Managing data
Working at another site

To scope to another site

Step 1. Open the Console at site 002.

Step 2. Choose CHANGE SITE from the File menu.

Figure 5-19 Change Site dialog box

Step 3. Select Site 003 from the drop-down list of sites.

Step 4. To return to the original site or scope to another site, repeat step 2 and
select the desired site ID.

The Console always returns to its home site when you stop and restart it.
That is, even if you don’t scope back to your home site before you shut
down the Console, you will be at your home site (site 002 in this example)
the next time you start the Console.

94 Chapter 5
6 Maintaining sites

95
 Maintaining sites
Controlling replication activity

Controlling replication activity

The Replication page lets you set the data scanning and data transfer
schedules at Primary sites. (The schedules apply to the Primary site
where they are set and to any Satellite sites managed by the Primary
site.) These schedules instruct Site manager to scan the database and
replicate new and changed data to other sites. You can set different
replication schedules for each class of data that Site manager scans.
To access the Replication page, select SITE from the Console Configure
menu, then choose the Properties button and select the Replication tab.

Figure 6-1 Console Replication page

sets how
frequently
classes of
DTA data
are
scanned
sets (at the
Primary child site)
how frequently
data transfers
between sites
sets the
method of
transfer
between sites

The Replication page lets you set the data scanning and data transfer
schedules at Primary sites. (The schedules apply to the Primary site
where they are set and to all the sites managed by the Primary site.)
These schedules instruct Site manager to scan classes of data such as
software inventory or distribution jobs, and replicate (transfer) new and
changed data to other sites.

96 Chapter 6
 Maintaining sites
Controlling replication activity

You can set a unique data scanning schedule for each class of DTA data
in the database. However, you can set only one common schedule for
transferring the transaction files that contain changes to data,
regardless of data class. For example, you can have Site manager scan
the software inventory data class, and the Distribution log class daily,
but the resulting transaction files created from both scans are
transferred (rolled up) to the parent site according to a common transfer
schedule.
You can revise replication properties only for Primary sites. For Satellite
sites, all replication properties are inherited from the managing Primary
site. If you use the Primary site Console to view site properties for a
Satellite site, the Replication page only displays the Transfer Method,
which must always be Direct.
How frequently you replicate data depends on your business needs and
your network's capacity and load patterns. To ease the traffic load on
your network during business hours, you can schedule replication to
occur at times when there is less activity on the network, such as nights
or weekends. When you schedule data roll-up at non-peak times, you
generally have a greater lag between the time when data changes at the
originating site and the time when it is available at the central site.
The Replication page is divided into three areas, which are described in
the next sections. For step-by-step instructions on modifying a
replication schedule, see “Modifying replication schedules” on page 100.

Data scanning schedules

You can set an individual schedule for each class of DTA data in the
database (for example, Distribution logs) listed in the Data Scanning
Schedules list box (see Figure 6-1). The default setting for all data
scanning schedules is every fifteen minutes.

• Properties: You can select a database category from the Data

Scanning Schedules list box and click Properties to configure a data
scanning schedule. The Data Scanning Schedule dialog box appears
so you can enable or disable scanning and set the frequency, start
date, and start time when Site manager will scan that particular
database category and create transaction files for replication.

Chapter 6 97
Maintaining sites
Controlling replication activity

For optimum replication performance, stagger the Site Information data

scanning schedule with respect to the other data scanning schedules. For
example, if the Computers data scanning schedule was set to every 15
minutes, the Software Inventory, Applications, and Vendors schedules to
Weekly, and the Software Distribution schedule to Daily, then you would
want to set the Site Information schedule to something different than
any of the aforementioned schedules.
Also, replication is faster when you set the data scanning schedules for a
child site at the child site itself. You can do this by either scoping to the
child site from the Console of the parent, or by physically visiting the
child site.

Transfer schedule
You set the transfer schedule only at Primary child sites. The transfer
schedule does not apply to Satellite sites. Instead, Satellite sites use
minimum interval set in the data scanning schedule of the managing
site.
For example, if the data scanning schedule at the managing sites had a
fifteen minute schedule set for Computers, a ten minute schedule set for
Software Distribution, and a forty minute schedule set for Applications,
the Satellite site would use the ten minute schedule for its transfer
schedule.
Transfer Schedule options are described below.

• Disable Data Transfer: Disables Site manager from transferring

transaction files between sites.
• Frequency: You can set the frequency, start date, and start time when
Site manager transfers the transaction files that were created since
the last replication. The default setting is every 30 minutes.

98 Chapter 6
 Maintaining sites
Controlling replication activity

You can only set the transfer schedule between two Primary sites from
the child site. However, modifications to the Transfer schedule take effect
faster if you change the schedule from the child site Replication property
page at the Console at the parent site, rather than scoping or physically
going to the child site itself. This is because DTA always uses Site
manager at the parent site to transfer data records to and from a child
site.
To change child site properties (such as replication) from the parent site,
access the Console at the parent site, choose SITE from the Configuration
menu, select the child site in the Site Tree page, and then click
Properties to select the child site Replication page, where you can then
make Transfer schedule modifications from the child site.

Transfer method
You set the transfer method (and schedule) only at Primary child sites.
Satellite sites must use Direct as the transfer method.

NOTE The dialog boxes you use to configure the transfer method are discussed
in “To configure replication information” on page 101.

• Transfer Method: You can select Direct, FTP, or TCP/IP as the

transfer method between Primary sites. (Satellite sites only use
Direct). Each connection method has specific requirements:

— Direct: (Default) Transfers data between sites by mapping a drive

from the parent site to the remote volume or share on the child
site and copying files. To use the Direct connection method, you
must be running a supported Network File System, such as
NetWare or Windows NT. Site manager at the parent site must
also have read/write access to the \DATA directory at the child
site, that is, you must use the site server account at the child site
to set the Direct option.

Chapter 6 99
 Maintaining sites
Controlling replication activity

— TCP/IP: For replication using TCP/IP, each management server

must have a valid IP address, and Site manager must be running
at both sites.
— FTP: For replication using FTP, the target site file server must be
an FTP file server, and the site server HPDTA\DATA directory
must be accessible using the FTP share.
• Properties: To specify connection settings (transfer speed, for
example) for the transfer method.

Modifying replication schedules

Although you see the replication page during site installation, DTA
recommends that, except for the transfer method, you accept the default
settings during software installation, and change them afterwards, if
necessary. You can change replication settings at any time.

NOTE For remote installation, you must select Direct as a transfer method, or
replication between the child and parent site will not work.

Any schedule changes you make take effect after the next scheduled scan
or transfer, or you can exit and restart Site manager to have the changes
take effect immediately.
For example, if you had originally set database scans for once a month
but are now changing them to once a week, the new scanning schedule
takes effect after the next monthly scan. To put the weekly scans into
effect immediately, stop and restart Site manager after you make the
change in the Replication page.
For optimum replication performance, follow these guidelines:

• Stagger the Site Information data scanning schedule with respect to

the other data scanning schedules. For example, if the Computers
data scanning schedule was set to every 15 minutes, the Software
Inventory, Applications, and Vendors schedules to Weekly, and the
Software Distribution schedule to Daily, then you would want to set
the Site Information schedule to something different than any of the
aforementioned schedules.

100 Chapter 6
 Maintaining sites
Controlling replication activity

• Set the data scanning schedules for a child site at the child site itself.
You can do this by either scoping to the child site from the Console of
the parent, or by physically visiting the child site.
• Set the Transfer schedule between two Primary sites from the child
site Replication page at the parent site Console (rather than scoping
or going to the child site to make the modification).
The following procedure guides you through the replication modifications
from a single site. Given the guidelines above, however, you may want to
perform Steps 1 through 9 at the parent site Console and then resume
with Step 10 when you have scoped to or are physically at the child site
and can access its Console locally.

To configure replication information

Step 1. If you want to change the data scanning schedule for a database, select a
class of data (for example, Computers) from the Data Scanning
Schedules list box and click Properties.

Figure 6-2 Data Scanning Schedule Properties dialog box

Step 2. Do one of the following:

• Choose Disable Data Scanning if you do not want Site manager to

scan the database for new or changed data.
• Choose Enable Data Scanning to set up a data scanning schedule for
Site manager to scan the database at the frequency and time you
specify.

Chapter 6 101
 Maintaining sites
Controlling replication activity

Step 3. If you checked Enable Data Scanning, select the frequency to specify how
often data scanning occurs. Choose one of the following:

• Custom: Scans data at the date, time, and interval you specify in the
Start Date, Start Time, and (hh:mm) text boxes.

• Hourly: Scans data hourly at the time and date specified in the Start
Date and Start Time text boxes.

• Daily: Scans database once a day beginning at the time and date
specified in the Start Date and Start Time text boxes.
• Weekly: Scans database once a week beginning at the time and date
specified in the Start Date and Start Time text boxes.

• Biweekly: Scans database once every two weeks beginning at the time
and date specified in the Start Date and Start Time text boxes.

• Monthly: Scans database once a month beginning at the time and

date specified in the Start Date and Start Time text boxes.
• Bimonthly: Scans database once every two months beginning at the
time and date specified in the Start Date and Start Time text boxes.

Step 4. Enter the month, day, and year in the Start Date text box for the first
data scan you are scheduling.

Step 5. Enter the hour, minute, and am/pm for the first data scan you are
scheduling.
Step 6. If you specified a Custom time interval for Site manager to scan the
database, enter the interval in the (hh:mm) text box.

Step 7. If you want Site manager to replicate the entire DTA database the next
time it scans it, check Replicate All Data At Next Scheduled Time.

You might want to choose this option if, for example, you lost all your
data at the parent site. Replicating all data takes considerably more time
than replicating new or changed data only. If you choose this option, Site
manager resets the option, so that complete replication occurs only once
each time you check this box.

102 Chapter 6
 Maintaining sites
Controlling replication activity

Step 8. Do one of the following:

• If you want to apply the schedule to the entire DTA database, select
All Schedules.

• If you want to apply the schedule to only the class of data you
selected, choose Selected Schedule.

Step 9. Click OK.

The Replication property page reappears.

Step 10. Do one of the following:

• Specify a transfer schedule to determine how often Site manager at

the Primary parent site connects to this site for data transfer. If you
select this option, go to step 11.
• Select Disable Data Transfer if you do not want to transfer data to or
from this site. If you select this option, go to step 15 or step 18.

Step 11. In the Frequency drop-down list box, choose one of the following:

• Custom: Scans data at the date, time, and interval you specify in the
Start Date, Start Time, and (hh:mm) text boxes.

• Hourly: Scans data hourly at the time and date specified in the Start
Date and Start Time text boxes.

• Daily: Scans database once a day beginning at the time and date
specified in the Start Date and Start Time text boxes.

• Weekly: Scans database once a week beginning at the time and date
specified in the Start Date and Start Time text boxes.
• Biweekly: Scans database once every two weeks beginning at the time
and date specified in the Start Date and Start Time text boxes.

• Monthly: Scans database once a month beginning at the time and

date specified in the Start Date and Start Time text boxes.

• Bimonthly: Scans database once every two months beginning at the

time and date specified in the Start Date and Start Time text boxes.
Step 12. If you specified a Custom time interval for Site manager to send data,
enter the interval in the (hh:mm) text box.

Chapter 6 103
 Maintaining sites
Controlling replication activity

Step 13. In the Start Date text box, enter the month, day, and year for the first
data scan you are scheduling.

Step 14. In the Start Time text box, enter the hour, minute, and am/pm for Site
manager to start sending data.

Step 15. Specify the Transfer Method from the drop-down list box.

Step 16. Click Properties to specify the connection settings for the Transfer
Method.

If you selected Direct as the transfer method, the Direct Connect

Configuration dialog box appears. Go to the Direct section of step 17.

Figure 6-3 Direct Connect Configuration dialog box

If you selected TCP/IP as the transfer method, the TCP/IP dialog box
appears. Go to the TCP/IP section of step 17.

NOTE Be sure to enter the address or DNS name of the child site.

Figure 6-4 TCP/IP dialog box

104 Chapter 6
 Maintaining sites
Controlling replication activity

If you selected FTP as the transfer method, the FTP Transport

Configuration dialog box appears. Go to the FTP section of step 17.

Figure 6-5 FTP Transport Configuration dialog box

Step 17. Enter connection information.

For the Direct connection type, specify the user name and password for
the Site manager at the parent site. Use the site server account for the
child site. Specify the user name with the domain name of the child site,
that is, in the following format:

Domain_name/User_name

For the TCP/IP connection type, specify either the DNS (domain name
server) name or the IP address of the site you are now configuring.

For the FTP connection type, specify the following:

• IP address of the FTP server

• User name and password required to log into the FTP server.

Make sure that the Inbox and Outbox pathnames are correct.

Step 18. Click OK.

Step 19. When you have entered all the information for the new site, click OK.

Chapter 6 105
 Maintaining sites
Controlling replication activity

Controlling the order of data replication to multiple

Satellite sites
Because Satellite sites do not have a Site manager, they rely on their
parent Primary sites to handle the replication process for them. The Site
managers at these Primary parent sites act as proxies for the Satellite
sites. When a Primary site has multiple child Satellite sites, the Primary
Site manager determines the sequence by which it will act as proxy for
each child Satellite site. The sequence is called the proxy order. By
default, the proxy order is dynamic, based on internal variables.
You can change the order in which data is replicated to multiple Satellite
sites by editing the site configuration file for the Primary parent site.

To change the order of data replication to multiple Satellite sites

Step 1. Make a note of the Site IDs of the sites for which you want to control the
proxy order.

Step 2. Using a text editor, open the Primary site configuration file,
NADMIN.INI located in the \CONSOLE directory on the site server.

Step 3. Add the following section to the NADMIN.INI file:

[Replication]
Proxy_Order=ID1,ID2,ID3,...IDn

where ID1 is the three-character site ID for the first site in the
replication sequence, ID2 is the site ID for the second site in the
replication sequence, ID3 is the third, and IDn is the last site in the
replication sequence.

Step 4. Save the NADMIN.INI file and exit the text editor.

Site manager at the Primary parent site will always act as a replication
proxy first to the sites you added to the NADMIN.INI, in the order you
specified them, before it replicates any data to and from any other child
Satellite sites not included in the proxy order string of the NADMIN.INI
file.

106 Chapter 6
 Maintaining sites
Modifying and monitoring sites

Modifying and monitoring sites

You can modify or monitor site information through many of the same
pages that you used to install and add sites (described in Chapter 8,
“Adding a site,” on page 167). The Console Site Configuration dialog box
has seven tabs that provide access to the following pages, which you use
to modify sites:
• General: View site information, revise the site description and time
zone, or change the connection mode of a site.
• Network: Change an incorrectly specified network operating system
to the correct one operating on the DTA site server.
• Location: View site server information.
• Servers: Add and delete servers to be managed by a particular site.
• Replication: Modify the replication schedules and settings. These
page settings are discussed in the “Controlling replication activity” on
page 96.
• Database: Specify a new DBMS user account, if you have changed
yours since initially setting up DTA. Also, specify a new computer
name for the DTA database server, or change the way DTA identifies
the database server.
• Managers: View management server information.

To access the Site Configuration dialog box

Step 1. Choose SITE from the Configure menu.

Step 2. On the Site Tree property page, select the site you want to modify or view
information about and click Properties.
The Site Configuration dialog box displays the General page.

Step 3. To display another page, click its tab.

These property pages are discussed in the following sections.

Chapter 6 107
 Maintaining sites
Modifying and monitoring sites

Changing the communication mode of a site

When you install or add a site, you are prompted by the DTA Setup
program to specify the communication mode of the site. Installing a site
in connected mode means that the Software Distribution agents running
at site have access to a TCP/IP Winsock connection through which they
receive distribution jobs from the DTA manager. A site that is
disconnected does not provide a TCP/IP Winsock connection, and so
agents do not have continuous connection with the DTA manager.
Typically, you might install a site in disconnected mode if have a Satellite
site across a WAN link and don’t want the workstations at the Satellite
to communicate with DTA components at the parent site across this link.
You might also choose to have a disconnected site to reduce network
traffic on an already near-capacity network infrastructure. You can only
run Satellite sites in disconnected mode.

To change the connection mode of a Satellite site

Step 1. Choose SITE from the Configure menu.

Step 2. Select the site you want to change from the Site Tree property page.

Step 3. Select properties to display the General page.

Figure 6-6 Site Properties General page

108 Chapter 6
 Maintaining sites
Modifying and monitoring sites

Step 4. Check the box next to Communications mode: Run Agents Disconnected
From Manager to now run the site in disconnected mode.

Uncheck the box to run the site in connected mode.

Step 5. Click Apply to save your changes.

Revising site information

You can change the description of a site, or correct the time zone if you
specified it incorrectly during Setup.

To revise a site description or correct a time zone

Step 1. Choose SITE from the Configure menu.

Step 2. Select the site you want to modify from the Site Tree property page.

Step 3. Select properties to display the General page, shown in “Changing the
communication mode of a site” on page 108.
Step 4. Enter a new description of the site in the Description field, as necessary.

Step 5. Select the correct time zone as necessary.

Step 6. Click Apply to save your changes.

Specifying the correct NOS for the site server

If the site server NOS was incorrectly specified during site installation,
you can correct it through the Network page.
If the NOS was specified correctly, but you have since changed the site
server NOS, you must remove the DTA software from the site, delete the
site, and then reinstall it. You then can specify the new NOS during DTA
Setup.

Chapter 6 109
 Maintaining sites
Modifying and monitoring sites

To specify the correct site server NOS

Step 1. Choose SITE from the Configure menu.

Step 2. Select the site you want to modify from the Site Tree property page.
Step 3. Select properties and then click Network to display the Network page.

Figure 6-7 Site Properties Network page

Step 4. Select the NOS of the site server from the Network Operating System
list box.

If you select NetWare Directory Services (NDS) as the NOS, the NetWare
NLS (National Language Support) subdirectory must be in the search
path for both network administrators and users in order for DTA to work
with directory services. The default path is usually SYS:PUBLIC\NLS.

Step 5. Click Apply to save your changes.

110 Chapter 6
 Maintaining sites
Modifying and monitoring sites

Specifying servers to be managed

Before you can distribute jobs to or perform inventory scans on servers at
a site, they must first be specified as managed servers. You can identify
the servers to be managed from this site through the Servers page.
Server management includes two types of activities:

• Distribution of software to a server

• Inventory of software on a server.

CAUTION You cannot specify the same server for more than one site.

To specify or revise managed servers

Step 1. Choose SITE from the Configure menu.

Step 2. Select the site with servers to manage from the Site Tree property page.

Step 3. Select Properties and then click Servers to display the Servers page

Figure 6-8 Site Properties Servers page

Chapter 6 111
 Maintaining sites
Modifying and monitoring sites

Step 4. Click Add/Delete to display the Select Recipient Servers dialog box.

Step 5. Select Servers from the Object Type drop-down list box.

Step 6. Do any of the following:

• Select the servers to which you want to send jobs from the Available
list box and click Add.

• Select the servers you want to remove from the Selected list box and
click Delete.

• To save your server list to a file, click Save, then name the file to be
saved on the Save Net Objects File window.

• To load a list of servers from a previously saved file, click Load, then
select the file name from the Load Net Objects File window.
• To append the contents of a previously saved file to the displayed list
of servers, click Append, then select the file name from the Load Net
Objects File window.

• Click Network to display a list of servers on another network.

Step 7. Click OK when you are finished with the server list.
Step 8. On the Servers page, for each server in the list, enter the name and
password of the user responsible for executing the distribution jobs and
inventories. (If the server has not been configured with a user name and
password, then you don’t need to specify one here.)

Highlight the servers one at a time and enter the user name and
password for each. If you enter an incorrect name or password, the job
will be unsuccessful on the affected server.

Step 9. Do one of the following:

• Click Apply to save the list to the database and remain in the current
dialog box.

• Click OK to save the list to the database and close the current dialog
box.

112 Chapter 6
 Maintaining sites
Modifying and monitoring sites

Specifying revised database server information

If a DBMS user account or database server computer name is revised
after site installation, you must specify the new information in the
Database page.

NOTE You can only use the Database page to revise database server
information if you have a dedicated database server. If the database
server at the site resides on the same server as the site server,
management server, or both, call technical support for instructions.

To specify a revised DBMS user account or database server computer

name

Step 1. Stop DTA manager and Site manager through the SmartDeploy agent,
using the Control Managers page in the Console.

Step 2. Choose SITE from the Configure menu.

Step 3. Select the site from the Site Tree property page.

Chapter 6 113
 Maintaining sites
Modifying and monitoring sites

Step 4. Select Properties and then click Database to display the Database page.

Figure 6-9 Site Properties Database page

Step 5. Do any of the following:

• Enter the revised User ID or Password in the appropriate fields in the

Database Information group box.

• Click the Browse button (...) to select the new computer name of the
database server.
Step 6. Click Apply to save the changes.

Step 7. Restart DTA manager and Site manager through the SmartDeploy
agent, using the Control Managers page in the Console.

Changing the way DTA identifies the database server

By default, DTA identifies the database server by computer name.
During DTA Setup, If you want to change the current way of identifying
the database server, you can do so through the Database page.

114 Chapter 6
 Maintaining sites
Modifying and monitoring sites

To modify the way DTA identifies the database server

Step 1. Stop DTA manager and Site manager through the SmartDeploy agent,
using the Control Managers page in the Console.

Step 2. Choose SITE from the Configure menu.

Step 3. Select the site from the Site Tree property page.
Step 4. Select Properties and then click Database to display the Database page.

Step 5. Click Advanced Settings to display the Advanced Connections Settings

dialog.

Figure 6-10 Advanced Connection Settings dialog box

Step 6. To instruct DTA use an IP address to connect to the database server:

a. Make sure that TCP/IP is specified as the Network Protocol.

b. Select the IP Address option.

c. Type the new static IP address in the IP Address field. Note that this
field only verifies the format of an IP address; it does not validate it.
Step 7. If necessary, enter a revised port in the Port No. field.

Step 8. Select the Computer name option to return DTA to the default method of
connecting to the database server, or click Defaults to return all default
settings, including port and network protocol.

Step 9. Click OK to return to the Database page.

Chapter 6 115
 Maintaining sites
Modifying and monitoring sites

Step 10. Click Apply to save the changes.

Step 11. Restart DTA manager and Site manager through the SmartDeploy
agent, using the Control Managers page in the Console.

116 Chapter 6
 Maintaining sites
Viewing management server information

Viewing management server information

You can view management server information through the Managers
page.

To view management server information

Step 1. Choose SITE from the Configure menu.

Step 2. Select the site from the Site Tree property page.

Step 3. Select Properties and then click Managers to display the Managers page.

Figure 6-11 Site Properties Managers page

The page displays the name and volume of the management server in the
NT Server Information group box. In the NT User Account Information
group box, it displays the user ID and password for the Managers
account.

Chapter 6 117
 Maintaining sites
Viewing site server location

Viewing site server location

You can view the location and name of the site server through the
Location page.

To view site server information

Step 1. Choose SITE from the Configure menu.

Step 2. Select the site from the Site Tree property page.

Step 3. Select Properties and then click Location to display the Location page.

Figure 6-12 Site Properties Location page

The page displays the current site server pathname.

118 Chapter 6
 Maintaining sites
Repositioning a site

Repositioning a site
You can change the way data is replicated in your networking
environment by changing the relationship between sites in a tree. For
example, you can delete a child site from one parent and add it to a
different location in the site tree, so that it has a new parent.
Be aware of the following when you reposition sites:
• Consider your existing hierarchy. For example, a Primary site cannot
be a child site to a Satellite site, and a Satellite site cannot be a child
to another Satellite site.
• The latency period between the time you make changes and the time
the changes take effect depends on your replication schedule. Unless
you change the Site manager schedule to force an immediate
replication cycle, DTA replicates your changes to the database for
each site during the next scheduled replication.

To assign a new parent Primary site

Step 1. Delete the site and its children from the current site tree. See “Deleting
sites” on page 125 for instructions on deleting sites.

Step 2. Wait until the deletion has replicated throughout the site tree.
Step 3. Merge back the disconnected tree. See “Merging DTA 5.0 site trees” on
page 120 for instructions on merging trees.

Chapter 6 119
 Maintaining sites
Merging DTA 5.0 site trees

Merging DTA 5.0 site trees

You may need to merge two or more DTA 5.0 site trees into one tree,
particularly if your rollout was incremental. You do this by adding the
central site of one site tree (the “child” site tree) to the tree that you want
to enlarge (the “parent” site tree). Then the former central site and all of
the sites under it become part of the parent tree.

Example
You have a site tree that includes all the sites in your Los Angeles office,
and you have another site tree for the sites in your New York office. You
decide to merge the Los Angeles tree into the New York tree. In this
example, the Los Angeles site tree is the child tree, and New York is the
parent tree.
You choose the site within the New York tree that will be the parent to
the top level (central site) of the Los Angeles sites. (For this example, the
ID of the New York parent site is NY4, and the Los Angeles central site is
LA1.) NY4 must be a Primary site. You then merge NY4 and LA1.
The entire Los Angeles site tree merges under the New York site tree, at
NY4 specifically. The former central site (LA1) of the Los Angeles tree is
now a child to NY4, and the hierarchy below LA1 is the same as it was in
the Los Angeles tree.

Merging trees
Before merging site trees, make sure there are no duplicate site IDs in
any of the trees you are merging.

To merge two DTA 5.0 site trees

Step 1. Turn off all the DTA managers at the parent and child sites where the
merge will occur. (The “child” site is the central site of the tree to be
merged; the “parent” site is the point at which the child site is joined to
the tree that is to be enlarged.)
Use the SmartDeploy agent to stop the managers. See “Controlling
managers and application agents” on page 149 for instructions on
stopping the managers.

120 Chapter 6
 Maintaining sites
Merging DTA 5.0 site trees

Step 2. Access the Console at the site in the parent site tree where the child site
tree will be attached.

Step 3. Choose SITE from the Configuration menu.

Step 4. Choose MERGE from the Site Configuration page.

Figure 6-13 Merging sites dialog box

Step 5. Select DTA 5.0 for the Child Site Version.

Step 6. Click Browse (...), and select the site server \\HPDTA\DATA directory
(\\server_name\volume\HPDTA\DATA).

Step 7. Click OK.

The changes take effect immediately at the site where you performed the
merge operation and at the top of the child site tree (that is, the former
central site). The rest of the sites in the new, enlarged site tree are
“unaware” of the changes until the next replication.

Chapter 6 121
 Maintaining sites
Splitting a site tree

Splitting a site tree

You may have a large site tree that you want to split into two or more
smaller site trees. You do this by deciding which site in the existing tree
will be the central site in the new tree, then you remove that site from
the existing tree. The new central site and all the sites under it make up
the new tree.
The site you remove becomes a new central site.

NOTE Before splitting a site tree, make sure that replication has completed
between the child site that you want to be the central site of the new site
tree and its current parent site. The first half of the procedure below
explains how to do this.

To split a site tree

Step 1. Disable the data scanning and transfer schedule at the child site by
doing the following:

a. Select SITE from the Console Configure menu, then highlight the new
parent Primary site from the Site Tree page.

b. Click Properties and select the Replication tab.

c. Click Properties from the Data Scanning Schedule group box to
display the Data Scanning Schedule dialog.

d. Select the option to disable data scanning and click OK.

e. Click Apply and close the Replication page.

Step 2. Wait half a day or until all data rolls up to the parent site.

• Check the Software Distribution logs at the parent site to verify that
any distribution jobs intended for the child site have completed.

122 Chapter 6
 Maintaining sites
Splitting a site tree

• If the child site is a Primary, check child site server

\\HPDTA\DATA\BIN.IN directory to make sure all .RTF
transaction files have replicated to the parent site.

• If the child site is a Satellite, check child site server

\\HPDTA\DATA\BIN.IN directory to make sure all agent
transaction files have replicated to the parent site.

If files still remain in the \BIN.IN directories after half a day, wait
overnight, and check again.
Step 3. Make sure all distribution jobs have run at the child site where you plan
the split.

Step 4. Stop all DTA agents and managers through the SmartDeploy agent at all
sites, using the Console Control Agents and Control Managers pages.
(From the Console, select the Task menu, then choose CONTROL AGENTS
and CONTROL MANAGERS to access these pages, respectively.)

Step 5. Disable the data scanning schedule at the current parent Primary site by
doing the following:
a. Select SITE from the Console Configure menu, then highlight the new
parent Primary site from the Site Tree page.

b. Click Properties and select the Replication tab.

c. Click Properties from the Data Scanning Schedule group box to

display the Data Scanning Schedule dialog.
d. Select the option to disable data scanning and click OK.

e. Click Apply and close the Replication page.

Step 6. In the Site Tree page, highlight the child site that you want to be the
central site of the new site tree.
Step 7. On the Site Tree page, select the site to be the new central site and click
Remove.

Step 8. Click Yes. The site and all the sites under it are removed from the
original site tree.

Step 9. Restart the DTA managers and agents through the SmartDeploy agent,
as described in step 4.

Chapter 6 123
 Maintaining sites
Splitting a site tree

Step 10. Enable the data scanning and transfer schedules that were disabled in
Steps 1 and 5.

The changes take effect immediately at the site where you performed the
split operation and at the top of the new site tree (that is, the new central
site). The rest of the sites in the two trees are “unaware” of the changes
until the next replication cycle.

124 Chapter 6
 Maintaining sites
Deleting sites

Deleting sites
To delete a site from a site tree, first remove the site from the tree and
then delete the DTA software from the servers and managed computers
at the site.
If the site you are deleting does not have child sites under it, you can
remove the site and immediately uninstall the software.
If the site you are deleting has child sites under it, you must remove the
parent site’s immediate children from the tree before you uninstall the
software from the parent site. Otherwise, you will not be able to
successfully reattach the child sites to the tree.

To delete a site from a site tree

Step 1. Make sure all distribution jobs have run at all sites.

Step 2. Disable the data scanning schedule at the Primary parent site of the site
to be deleted by doing the following:

a. Select SITE from the Console Configure menu, then highlight the
Primary parent site from the Site Tree page.

b. Click Properties and select the Replication tab.

c. Click Properties from the Data Scanning Schedule group box to

display the Data Scanning Schedule dialog box.

d. Select the option to disable data scanning and click OK.

e. Click Apply and close the Replication page.

f. If the site you are deleting is a Satellite, skip to Step 5.

Step 3. If the site you are deleting is a Primary, highlight it in the Site Tree
page.

Chapter 6 125
 Maintaining sites
Deleting sites

Step 4. Disable the data scanning and transfer schedule of the site to be deleted
by doing the following:

a. Repeat steps 2b through 2d above.

b. In the Transfer Schedule group box of the Replication page, select the
option to disable data transfer.

c. Click Apply and close the Replication page.

Step 5. Wait half a day or until all data rolls up to the parent site.

• Check the Software Distribution logs at the parent of the site you are
deleting to verify that any distribution jobs intended for the child site
have completed.

• If the site you are deleting is a Primary, check the child site server
\\HPDTA\DATA\BIN.IN directory to make sure all .RTF
transaction files have replicated to the parent site.

• If the site you are deleting is a Satellite, check the child site server
\\HPDTA\DATA\BIN.IN directory to make sure all agent
transaction files have replicated to the parent site.

If files still remain in the \BIN.IN directories after half a day, wait
overnight, and check again.

Step 6. Stop all DTA agents and managers (at both the site to be deleted and its
parent) through the SmartDeploy agent, using the Console Control
Agents and the Control Managers pages. (From the Console, select the
Task menu, then choose CONTROL AGENTS and CONTROL MANAGERS,
respectively, to access these pages.)
Step 7. Access the Console at the parent of the site you want to delete.

Step 8. Choose SITE from the Configure menu.

Step 9. On the Site Tree page, select the site to be deleted and click Remove.
Step 10. Click Yes.

The site and all the sites under it are removed from the original site tree,
but they are still active DTA sites.

Step 11. Restart the DTA managers and agents (at both the site to be deleted and
its parent) through the SmartDeploy agent.

126 Chapter 6
 Maintaining sites
Deleting sites

Step 12. Enable the data scanning and transfer schedules that were disabled.

Step 13. Wait until removal is propagated throughout the site tree. (To confirm
that information has been replicated, check the \BIN.IN directory for
sites belonging to the deleted branch.)

Step 14. If the deleted site has any children, delete them from the tree by
repeating the steps above before you remove the software.

After you finish deleting the site, you can reattach the “orphan” sites to
the tree if you wish.
Step 15. Remove the DTA software (agents, managers, Console, and data) from
the servers and managed computers at the deleted site. For instructions
on deleting DTA software, see Appendix A , “Removing DTA,”.

Step 16. If you want to reattach the child sites of the site you just deleted, from
the Site Configuration dialog box, select the site in the tree that you
want to be the new parent and merge the disconnected tree. See
“Merging DTA 5.0 site trees” on page 120 in this chapter for instructions.

Chapter 6 127
 Maintaining sites
Renewing expired DTA accounts

Renewing expired DTA accounts

Occasionally, network accounts that DTA requires expire. After these
accounts are renewed, DTA must be instructed to use them again.
If the Site server, DBMS, or DTA Managers account expires or changes,
first renew those accounts, then use the DTA NACCESS tool to renew
them with DTA.
For more information on the Site server, DBMS, or DTA Managers
accounts, see Chapter 3, “Resource requirements,” on page 27

To renew an expired DBMS account

Step 1. From the Site Configuration dialog box, select the site for which the
DBMS account has expired.

Step 2. Select PROPERTIES and then click DATABASE, to display the Database
page.

Step 3. Enter the new account information.

This procedure saves the new account information into the database and
updates the registry information for the management server for this site.
In the event that the registry information does not get updated, you can
manually update the management server registry information by
running NACESS /prompt:DBMS from the management server command
line to display the DTA NACESS tool and enter the account information.

To renew an expired Site server account

Step 1. Run NACESS /prompt:SITE from the management server command line
to display the DTA NACESS tool.

Step 2. Enter the new account information.

128 Chapter 6
 Maintaining sites
Renewing expired DTA accounts

To renew an expired DTA Managers account

Step 1. Run NACESS /prompt:NTSVC from the management server command

line.

Step 2. From the Control Panel, go to the Services Control Manager.

Step 3. For each of the following services, click STARTUP and enter the account
information:
• DTA Replication Service

• DTA Server Inventory Server.

Chapter 6 129
 Maintaining sites
Launching a program remotely

Launching a program remotely

DTA lets you launch applications on managed computers at Primary and
Satellite sites. You can use the remote launch feature, for example, to
launch pcANYWHERE on a managed computer.
Remote program launches are controlled by the SmartDeploy agent.
Programs launch according to the SmartDeploy agent polling cycle, that
is, when the SmartDeploy agent checks its configuration file for new
instructions.
You can configure the polling cycle through the Console, in the
SmartDeploy Agent Configuration page. See “Configuring the
SmartDeploy agent” on page 142.

To launch a program on a managed computer

Step 1. Select COMPUTERS from the Console Browse menu to display the
Computers viewer.

Step 2. From the viewer, select the computer on which to launch the program.

130 Chapter 6
 Maintaining sites
Launching a program remotely

Step 3. Do one of the following:

• Right-click the computer and select LAUNCH PROGRAM.

• Select LAUNCH PROGRAM from the Computers menu.

Figure 6-14 Program Launch Request dialog box

Step 4. Type the pathname of the program you want to launch on the target
computer. If you use a drive letter, the pathname must be the same at the
target computer.
Step 5. Select Launch to enable the remote launch of the application.

The program will start on the target computer within the SmartDeploy
agent polling cycle, as reported in the dialog.

Step 6. Click Close when the program has launched. The Launch Status must
report success or failure before you can launch a program on the next
computer. You can minimize the dialog while waiting for a status.

Chapter 6 131
 Maintaining sites
Installing an additional Console

Installing an additional Console

By default, DTA installs the Console to the management computer and
site server. However, you can install as many Consoles as necessary to a
site.
Consoles must be installed on computers running Windows NT 4.0 (SP4
or higher). See Chapter 3, “Resource requirements,” on page 27 for more
information on Console requirements.

To install a Console to another computer

Step 1. At the computer to which you want to install the additional Console, do
one of the following:

• Map a drive to the site server \HPDTA\CONSOLE directory and run

SETUP from the run line, using that drive letter path.

• Run SETUP from the run line, using the UNC path to the site server
\HPDTA\CONSOLE directory.

Step 2. Click Next until the program displays the Console Type dialog

Figure 6-15 Console Type dialog box

132 Chapter 6
 Maintaining sites
Installing an additional Console

Step 3. Select the Local or Network option. The Local option installs all Console
files to the local hard disk of the computer. The Network option installs
only the ODBC driver to the local hard disk, and runs the Console from
the site server.

Step 4. Click Next to review the location where DTA will install the files. To
change the location, click Browse and select another directory.

Step 5. Click Next to review your install settings.

Step 6. Click Next to copy the files.

Step 7. Do one of the following:

• Click Finish to complete the installation and launch the newly

installed Console

• Uncheck the launch box and click Finish to complete the installation
without launching the newly installed Console.

Chapter 6 133
 Maintaining sites
Moving managers

Moving managers
Managers install allows you to re-install the DTA managers on a new
computer after the site has been installed. This should be done only in
situations where it is absolutely necessary to do so, such as when the
existing management server is becoming inoperable.
Since DTA only allows one instance of the managers to be active at any
time, the managers install incorporates both a new managers install and
an old managers uninstall in one step. It is not necessary to uninstall the
old managers prior to installing the new one. Managers install can be
used to install to the current computer or to a remote computer. However
it is recommended to run it from the computer being installed to.

To move managers to another computer

Step 1. Execute SETUP.EXE in the site \CONSOLE directory and choose

MANAGERS.

Step 2. Specify the computer and share name to install to.

Step 3. Enter the account name and password needed to run as services.

Step 4. Enter the Database username and password.

Managers install will then copy and install to the new management
server, and then stop and uninstall the managers from the old
management server in one process. If the old management server is not
on at the time of the move, you must separately uninstall the old
managers when the computer is available.

134 Chapter 6
 Maintaining sites
Adding an application

Adding an application
You can add an application to DTA, such as pcANYWHERE, by running
SETUP.EXE from the DTA CD or from the site server \HPDTA\DATA
directory. SETUP.EXE runs a wizard that steps you through the process
of performing a Custom installation of DTA, which allows you to add an
application.

To add an application

Step 1. From the DTA CD or the site server \HPDTA\DATA directory, run
SETUP.EXE.

Step 2. Follow the wizard until the Setup Type page appears, and then select
the Custom option to install selected components.

Figure 6-16 Setup Type page

Chapter 6 135
 Maintaining sites
Adding an application

Step 3. In the Site Server Location page, select a destination directory.

Figure 6-17 Site Server Location page

Step 4. In the Select DTA applications page, select the applications you want to
add.

Figure 6-18 Select DTA applications page

136 Chapter 6
 Maintaining sites
Adding an application

Step 5. Database User Access Account page, enter the user name and password
to connect with the SQL database.

Figure 6-19 Database User Access Account page

Step 6. In the Setup Review page, confirm the components you want to install by
clicking Next.

Figure 6-20 Setup Review page

Chapter 6 137
Maintaining sites
Adding an application

138 Chapter 6
7 Managing the SmartDeploy
agent

139
Managing the SmartDeploy agent
SmartDeploy agent features

SmartDeploy agent features

DTA provides the SmartDeploy agent to ease deployment and
maintenance of the DTA managers and application agents.
You use the SmartDeploy agent to install the DTA application agents
and, once installed, control them. You also use the SmartDeploy agent to
control the DTA manager and Site manager.
The SmartDeploy agent includes these major features:

• Self-installing—When you configure the SmartDeploy agent through

a wizard during DTA installation, the SmartDeploy agents installs
itself on managed computers (or on the server, if you have configured
it to run that way).
• Self-repairing—If any component of the SmartDeploy agent becomes
corrupted, or is missing, the agent repairs itself automatically,
without any needed intervention from the system administrator.
• Centrally controls managers and application agents—After
installation, when you have set up the managed computers to launch
agents, you can use the SmartDeploy agent to centrally start, stop,
remove, upgrade, and schedule the DTA managers or application
agents running on managed computers at the site. You can do this
through the Console.

140 Chapter 7
 Managing the SmartDeploy agent
SmartDeploy agent installation

SmartDeploy agent installation

During DTA installation, DTA provides a SmartDeploy agent wizard the
guides you through configuration for the agent. This wizard starts the
first time a Console is launched.
After you complete the wizard, you set up computers to run the
SmartDeploy agent so it can install and run on the managed
workstations.
The wizard and the steps you take to set up the managed workstations
are covered in Chapter 8, “Adding a site,” on page 167.

NOTE DTA does not provide a SmartDeploy agent wizard for Satellite sites as
they don’t have Consoles. Satellite sites inherit SmartDeploy
configuration settings from their managing Primary sites. You can,
however, change the inherited settings by using the Console
configuration pages, as described in “Configuring the SmartDeploy
agent” on page 142.

Chapter 7 141
Managing the SmartDeploy agent
Configuring the SmartDeploy agent

Configuring the SmartDeploy agent

At the end of DTA Setup, DTA prompts you to start the SmartDeploy
agent wizard. This wizard contains the configuration options that specify
how and where the SmartDeploy agent runs. The DTA Console provides
these same configuration options with an added scheduling page. For
more information on completing the SmartDeploy agent wizard, see
“Running the SmartDeploy agent wizard at Primary sites” on page 192.
The SmartDeploy agent configuration pages you access through the
Console are covered in the following sections.

SmartDeploy agent configuration pages

To access the SmartDeploy agent configuration pages, choose
SMARTDEPLOY AGENT from the Console Configure menu. A Property
sheet displays showing three configuration tabs containing configuration
options. These pages are in the sections below.

142 Chapter 7
 Managing the SmartDeploy agent
Configuring the SmartDeploy agent

Run Options page

Figure 7-1 shows the run options for the SmartDeploy agent.

Figure 7-1 SmartDeploy agent Run Options

The run options are described below.

SmartDeploy Agent Location
In the SmartDeploy agent wizard during DTA installation, you select one
of the following two options to specify where and how you want the
SmartDeploy agent to run (The application agents automatically
configure to run the same way.):

• Run From Agents Directory On Site Server (disabled): This option

stores and runs the agent from the \AGENTS directory on the site
server. Storing agents on the server saves local hard disk space on the
managed computers, however, more bandwidth is required to run the
agent across the network.

Chapter 7 143
Managing the SmartDeploy agent
Configuring the SmartDeploy agent

After the agents are installed on the managed computers, these

options are disabled. If you need to switch the run from location, use
the procedure “To switch the way SmartDeploy agent runs” on page
163.
• Store And Run From Local Disk On Managed Computers (default)
(disabled): This option stores and runs the agent from the local hard
disk of each managed computer. Storing agents locally is the most
stable approach, because it ensures that if the server fails, DTA
agents can still run on the workstations. Choose this option for laptop
computers; otherwise, laptop users will receive a page fault error
when they unlock their laptops.
After you set up the managed computers (by editing the login script
or policy files of the login server), DTA installs and runs the
SmartDeploy agent from the Windows install directory (for example,
C:\WINDOWS) of \HPDTA\AGENTS directory of the local hard
disks.
Once you choose this option, you cannot change it unless you follow
the procedure, “Switching the way SmartDeploy agent runs” on page
163.
Run As Service On Windows NT Computer: Instructs the SmartDeploy
agent to install and run as an NT System Service on managed NT
computers. Running agents as a Service provides you with the following
differences in functionality:

• Agents assume the same access rights as the account used for login by
the NT System Services. NT System Services may have control over
certain operations on NT workstations that otherwise are not
available.
• End-users do not have to be logged onto the managed computers for
NT System Services to work.
• NT System Services run invisibly, and as such, do not display
workstation messages to end-users, as can agents running as
application executables.
• In environments with combinations of Windows NT, 2000
Professional, or Windows 9x computers, you can select the checkbox
and DTA will install the agent as a service on NT and 2000
Professional computers and as an application executable on Windows
9x computers.

144 Chapter 7
 Managing the SmartDeploy agent
Configuring the SmartDeploy agent

NT account information
If you have selected to run agents as NT System Services, you must
supply an NT System Services account for the SmartDeploy agent, so it
can run with the correct access rights on managed computers. This
account should be set up before you install DTA.
If any changes are made to the SmartDeploy agent account after initial
DTA Setup, you must reflect those changes here. For more information
on this account, see the SmartDeploy agent account section in Chapter 3,
“Resource requirements,” on page 27
If you are using a Domain administrator account for this account, specify
the NT User name as follows:
Domain_name\user_name
If you are running agents on workstations in a Windows NT Workgroup
environment, specify the NT User name as follows:
.\user_name
Use Same Account To Access DTA Site Server: Along with an NT System
Service account, the SmartDeploy agent requires an account has access
to the DTA site server. If the user name and password you use for your
Site Server account is the same as the one for the SmartDeploy agent
account, leave the checkbox to use the same account to access the DTA
Sites Server selected. Otherwise, uncheck the box and enter the user
name and password for the Site Server account. If you have installed
DTA on a NetWare server, clear the checkbox.

Chapter 7 145
 Managing the SmartDeploy agent
Configuring the SmartDeploy agent

Configuration page
Figure 7-2 shows the configuration options for the SmartDeploy agent.

Figure 7-2 SmartDeploy agent Configuration options

The configuration options are described below.

SmartDeploy Agent Settings
You can modify how the SmartDeploy agent runs with the following
settings:

• Check Every n Minute(s) For Smartdeploy Agent Changes: Specifies

the number of minutes the SmartDeploy agent polls its configuration
file, SAGENT.INI, for new or changed configuration information.
Configuration information can be instructions to stop, start, remove,
or update agents. Or it can also be any changes you make to the Run
Options or Configuration pages.

146 Chapter 7
 Managing the SmartDeploy agent
Configuring the SmartDeploy agent

• Wait n Second(s) Before Starting DTA Applications: Specifies the

number of seconds SmartDeploy agent waits before starting the
application agents on managed computers. You may want to specify
an interval if the managed computers have a number of applications
running on them.
For example, if you have set up managed computers to perform virus
scans of their boot drives every time users log onto them, you might
want to delay the SmartDeploy agent five minutes or longer to let the
scans complete. You might also want to delay the SmartDeploy if your
network maps multiple drives when users first log onto their
computers. Because drive mapping during logon can often be a
lengthy process, delaying the SmartDeploy agent three or four
minutes will allow the mapping process to complete before another
process begins.
• Minimum Required Connection Speed Between Managed Computer
And DTA Site Server: Specifies the slowest speed in bits per second at
which the SmartDeploy agent can work.
• Run SmartDeploy Agent Hidden: Instructs the SmartDeploy agent
not to appear in the system tray on managed computers. If this option
is selected, you must reboot to enable the option.The agent always
displays in the system tray on the management server.
Deployment Settings
Deployment settings allow you to specify the number of nodes at a given
site and the amount of network bandwidth to use to install the agents to
them. After DTA is installed, you may have computers you want to add
to a site.
• No. Of Computers Managed At This Site (Approximately): Lets you
specify the approximate number of computers you want DTA to
manage at a site. If you are adding computers to a site, specify the
total number of managed computers, adding the new ones to the old
ones. For example, if you already have 100 managed computers at the
site and want to add 25, specify 125 in the box.

Chapter 7 147
Managing the SmartDeploy agent
Configuring the SmartDeploy agent

• Approximate Bandwidth Usage: Lets you set the available bandwidth

that DTA can use to deploy the agents to managed computers at a
site.
• Estimated Deployment Time (Approximately): Read-only. After you
have specified the number of computers to be managed at the site and
the amount of bandwidth to use, calculates and displays the
approximate maximum time DTA will require to install agents to
each managed computer, once each computer is logged onto the
network.

148 Chapter 7
 Managing the SmartDeploy agent
Controlling managers and application agents

Controlling managers and application agents

The SmartDeploy agent can start, stop, or remove DTA managers,
application agents, or itself.

Controlling agents on managed computers

To stop, start, or remove the SmartDeploy agent or other application
agents running on managed computers, select CONTROL AGENTS from the
Console Tasks menu.

Figure 7-3 Control Agents page

The options for controlling the agents that run on managed computers
are described below. Basically, you can control all applications through
the SmartDeploy agent by using the settings in the SmartDeploy Agent
group box, or you can control specific application agents through the
settings in the Application Agents group box.

Chapter 7 149
Managing the SmartDeploy agent
Controlling managers and application agents

SmartDeploy Agent group box

You can start and stop the SmartDeploy agent on all managed computers
at a site, or you can remove it from all managed computers. If you want
to remove the SmartDeploy agent on selected managed computers at a
site (rather than all of them), you can do so by using the Remote Service
Installer. For instruction on using the Installer, see “Using RSI to install
the SmartDeploy agent to selected computers” on page 204. When you
start, stop, or remove the SmartDeploy agent, it also starts, stops, or
removes all of the application agents running on managed computers. (It
does not stop, start, or remove any agents running on the management
server, however.)

• Start: Enables the SmartDeploy agent and all application agents to

start running on all managed computers at a site, but only after the
SmartDeploy agent has queried its configuration file (SAGENT.INI)
for the new instructions to start.
• Stop: Enables the SmartDeploy agent and all application agents to
stop on all managed computers at a site. Again, the SmartDeploy
agent and the application agents only stop after the SmartDeploy
agent has queried for the new instructions to stop.
• Remove: Enables the SmartDeploy agent to remove itself and all
application agents from all managed computers at a site. The
SmartDeploy agent only removes itself and the application agents
after it queries its configuration file for the instruction.
Application Agents group box
If you want control individual agents, rather than having the
SmartDeploy agent control all agents globally, you can do so with this
group box. However, any setting you make in the SmartDeploy Agent
group box above override the settings you make in this group box.

• Enable: Enables the agent you select in the list box to start on all
managed computers at a site, but only after the SmartDeploy agent
gets the instruction to start from its configuration file.
• Disable: Enables the agent you select in the list box to stop on all
managed computers at a site, but only after the SmartDeploy agent
gets the instruction to stop from its configuration file.
• Schedule: Displays the Schedule dialog box to set run times and
frequency settings for the selected agent. See “Setting schedules for
the application agents” on page 155.

150 Chapter 7
 Managing the SmartDeploy agent
Controlling managers and application agents

• Uninstall The Application Agents: Removes all application agents,

but not the SmartDeploy agent. The SmartDeploy agent removes the
application agents from running on managed computers only after it
gets the instruction from its configuration file.
• Install The Application Agents (If They Were Previously Uninstalled):
Installs all previously uninstalled application agents. Use this option
only to re-install all application agents. It does not re-install the
SmartDeploy agent. The SmartDeploy agent installs application
agents only after it gets the instruction from its configuration file.
You can set how often the SmartDeploy agent queries for new
instructions from its configuration file in the SmartDeploy Agent
Configuration page in the Console. For more information on this setting,
see “Configuration page” on page 146.

Chapter 7 151
 Managing the SmartDeploy agent
Controlling managers and application agents

Controlling managers and agents on the management

server
To stop, start, or remove the SmartDeploy agent, DTA manager, Site
manager, Server Distribution agent, or Server Inventory agent running
on the management server, select CONTROL MANAGEMENT SERVER from
the Console Tasks menu.

Figure 7-4 Control Management Server page

The options for controlling the managers and agents that run on the
management server are described below.

152 Chapter 7
 Managing the SmartDeploy agent
Controlling managers and application agents

SmartDeploy Agent
You can enable the SmartDeploy agent, managers and server agents to
run on the management server, or you can disable them from running. If
you want to control a specific manager or server agent rather than all of
them at once, use the settings in the Services group box, described below.

• Start: Enables the SmartDeploy agent, managers, and the server

agents to start running on the management server. Server agents and
managers start running only after the SmartDeploy agent does. The
SmartDeploy agent does not start running until you restart the
management server after setting this option and, once started, only
after it queries its configuration file (SAGENT.INI) for the new
instructions to start.
• Stop: Enables the SmartDeploy agent, managers, and the server
agents to stop running on the management server. The SmartDeploy
agent does not terminate managers and server agents until it queries
its configuration file (SAGENT.INI) for the new instructions to stop.
After it stops the managers and server agents, it terminates itself.
Services group box
If you want to control individual managers or server agents, rather than
having the SmartDeploy agent control them as a group, you can do so
with this group box. However, any setting you make to the SmartDeploy
Agent group box above override the settings you make in this group box.

• Enable: Enables the manager or server agent you select in the list box
to start on the management server, but only after the SmartDeploy
agent gets the instruction to start the manager or agent from the
SmartDeploy agent configuration file.
• Disable: Enables the manager or server agent you select in the list
box to stop on the management server, but only after the
SmartDeploy agent gets the instruction to stop the manager or agent
from the SmartDeploy agent configuration file.
• Schedule: Displays the Schedule dialog box for the selected manager
or server agent. See “Setting schedules for DTA Services” on page
159.

Chapter 7 153
Managing the SmartDeploy agent
Controlling managers and application agents

You can set how often the SmartDeploy agent queries for new
instructions from its configuration file in the SmartDeploy Agent
Configuration page in the Console. For more information on this setting,
see “Configuration page” on page 146.

154 Chapter 7
 Managing the SmartDeploy agent
Setting schedules for the application agents

Setting schedules for the application agents

You can schedule when you want the Software Distribution agent to stop
running. You can also schedule how often the hardware and software
inventory agents perform scans on managed computers.

NOTE To schedule how often the Software Distribution agent polls for jobs, see
the Software Distribution Guide.

To set schedules for the DTA application agents

Step 1. At the management server of the site for which you want to schedule the
agents, select HP OPENVIEW DESKTOP ADMINISTRATOR CONSOLE from
the Start menu Programs group.

Step 2. Select CONTROL AGENTS from the Tasks menu.

Figure 7-5 Control Agents dialog box

Chapter 7 155
 Managing the SmartDeploy agent
Setting schedules for the application agents

Step 3. In the Application Agents group box, highlight Distribution from the list,
if you want the Software Distribution agent to stop running for a period
of time. Otherwise, skip to step 7.

Step 4. Click Schedule.

Figure 7-6 Schedule dialog box

Step 5. Select how often you want the Software Distribution agent to run on the
managed computers at the site. Depending on the Execution Frequency
you select, other frequency settings, such as Day and Hour may be
required.

• Never Stops: (Default) Continually runs the agent on managed

computers.

• Stops Daily: Instructs the agent to stop running once each day at the
hour and for the interval you specify.

• Stops Weekly: Instructs the agent to stop once a week on a day you
specify. You also specify the hour of the day and the period of time in
which you want the agent to stop running.

• Stop Monthly: Instructs the agent to stop once a month. You specify
the day of the month, the hour of the day, and the period of time in
which you want the agent to stop running.

• Stop Quarterly: Instructs the agent to stop once a month. You specify
month 1, 2, or 3 of the quarter. You can also indicate the day of the
month, the hour of the day, and the period of time in which you want
the agent to stop running.

156 Chapter 7
 Managing the SmartDeploy agent
Setting schedules for the application agents

• Stop Semiannually: Instructs the agent to stop once every six months.
You specify a month from 1 to 6. You can also indicate the day of the
month, the hour of the day, and the period of time in which you want
the agent to stop running.

• Stop Annually: Instructs the agent to stop once a year. You specify a
month from 1 to 12. You can also indicate the day of the month, the
hour of the day, and the period of time in which you want the agent to
stop running.

Step 6. Click OK to return to the Control Agents dialog box. The agent’s new
schedule displays in the Schedule column of the list. (You may have to
scroll to see it.)
Step 7. Highlight Hardware Inventory in the list and click Schedule.

Figure 7-7 Schedule dialog box

Step 8. Select how often you want the Inventory agent to perform hardware
scans on the managed computers at the site. Depending on the Execution
Frequency you select, other frequency settings, such as Day and Hour
may be required.

• Runs Daily: (Default) Instructs the agent to perform hardware scans

once each day. You specify the earliest and latest times the agent can
start the scans.

• Always Runs: When SmartDeploy agent is running as an application,

the Inventory agent runs when the end-user logs on to the computer.
When the SmartDeploy agent is running as a service, the Inventory
agent starts when the end-user reboots the computer.

Chapter 7 157
 Managing the SmartDeploy agent
Setting schedules for the application agents

• Runs Weekly: Instructs the agent to perform hardware scans once a

week on the day you specify. You also specify the earliest and latest
times the agent can start scans.

• Runs Monthly: Instructs the agent to perform hardware scans once a

month on a day (1 to 30). You also specify the earliest and latest times
the agent can start the scans.

• Runs Quarterly: Instructs the agent to perform hardware scans once

every three months. You specify month 1, 2, or 3 of the quarter, the
day of the month (1 to 30), and the earliest and latest times the agent
can start the scans.
• Runs Semiannually: Instructs the agent to perform hardware scans
once every six months. You specify a month from 1 to 6, the day of the
month (1 to 30), and the earliest and latest times the agent can start
the scans.

• Runs Annually: Instructs the agent to perform hardware scans once a

year. You specify a month from 1 to 12, the day of the month (1 to 30),
and the earliest and latest times the agent can start the scans.

Step 9. Click OK to return the Control Agents dialog box. The agent’s new
schedule displays in the Schedule column of the list. (You may have to
scroll to see it.)
Step 10. Repeat steps 7 to 9 for Software Inventory.

Step 11. When done, click OK from the Control Agents dialog box.

158 Chapter 7
 Managing the SmartDeploy agent
Setting schedules for DTA Services

Setting schedules for DTA Services

You can schedule when you want the managers and the Server
Distribution agent to stop running for a period of time, for example,
during database or site backup. You can also schedule how often the
Server Inventory agent performs scans.

NOTE To schedule replication activity, see “Controlling replication activity” on

page 96. To schedule Server Distribution agent polling, see the Software
Distribution Guide.

To set schedules for DTA Services on the management server

Step 1. At the management server of the site for which you want to schedule the
services, select HP OPENVIEW DESKTOP ADMINISTRATOR CONSOLE from
the Start menu Programs group.

Step 2. Select CONTROL MANAGEMENT SERVER from the Tasks menu.

Figure 7-8 Control Management Server

Chapter 7 159
 Managing the SmartDeploy agent
Setting schedules for DTA Services

Step 3. In the Services group box, highlight Server Distribution Agent from the
list.

Step 4. Click Schedule.

Figure 7-9 Schedule dialog box

Step 5. Select how often you want the Server Distribution agent to stop running
on the management server. Depending on the Execution Frequency you
select, other frequency settings, such as Day and Hour may be required.
• Never stops: (Default) Continually runs the agent on the
management server.

• Stops Daily: Instructs the agent to stop running each day at the hour
and for the interval you specify.

• Stops Weekly: Instructs the agent to stop running once a week on a

day you specify. You also specify the hour of the day and the period of
time in which you want the agent to stop running.

• Stop Monthly: Instructs the agent to stop running once a month. You
specify the day of the month, hour of the day, and the period of time in
which you want the agent to stop running.

• Stop Quarterly: Instructs the agent to stop running once every three
months. You specify month 1, 2, or 3 of the quarter. You also specify
the day of the month, hour of the day, and the period of time in which
you want the agent to stop running.

160 Chapter 7
 Managing the SmartDeploy agent
Setting schedules for DTA Services

• Stop Semiannually: Instructs the agent to stop running once every six
months. You specify a month from 1 to 6. You also specify the day of
the month, hour of the day, and the period of time in which you want
the agent to stop running.

• Stop Annually: Instructs the agent to stop running once a year. You
specify month from 1 to 12. You also specify the day of the month,
hour of the day, and the period of time in which you want the agent to
stop running.

Step 6. Click OK to return to the Control Management Server page. The agent’s
new schedule displays in the Schedule column of the list. (You may have
to scroll to see it.)
Step 7. Repeat steps 3 to 6 for DTA Manager and Replication Manager.

Step 8. Highlight Server Inventory Agent in the list and click Schedule.

Figure 7-10 Schedule dialog box

Step 9. Select how often you want the Server Inventory agent to perform
software scans on the management server. Depending on the Execution
Frequency you select, other frequency settings, such as Day and Hour
may be required.

• Runs Daily: (Default) Instructs the agent to perform hardware scans

once each day. You specify the earliest and latest times the agent can
start the scans.

• Always Runs: When SmartDeploy agent is running as an application,

the Server Inventory agent runs when the end-user logs on to the
computer. When the SmartDeploy agent is running as a service, the
Server Inventory agent starts when the end-user reboots the
computer.

Chapter 7 161
 Managing the SmartDeploy agent
Setting schedules for DTA Services

• Runs Weekly: Instructs the agent to perform software scans once a

week on the day you specify. You also specify the earliest and latest
times the agent can start scans.

• Runs Monthly: Instructs the agent to perform software scans once a

month on a day (1 to 30). You also specify the earliest and latest times
the agent can start the scans.

• Runs Quarterly: Instructs the agent to perform software scans once

every three months. You specify month 1, 2, or 3 of the quarter, the
day of the month (1 to 30), and the earliest and latest times the agent
can start the scans.
• Runs Semiannually: Instructs the agent to perform software scans
once every six months. You specify a month from 1 to 6, the day of the
month (1 to 30), and the earliest and latest times the agent can start
the scans.

• Runs Annually: Instructs the agent to perform software scans once a

year. You specify a month from 1 to 12, the day of the month (1 to 30),
and the earliest and latest times the agent can start the scans.

Step 10. Click Ok to return to the Control Management Server dialog box. The
agent’s new schedule displays in the Schedule column of the list. (You
may have to scroll for it.)
Step 11. When done, click OK from the Control Management Server dialog box.

162 Chapter 7
 Managing the SmartDeploy agent
Switching the way SmartDeploy agent runs

Switching the way SmartDeploy agent runs

You can configure SmartDeploy agent to run from the \AGENTS
directory on the site server or to run from the local disk of the managed
computer.

To switch the way SmartDeploy agent runs

Step 1. Select CONTROL AGENTS from the Console Tasks menu.

Figure 7-11 Control Agents page

Step 2. In the SmartDeploy Agent area of the Control Agents page, select the
Remove option.

Step 3. Verify that the agents have been removed.

Chapter 7 163
 Managing the SmartDeploy agent
Switching the way SmartDeploy agent runs

Step 4. Delete the SAGENT.LOG file from the site server \DATA\SAGENT
directory.

The log file contains a list of all of the computers that had SAGENT
installed on them.

Step 5. Select SMARTDEPLOY AGENT from the Console Configure menu.

Step 6. In the SmartDeploy Agent Configuration dialog box, select the Run
Options page.
Step 7. In the SmartDeploy Agent Location group box, select how you want
SmartDeploy agent to run, and then click OK.

Smart Deploy agent will install the new configuration the next time it
queries for configuration changes.

164 Chapter 7
 Managing the SmartDeploy agent
SmartDeploy agent problems and solutions

SmartDeploy agent problems and solutions

Solutions to known problems are described in the following sections.

Installed program does not appear

SmartDeploy agent is installed on a managed computer, but it does not
appear.

Solution
Check the following:

• In the DTA Console, select CONTROL AGENTS from the Tasks menu. In
the SmartDeploy Agent group box of the Control Agents dialog box,
make sure the Start option is selected.
• If the SmartDeploy agent is configured to run as a Service, make sure
you can log on to the current computer with the same NT account
information listed in the NT Account Information group box of the
SmartDeploy Agent Configuration dialog Run Options page.
• Make sure you have administrative privileges on the managed
computer. If you do not have administrative privileges and logon to
the NT computer with a normal user account privileges,
SAGENT.EXE fails to install and creates an entry in the
NTTARGET.LOG file located in the site server \DATA\SAGENT
directory. The SmartDeploy agent on the management server will
target and perform installation to the computer listed in the
NTTARGET.LOG file.
• If the SmartDeploy agent did not install completely, run
DTACLEAN.EXE from the site server \CONSOLE directory to
remove the SmartDeploy agent from the service control and registry
keys.

Chapter 7 165
Managing the SmartDeploy agent
SmartDeploy agent problems and solutions

Fails to launch error message

In the SmartDeploy Agent Status window, you get the error message:
Fails to launch xxxxxx.exe error=8nnnnnnn.
The status window is accessed by clicking the SmartDeploy agent icon in
the windows task bar.
The problem is the component did not properly register.

Solution
Delete the Build # registry key using the Regedit registry editor.

1. In the Registry Editor dialog box, go to the following directory:

HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\DTA\5.0
\SAGENT\BUILD #
2. Delete the Build # registry component.
SmartDeploy agent will register the component in the next polling
cycle.
This solution can only be performed at the computer that is
displaying the error; you cannot perform this procedure remotely.

166 Chapter 7
8 Adding a site

167
Adding a site
Assumptions

Assumptions
This chapter assumes you have already installed an initial, central site
according to your deployment planning. Initial site installation is covered
in deployment training. For more information on obtaining deployment
training and assistance, see Chapter 1, “About DTA Administration,” on
page 13.
This chapter also assumes that you have a deployment plan in place for
the additional sites you install in your environment.

168 Chapter 8
 Adding a site
Adding a child site

Adding a child site

You may decide at some point that you need to add site to your initial site
or tree. Two methods are available for adding a child site: remote install
and CD install.
For the remote install method, you add the site and then schedule when
you want DTA to copy the necessary files over the network to the new
site location.
For a CD install, you add a child site and then take your DTA CD to the
install computer at the added site to complete the site installation. (You
can also use an install directory on the network if you don’t want to use a
CD).
If you use the CD install method, you do not have to copy large quantities
of data across the network.

Chapter 8 169
 Adding a site
Adding a child site

See Table 8-1 for a list of the benefits and drawbacks of each method.
Table 8-1 Install method comparisons

Remote install

Benefits Least labor intensive; easier and quickest when installing

across a LAN link.

Drawbacks Must always consider bandwidth capacity must be

considered across WAN link. Frequently, installing
software across a WAN link is more time-consuming,
especially when the link is intermittent, unreliable, or is
handling traffic near capacity. Also, if remote install fails
during the copy process, someone must physically go to
the child site (or use a remote control solution) to resolve
the problem.

CD install

Benefits More efficient method when installing across WAN links

that are intermittent, unreliable, or whose network traffic
is near-capacity, or at least has bursts of traffic often
enough to warrant the link a repeatedly slow connection.
Slow connections can occur despite the line connection
speed. For example, a T1 line could be just as slow as a
128K line because of traffic bursts which slow the
connection speed.

Drawbacks Often more than one person is required (one at parent site,
another at the child site to perform the CD install). If no
one at the child site is able to perform the CD install, you
can alternatively use a remote control solution. A remote
control solution requires that someone at the child site
inserts the DTA Setup CD in the target install computer.

In general, you should perform a CD install any time you are installing
DTA software across a WAN link. If you are installing software across a
LAN link, a remote install may be easier and just as fast. In either
method, you must first add the site before installing it.
If you plan to install a satellite site across a WAN link, make sure to
install it in disconnected mode to obtain optimal performance.
The procedures for each method are described in the following sections.

170 Chapter 8
 Adding a site
Adding a child site

Before adding a child site

Before you begin the remote installation or CD installation procedure, be
sure that you have the following in place:
• The site ID for the site you want to add.
• The site server location of the \DATA, \CONSOLE, and \AGENTS
directories. If you want to install the site server to a shared directory
other than the default \HPDTA, first create that shared directory.
• If the site to be added is a Primary and you are not planning to install
the management or database server to the site server location, make
sure you know the computer names of those servers. If you want to
install the management or database server to a shared directory
other than the default \HPDTA directory, you must first create the
shared directory on those servers.
• If you are performing a CD installation, the DTA CD or a directory
containing a copy of it on the network.
• Access to the child site directories from the Console where you are
performing the Add procedure. To have access to these directories,
you must already have set up the user names and passwords at the
child site location for the following DTA accounts:
— DTA site server account
— DBMS user account (Primary child sites only). The DBMS account
cannot be the NT System Service account for the database; it must
be the SQL Server database account.
— Managers account (Primary child site only)
— SmartDeploy agents account.
• If the site to be added is a Primary and you plan to use the Microsoft
SQL Server DBMS with DTA, make sure an existing Microsoft SQL
Server DBMS is installed at the child site, with the DTA database
already set up. For information on setting up the DTA database, see
“System requirements” on page 28.
• The Microsoft SQL Client software installed on the management
server and database sever locations, as well as the server from which
you plan to perform the remote or CD installation.

Chapter 8 171
Adding a site
Adding a child site

• Version 3.5 of ODBC Manager installed on the management server

and database server locations at the child site. If you have a version
other than 3.5 installed, the installation fails. (If no Manager is
installed, DTA installs the correct version automatically.)
• If you are adding a child site to a Domain that is different than the
parent Domain, and your organization does not use master, or
account domains, you must do the following:
— Set up a two-way trust relationship between the domains.
— Add the parent site server account (which is either an
Administrator account prefaced by the parent site Domain) to the
Domain Admin or Administrators group at the child site Domain.
(Alternatively, you can add the child site server account to the
Domain Admin or Administrators group as the parent site
Domain.)
— Restart the Primary Domain Controller (PDC) at the Domain to
which you added the account.
— To add the site, log into Parent site Domain using the account you
just added.
For more information on account requirements, see Chapter 3, “Resource
requirements,” on page 27

Performing a remote installation

The basic steps to a remote installation are as follows:

• Add the site

• Install the site across the network, according to the schedule you set.
The site installs according to your schedule. You add and install the child
site from the Console of the parent site. These steps are covered below.

172 Chapter 8
 Adding a site
Adding a child site

To add the site

Step 1. At the Console of the parent site, select SITE from the Configuration
menu to display the Site Configuration dialog.

Figure 8-1 Site Tree page

Chapter 8 173
 Adding a site
Adding a child site

Step 2. Select the site to which you want to add the child, and then click Add.

Figure 8-2 Add Site page

Step 3. Enter the basic identifying information about the new site: a unique ID,
name, and a brief description. Description is optional.
Step 4. Select a time zone.

Time Zone defaults to the time zone of the parent site to which you are
connecting the new site. Change this value if the time zone of the site you
are adding is different than the one to which it will be connected. Be
aware, however, that when data is replicated across time zones, the time
zone at the originating site is always used. For example, for jobs that are
distributed to a child site with a different time zone than the parent site,
the time stamp on it in the distribution log for that job will reflect the
time zone of the parent site, not the child site.

Step 5. If you do not want a Winsock connection between the parent site and the
workstations at the child site, check the Communication mode option to
run agents disconnected from managers. Typically, you select this
communication mode when installing a Satellite site to serve mobile
users.

174 Chapter 8
 Adding a site
Adding a child site

Step 6. Specify the parent and child site type.

• By default, the Parent Site selection displays the site you chose in the
Site Tree page. (You can change this entry if you want the new site to
be connected to a different parent.)

• In Site Type field, specify the type of site you are adding. See “Types
of sites” on page 50 for descriptions of site types.

Step 7. Click Next to choose the site server path at the child site.

Figure 8-3 Location page

Step 8. Choose BROWSE to select the UNC pathname of the destination directory
on the site server where you want to store the \CONSOLE, \AGENTS,
and \DATA directories.

You can choose a destination directory that has already been set up as a
shared directory, or you can let DTA automatically create \HPDTA as
the shared directory under the root directory by entering C$\HPDTA or
D$\HPDTA after the computer name, as appropriate.

Chapter 8 175
 Adding a site
Adding a child site

For example, if the computer name of the site server is LA_ADMIN and
the hidden root share is the C: drive, then you would enter the following
as the new site server path:

\\LA_ADMIN\C$\HPDTA

When you click Next to install the site server to the install computer.
DTA displays a message, reporting that it will automatically create an
HPDTA share for you, with full permission rights for all users.
Click Yes to accept this configuration, or No to return to the Site Server
Location screen and choose another UNC pathname.

You have the option of changing the \HPDTA directory name, but it is
not recommended.

Step 9. Leave the box to install the site by CD unchecked.

Step 10. Click Next

Figure 8-4 Direct Connect Configuration dialog box

Do one of the following:

• If you are adding the child site to the same Domain as the parent site,
enter the user name and password for the DTA site server account at
the parent site.

176 Chapter 8
 Adding a site
Adding a child site

• If you are adding site to a different Domain but your organization

does not use master, or account Domains, enter the account that has
the access to the child site. If it is a Domain Administrator account,
preface it by the Domain name. For example, if the Domain name is
DMSO-LP1 and the Domain Administrator account is Administrator,
you would enter:

DMSO-LP1\Administrator

• If you are in a Windows NT Workgroup environment, enter the user

name and password of the local Administrators account (it must be
synchronized), prefaced by “.\” For example, if the user name is
Administrator, you would enter:
.\Administrator

Step 11. Click OK to set the network type.

Figure 8-5 Network page

Chapter 8 177
 Adding a site
Adding a child site

Step 12. In the Network Operating System field, select the NOS of the site server
where you are placing a site.

If you select NetWare Directory Services (NDS) as the NOS, the NetWare
NLS (National Language Support) subdirectory must be in the search
path for both network administrators and users in order for DTA to work
with directory services. The default path is usually SYS:PUBLIC\NLS.

Step 13. If you are installing a Satellite site, skip to step 19; otherwise, click Next
to enter information about the DBMS at the child site.

Figure 8-6 Database page

Step 14. Specify database information:

• Select the database you are using at the child site from the Database
list box. If you are installing the bundled version of SOLID, also check
the box to install the database server.
• Enter the user name and password of the DBMS account for your
database. If you are installing the bundled version of SOLID DBMS,
DTA creates an account using the information you enter here.

178 Chapter 8
 Adding a site
Adding a child site

If you are using Microsoft SQL Server, the DBMS account must be the
account for the Microsoft SQL Server database rather than the NT
System Service account. You must also have the Microsoft SQL Client
software installed on the server from which you are installing the
DTA software; otherwise DTA will not be able to access Microsoft
SQL Server. See Chapter 3, “Resource requirements,” on page 27 for
more information on DBMS account requirements.

• As an option for the Microsoft SQL Server database, select Advanced

Settings to instruct DTA to connect to the database server using a
specific port other than the default 1313, or a static IP address
instead of the default setting of the server’s computer name
(connecting with a static IP address is typically fastest).

The following dialog box appears.

Figure 8-7 Advanced Connection Settings dialog box

To change the port setting, enter the new port in the Port field.
To specify a static IP address, select the option to use an IP address
and enter the static address in the IP Address field. (DTA does not
validate this address when you select OK to accept the new setting,
however it does verify that the address has been entered in the proper
format and displays an error message if the format is incorrect.)

To reset to default settings, click Defaults.

When done, Click OK.

Chapter 8 179
 Adding a site
Adding a child site

Step 15. Specify Database Server information:

By default, DTA displays the name and shared directory of the computer
you selected as the site server.

Keep the default setting to install the database server to the same
location as your site server, or browse to choose a different computer for
the database server. Enter the shared directory for that server.

If you are installing the bundled version of SOLID 3.0 for Windows NT,
DTA installs the \SOLID directory to this location.
Step 16. Click Next to display the replication schedules.

Figure 8-8 Replication page

Make sure the Transfer Method is set to Direct, otherwise the site
installation will fail.
It is not recommended that you change any replication settings at this
point. Use the default replication settings, which you can change later in
the Console Replication page, as necessary.

For more information on changing replication settings in the Console, see

“Controlling replication activity” on page 96.

180 Chapter 8
 Adding a site
Adding a child site

Step 17. Click Next to enter management server information.

Figure 8-9 Managers page

By default, DTA displays the name and shared directory of the computer
you selected as the database server.

You can leave the default setting to install the DTA managers to the
same location as your site server, or browse to choose a different
computer for the management server. Enter the shared directory for that
server.

DTA installs the \MANAGERS directory to the location you specify.

Step 18. Browse (...) to select a user name for the DTA managers account. Enter a
password.

The DTA Managers account is an NT System Service account. It allows

DTA managers to run on the management server.
If you installed the management server to a Primary Domain Controller
(PDC), the DTA Managers account must be a Domain Administrator
account. Enter the Domain Administrator User ID in the following
format;

Domain\UserID

Chapter 8 181
 Adding a site
Adding a child site

If you are installing the management server to a NT Workgroup

environment, the DTA managers account must have local administrator
rights. Enter the local administrator account in the following format:

.\UserID

Step 19. Click Next to review your settings.

Step 20. When ready, click Finish to Add the site. The newly added child site
should appear in the Site Tree page of the Console Site Configuration
dialog, as shown in Figure 8-10, with the text “[Not Installed]” next to it.

Figure 8-10 New child site in Site Tree page

The site has now been added to the site tree (as shown), but the site
software is not yet installed. Continue with the next procedure to install
the site.

182 Chapter 8
 Adding a site
Adding a child site

To install the site software across the network

Step 1. From the Site Tree page of the Console Site Configuration dialog, click
Install to begin the remote installation.

Figure 8-11 Remote Site Installation Site List page

Step 2. Select the child site to install. Be sure that a check appears in the
checkbox for the site you want to install.

Step 3. Click Next to specify a time for the remote installation to begin.

Chapter 8 183
 Adding a site
Adding a child site

Figure 8-12 Remote Site Installation Schedule page

• Click Now to begin the installation immediately

• Click Schedule to set a time for later installation.

Make sure that both Site manager and DTA manager are running at the
Parent site or sites at the time that the installation is scheduled.

Step 4. Click Next to specify the location of the DTA source files.

Figure 8-13 Remote Site Installation Source Files Location page

184 Chapter 8
 Adding a site
Adding a child site

You can either specify a path to a network directory where you have
stored a copy of the DTA CD, or you can specify a the drive on the install
computer where you will insert the DTA CD. DTA will then copy the DTA
CD source files from the network directory or the install computer CD
drive at the parent site.

Click Browse to select a network directory UNC pathname or local CD

drive.

Step 5. Do one of the following:

• If you want the installation to proceed while logging all information
to a log file and displaying only summary information to a status
screen, check the box for silent installation.

• If you want the installation to write to a log file and display all of the
logged information to the status screen as well, uncheck the box.

The installation process writes an entry reporting successful installation

to a child site log file located in the \TEMP directory of the boot drive of
the local install computer. The name of the log file carries the site ID of
the added site. For example, if you have added child site LA1, the log
name is DTA_LA1.LOG.

You can use this log file to verify that the site installed successfully.

Step 6. If the source files are on the DTA CD, make sure the CD is inserted into
the drive at the install computer.

Chapter 8 185
 Adding a site
Adding a child site

Step 7. When ready, click Finish.

• If you have selected to perform the installation immediately, the

Remote Install status screen appears (shown in Figure 8-14 in silent
installation mode).

Figure 8-14 Remove Installation status screen

DTA proceeds to copy files over the network to the new child site.

When DTA finishes, you see a progress message in the dialog that
reports a successful installation. Go to Step 9.

If you see a message reporting that site installation was not

successful, open the child site log, located in the \TEMP directory of
the boot drive of your install computer. The log contains status
information about the installation process. For example, if you
installed to a location that was using an outdated (earlier than 3.5)
version of ODBC Manager, then the site installation would fail and
DTA would write the reason for the failure to this log.

186 Chapter 8
 Adding a site
Adding a child site

• If you selected to schedule the installation, the installation program

returns you to the Console Site Configuration dialog. From the dialog,
select the Scheduled Remote Install tab to display the schedule for
remote installation.

Figure 8-15 Scheduled Remote Install page

Step 8. Make any final adjustments or cancellations as necessary:

• To remove the installation from the schedule, select the site and click
Remove.

• To change the schedule time, first exit the Remote Install Agent
screen, then click Properties from the Scheduled Remote Install tab to
display the Remote site installation Setup program again. Modify the
schedule as necessary, and then click Next to move through the rest of
the program (you can also change your previous source file location).
Any modifications to the schedule appear in the Scheduled Remote
Install tab.

When DTA starts the installation process according to the schedule,

you see the Remote Install status screen. Again, when the
installation completes, a message displays reporting that the
installation was successful.

Chapter 8 187
 Adding a site
Adding a child site

Step 9. If necessary, click Exit to close the Remote Install Status screen after the
installation completes successfully.

Step 10. From the Console Site Configuration dialog box, select Refresh to update
the dialog. The word “Installed” should now appear next to the added site
as shown in Figure 8-16.

Figure 8-16 New site in Site Tree page

After the site is installed, the next step is to run the SmartDeploy agent
wizard, if you installed a Primary site. You can run the wizard from the
management server Console at the newly added site. Continue with
“Running the SmartDeploy agent wizard at Primary sites” on page 192.
If you installed a Satellite site, see “SmartDeploy agent configuration at
Satellite sites” on page 197.
The site is not fully installed until managed computers have been set up
to launch agents. Continue with ““Setting up managed computers to
launch agents” on page 198 after you run the SmartDeploy agent wizard.

188 Chapter 8
 Adding a site
Adding a child site

Performing a CD installation
The basic steps to a CD install are as follows:
• Add the site
• Complete the remote install program, but only to validate settings
• Go to the newly added site and use the DTA CD (or a copy of it on the
network) to install the site software.
The site installs according to your schedule. You add and install the child
site from the Console of the parent site. These steps are covered below.

To add a site

Step 1. Repeat Steps 1 through 7 of the “To add the site” on page 173.

Step 2. For Step 8, check the box to install the site by CD.

Step 3. Complete the remainder of the procedure to add the site.

The child site has now been added to the site tree (as shown in Step 20 of
the same procedure.)
So far, you have only specified child site settings you have not installed
any software. The next step to installing a site by CD is to validate the
settings you just specified. You do this with the remote install program.
The difference with using the remote installation program for a CD
installation, no DTA software is copied over the network; only settings
are validated. When you validate settings, you complete the Remote
Install program without making any changes to the settings you just
specified.

To validate your settings with the remote install program

Step 1. From the Site Tree page of the Console Site Configuration dialog, click
Install. The Remote Install program appears.

Step 2. Click Next until you reach the review screen.

Step 3. Click Finish.

A progress screen displays while DTA validates your settings. When

validation is completed, you see the message “The new site is ready to
install via CD”.

Chapter 8 189
 Adding a site
Adding a child site

DTA also writes any remote installation messages to a child site log,
located in the \TEMP directory of the boot drive of the computer.

The name the log takes depends on the site ID of the child site. For
example, if you have added child site S10, the log name is
DTA_S10.LOG.

You can now go the newly added site (or instruct someone at that site) to
install the site software with the DTA CD. Or, if you have placed an
image of the DTA CD in a network directory, you can run Setup from
that directory to install the site software.
The purpose of the CD Install program is to install DTA software
according to the settings you specified when you added the site.
Therefore, the CD install program does not prompt you for any new
settings; it simply installs the software and validates the settings
against the logon account at the install computer.

NOTE Although DTA validated these same settings during the Remote install
program, it only checked them against the logon account of the
management server (or install computer) at the parent Primary site.
Because the logon account at the install computer of the Satellite site
may be different, DTA must validate the settings against the logon
account at the Satellite site install computer too.

Continue with the next procedure to install the site by CD.

To install the software by CD

Step 1. Identify the install computer at the newly added site. If you are
installing a Primary site, this is the management server.

If the new site is a Satellite, select a computer that runs Windows NT 4.0
(SP4) or later. See Chapter 3, “Resource requirements,” on page 27 for
more information on install computer requirements.

Step 2. Insert the DTA Setup CD in the CD drive of the install computer at the
child site. If you are installing from a network directory, have the
pathname to that directory ready.

190 Chapter 8
 Adding a site
Adding a child site

Step 3. Type the path to the Setup CD at the command line of the install
computer:

If you are installing from the Setup CD, type the UNC path to the DTA
site server and shared directory in the following format:

D:SETUP /path:“\\UNC path to site server shared directory”

where D: is the letter of the install computer CD drive,

For example, if your site server name and share are NWORKS\HPDTA,
you would type the following:

D:SETUP /path:“\\NWORKS\HPDTA”

If you are installing from a network directory, first map a drive or type
the UNC pathname to the site server and shared directory of the site to
be installed, and then type the following at the command line:
site server path:SETUP /path“\\UNC path to site server
shared directory”
where site server path is the drive mapping or UNC pathname to the
DTA site server.

Step 4. Press Enter to start the CD installation process.

DTA installs the software and validates the site settings against the
logon account of the install computer at the Satellite site.

When the software is installed, DTA writes an entry reporting successful

installation to a child site log file located in the \TEMP directory of the
boot drive of the local install computer. The name of the log file carries
the site ID of the added site. For example, if you have added child site
SB1 the log name is DTA_SB1.LOG You can use this log file to verify
that the site installed successfully.

If you see a message reporting that site installation was not successful,
open the child site log, located in the \TEMP directory of the boot drive
of your computer where the DTA CD is inserted. The log contains status
information about the installation process. If, for instance, you installed
to a location that was using an outdated (earlier than 3.5) version of
ODBC Manager, then the site installation would fail and DTA would
write the reason for the failure to this log.

Chapter 8 191
 Adding a site
Adding a child site

The newly added site appears in the Console Site Configuration dialog,
but the text “Installed” does not display next to it until a full replication
cycle occurs to update site information at the parent site.

The next step is to run the SmartDeploy agent wizard, if you installed a
Primary site. You can run the wizard from the management server
Console at the newly added site. Continue with the procedure “Running
the SmartDeploy agent wizard at Primary sites” on page 192.

If you installed a Satellite site, see “SmartDeploy agent configuration at

Satellite sites” on page 197.
The site is not fully installed until managed computers have been set up
to launch agents. Continue with “Setting up managed computers to
launch agents” on page 198 after you have run the SmartDeploy agent
wizard.

Running the SmartDeploy agent wizard at Primary

sites
After you add a Primary child site and install the software to the new
site, access the configuration wizard at the added site to set up
SmartDeploy agent installation to managed computers.

To Run the SmartDeploy agent wizard

Step 1. At the management server Console of the newly added Primary site,
select HP OPENVIEW DESKTOP ADMINISTRATOR CONSOLE from the Start
menu Programs group.

Step 2. To access the Console and start the wizard, enter the user name and
password for your DBMS account at the child Primary site.
The Console opens, displaying the first screen of the SmartDeploy agent
wizard.

Step 3. Review the wizard text and click Next when ready.

192 Chapter 8
 Adding a site
Adding a child site

Step 4. Select how you want to store and run the SmartDeploy agent.

Figure 8-17 Run Options page

Run Agents From Directory On Site Server: This option stores and runs
the agent from the \AGENTS directory on the site server. Storing agents
on the server saves local hard disk space on the managed computers,
however, more bandwidth is required to run the agent across the
network.

After the agents are installed on the management computers, these

options are disabled. If you need to switch the run from location, use the
procedure “To switch the way SmartDeploy agent runs” on page 163.
Store And Run From Local Disk Of Managed Computer: (default) This
option stores and runs the agent from the local hard disk of each
managed computer. Storing agents locally is the most stable approach,
because it ensures that if the server fails, DTA agents can still run on the
workstations. If you are deploying DTA to laptop computers, choose this
option; otherwise, laptop users will receive a page fault error when they
undock their laptops.

Chapter 8 193
 Adding a site
Adding a child site

After you set up the managed computers (by editing the login script or
policy files of the login server), DTA installs and runs the SmartDeploy
agent from the Windows install directory (for example, C:\WINDOWS)
of the local hard disks. DTA copies the rest of the files to the
\HPDTA\AGENTS directory of the local hard disks.

After the agents are installed on the management computers, these

options are disabled. If you need to switch the run from location, use the
procedure “To switch the way SmartDeploy agent runs” on page 163.

Step 5. To run the SmartDeploy agent as an NT System Service, leave the

checkbox Run As A Service On Windows NT Computers selected. To run
the agent as an application executable, uncheck the box.

In environments with combinations of both Windows NT, 2000

Professional, and Windows 9x computers, you can select the checkbox
and DTA will install the agent as a Service on NT computers and as an
application executable on Windows 9x computers.
Step 6. If you selected to run SmartDeploy agent as an NT System Service, enter
the user name and password for the SmartDeploy agent account under
NT Account Information.

This account provides the agent access to managed computers. If the

managed computers belong to an NT domain, use a Domain
administrator account in the following format: Domain\user_name.

If you are using a local administrator account, you must make sure that
all managed computers have one common user ID and password
assigned to them. The SmartDeploy agent will not be able to run from
the local disk of managed computers unless those computers have been
synchronized with a common user ID and password. Use a local
administrator account in the following format: .\user_name.
Step 7. If the user name and password you use for your Site Server account is
the same as the one for the SmartDeploy agent account, leave the
checkbox Use The Same Account To Access DTA Site Server selected.
Otherwise uncheck the box and enter the user name and password for
the Site Server account.

194 Chapter 8
 Adding a site
Adding a child site

Step 8. Click Next to display the Configuration information.

Figure 8-18 Confirmation information page

Set or confirm the following configuration information for the

SmartDeploy agent.

• Check Every n Minute(s) For SmartDeploy Agent Changes: Enter the

number of minutes you want the SmartDeploy agent to wait to polls
its configuration file, for new or changed configuration information.
Configuration information can be instructions to stop, start, remove,
update, or schedule agents. Or it can be any changes you make to the
Run Options or Configuration wizard panels. (These panels are also
available as dialogs in the Console).

• Wait n Seconds(s) Before Starting DTA Applications: Enter the

number of seconds you want the SmartDeploy agent to wait before
starting the application agents on managed computers. You may want
to specify an interval if, for example, the managed computers have a
number applications running on them.

Chapter 8 195
 Adding a site
Adding a child site

For example, if you have set up managed computers to perform virus

scans of their boot drives every time users log onto them, you might
want to delay the SmartDeploy agent five minutes or longer to let the
scans complete. You might also want to delay the SmartDeploy if your
network maps multiple drives when users first log onto their
computers. Because drive mapping during logon can often be a
lengthy process, delaying the SmartDeploy agent three or four
minutes will allow the mapping process to complete before another
process begins.

• Minimum Required Connection Speed Between Managed Computer

And DTA Site Server: Select the slowest possible speed in bits per
second at which you want to SmartDeploy agent to work.

• Run SmartDeploy Agent Hidden: Select if you want the SmartDeploy

agent not to appear in the system tray or as an icon on managed
computers. The Agent always displays in the management server
system tray.

• No. Of Computers Managed At This Site (Approximately): Specify the

approximate number of computers you want DTA to manage at a site.

• Approximate Bandwidth Usage: Set the available bandwidth you

want DTA to use to deploy the agents to managed computers at a site.

• Estimated Deployment Time (Approximately): Read-only. Based on

the approximate number of computers you specified and the
bandwidth usage you selected, DTA calculates the most efficient
interval to stagger deployment, adds the times, and reports the total
deployment time for all managed computers you indicated. This
calculation does not reflect the time the managed computer is logged
off the network.

Step 9. Click Next to display the final wizard panel and review the information.
Under certain conditions, the following message appears:

You must first logoff to be granted rights to run this job.

This message appears under the following conditions:

• Agents were just installed or upgraded (while the end-user was

logged on) and the end-user has not yet logged off and. . .

• The end-user is not a member of the Local Administrators group

and . . .

196 Chapter 8
 Adding a site
Adding a child site

• An interactive distribution job that requires the end-user to be

elevated to Local Admin is being pushed, or . . .

• The end-user ran SDMenu to pull a job that requires the end-user to
be elevated to Local Admin (by default pull jobs are considered
interactive by SDMenu).

For more information on push and pull distribution jobs, see the
Software Distribution Guide.

At this point in the installation process, you have readied the

SmartDeploy agent for installation. The next step is to set up the
managed computers to install the SmartDeploy agent (and the rest of the
agents). The text in the panel discusses several methods for doing this.
See “Setting up managed computers to launch agents” on page 198 for a
complete explanation of methods and instructions.

A DTA site is not fully installed until managed computers have been set
up (by login script or policy file) to launch agents. See “Setting up
managed computers to launch agents” on page 198 for instructions on
how to do this.

SmartDeploy agent configuration at Satellite sites

Satellite sites inherit SmartDeploy agent configuration settings from
their parent Primary site. DTA does not provide a wizard for the agent at
Satellite sites.
If necessary, you can change these settings by scoping to the Satellite site
from the Parent site Console and then using the SmartDeploy agent
configuration pages at the parent Console to make changes (Satellite
sites do not have their own Consoles).
You may need to configure the agent a Satellite site if, for instance, you
were planning to use a different NT System Service account for the
SmartDeploy agent account at the site.
To scope to a Satellite site, see “Working at another site” on page 93 and
“Configuring the SmartDeploy agent” on page 142 for explanations of the
various configuration settings.
Be aware that unless you scope to the Satellite site first, any changes you
make to the SmartDeploy agent at the parent site will only effect the
parent site. DTA does not replicate SmartDeploy agent configuration to
child sites.

Chapter 8 197
Adding a site
Setting up managed computers to launch agents

Setting up managed computers to launch

agents
After DTA installs the SmartDeploy agent, you must prepare the
managed computers at your site to start it. When the SmartDeploy agent
starts, it runs the rest of the application agents.
More than one method is available for setting up agents on managed
computers. Use this section to determine which methods best suit your
environment.
With previous versions of DTA, you used login scripts to install the DTA
agents, and then were required at some later time to remove the agent
pathnames from the login script once the agents were installed. You were
also required to build logic into your login scripts to prevent agents from
workstations where they were deploying to already installed. The
SmartDeploy agent now takes care of these challenges. It installs agents
only if the workstation is not currently managed by DTA. It also
automatically updates itself and the DTA application agents as
necessary.
Before the SmartDeploy agent (and its application agents) can run on
managed computers, you must first set up each managed computer to
launch the SmartDeploy agent. You can set up managed computers by
providing them with a path to the SmartDeploy agent executable file, for
example:
\\server\vol\HPDTA\AGENTS\SAGENT.EXE
where SAGENT.EXE is the SmartDeploy agent executable file.
When the managed computers process the path, DTA installs and runs
the SmartDeploy agent according to the instructions you specified in the
SmartDeploy wizard.
One way to provide a path would be to go to each managed workstation
and type the path to the SmartDeploy agent executable file at the run
line. Of course, this method is too labor-intensive in production
environments, to say the least.
As long as your networking environment can centrally manage network
resources, the SmartDeploy agent can be deployed centrally, either from
login scripts or policy files.

198 Chapter 8
 Adding a site
Setting up managed computers to launch agents

DTA also provides deployment methods in environments that are not

designed for centralized management, such as Windows NT Workgroups.
Your networking environment will dictate to a great extent which
deployment method you can use. Networking environments and
deployment methods are discussed in the sections below. If you want to
deploy only to a select group of Windows NT or 2000 Professional
computers, you can do so by using the Remote Service Installer (RSI), or
by creating a log file for the SmartDeploy agent that contains a
predefined list of target computers. See “Deploying SmartDeploy agent
to selected Windows NT or 2000 Professional computers” on page 202.

Login scripts
You can add the SmartDeploy agent pathname to a login script (or
scripts) by editing the login script file. When a user logs onto a computer,
the login script executes the command containing the SmartDeploy
agent pathname, and the agent starts on that computer.

User policy files

For registry-based (32-bit) computers, you can create a user policy file
containing a Run key with the SmartDeploy agent pathname and store
the file in its associated directory on the file server. When a user logs
onto a computer, this policy file on the server is merged with the Registry
of the Windows 9x or NT computer launching the agent.
Like login scripts, policy files runs SmartDeploy agent at the first login
as well as every subsequent login.

Windows NT Domain environments with Domain

logins
For Windows NT Domain environment where users log into a central
domain login script, you can deploy the SmartDeploy agent either
through a login script or policy file.

Chapter 8 199
Adding a site
Setting up managed computers to launch agents

For login scripts

Go to the Domain logon server and edit the login script to include the
SmartDeploy agent pathname,
\\server\vol\HPDTA\AGENTS\SAGENT.EXE
where SAGENT.EXE is the SmartDeploy agent executable file.
If you are creating a new login script, make sure to open the User
Manager for Domains and add the login script to the appropriate
Username profiles.

For policy files

Use the Microsoft System Policy Editor (poledit) to add the SmartDeploy
agent pathname (\\server\vol\HPDTA\AGENTS\SAGENT.EXE) as a
registery run key to the appropriate user policy files.
For Windows NT, save the policy as NTCONFIG.POL; for Windows 9x, save
the policy as CONFIG.POL.
See your Microsoft Windows NT 4.0 Server documentation for
information on poledit.
For more information on editing or creating login scripts and user
profiles, see your Microsoft Windows NT implementation documentation.
For information on Microsoft policies, you can also refer to Microsoft
Knowledge Base article Q161334, which is the first of a six part series.

Windows NT Domain environments with local logins

For Windows NT Domain environments where users log in with a local
login script, you can deploy the SmartDeploy agent using the Remote
Service Installer (RSI).
If you are using local logins in a Windows NT Domain environment, you
must run the SmartDeploy agent as an NT System Service.
You can access the RSI tool through the DTA Console. For instructions on
using it, see the section “Deploying SmartDeploy agent to selected
Windows NT or 2000 Professional computers” on page 202.

200 Chapter 8
 Adding a site
Setting up managed computers to launch agents

Windows NT Workgroup environments

Because Windows NT Workgroup environments administer user names
locally at the workstation level, policy files and login scripts do not work
for agent deployment.
To initialize the SmartDeploy agent in this environment, you must run it
from each managed computer. One way to do this is to physically go to
each managed computer and enter the SmartDeploy agent pathname at
the Windows run line.
Or, if you are satisfied with the method you have already developed for
handling global tasks with your Workgroup user population, you might
want to incorporate it for the SmartDeploy agent too.
One example of a way to distribute the SmartDeploy agent pathname in
Workgroup environments is to email the user population with
instructions on entering the agent pathname from the run line of their
computers.
If you plan to target Windows NT or 2000 Professional computers, you
could deploy the agent using the “log file” method, in which you create a
log of predefined computers on which you want the agent to install. For
instructions, see “Deploying SmartDeploy agent to selected Windows NT
or 2000 Professional computers” on page 202.
Regardless of the method you decide upon, if you are running the
SmartDeploy agent as an NT System Service in a Workgroup
environment, the SmartDeploy agent account must be synchronized on
every computer. To be synchronized, the same user name and password
with administrative rights must be used on each Workgroup computer.
See the “System requirements” on page 28 for more information on the
SmartDeploy agent account.

NetWare NDS and Bindery environments

In NetWare NDS or Bindery environments, you use login scripts to
deploy the SmartDeploy agent.
For NetWare 3.x environments, you can add the SmartDeploy agent
pathname to the login script through the NetWare SYSCON.EXE.
For NetWare 4.x and 5.0 environments, you can edit the login script
through the NWAdmin95.
See your NetWare documentation for more information on creating and
modifying NetWare login scripts.

Chapter 8 201
Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

Deploying SmartDeploy agent to selected

Windows NT or 2000 Professional computers
The SmartDeploy agent wizard installs the SmartDeploy agent (and
therefore all DTA application agents) globally, on every managed
computer whose login script or policy file has been set up with the
SmartDeploy agent path.
If you don’t want to deploy the SmartDeploy agent globally, but would
rather install it only on selected Windows NT or Windows 2000
Professional computers, you can do so in either of two ways:

• By using the Remote Service Installer (RSI)

• By creating a log file that lists the target computers and which the
SmartDeploy agent uses for deployment instructions.
To use either method, the SmartDeploy agent must be configured
(through the Console) to run as an NT System Service on the local hard
disks of managed computers. To use RSI, all Windows NT or 2000
Professional computers you are deploying to must be members of a
Windows NT domain. To use the Log file method, all computers must be
members of either a Windows NT domain or a Windows Workgroup, but
not a combination of the two.
Both methods deploy the agent in real-time, although the log file method
will retry SmartDeploy installation continuously if it detects that a
computer is turned off.
Using the log file method, you can deploy the agent to computers even
when the user is not logged onto the computer.
The Remote Service Installer also lets you remove (or upgrade) the
SmartDeploy agent from selected NT or 2000 Professional computers.
The procedures for each method follow.

Using the log file method to install the SmartDeploy

agent to selected computers
Using this method, you create a predefined list of computers, which you
store on your site server in a log file.

202 Chapter 8
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

To install agents to selected computers

Step 1. Make sure you have configured the SmartDeploy agent through the
Console to run as an NT System Service on the local hard drives of
managed computers. See “Configuring the SmartDeploy agent” on page
142.

Step 2. Using a text editor, create a text file called “NTTARGET.LOG” in your
site server \DATA\SAGENT directory.

Step 3. Open NTTARGET.LOG and type the following entry: [Log]

Step 4. Under the [Log] entry, type the computer names of the Windows NT and
2000 Professional computers to which you want to install the
SmartDeploy agent. Use the following format:

[Log]
Computer name=UNC path to \DATA directory at remote site;

Where Computer name is the Windows NT or 2000 Professional

computer and UNC path to \DATA directory at remote site is the
location of the \DATA directory on the site server to which the specified
computer is connected. Always end the pathname with a semi-colon (;).

If the computer you have specified is connected to the current site server,
that is, to the site server on which you created and stored your
NTTARGET.LOG file, then you do not have to specify a path.

For example, you might create the following NTTARGET.LOG file:

[Log]
JANE_NT= STEVE_NT=\\LA-ADMIN\HPDTA\DATA;
ROVER_NT=\\NWORKS\HPDTA\DATA;
SB_2000=
Both JANE_NT and SB_2000 are computers at the site from which you
are installing SmartDeploy agent. STEVE_NT and ROVER_NT, on the
other hand, are computers at a site other than the one you are going to
install from. Because these computers are members of remote sites, the
SmartDeploy agent requires a pathname to their site’s \DATA directory.

Step 5. Repeat Step 4 for each targeted Windows NT or 2000 Professional

computer in your list.

Chapter 8 203
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

Step 6. Save the file and exit.

After the first minute and every minute thereafter, the DTA takes five
computers from the log file list and attempts to deploy the SmartDeploy
agent to them. You can check the installation status of each individual
computer by opening the SmartDeploy agent icon, which runs in the
system tray of your management server. Scroll as necessary to track the
status. When deployment finishes, the SmartDeploy agent status dialog
displays a successful installation message. (You can also check for status
messages in the SAGENT.LOG file, located in the DATA\SAGENT
directory on your site server.)

Using RSI to install the SmartDeploy agent to selected

computers
RSI is available from the management server Console.

To install agents to (or remove them from) selected computers

Step 1. Make sure you have configured the SmartDeploy agent through the
Console to run as an NT System Service on the local hard drives of
managed computers. See “Configuring the SmartDeploy agent” on page
142.

Step 2. From the management server Console, select RSI from the Tools menu.
The main dialog box for the Installer appears.

204 Chapter 8
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

Step 3. Select Options to open the Options dialog box.

Figure 8-19 RSI Options dialog box

Step 4. If necessary, change any of the following paths in the Copy Options group
box:
• Source Directory: Specifies the path to the site server \AGENTS
directory. By default displays the site server of the site where you are
running RSI.

• Destination Directory: Specifies the directory on the managed

Windows NT computer or computers where RSI will install the agent
files. By default, the shared directory displayed reflects that of the
currently managed computers at the site where you are running RSI.
Change only if the destination path of your target computer or
computers is different.

Chapter 8 205
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

• Destination Share: Specifies the shared directory on the managed

Windows NT computer or computers where RSI will install the agent
files. By default, the shared directory displayed reflects that of the
currently managed computers at the site where you are running RSI.
Change only if the share of your target computer or computers is
different.

• Location of DTA Site: Specifies the location of the SmartDeploy agent

configuration file that RSI copies to the target workstations. By
default, this reflects the site where you are running RSI. If you want
to install the SmartDeploy agent to target workstations at a different
site, enter a UNC path or drive mapping to the site server.

Step 5. In the Windows NT System Service Options group box, select the option
to install or remove the SmartDeploy agent, as appropriate. If you are
checking for current status, check the option to only display current
status and continue with “Displaying the status of a SmartDeploy
Service on computers” on page 210.
Step 6. If necessary, change any settings in the Advanced User Settings group
box, although it is recommended that you leave them as is. See the
“Advanced user settings” on page 210 for information on these settings.

206 Chapter 8
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

Step 7. When done, click OK to display the main dialog again.

Figure 8-20 Select Computers dialog box

Chapter 8 207
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

Step 8. From the main dialog, click Computers to open the Select Computers
dialog.

Step 9. Select the NT Domain of the computer or computers in the Domain list
box.

Step 10. Under Available Machines, click the computer or computers to which you
want to install the agents. You can make multiple selections.

Step 11. Click the >> button to add the computers to the Selected Machines list.
To remove a computer from the Selected Machines list, click <<.

Step 12. When done, select OK to return to the main dialog.

Step 13. Select Install or Remove, as appropriate.

As the installation proceeds, you see status messages display in the
Installation Log. Also, computers you selected move from the In Progress
list to the Machine Status list, which reports successful or unsuccessful
installations.

If the installation is not successful, a status message displays in the

Installation Log.

208 Chapter 8
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

To pause the installation

You can pause the entire installation process, and then resume it or
terminate it. (You cannot pause the process for a single computer or
sub-group of computers.)
Step 1. To pause the installation, select Pause from the main dialog. The
installation process pauses.

Step 2. To resume the installation, select Resume.

To terminate the installation

After you pause an installation job, you can terminate the entire
installation process. (You cannot terminate the process for a single
computer or sub-group of computers.)
Step 1. Select Pause from the main dialog.

Step 2. Select Terminate to open the Terminate dialog.

Step 3. Select one of the following options:

• Allow Computers In Progress To Finish (recommended)

• Terminate Operations Immediately.

Step 4. Select OK to start the termination process or Cancel to cancel the

termination process.

After the job terminates, the Exit button on the main dialog reactivates.

To view the log

To verify if RSI has successfully installed the SmartDeploy agent to
Windows NT and 2000 profession computers, you can view the Remote
Installer log. To view the log, select VIEW LOG from the main dialog box.

Chapter 8 209
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

Displaying the status of a SmartDeploy Service on computers

You can check the status of the SmartDeploy agent NT System Services
that are running on managed NT computers.

To check the status of the SmartDeploy agent Services

Step 1. Repeat steps 1 through 3 of the procedure “To install agents to (or
remove them from) selected computers” on page 204.
Step 2. Select the option to Only Display Current Status of SmartDeploy
Services.

Step 3. Click OK to return to the main dialog.

Step 4. Click Computers to open the Select Computers dialog.

Step 5. Select the NT Domain of the computer or computers in the Domain list
box.

Step 6. Under Available Machines, click the computer or computers for which
you want to obtain a status for the remote managed computer. You can
make multiple selections.

If no agents are installed as NT System Services on a particular

managed computer, the Remote Service Installer still displays a status
message for that computer, reporting that no Services are installed.
Step 7. Click the >> button to add the computers to the Selected Machines list.

Step 8. To remove a computer from the Selected Machines list, click <<.

Step 9. When done, select OK to return to the main dialog.

Step 10. Select Status.

The current status displays in the Installation Log for the SmartDeploy
Services on managed computers.

Advanced user settings

When you install, update, or remove SmartDeploy Services, you have the
option of specifying some or all advanced settings listed below. These
settings let you fine-tune the performance and behavior of the Remote
Service Installer. You can access the settings by clicking Options from the
HP OpenView DTA Remote Service Installer dialog. The advanced
settings are described below.

210 Chapter 8
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

Maximum Number of Worker Threads: You can set the number of worker
threads to a value from 1 to 60. The value you set determines the
maximum number of simultaneous installations that can occur at any
given time. One worker thread is assigned to each computer until all the
available threads have been assigned. Once an installation completes for
a particular computer, the thread is re-assigned to another computer, if
any are pending.
This setting determines the amount of network traffic that the Remote
Service Installer generates during an installation (and in particular,
during file copy operations). Decrease the value of this setting if more
than a few file copy errors occur during installation.
Number of Login Retries Before Terminating: If the previous login was
unsuccessful, instruct the Remote Service Installer to retry logging in
the specified number of times before terminating.
Seconds Delayed Before Retrying Login: This setting instructs the
Remote Service Installer to wait the number of seconds you specify
before it attempts to install to the target computer.
Number of Copy Retries Before Terminating: This setting instructs the
Remote Service Installer to retry a file copy operation the number times
you specify before terminating the installation job and displaying an
error message.
Seconds Delayed Before Retrying Copy: This setting instructs the
Remote Service Installer to delay the next attempt at a file copy
operation for the number of seconds you specify. The delay you specify
equals the number of seconds that one or more of the worker threads are
suspended before retrying a copy operation
Because worker threads contribute to network traffic, it is not unusual
for a copy operation to fail during high network traffic periods, or
because of an overburdened Network Interface Card. Another reason
may be that the target computer is no longer available, for example, it
has been turned off.
Suspending the worker thread for a specified interval gives the network
(or the interface card) a chance to temporarily reduce network traffic
before continuing on with a copy operation. In effect, this setting offers
the Remote Service Installer some self-management capabilities.

Chapter 8 211
 Adding a site
Deploying SmartDeploy agent to selected Windows NT or 2000
Professional computers

However, if you still see frequent copy file errors, too much network
traffic exists for this setting to handle. Decrease the number of worker
threads with the Maximum Number of Worker Threads option to reduce
the number of simultaneous installations, which further eases network
traffic.

Setting for Level of Detail in Installation Log

• 1=Displays all details in the Installation Log except file copy and
directory creation messages.
• 2=Displays all details in the Installation Log including file copy
messages.
• 3=Displays all details in the Installation Log including file copy and
directory creation messages.

Rebooting managed computers remotely

Using RSI, you can remotely reboot managed Windows NT or 2000
Professional workstations at your site. The process for remotely
rebooting one or more of these workstations is two-fold: first you reset
the RebootOnly registry value, and then you provide the reboot command
through RSI.

To reboot managed computers

Step 1. At management server (or the computer where you are running RSI),
locate the following registry key:
HKEY LOCAL MACHINE\SOFTWARE\Hewlett-Packard\DTA\5.0\Remoteinstaller

Step 2. Set the RebootOnly registry key value to 1 to enable the RSI reboot
option. (A value of 1 enables the reboot option; a value of 0 disables it.)
Step 3. Start the Remote Service Installer from the Console and in the main
dialog of RSI, select the Windows NT and 2000 Professional computers
you want to reboot by remote control.

Step 4. Select the Reboot button, which is now active.

Step 5. The Remote Service Installer remotely restarts the managed computers
you selected.

212 Chapter 8
A Removing DTA

213
Removing DTA

This appendix contains instructions for removing DTA software from

servers and managed computers.
Removing DTA is a two-step process. First, you remove the agents
running on managed computers. Then you remove the DTA software
using the DTA uninstall program.

214 Appendix A
 Removing DTA
Removing agents from managed computers

Removing agents from managed computers

Before you can use the uninstall program, you must first remove the
SmartDeploy agent and all application agents running on the managed
computers at a site.

To remove the agents from managed computers

Step 1. From the Console at the management server, select CONTROL AGENTS
from the Tasks menu.

The Control Agents dialog appears.

Step 2. Select the Remove option from the SmartDeploy agent group box.
The SmartDeploy agent will remove itself and the other DTA agents
from the managed computers the next time it queries for new
instructions.

For agents running across the management server, this step will remove
the registry keys from the managed computers.

It queries for new instructions according to a polling schedule you set in

the Console SmartDeploy Agent Configuration page. See “Configuring
the SmartDeploy agent” on page 142 for more information on this
setting.

After the SmartDeploy agent removes itself and the application agents
from the managed computers, only the HPDTA\DATA directories
remain on them.
If necessary, you can go to the managed computers and delete this
directory structure; however, if there is a chance that you might want
DTA to manage any of the computers again, you may want to leave the
directories on those computers. DTA leaves a the NEF.INI file, required
for continuity in inventory scans, in the \HPDTA directory.
Ensure all agents are uninstalled before you uninstall the site.

Appendix A 215
 Removing DTA
Removing DTA software

Removing DTA software

When you use the DTA uninstall program to delete the DTA software, it
removes the \HPDTA directory structures from the site server and
management server, and it removes the DTA program group.
You use an uninstall program to remove DTA software. You can only run
the uninstall program from the same computer from which you installed
DTA.
It does not remove the database, unless you installed the bundled
version of SOLID 3.0 that shipped with DTA.
If you have installed additional Consoles, they will not be removed in this
procedure. Remove additional Consoles before or after this uninstall
procedure by using Steps 2 and 3 below. You uninstall from the computer
where the Console is installed.
Uninstall the DTA software from the computer at which it was installed.
For remotely installed (or CD installed) sites, uninstall from the
management server at the site. For Satellite sites, manually delete the
\HPDTA directory.

To uninstall the DTA software

Step 1. Delete the site from the Site Tree page in the Console, as described in
“Deleting sites” on page 125.

Step 2. From the Start menu at the management server, select CONTROL PANEL
from the Settings program group.

Step 3. Double-click Add/Remove programs.

Select HP OPENVIEW DESKTOP ADMINISTRATOR from the list box and
click Add/Remove.

Windows launches the uninstall program, which removes the software.

NOTE If you have modified your login script or policy files to launch DTA
agents at the site, you must modify the scripts or policy files again to
remove the run instructions.

216 Appendix A
 Removing DTA
Removing DTA software

Step 4. If you are deleting a child site, select SITE from the Console Configure
menu and highlight its parent or central site and remove it from the site
tree. Changes to the site tree will be propagated per the replication
schedule.

Appendix A 217
Removing DTA
Removing DTA software

218 Appendix A
B Command-line switches

219
Command-line switches

This appendix lists the command-line switches that DTA provides for
agents and managers. DTA agents are stored in the site server
HPDTA\AGENTS directory. DTA managers are stored in the
management servers HPDTA\MANAGERS directory.

220 Appendix B
 Command-line switches
Agent switches

Agent switches
Table B-1 Agent Switches

Software Distribution
Server Inventory

SDMENU32.EXE
NAINVSVR.EXE
NAINVW32.EXE

DSTAGT32.EXE
Switch

SAGENT.EXE
SmartDeploy
(bolded characters
Description
represent the quick

Inventory

SDMenu
command)

/ADDUNKNOWNS Adds any unknown

applications to the • •
application database

/ALLOWROAMING Allows the agent to run at

sites other than the home • •
site
/CONNECTION:connectio Specifies the minimum
n speed connection speed for mobile •
users

/DATA:path Specifies a new data location

of the agent configuration
files for the agents to
• •
manage (overrides the
location specified in
NADMIN.DAT)

/DISABLE Disables the agent •

/DMI Enables DMI usage •

/DMIEXT Collects DMI extended

information when a MIF •
extension is specified

/ENABLE Enables the agent •

Appendix B 221
 Command-line switches
Agent switches

Table B-1 Agent Switches (Continued)

Software Distribution
Server Inventory

SDMENU32.EXE
NAINVSVR.EXE
NAINVW32.EXE

DSTAGT32.EXE
Switch

SAGENT.EXE
SmartDeploy
(bolded characters
Description
represent the quick

Inventory

SDMenu
command)

/ENABLESERVER Enables the server agent •

/EXCLUSIVE Does not share CPU cycles

•
with other applications

/EXTENSIONS:list Specifies the file extension

(such as .COM or .EXE) for • •
the agent to scan
/FASTLOG Limits the event recorded in
the log to everything but File
•
Replace and Copy File
actions

/FILE:full path to Specifies the indicated SDP

•
SDP file file as the job to execute

/FULLSCAN Forces a full software scan •

/FULLSCANAFTER:date Forces a full software scan
•
after the specified date

/FULLSCANFIRSTTIME Forces a full software scan if

•
one hasn’t occurred yet

/HIDDEN Does not display an icon

• • •
when the agent is minimized
/IDLECPU:seconds Runs the agent when a
workstation is idle for the •
specified number of seconds

222 Appendix B
 Command-line switches
Agent switches

Table B-1 Agent Switches (Continued)

Software Distribution
Server Inventory

SDMENU32.EXE
NAINVSVR.EXE
NAINVW32.EXE

DSTAGT32.EXE
Switch

SAGENT.EXE
SmartDeploy
(bolded characters
Description
represent the quick

Inventory

SDMenu
command)

/JOB:jobtitle Specifies the indicated job

•
title as the job to be executed

/LOGIN:name Overrides the value of the

•
Last Login Name field

/MACHINENAME:name Overrides the value of the

Machine Name field (16 byte •
maxium)
/MAINAPPS Scans software for and
collects only main • •
applications

/MAXIMIZED Runs the agent maximized • •

/MINIMIZED Runs the agent minimized • •

/NOAPM Skips Advanced Power
•
Management test

/NOAST Skips the AST-specific test •

/NOBENCHMARK Skips the benchmark test •

/NOCDROM Skips the test on the
•
CD-ROM

/NOCHANGES Does not track Changes

•
Made

/NOCOMPAQ Skips the Compaq-specific

•
tests

Appendix B 223
 Command-line switches
Agent switches

Table B-1 Agent Switches (Continued)

Software Distribution
Server Inventory

SDMENU32.EXE
NAINVSVR.EXE
NAINVW32.EXE

DSTAGT32.EXE
Switch

SAGENT.EXE
SmartDeploy
(bolded characters
Description
represent the quick

Inventory

SDMenu
command)

/NOCPU Skips the CPU test •

/NODELL Skips the Dell-specific tests •

/NODISKCACHE Skips the disk cache test •

/NODISKS Skips the physical disks test •

/NODISPLAY Does not show the status of

• •
the agent as it is running

/NOHARDWARE Skips all hardware tests •

/NOHP Skips all HP-specific tests •

/NOIBM Skips the IBM-specific tests •

/NOJOYSTICK Skips the joystick test •

/NOKEYBOARD Skips the keyboard test •

/NOLOGICAL Skips the logical drives test •

/NOMOUSE Skips the mouse test •

/NONETLOGICAL Skips the networks logical
•
drives test

/NOPCA Skips the test for

•
pcANYWHERE

/NOPORTS Skips the I/O ports test •

224 Appendix B
 Command-line switches
Agent switches

Table B-1 Agent Switches (Continued)

Software Distribution
Server Inventory

SDMENU32.EXE
NAINVSVR.EXE
NAINVW32.EXE

DSTAGT32.EXE
Switch

SAGENT.EXE
SmartDeploy
(bolded characters
Description
represent the quick

Inventory

SDMenu
command)

/NOPROMPTS Skips prompts for custom

•
and property tag fields

/NOSERVERSOFTWARE Skips the server software

test when the Inventory •
Server agent is running

/NOSLOTS Skips the test on expansion

•
slots
/NOSOFTWARE Skips the software inventory
•
test

/NOSYSTEM Skips the system test •

/NOTIFY Runs SDMenu to check for

new and upgrade •
Subscription jobs
/NOTRACKEDFILES Skips the test for tracked
•
files

/NOVIDEO Skips the video test •

/NOWINENV Skips the Windows

•
environment test
/NOWINIP Skips the Windows IP
•
network test

/NOWINLOADIP Performs an IP query only if

the IP stack has already •
been loaded

Appendix B 225
 Command-line switches
Agent switches

Table B-1 Agent Switches (Continued)

Software Distribution
Server Inventory

SDMENU32.EXE
NAINVSVR.EXE
NAINVW32.EXE

DSTAGT32.EXE
Switch

SAGENT.EXE
SmartDeploy
(bolded characters
Description
represent the quick

Inventory

SDMenu
command)

/NOWINMEMORY Skips the Windows memory

•
test

/NOWINNET Skips the Windows

•
networking test

/NOWINPRINTERS Skips the Windows printers

•
test
/NOWINVIDEO Skips the Windows video test •

/PLATFORM:index Specifies application type to

be scanned, where the index
is an integer representing a
platform: 1 (DOS); 2 (Win16);
• •
4 (Win32); 8 (OS/2); 16
(unknown). Add numbers to
specify more than one
platform

/POLLDELAY:minutes Delays polling by the

•
specified minutes
/PROMPT Prompts the user •

/PROMPTWHENHIDDEN Prompts user even if the

•
agent is running hidden

/QUIET Disables agent from

displaying progress •
messages

226 Appendix B
 Command-line switches
Agent switches

Table B-1 Agent Switches (Continued)

Software Distribution
Server Inventory

SDMENU32.EXE
NAINVSVR.EXE
NAINVW32.EXE

DSTAGT32.EXE
Switch

SAGENT.EXE
SmartDeploy
(bolded characters
Description
represent the quick

Inventory

SDMenu
command)

/RUNONCEADAY Runs the agent only once a

•
day

/SCANONCEADAY Scan for software once a day •

/SERVERAGENT Lets the system

administrator distribute jobs •
to servers
/SHAREDCPU:shareindex Runs the agent in the
background and share the
CPU with other processes;
•
valide range for shareindex
is 1 to 50, which represents
100 to 5000 milliseconds

/TFILEDIR:path Specifies the location of

transaction files if the • •
default directory is not used

/TIMEOUT:seconds Specifies the indicated time

limit (0 to 65,000 seconds) for
•
a partial software scan; 3
seconds is the default
/VIEW:full path to Displays information about
SDP or JIF SDPs, such as the job title •
and version

Appendix B 227
 Command-line switches
Manager switches

Manager switches
Table B-2 Manager Switches

Site manager Service

Switch

REPSERV.EXE
REPMGR.EXE

DTAMGR.EXE
DTA manager
Site manager
(bolded characters
Description
represent the quick
command)

/DATA:path Specifies a data location to

manage (overrides the location •
specified in NADMIN.DAT)
/INSTALL:”user password” Installs the service for the
• •
specified user and password

/REMOVE Removes the service • •

/SITE:siteID Specifies the three-character site

•
ID
/START Starts the service • •

/TERMINATE Runs the manager through the

cycle for the current site only;
•
does not start the proxy cycles for
the child sites

228 Appendix B
C Tools and Utilities

229
 Tools and Utilities

Desktop Administrator provides several tools and utilities that are

useful for troubleshooting. Table C-1 lists the tools and utilities available
with DTA, the directories in which they are located, and which
component of the product you use them to troubleshoot.
Table C-1 Tools and utilities with DTA

Tool or Utility Directory Inventory Software SOLID Install

Distribution Database

APPIMPRT.EXE \CONSOLE,
•
\MANAGERS

DTACLEAN.EXE \CONSOLE,
•
\MANAGERS

DTACPI.EXE \CONSOLE,
• •
\MANAGERS

NACCESS.EXE \CONSOLE,
•
\MANAGERS

OAREDIT.EXE \CONSOLE,
•
\MANAGERS

SDLDMP32.EXE \UTILITY •

SERVCTRL.EXE \CONSOLE,
•
\MANAGERS

SOLCON.EXE \SOLID •

SOLSQL.EXE \SOLID •

TFILEAGE.EXE \UTILITY • •

TFILECHK.EXE \UTILITY • •

TFILEDMP.EXE \UTILITY • •

230 Appendix C
 Tools and Utilities
APPIMPRT.EXE

APPIMPRT.EXE
The APPIMPRT tool allows you to import DTA 4.x Applications and
Publishers database records into the DTA 5.0 database if you chose not
to convert them during the upgrade process.
The APPIMPRT tools supports the following command line switches:
• /Userid Username for database login.
• /Password Password for database login.
• /Cleanup Cleans up the Applications and Vendors database tables.
• /Hide Run APPIMPRT hidden. No progress dialog boxes appear
while the tool is running.
To import Applications data, use the following command:
APPIMPRT APP.CSV /USERID:userid /PASSWORD:password
To import Vendors (formerly Publishers in DTA 4.x) data, use the
following command:
APPIMPRT VENDOR.CSV /USERID:userid /PASSWORD:password
If you do not want to see progress messages during the import process,
add the /Hide switch to the command line.
If the import failed and you want to delete all of the data from both the
Applications and Vendors tables, use the following command:
APPIMPRT /USERID:userid /PASSWORD:password /CLEANUP
Note that you cannot specify only one table to clean up.
You can then re-import data into each table. Even if you do not clean up
the tables before re-importing data, the old data is lost, because the
import process overwrites any data in the tables.
APPIMPRT.EXE is stored in the \CONSOLE and \MANAGERS
directories.

Appendix C 231
Tools and Utilities
DTACLEAN.EXE

DTACLEAN.EXE
The DTACLEAN tool allows you to remove the services, registry keys,
and Programs menu items from the DTA site server, management server,
or any managed computer. With DTACLEAN you can also chose to
remove the bundled SOLID database. After you use DTACLEAN.EXE,
you can delete the DTA directories and files manually. You use
DTACLEAN.EXE if you want to uninstall DTA agents on a target
managed computer or if you are having difficulty removing the product
using the uninstall program.
DTACLEAN.EXE is stored in the \CONSOLE and \MANAGERS
directories.

232 Appendix C
 Tools and Utilities
DTACPI.EXE

DTACPI.EXE
The DTACPI tool allows you to view a standalone property sheet for a
specific computer. This property sheet displays comprehensive
information collected by DTA about the computer, such as hardware and
software inventory and distribution job logs. There are six different
ways to specify a computer:
• To use user name of the computer as the key, run DTACPI with
/USR:MachineName\User_Name or /USR:DomainName\User_Name
command line option depending on whether the logon is to the
machine or to the domain
• To use NIC address of the computer as the key, run DTACPI with
/NIC:NIC_Address command line option
• To use name for the computer as the key, run DTACPI with
/NAM:Computer_Name command line option
• To use IP address of the computer as the key, run DTACPI with
/IPS:IP_Address command line option
• To use IP host name of the computer as the key, run DTACPI with
/IPH:IP_HostName command line option
• To use DTA Machine ID of the computer as the key, run DTACPI with
/OID:Machine_ID command line option.
The command line entries you use with DTACPI.EXE have to exactly
match the way data is stored in the DTA database. Here are some
examples:
DTACPI.EXE /USR:SM-DOMAIN9\JSMITH
DTACPI.EXE /NIC:00104B67CB5B
DTACPI.EXE /NAM:SM-PC45
DTACPI.EXE /IPS:15.93.9.217
DTACPI.EXE /IPH:SM-PC45
DTACPI.EXE /OID:{6D0760E0-6A7E-11D3-AF49-00A0244D3637}
DTACPI.EXE is stored in the \CONSOLE and \MANAGERS
directories.

Appendix C 233
Tools and Utilities
NACCESS.EXE

NACCESS.EXE
The NACESS tool allows you to specify accounts that have been renewed
for the DTA site server, DBMS, and DTA managers.
From the management server command line, you can run NACCESS by
entering the following:

/prompt:SITE To specify the new account for the DTA site server.

/prompt:DBMS To specify the new DBMS account.

/prompt:NTSVC To specify the new account for the DTA managers.

See the “Renewing expired DTA accounts” on page 128 for more
information on using NACCESS.
NACCESS.EXE is stored in the \CONSOLE and \MANAGERS
directories.

234 Appendix C
 Tools and Utilities
OAREDIT.EXE (Object Address Resolution)

OAREDIT.EXE (Object Address Resolution)

The OAREDIT tool allows you to view and configure how and where
workstation agents can attempt to connect to DTA manager.
When you launch OAREDIT.EXE, you view and configure the
SERVICES.DAT file, located in the \DATA directory. SERVICES.DAT
contains host names and their IP and IPX addresses. The information
stored in SERVICES.DAT is dynamic and is updated every time the DTA
manager is started. DTA manager registers its server name and
addresses so that managed computers can retrieve the addresses in
order to connect to the server. Site manager replicates any updates
made to SERVICES.DAT to Satellite sites.
OAREDIT.EXE can be used to verify that agents running on managed
computers within a site are connecting to DTA manager on the correct
management server. You may want to verify this, for example, after
remote site installations. It can also be used to enable or disable the IP
or IPX protocols immediately following an installation and before DTA
agents are deployed on managed computers.
OAREDIT.EXE is stored in the \CONSOLE and \MANAGERS
directories.

Appendix C 235
Tools and Utilities
SDLDMP32.EXE

SDLDMP32.EXE
The SDL Dump utility allows you to obtain extensive debug information
through specific Inventory hardware tests on a workstation at the
Windows level.
To use utility, copy the SDL Dump files to a directory on the workstation
on which you plan to perform the tests. (You do not have to place the SDL
Dump files in any of the \HPDTA directories.) After you copy the files,
run the executable, included near the bottom of the following list of
required SDL Dump files:
• SDLDMP32.EXE
• HPSBM16.DLL
• HPSBM32.DLL
• HPSDL16.DLL
• HPSDL32.DLL
• HPSTHK16.DLL
• HPSTHK32.DLL
• HPKRNL.VXD
• HPSBMMB.VXD
• COMPOBJ.DLL
• MFC42.DLL
• MSVCRT.DLL
You can also place the SDL Dump utility in a shared location on the
network for easy access from any machine.
SDLDMP32.EXE is stored in the \UTILITY directory.

236 Appendix C
 Tools and Utilities
SERVCTRL.EXE

SERVCTRL.EXE
The SERVCTRL tool allows you to remotely stop, start, or remove any
service on an NT 4.0 computer including the DTA site server and
managed computers as long as you have administrative rights to the
computer.
If you use SERVCTRL.EXE to stop a DTA service, it only stops it until
the next polling cycle. SmartDeploy agent will restart the service at the
next polling cycle. To prevent this you must also stop SmartDeploy
agent.
SERVCTRL.EXE is stored in the \CONSOLE and \MANAGERS
directories.

Appendix C 237
Tools and Utilities
SOLCON.EXE (SOLID Remote Control)

SOLCON.EXE (SOLID Remote Control)

The SOLCON tool allows you to remotely control or get information from
the bundled SOLID database.
The command line syntax for the SOLCON tool is:
solcon [options] [servername] [username password]
The SOLCON tool connects to the first server specified in the [Com]
Connect= parameter in the SOLID.INI file.
Table C-2 lists the choices for the options command:
Table C-2 Options command and descriptions

Option Description

-c<dir> Change working directory

-e<string> Execute command string

-f<filename> Execute command string

from file
-h, -? Help=Usage

You can give the connection information at the command line to override
the connect definition in SOLID.INI. For example, solcon “tcpip
MyComputer 1313”.

238 Appendix C
 Tools and Utilities
SOLCON.EXE (SOLID Remote Control)

After the connection to the server is established, the command prompt

appears. Table C-3 describes the available commands.
Table C-3 Line commands

Command Abbreviation Explanation

backup bak Makes a backup of the database.

The default backup directory is the
[backup_directory] one defined in configuration
parameter
General.Backup.Directory. The
backup directory may also be given
as an argument. For example,
backup abc creates a backup on
directory “abc.” All directory
defintions are relative to the SOLID
Embedded Engine working
directory.

backuplist bls Displays a status list of last

backups.
close clo Closes server from new connections;
no new connections are allowed.

errorcode ec Displays a description of an error

[SOLID_error_code] code. Give the code number as an
argument. For example, errorcode
100033.

exit ex Exits SOLID Remote Control.

help ? Displays available commands.

makecp mcp Makes a checkpoint.

messages mes Displays server messages.

monitor {on | off} mon Sets server monitoring on and off.
[user username | user id] Monitoring logs user activity and
SQL calls to SQL-TRACE.OUT file.

open ope Opens server for new connections;

new connections are allowed.

Appendix C 239
 Tools and Utilities
SOLCON.EXE (SOLID Remote Control)

Table C-3 Line commands (Continued)

Command Abbreviation Explanation

report filename rep Generate a report of server info to a

file given as an argument.

shutdown sd Stops SOLID Embedded Engine.

status sta Displays server statistics.

status backup sta bak Displays status of the last started

backup. The status can be one of
the following:

• If the last backup was successful

or any backups have not been
requested, the output is 0
success.
• If the backup is in process; for
example, started but not ready
yet, the output is 14003
ACTIVE.
• If the last backup failed, the
output is: errorcode ERROR
where the errorcode shows the
reason for the failures.

throwout {username|userid to Exits users from SOLID Embedded

|all Engine. To exit a specified user,
give the user id an argument. To
throw out all users, use the keyword
ALL as an argument.

userlist [-l] [name|id] ul Displays a list of users, option -l

displays more detailed output.

version ver Displays the server version

information.

pid pid Returns server process id.

240 Appendix C
 Tools and Utilities
SOLCON.EXE (SOLID Remote Control)

Table C-3 Line commands (Continued)

Command Abbreviation Explanation

parameters [name] par Displays server parameter values.

For example,

• parameter used alone displays

all parameters.
• parameter general displays all
parameters from section
“general.”
• parameter general.readonly
displays a single parameter
“readonly” from section
“general.”

perfmon [-c] pmon Returns performance statistics from

the server. The -c option returns all
values as counter. By default, some
values are averages/second.

trace {on | off}sql | rpc | sync tra Sets server trace on or off. This
command is similar to the monitor
command, but traces different
entities and a different level. By
default, the output is written to the
SQL-TRACE.OUT file.

SOLCON.EXE is stored in the \SOLID directory.

Appendix C 241
Tools and Utilities
SOLSQL.EXE (SOLID SQL Editor)

SOLSQL.EXE (SOLID SQL Editor)

The SOLSQL tool allows you to create a Read-only account for the
bundled SOLID database.
From the \SOLID directory on the DTA database server, run:
solsql.exe -f<path to readuser.sql>
Enter the database username and password when prompted, or you can
enter it as part of the command line.
For example, if ReadUser.sql is in c:\hpdta\console\isupport\database,
use:
solsql.exe -fc:\hpdta\console\isupport\database\readuser.sql
If the DTA CD is in the D: drive, use:
solsql.exe -fd:\isupport\database\readuser.sql
To enter the username “HPDTA” and password “test” at the command
line (using the script file from the DTA CD in the D: drive), use:
solsql.exe -fd:\isupport\database\readuser.sql HPDTA test
SOLSQL.EXE is stored in the \SOLID directory.

242 Appendix C
 Tools and Utilities
TFILEAGE.EXE

TFILEAGE.EXE
The TFILEAGE utility allows you to view and reinstate expired DTA
transaction files. The TFILEAGE utility is useful for determining how
old a transaction file is or if it has expired. Site manager moves expired
transaction files to the \BADTFILE directory. Once a transaction file has
expired (after 30 days), it can be reinstated with this utility.
TFILEAGE.EXE is located in the \UTILITY directory.

Appendix C 243
Tools and Utilities
TFILECHK.EXE

TFILECHK.EXE
The TFILECHK utility checks the integrity of the DTA transaction files.
It is a DOS based utility that runs from a command line and reports the
errors that are associated with transaction file architecture.
TFILECHK.EXE is located in the \UTILITY directory.

244 Appendix C
 Tools and Utilities
TFILEDMP.EXE

TFILEDMP.EXE
The TFILEDMP utility displays the contents of a DTA transaction file on
the screen. You can use it with the “>” or “|” DOS parameter to write the
contents to a file or to a printer. You can read the header of the
transaction file; however, the contents of the transaction file are in HEX
format.
You can use this utility to identify the workstation that created the DTA
transaction file. Bytes 11 through 16 of the HEX dump correspond to the
NIC address of the creating workstation.
TFILEDMP.EXE is located in the \UTILITY directory

Appendix C 245
Tools and Utilities
TFILEDMP.EXE

246 Appendix C
D SOLID database maintenance

247
 SOLID database maintenance
Scheduling the backup of SOLID database files

Scheduling the backup of SOLID database

files
Backups are made to secure the information stored in your database
files. If you have lost your database files because of a system failure, you
can continue working with the backup database.
The SOLID database and log files can be backed up using one of the
following methods:
• Scheduled Backup—Uses SOLID’s scheduler to back up the
database without shutting down the SOLID server. A scheduled
backup uses a timed command that starts the backup according to a
pre-defined schedule. A scheduled backup can be done while the
database is open and in-use.
• Generic Backup—Requires a shut down of the SOLID server before
a typical server backup (tape/CD) procedure set by the administrator.
Scheduled backup is recommended since it requires the least amount of
work, provides uninterrupted database access, and provides automatic
log file cleanup.
It is recommended that a backup be done every day, and that you keep at
least the last five day’s backups. If backup is done at night while
database is not in use, it can be completed overnight (for a database of
approximately 10GB).

Scheduled backup
Ideally, you should backup the database files to a local physical hard disk
different than the disk containing the live database files. For example, if
your hard disk 0 is C: and hard disk 1 is D:, with your database installed
on drive C:, you should set your backup to write to D: (the disk that does
not store the database files). This is to prevent total data loss in the
event of a hard disk failure or crash.

CAUTION Before scheduling a backup, be sure you have enough disk space in the
backup directory. You will need space for your database and log files.

248 Appendix D
 SOLID database maintenance
Scheduling the backup of SOLID database files

The backed up database files should be transferred to another medium,

such as tape or CD, for safe keeping between scheduled backups. The
next scheduled backup will overwrite files from the previous backup that
are in the same backup directory.
Scheduled backups require the following steps

1. Modify SOLID.ini.
2. Create backup directories.
3. Start or restart SOLID service.
4. Implement a procedure to transfer the backed up files to tape or CD.

Modify SOLID.ini
A simple schedule can be set by modifying solid.ini as follows:
[Srv] section header
At=<time> backup use 24-hr format HH:MM

[General]
BackupDirectory=<default backup path>
CheckPointDeleteLog=No

For example, to schedule a backup at 2:30am each morning to

d:\Backup, use:
[Srv]
At=02:30 backup

[General]
BackupDirectory=<default backup path>
CheckPointDeleteLog=No

The scheduler entry, “At=”, takes the following parameters for backup:
[Srv] section header
At=[day] <time> backup [path][,] [ ] = optional

Appendix D 249
 SOLID database maintenance
Scheduling the backup of SOLID database files

As you can see, SOLID does allow some customization for scheduled
backup, such as day of the week and backup location. For example, if you
want the backup to be done as follows:
Mon-Fri: 1am to d:\Backup\weekday
Sat: no backup
Sun: 2am to d:\Backup\sun

Your solid.ini should include the following lines:

[Srv]
At=sun 02:00 backup d:\backup\sun,mon 01:00
backup,tue 01:00 backup,wed 01:00 backup,thu 01:00
backup,fri 01:00 backup

[General]
BackupDirectory=<default backup path>
CheckPointDeleteLog=No

Create backup directories

SOLID does not create the backup directory. If the specified backup
directory does not exist, backup will fail. You can check SolMsg.out to
see if the backup was successful.

CAUTION Before scheduling a backup, be sure you have enough disk space in the
backup directory. You will need space for your database and log files.

Start or restart SOLID service

SOLID.exe reads solid.ini at startup. You must restart SOLID for the
entries to take effect. In the case of DTA, you will need to stop the
SOLID service then start it again.

250 Appendix D
 SOLID database maintenance
Scheduling the backup of SOLID database files

Implement a procedure to transfer the backed up files to tape or

CD
This is a part of the normal server backup procedure done by the
network administrator. However, since the server is not shut down and
the working database files remain in use, a “normal” server backup set
by the administrator must exclude the working \SOLID directory. But
make sure the SOLID backup directory is included.
For example, if your have the following:
Server and database files in: c:\HPDTA\SOLID
Backup directory set to: d:\DBbackup

Your server backup should:

Exclude: c:\HPDTA\SOLID
Include: d:\DBbackup

Here are some additional things to keep in mind:

• The log files (*.log) are automatically deleted after each backup.
• You must use HH:MM 24-hour format (i.e. 21:30, 02:00), H:MM will
also work (i.e. 2:00).
• If you schedule more than one backup in the same day, make sure
that you give sufficient time for the first backup to complete before
the next one starts, you can estimate the time it takes to backup a
database by executing admin command ‘backup’ from ssqlw.exe.
• The backup directory must exist or backup will fail.
• Don’t forget to remove the CheckPointDeleteLog= entry after the
timed backup schedule is set.
• Schedule backup at non-busy hours.
• Backups to a network path or other media directly (Jazz disk, optical
disk, CD-R/CD-RW, tape) are not recommended due to higher failure
potentials.

Appendix D 251
SOLID database maintenance
Scheduling the backup of SOLID database files

• After the backup schedule is set, if any of these entries exist under
[General], make sure you either delete them (to reset to following
defaults) or set them as follows:
[General]
CheckPointDeleteLog=No
BackupDeleteLog=Yes
BackupCopyIniFile=Yes
BackupCopyLog=Yes
• When SOLID is run as a service, it is not aware of network mapped
drives, only physically attached storage devices. If the backup
directory is a mapped drive (for example, the H: drive mapped to
\\hp-tools\qa), the backup will fail if SOLID is running as a service.

Generic backup
After stopping SOLID server, the database and log files are no longer in
use and can be backed up using any backup method.
Typically, the following is done:

1. Stop SOLID service.

2. Run the server backup program/procedure to backup *.db and *.log
files.
3. Start SOLID service.

252 Appendix D
 SOLID database maintenance
Restoring backups

Restoring backups
There are two ways to restore a backup. You can:
• Return to the state when the backup was created
• Return a backup database to the current state using log files to add
data that was inserted or updated after the backup was made.

To return to the state when the backup was made

Step 1. Shut down SOLID Embedded Engine, if it is running.

Step 2. Delete all log files from the log file directory.
The default log file names are sol00001.log, sol00002.log, etc.

Step 3. Copy the database file(s) from the backup directory to the database file
directory.

Step 4. Start SOLID Embedded Engine.

This method will not recover any data inserted after the backup because
no log files exist from which to recover the data.

To restore a backup database to the current state

Step 1. Shut down SOLID Embedded Engine, if it is running.

Step 2. Copy the database file(s) from the backup directory to the database file
directory.

Step 3. Copy the log files from the backup directory to the log file directory.

If there are log files with the same file names, do not replace those log
files in the log file directory with log files from the backup directory.

Step 4. Start SOLID Embedded Engine.

SOLID Embedded Engine automatically uses the log files to perform a
roll-forward recovery.

Appendix D 253
SOLID database maintenance
Restoring backups

Correcting a failed backup

When SOLID Embedded Engine is performing a backup, the ADMIN
‘status backup’ command returns the value ‘ACTIVE.’ Once the backup is
completed, the command returns either ‘OK’ or ‘FAILED.’
If the backup failed, you can find the error message that describes the
reason for the failure from the solmsg.out file. Correct the cause of the
error and try the backup again. The most common causes for failed
backups are:

• The backup media is out of disk space.

• The backup directory does not exist.
• A database directory is defined as the backup directory.

254 Appendix D
 SOLID database maintenance
Database Support Installer

Database Support Installer

You can run this setup either from the DTA CD under
DATABASE\SETUP.EXE, from the site in
CONSOLE\DATABASE\SETUP.EXE, or by selecting Upgrade ODBC
from the CD Browser which automatically launches when the DTA CD is
inserted into the computer.
The DTA Database Support Installer is used to install the following:
• ODBC Manager 3.5
• SOLID 3.0 Client (SOLID ODBC Drivers)
• SOLID Server 3.0 (Embedded Engine DBMS)
Each of these components is described in this document under
“Components” on page 257.
This installer does not support remote installation. All selected
components will be installed to the computer running SETUP.EXE.

Appendix D 255
 SOLID database maintenance
Database Support Installer

When to use Database Support Installer

There are many cases when the Database Support Installer is needed.
Table D-1 shows the components needed in each situation. The use of
this installer is not limited to what is stated in the table. After
understanding the purpose and limitations of this installer, you can use
this installer for any application you see fit.
Table D-1 Components of Database Support Installer

Usage ODBC 3.5 SOLID 3.0 SOLID

Manager Client Server 3.0

Older version of ODBC Manager exists on the

computer running DTA setup or computer •*
selected for Site Management Machine.

Fix/upgrade an existing SOLID client •* •

Allow connection to DTA database from

•* •
non-DTA computers to generate reports, etc.

Upgrading/moving SOLID Server for DTA

•* •* •
5.0
*
DTA 5.0 requires ODBC Manager 3.5 or higher. ODBC 3.5 Manager needs to be installed
only if your computer is not compliant.

If you see the following error message when running the DTA installer,
you will have to run the DTA Database Support Installer to upgrade
your ODBC Manger to 3.5.
Warning: The ODBC version on “computer name” does not meet the
minimum requirements for DTA. Please run setup on “computer
name” from the database directory or enter a different machine.
The DTA installer installs ODBC Manager 3.5 only if no existing ODBC
Manager is found since upgrading an existing ODBC Manager may
require rebooting your computer, which interrupts the DTA installation
process.

256 Appendix D
 SOLID database maintenance
Components

Components

Running the installer (DTA Database Support

Installer)
When run on an NT computer, Setup displays questions regarding
moving a database server. Since the SOLID Server 3.0 component is for
moving the database server, it only displays if you answer “Yes” to all of
the following questions:

1. Do you already have a DTA 5.0 site installed?

2. Do you want to move an existing SOLID database server from a DTA
site?
3. Continue with database move?
No further questions display if you answer “No” to any of these
questions, and the SOLID Server 3.0 component installation is disabled.
This is to prevent unintentional installation of SOLID prior to DTA
installation.

OS Support
The DTA Database Support Installer supports the following
OS/component combinations as shown in Table D-2.
Table D-2 OS component combinations

DTA D/B Installer Supported Destination Supported Destination

(Win 95/98) (Win 95/98) (Win NT 4.0) (Win NT 4.0)

ODBC Manager 3.5 Yes System Yes System32

SOLID 3.0 Client Yes System Yes System32

(SOLID ODBC
Drivers)

SOLID Server 3.0 No N/A Yes User defined

(Embedded Engine
DBMS)

Appendix D 257
SOLID database maintenance
Components

Since DTA requires its DBMS to be on a Windows NT 4.0 computer

running as a service, this installer does not allow you to install SOLID
Server 3.0 to a Windows 9x computer.

Component Defaults
For ODBC Manager 3.5 and SOLID 3.0 Client, the installer
automatically detects the components and only checks those that are not
installed (or not compliant).
SOLID 3.0 is not selected by default to prevent unintentional
installation. This component should only be selected if you are moving
the SOLID database server for a DTA 5.0 site.

Dependencies
The component dependencies are as follows:

• SOLID Server 3.0 requires SOLID 3.0 Client and ODBC Manager 3.5.
• SOLID 3.0 Client requires ODBC Manager 3.5.
• ODBC Manager 3.5 has no dependencies.
The installer checks the necessary component(s) and displays an error
message if they are missing or non-compliant. It then returns to the
same component selection panel and checks all necessary components.

ODBC Manager 3.5

Selecting ODBC Manager 3.5 installs or upgrades your ODBC Manager
to version 3.5. If you have a newer version installed on your computer
and click Next with this component selected, a confirmation dialog box
appears asking you to enter DOWNGRADE to continue. This
confirmation is to prevent the accidental downgrade of your ODBC
Manager. If you have a newer version installed on your computer, it is
likely that one or more applications require it. Downgrading from a
newer ODBC Manager may result in errors and loss of functionality for
these applications.
The only time the DOWNGRADE option should be used is if your
computer contains an unstable version of ODBC, which may be the result
of a failed installation of an application or data corruption due to disk,
OS, or other failures. In most cases, if this component is not checked by
the installer by default, you should not check it.

258 Appendix D
 SOLID database maintenance
Components

The ODBC Manager is installed to the System folder under Windows 95

and 98, and to the System32 folder under Windows NT 4.0.
In compliance to Microsoft guidelines, the ODBC Manager cannot be
uninstalled.

SOLID 3.0 Client (SOLID ODBC Driver)

The SOLID 3.0 Client, along with the ODBC Manager, is necessary for a
computer to communicate with the DTA SOLID server.
Selecting SOLID 3.0 Client installs or upgrades your existing SOLID
Client. Since the SOLID Client files use version-specific file names,
existing SOLID clients older than 3.0 are not affected. Multiple versions
of the SOLID client can co-exist. If there is an existing SOLID 3.0 Client,
it will be overwritten.

SOLID Server 3.0 (SOLID Embedded Engine DBMS)

This component will only be visible if the computer you run Setup from is
an NT 4.0 computer and you have answered “Yes” to all questions,
confirming that you are moving a SOLID database server of a DTA 5.0
site during Setup. Selecting SOLID Server 3.0 installs the SOLID
DBMS. This option is only used if you are upgrading or moving your
DTA SOLID Database to a different computer. For instructions on
moving the SOLID database to a different computer, see “Moving a
SOLID database” on page 261.
For moving the database files to a different location on the same
computer, see “Repositioning a site” on page 119.
When prompted for the destination location (Choose Destination
Location panel), make sure you select a path to a local drive. SOLID does
not run as a service if its files reside on a network server or another
machine.
This install does not overwrite an existing SOLID server. This is to
prevent installing over an existing DTA 5.0 site’s SOLID database
server, which results in complete site data loss. If the detected SOLID is
from a bad installation, you may need to remove SOLID.

Appendix D 259
SOLID database maintenance
Components

The installer will detect the following:

• SOLID service installed

• SOLID.exe running
• SOLID database file (SOLID1.DB) in the selected path.
If any of the above is detected, the installer displays an error message
indicating what it has detected, then it returns to the component panel
and clears SOLID Server 3.0.

260 Appendix D
 SOLID database maintenance
Moving a SOLID database

Moving a SOLID database

The following procedure moves a SOLID database to a different
computer for an existing site.

To move a SOLID database

Step 1. Stop all the managers and the Console at the site for which you want to
move the SOLID database. Make sure no DTA component is connected to
the SOLID server.

Step 2. Shutdown the SOLID server.

Step 3. Run the Setup program on the computer on which you want to install the
SOLID database. Run the setup program from the \DATABASE
directory under the \CONSOLE directory of the site server or from the
\DATABASE directory of the DTA CD.

Step 4. While running the Setup program from the Select Components screen,
check SOLID 3.0 Client and SOLID Server 3.0 (Embedded Engine)
components.

Step 5. After SOLID is installed on the new machine, delete SOLID.ini, *.log,
and *.db files created during installation. Then, copy SOLID.ini, *.log,
and *.db files from the previous installation of SOLID or from your
restored backup. These files are located in the \SOLID directory of the
previous database computer.

Step 6. Start the SOLID service at the computer on which you installed SOLID.

Step 7. Start the SOLID service at the original installation computer. The
Console will not come up unless you do this, because it is still pointing to
the original one.

Step 8. Run the Console and go to the Site Configuration dialog box.

Step 9. Select the site from which you are moving the SOLID database and click
PROPERTIES.

Step 10. Go to the Database page and enter the new computer name in the
Computer Name field in the Database Server Information group.

Step 11. Click OK to save this change.

Appendix D 261
 SOLID database maintenance
Moving a SOLID database

Step 12. After the change is saved, shutdown the Console.

Step 13. Stop the SOLID server at the original (old) installation.

Step 14. Restart the managers.

Step 15. Restart the Console.

NOTE When installing the SOLID server on the new machine, you should use
the same userid and password for the database account as you did for the
original installation. If you enter a different userid and password, it will
not take effect because the userid and password are stored with the
database, which is overwritten with the original database after
installation. You will not be able to connect to the SOLID server using a
different userid and password after the SOLID database has been
overwritten by the new installation.

262 Appendix D
 SOLID database maintenance
Deleting a SOLID database

Deleting a SOLID database

The following procedure deletes a SOLID database from a computer.

To delete a SOLID database

Step 1. From the \CONSOLE directory of the computer where the SOLID
database is installed, run DTACLEAN.EXE.

Step 2. In the Options area of the DTA Clean dialog box, check Remove DTA
Database Service, and then click OK.

The message “Removing SOLID database server” appears.

The DTA Clean dialog box displays “Ready” when the process is finished.

Step 3. Manually remove the following directories and their files:

\HPDTA\SOLID
\HPDTA\CONSOLE
\HPDTA\MANAGERS

Step 4. Click Done to close the DTA Clean dialog box.

Appendix D 263
SOLID database maintenance
Deleting a SOLID database

264 Appendix D
 Index

Symbols setting up managed computers commands

.AOT, 63 for launching, 198 line, 239
.BMT, 63 SmartDeploy interactions, 21 options, 238
.DIF, 90 storing, 47 comma-separated values file
.DLD, 63 switches, 221 format, 90
.INT, 63 system requirements, 36 communications
.NTF, 64 transaction files, 63 changing mode of a site, 108
.RTF, 64 See also individual agents protocols, 29
.TXT, 90 APPIMPRT tool, 231 components
.WKS, 90 application agents defaults, 258
controlling, 149 dependencies, 258
Numerics group box, 150 requirements, 32
setting schedules, 155 configuration pages
2000 Professional applications SmartDeploy agent, 142
agents setup, 48 adding, 135 configuring SmartDeploy agent
deploying SmartDeploy agent, information replication, 62 options, 146
202 architecture elements, 23 connection
authentication, user, 39 changing mode, Satellite site,
A 108
accounts B database, 29
NT information, 145 backups minimum speed, 29
renewed, specifying, 234 correcting failed, 254 Winsock, 46
required, 39 creating directories, 250 Console, 23
requirements, 39 generic, 252 description, 44
agents restoring, 253 illustration, 68
communicating, 29 restoring to current state, 253 installing additional, 132
configuring workstations, 235 returning to original state, 253 location, 53
control by management server, scheduling, 248 requirements, 33
152 transfers to tape or CD, 251 tasks, 68
controlling, 149 Bindery environments, 201 core files, storage requirements,
controlling on managed 37
computers, 149 CSV, 90
C
functions, 46 Custom option, 55
installing to selected central site, 51
computers, 203 centralized configuration, 54 D
NT System Services, 47 child site, 51
adding, 169, 171 data
removing from managed changing display, 75
computers, 215 comparing installation
methods, 170 exporting, 90
running, 47 ODBC, 91
set up, 48 data scanning schedules, 98
color, changing display other file formats, 90
setting applications schedule, fan out, 62
155 Software Distribution log, 73
management, 67

Index 265
 Index

querying, 79 specifying a revised name, DTA

querying on a viewer, 79 113 accounts
replication order for multiple specifying revised informa- expired, renewing, 128
Satellite sites, 106 tion, 113 managers, 128
resorting support, 23 manager, 46
column, 78 see also backups; SOLID overview, 19
dialog, 78 database viewers, 68
roll up, 62 database management system. DTA NACCESS tool, 128
saving to other file formats, 90 See DBMS DTA Services, setting schedules,
schedules Database Support Installer, 255 159
child site scanning, 98 components, 256 DTACPI tool
scanning, 97 running, 257 standalone property sheet, 233
sorting, 77 using, 256 DTAUSER account, 39
summarizing, 87 dBASE III file format, 90 dual-processor server, 55
summarizing column, 87 DBF, 90 dynamic groups, 82
transferring, 23, 61 DBMS
method, 99 location, 30 E
Microsoft Windows, 23 renewing expired accounts, end-user. See user
Novell NetWare, 23 128 errors
schedule, 98 user account copying files, 212
Data Interchange Format, 90 Primary child sites, 171 SmartDeploy agent fails to
Data Scanning Schedules list requirements, 41 launch, 166
box, 97 specifying revised, 113 exporting data, 90
database debug information, 236 ODBC, 91
backing up, 239 deployment settings, 147 other file formats, 90
backups list, 239 Desktop Administrator. See DTA
connection requirements, 29 desktop environments,
F
description, 44 customizing, 21
disk space requirements, 37 Direct data transfers, 99 fan-out, 61
importing from DTA 4.x, 231 direct mapping protocols, 29 fields
installing, 255 directories, disk space copying values, 81
location, 29 requirements, 38 custom, 22
moving server, 257 distributed configuration, 59 modifying, 75
remote SOLID management, distribution jobs, information file errors, copying, 212
238 replication, 62 file server. See server
separate server, 56 Distribution Log data, 63 fonts, changing
server DMI compliant computers, 25 all viewers, 72
changing identifying method, Domain Administrator specific viewer, 73
114 account, 39
directory structure, 53 User ID, 181

266 Index
 Index

G J managers
group job-level flag, 48 account
creating, 82 Primary child site, 171
deleting, 87 L requirements, 41
information, 82 communicating, 29
launching programs remotely, control by management server,
130 152
H line commands, 239 controlling, 149
hardware local administrator account, 39 description, 45
inventory data, 63 log moving, 134
testing workstations, 236 file method, installing, 202 managing site, 50, 51
HP OpenView Desktop viewing, 209 Microsoft SQL Server, 21
Administrator. See DTA login scripts, 199 preparation, 31
Windows NT, 200 Microsoft SQL Server Client
I Logon account requirements, 40 requirements, 30
importing DTA 4.x database Lotus 1-2-3 file format, 90 Microsoft Windows NT, network
applications, 231 requirements, 28
inbox, 63 M Microsoft Windows, data
installation managed computers transfer, 23
computer requirements, 32 controlling agents, 149
database, 255 installing SmartDeploy agent, N
log, setting detail level, 212 197 NACESS tool, specifying
pausing, 209 remote control, 237 renewed accounts, 234
remote, 172 remote program launch, 130 NetWare
site software across the remote rebooting, 212 3.x environments, 201
network, 183 removing agents, 215 4.x /5.0 environments, 201
SmartDeploy agent, 141 requirements, 36 data transfer, 23
log file method, 202 setting up to launch agents, required, 28
software using CD, 190 198 requirements, 35
terminating, 209 Smart Deploy agent does not NetWare Directory Services
inter-site data transfer, 63 appear, 165 (NDS), 178
intra-site data transfer, 63 managed servers, specifying, 111 NetWare NDS environment, 201
Inventory management server NetWare NLS (National
description, 24 controlling agents/managers, Language Support)
storage requirements, 37 152 subdirectory, 178
Inventory agent directory structure, 53 Network Adapters, 22
function, 46 requirements, 34 Network Node Manager for
system requirements, 36 running SmartDeploy agent, Windows NT (NNMNT), 25
IPX/SPX. protocols, 29 153 network, displaying information,
ISQL_W tool, 31 separate, 57 68
ITSM Asset Manager, 25 viewing information, 117 NOS, specifying correct, 109

Index 267
 Index

Novell NetWare. See Netware Primary site exporting data to OBDC

NT System Services assigning as a new parent, 119 format, 91
account information, 145 description, 50 installing
running agents, 47 disk space requirements, 37 agents to selected computers,
operating system, 28 203
O Replication page, 96 Console to another computer,
OAREDIT (Object Address running SmartDeploy agent 132
Resolution editing) tool, wizard, 192 site software across the net-
configuring workstation scheduling data transfers, 98 work, 183
agents, 235 printing viewer contents, 88 software using CD, 190
object properties, modifying, 76 procedures launching program on
ODBC accessing the Site managed computer, 130
exporting data, 91 Configuration dialog box, merging two site trees, 120
manager, 30 107 modifying
real-time access, 92 adding object properties, 76
requirements, 30 application, 135 moving
support, 23 site, 173 manager, 134
ODBC Manager 3.5 site using the DTA CD, 189 SOLID database, 261
installing, 258 adding/deleting an object, 86 pausing installation, 209
management server, 172 assigning new parent Primary printing a viewer, 89
Online Documentation site, 119 querying on a viewer, 79
storage requirements, 37 changing removing agents from
OpenView Asset Manager, 25 all viewers displays, 70 managed computers, 215
OpenView IT/Operations, 25 connection mode. Satellite renewing
optimal performance, 55 site, 108 expired DBMS account, 128
options commands, 238 data replication order, 106 expired Site server account,
OS component combinations, Software Distribution log dis- 128
257 play colors, 73 Managers account, 129
outbox, 63 specific viewer display, 71 resorting
overview, 19 checking status, 210 data column, 78
configuring replication data from a dialog, 78
information, 101 restoring backup to current
P
copying field values, 81 state, 253
Parent site, 51 correcting a time zone, 109 returning to original backup
time zone, 174 creating a group, 82 state, 253
pcANYWHERE, 25 database server, modifying revising
performance, optimal, 55 DTA identification database server computer
policy files method, 115 name, 113
user, 199 deleting DBMS user account, 113
Windows NT, 200 groups, 87 managed servers, 111
Primary Domain Controller site, 125 site description, 109
(PDC), 172, 181 SOLID database, 263 running SmartDeploy agent
wizard, Primary site, 192

268 Index
 Index

saving data to other file remote installation, performing, SIF file import, 34
formats, 90 172 SmartDeploy agent account,
scheduling backups, 249 Remote Service Installer (RSI), 42
scoping to another site, 94 200 Software Distribution storage,
setting schedules for replication 37
application agents, 155 configuring information, 101 storage, 37
specifying controlling activity, 96 system, 28
correct site server NOS, 110 controlling the order to agents, 36
managed servers, 111 multiple Satellite sites, Inventory agent, 36
splitting a site tree, 122 106 SmartDeploy Agent, 36
summarizing column data, 87 data, 61 Software Distribution agent,
switching SmartDeploy agents schedules, modifying, 100 36
runs, 163 requirements roll-up, 61
terminating installation, 209 accounts, 39 RSI, installing SmartDeploy,
UNCs, configuring, 55 adding a child site, 171 204
using RSI to install/remove components, 32
agents, 204 computer installation, 32 S
validating setting with remote Console installation, 33 SAGENT.EXE, 48
install program, 189 core files storage, 37 SAGENT.INI, 48
viewers DBMS user account, 41 Satellite site
changing fonts (all), 72 disk space changing connection mode, 108
changing fonts (specific), 73 database, 37 description, 50
modifying fields, 75 directories, 38 disk space requirements, 37
viewing Primary site, 37 installing, disconnected mode,
management server informa- Satellite site, 37 170
tion, 117 DTA site server account, 40 operating system, 28
site server information, 118 Inventory storage, 37 replication data order, 106
product integration, 25 Logon account, 40 SmartDeploy agent
protocols managed computer, 36 configuration, 197
direct mapping, 29 management server, 34 schedules
support, 29 Managers account, 41 data transfer, 98
Microsoft SQL Server scanning data, 97
Q preparation, 31 setting DTA Services, 159
Query Analyzer tool, 32 Microsoft SQL Server Client, setting for application agents,
query frequency, SmartDeploy 30 155
agent, 151 network software, 28 SOLID database backups, 248
Novell NetWare, 35 SDL Dump utility, hardware
ODBC, 30 testing, 236
R
Online Documentation SERVCTRL tool, remotely
rebooting remotely managed storage, 37
computers, 212 controlling services, 237
resources, 27
Registered Events viewer, 69

Index 269
 Index

server deleting, 125 configuration, 195

centralized configuration, 54 DTA, 43 options, 146
database ID, 65 Satellite sites, 197
changing identifying method, information replication, 62 configuring, 142
114 installing software across the deploying Windows NT/2000
specifying revised informa- network, 183 Professional, 202
tion, 113 modifying, 107 features, 140
dual-processor, 55 monitoring, 107 function, 46
function configurations, 53 repositioning, 119 group box, 150
generating information report, revising information, 109 individual control, 153
240 scoping to another, 94 installation, 48, 141
managed separate server, 58 functions, 198
revising, 111 trees, 50 wizard, 192
specifying, 111 type characteristics, 51 installed program does not
management, separate, 57 working at another, 93 show, 165
separate see also server; Primary site; maintenance, 21
database, 56 child site managing, 139
distributed, 59 Site Configuration dialog box, Primary site, 192
site, 58 107 problems, 165
See also site server; sites; Site Information data scanning query frequency, 151
Primary site; child site; schedule, 98 running managers, 46
database server Site manager, 45 running on the management
Server Distribution agent transaction files, 63, 64 server, 153
function, 47 site server settings, 146
scheduling run time, 159 account requirements, 40 switching running, 163
Server Inventory agent location system requirements, 36
function, 47 viewing, 118 SmartDeploy Service
setting schedule, 159 remote control, 237 advanced user settings, 210
settings renewing an expired account, displaying, 210
deployment, 147 128 snapshot information files. See
SmartDeploy agent, 146 specifying management, 111 SIF
validating using the remote specifying the correct NOS, Snapshot technology, 21
install program, 189 109 SNMP compliant computers, 25
SIF file import requirements, 34 site tree software
site merging, 120 inventory data, 63
adding, 173 relationships, 51 removing, 216
adding, using DTA CD, 189 splitting, 122 Software Distribution
assigning a new parent SmartDeploy agent description, 24
Primary, 119 account, 171 log data, changing display
changing communication requirements, 42 color, 73
mode, 108 checking status, 210 storage requirements, 37
components, 44 Software Distribution agent, 46
correcting a time zone, 109 system requirements, 36

270 Index
 Index

SOLCON (SOLID Remote TFILEAGE utility, 243 W

Control) tool, 238 TFILECHK utility, 244 Windows 2000 Professional. See
SOLID 3.0 Client, installing, 259 TFILEDMP utility, 245 2000 Professional
SOLID 3.0 Embedded Engine time zone, parent site, 174 Windows 9x, agents setup, 48
bundled version, 23 tools, listing, 230 Windows NT
SOLID database TopTools Web, 25 agents setup, 48
bundled, 242 transaction files DBMS authentication, 31
deleting, 263 checking integrity, 244 deploying SmartDeploy agent,
maintenance, 247 description, 63 202
moving, 261 displaying, 245 Domain environments
read-only access, 39 expired Domain logins, 199
remote management, 238 reinstating, 243 local logins, 200
scheduling backup, 248 viewing, 243 remote control, 237
SOLID Embedded Engine transferring data SOLID Embedded Engine 3.0,
DBMS, 259 connection settings, 100 21
SOLID Server 3.0, installing, method, 99 Workgroup environments, 201
259 scheduling, 98 Windows NT Event Viewer, 45
SOLID service, starting, 250 Typical installation option, 55 Windows NT Workgroup
SOLID SQL Editor, 242 environment, 145
SOLID.ini, modifying, 249 U Winsock connection, 46
SOLID3.0 Embedded Engine, 21 UNCs (Universal Naming workstation
SOLSQL (SOLID SQL Editor) Conventions) basic data, 63
tool, 242 configuring, 55 hardware testing, 236
SQL Server database user upgrading caution, 14 modifying, 49
account requirements, 41 user
standalone property sheet, authentication, 39 Y
viewing, 233 policy files, 199
static groups, 82 year 2000 compliant, 20
utilities, listing, 230
adding/deleting an object, 86
storage requirements, 37
V
supervisor account, 40
switches, quick commands for vendor data replication, 62
agents, 221 viewers, 68
changing
T all displays, 70
specific display, 71
TCP/IP changing fonts
data transfers, 100 all viewers, 72
protocols, 29 specific viewer, 73
text file format, 90 modifying fields, 75
printing, 89
printing contents, 88

Index 271
Index

272 Index