Altiris Unix Software Delivery Solution User Guide

Altiris Unix Software Delivery Solution User Guide
Altiris®
UNIX Software Delivery Solution™5.6
User Guide
Notice
Copyright © 2000-2003 Altiris Inc. All rights reserved.
Product Version: 5.6
Document Date: July 14, 2003
Bootworks U.S. Patent No. 5,764,593.
RapiDeploy U.S. Patent No. 6,144,992.
Due to the inherently complex nature of computer software, Altiris does not warrant that the Altiris
software is error-free, will operate without interruption, is compatible with all equipment and
software configurations, or will otherwise meet your needs.
The content of this documentation is furnished for informational use only, is subject to change
without notice, and should not be construed as a commitment by Altiris. Altiris Inc. assumes no
responsibility or liability for any errors or inaccuracies that may appear in this documentation. For
the latest documentation, visit our Web site at www.altiris.com.
Altiris, the Altiris logo, BootWorks, Inventory Solution, LabExpert, PC Transplant, RapiDeploy,
and RapidInstall are registered trademarks of Altiris, Inc. in the United States.
Carbon Copy is a registered trademark licensed to Altiris, Inc. in the United States and a trademark
of Altiris, Inc. in other countries.
Altiris eXpress, Altiris Vision, Application Management Solution, Application Metering Solution,
Asset Control Solution, Asset Management Suite, Client Management Suite, Compliance Toolkit,
Conflict Analysis Solution, Contract Management Solution, Deployment Server, Deployment
Solution, Education Management Suite, Helpdesk, Helpdesk Solution,
HP Client Manager Software, Lab Management Suite, Migration Toolkit, Mobile Client for SMS,
My IT Forum, Notification Server, Problem Management Suite, Server Management Suite,
Server Monitor Solution, Site Monitor Solution, Software Delivery Solution,
TCO Management Solution, Unix Client for SMS, Unix Inventory Solution, Unix Software Deliver
Solution, Web Admin for SMS, Web Reports and other product names are trademarks of Altiris, Inc.
in the United States and other countries.
Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft
Corporation in the United States and/or other countries.
HP is a registered trademark of the Hewlett-Packard Corporation.
Compaq is a registered trademark of the Hewlett-Packard Corporation.
Macintosh is a registered trademark of the Apple Computer Corporation.
All other brand names are trademarks or registered trademarks of their respective companies.
UNIX Software Delivery Solution User Guide
2
Contents
UNIXGuide
Altiris®
User
Software Delivery Solution™5.6
Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Document Conventions
.............................................................. 6
Support
.......................................................................... 7
Training
.......................................................................... 7
Chapter 1: Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Introduction to UNIX Software Delivery Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Features of UNIX Software Delivery Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
New Features in UNIX Software Delivery Solution 5.6
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2: Setup and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
System Requirements
Notification Server
UNIX Computers
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Security Information and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agent Installation Security
.......................................................
Run Level Security
.............................................................
NS Server and NS Agent Transport Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NS Agent Listener
.............................................................
14
14
15
15
15
Step 1 – Get Notification Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download Notification Server and the UNIX Software Delivery Solution
....................
Install Notification Server
........................................................
A - Software Prerequisite Wizard
..............................................
B - Install Microsoft Database Engine (MSDE)
....................................
C - Install Additional Software Components
......................................
15
16
17
17
19
20
Step 2 - Install the Notification Server Software
Step 3 – Configure Altiris Notification Server
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Step 4 – Install the UNIX Software Delivery Solution
Upgrade to UNIX Software Delivery Solution 5.6
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Step 5 - Install the NS Agent to Target UNIX Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agent “Push” Installation
........................................................
Agent “Pull” Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNIX Log
....................................................................
Step 6 - Enabling the Software Delivery Solution Component of the NS Agent for UNIX
Install Solution Licenses
23
25
28
31
. . . . . . . . . . . 31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
UNIX Software Delivery Solution User Guide
3
Contents
Chapter 3: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
UNIX Software Delivery Solution and Notification Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Collections
...................................................................
Packages
....................................................................
My UNIX Packages
.........................................................
Packages vs. Policies
.......................................................
Packages - Execution Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
My UNIX Advertisements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNIX SW Delivery Policy Group
...............................................
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
35
36
36
37
38
38
39
40
41
UNIX NS Agent Configuration Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Collections - NS Agent
..........................................................
Packages - NS Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Policies - NS Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNIX NS Agent Configuration
.................................................
UNIX NS Agent Rollout Jobs
..................................................
Customize the UNIX NS Agent Configuration Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
43
44
45
45
47
48
Chapter 4: UNIX Agent Files, Settings, and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Agent Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Files, Links and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Files and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
49
50
50
50
NS Agent Configuration File
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Sample client.conf file
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Manual Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Manual Installation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Chapter 5: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Agent Installation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
NS Agent Installation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
NS Agent on WinNT Server Error
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
NS Agent Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Troubleshooting Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TCP/IP Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SSH and Telnet Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Domain Name System (DNS) Validation
.........................................
HTTP Communication Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FTP Validation
.............................................................
60
60
61
61
62
62
Additional Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Isolating issues in the subagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Using the log file
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Appendix A: Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Step-by-step How to Distribute a Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download Adobe Acrobat Reader
.................................................
Unzip the .GZ file
..............................................................
Uncompressing the .gz file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create a Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create a Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNIX Software Delivery Solution User Guide
64
65
65
66
70
73
4
Contents
Create a Policy or Advertisement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check the Policy or Advertisement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually installing Adobe Acrobat at the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify Success or Fail of Software Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check to see if the software package you sent installed successfully on the target UNIX computer.
83
Use Adobe Acrobat on the UNIX computer
..........................................
76
78
79
83
86
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
UNIX Software Delivery Solution User Guide
5
Preface
Before using this documentation, we recommend that you review the document conventions (see
“Document Conventions” on page 6).
Detailed information about Altiris products is included in each product’s documentation. The
product’s documentation is installed when the product is installed. To access Altiris product
documentation from the Web, go to our documentation Web page at www.altiris.com/support/
documentation.
If you have questions that are not answered in the documentation, we recommend that you use one
of our support options (see “Support” on page 7).
If you have feedback about this documentation, please send an e-mail message to our documentation
group at [email protected]
Document Conventions
The following table describes the conventions used in this document.
Document Conventions
What you see
Meaning
Altiris Notification
Server Product Guide
Note Most references to Altiris documents are hypertext links to those
References to other documents are italicized.
documents. For these links to work, the target document file must be in the
same location as the source document.
If viewing PDF documentation from our product CD or where the
documents were installed on your hard drive, the links will work.
If viewing a PDF document from our web site, the links to other Altiris
documents will not work. (The documents are stored in different folders).
If you download PDF documents from our web site and place them in the
same folder, the document references will link to the other PDF document
provided the target PDF document is in the folder.
Interface Element Name
File
> Save
server name/altiris/
documents
Buttons, menu items, tabs, and field names are displayed in bold text.
A series of mouse selections are represented in this format. The above
example means click on the File command on the menu bar, and then click
on the Save command.
A value in a path that depends on the user’s system is in italics. In this
example, server name needs to be replaced by the name of the user’s
server.
set variable = 123 Sample code is in Courier font.
www.altiris.com
Links to web pages are in blue text.
UNIX Software Delivery Solution User Guide
6
Preface
Support
Altiris is committed to providing world-class technical support and professional services to its
customers. Included with every product purchase is complimentary Electronic Support. For
customers who want a higher level of support, Altiris offers many fee-based services ranging from
Priority Support, which includes priority telephone and priority e-mail support, to on-site
consultation.
Before Contacting Support
We recommend that you do the following before contacting Support:
•
•
•
Download and install the latest version of the product and product updates from our web site
(www.altiris.com).
Read the product Release Notes. The Release Notes contain important information on the current
release including limitations and application specific workarounds. Many customer questions are
answered in the Release Notes.
Review the information in the Altiris support forums (go to www.altiris.com and click on
Support and then Forums). If you cannot find the answer to your question in the forums, you can
post your own question. The forums are monitored by our Support engineers, who will help you
with your questions.
Support Contact Information
Altiris is a global organization with operational centers in the following geographies:
•
•
•
Americas in Lindon, Utah covering North and South America
Asia Pacific in Sydney, Australia
Europe, Middle East, and Africa (EMEA) in Landau, Germany
Contact information for each of these operational centers is available at www.altiris.com/contact.
When contacting Support, please include the following information in the e-mail or have it ready
when calling:
•
•
•
•
Your name, e-mail address, and phone number
Product name and product version
Specific details about the problem, including specific system messages, error codes, and logs
Details about your system, including the operating system, applied services packs, hardware
configuration, network details, and other applications running on the system.
Training
To ensure that you are using Altiris products in the most effective way, Altiris offers in-depth,
instructor-led, hands-on courses. These courses will help you quickly learn the optimum methods
for installing, configuring, and managing your network using Altiris’ award-winning products. For
information about Altiris training, go to the following web site:
•
http://www.altiris.com/services/training/
UNIX Software Delivery Solution User Guide
7
Preface
UNIX Software Delivery Solution User Guide
8
Chapter 1:
Getting Started
If you are evaluating the UNIX Software Delivery Solution for the first time, you will want to go
directly to the Introduction to UNIX Software Delivery Solution link, where you can read an
overview and basic description of this product.
If you are an existing user of this product, go to the New Features link where you will find a list of
updates and enhancements that are new for UNIX Software Delivery Solution 5.6.
Quick Links
Introduction to UNIX Software
Delivery Solution (page 10)
Introduction and overview of the UNIX Software
Delivery Solution.
New Features in UNIX Software Description of updated features and
Delivery Solution 5.6 (page 10) enhancements, with links to more detailed
information in the documentation.
UNIX Software Delivery Solution User Guide
9
Chapter 1: Getting Started
Introduction to UNIX Software Delivery Solution
Introduction to UNIX Software Delivery Solution
Altiris® UNIX Software Delivery Solution™ 5.6 is a policy-based, software inventory management
solution that reduces the costs of deploying and managing UNIX and Linux systems. UNIX
Software Delivery Solution does so by allowing administrators to target and remotely install
software, patches, scripts and data files to UNIX and Linux systems.
The Altiris® Notification Server™ (NS) software is the core component for managing your
infrastructure systems. Altiris suites and solutions plug-in to the Notification Server architecture,
providing you the tools needed to monitor hardware and software, install software packages and file
updates, maintain security and BIOS settings, collect inventory, manage resources, and more.
Notification Server uses NS Agent software to gather information at each client computer for the
suites and solutions you have installed. The data is then sent to Notification Server’s centralized
database, where you can view, print, and create your own custom reports. Data collection can be
automated through the use of scheduled events.
Notification Policies and Alert Manager can be set up to respond to a variety of actions, which can
generate reports, send automated e-mail notifications to individuals or workgroups, and create work
items for support groups.
Notification Server data can integrate with Microsoft Systems Management Server (SMS). After NS
is configured, you can query, browse, or create reports in the SMS environment. Inventory Solution
for UNIX does not require any special configuration to be compatible with SMS.
For more information about Microsoft SMS Configuration, and all other Notification Server
functionality, see the Altiris Notification Server User Guide located at http://www.altiris.com/
support/documentation.
Features of UNIX Software Delivery Solution
The UNIX Software Delivery Solution lets you create software packages, consisting of files,
commands, or entire programs that can be deployed to client computers where the NS Agent is
installed. A Notification Policy is sent from the Notification Server to a collection of UNIX or Linux
computers, which tell the clients to go get the new package from the Notification Server. This
solution gives you the tools to manage software delivery of programs, commands and file updates.
New Features in UNIX Software Delivery Solution 5.6
New Features
UNIX Software Delivery Solution 5.6 has added some new features, which enhance the capabilities
of this solution. The key features include the following.
New Features List
Feature
Description
Security Additions
•
•
Support for HTTPS for Data Movement
Support for SSH for system communication
Scalability
•
•
Support for Checkpoint/restart
Bandwidth and CPU throttle
Updated Platforms
•
Updated to support the latest versions of UNIX and Linux (See
“System Requirements” on page 12)
Ease of Use
•
•
New plug-in agent architecture
New features for agent installation
UNIX Software Delivery Solution User Guide
10
Chapter 2:
Setup and Installation
This software delivery tool is a web-based plug-in program to the Altiris® Notification Server™,
which lets you deploy software programs and files to UNIX or Linux computers.
The topic list below is in the order of how you must proceed to setup and install the UNIX Software
Delivery Solution on the Notification Server. You MUST complete all topics of this chapter to be
fully installed with this product.
Important “Step 1 – Get Notification Server Software” on page 15 requires you to perform four
additional sub-steps before you can proceed to “Step 3 – Configure Altiris Notification Server” on
page 21.
Quick Links
System Requirements (page 12)
Requirements for both Notification Server and
UNIX computers.
Security Information and
Considerations (page 14)
Security information for the NS Agent, run level
security, and transport security.
Step 1 – Get Notification Server Get the Notification Server software from the
Software (page 15)
Altiris web site.
Step 2 - Install the Notification
Server Software (page 20)
How to install the Notification Server software.
Step 3 – Configure Altiris
Notification Server (page 21)
Configure the user identity, e-mail settings, and
the SQL server database.
Step 4 – Install the UNIX
How to install the UNIX Software Delivery
Software Delivery Solution (page Solution.
22)
Upgrade to UNIX Software
Delivery Solution 5.6 (page 23)
How to upgrade from a previous version of UNIX
Software Delivery Solution.
Step 5 - Install the NS Agent to
Target UNIX Computers (page
23)
The NS Agent for UNIX, methods of installation
to target computers.
Step 6 - Enabling the Software
Description of Enabling the Software Delivery
Delivery Solution Component of Solution components.
the NS Agent for UNIX (page 31)
Install Solution Licenses (page
31)
UNIX Software Delivery Solution User Guide
How to license Altiris products
11
Chapter 2: Setup and Installation
System Requirements
System Requirements
Notification Server
You must meet the requirements for both the “Notification Server” on page 12, and the “UNIX
Computers” on page 13, before you can proceed with the installation of this product.
Hardware
To scale the server to support thousands of computers, faster processors and more memory is
recommended.
Minimum Requirements
Hardware
Description
Processor
•
Pentium III 800 MHz or higher
RAM
•
512 MB (1 GB recommended)
File system
•
NTFS system partition
Disk space
•
•
20 MB for Notification Server and components
1 GB for SQL Server database.
Software
If you plan to use SQL Server as the database for Notification Server, be sure to install it prior to
running the Software Prerequisites Wizard. The wizard will check for a SQL database and if one is
not present, you will be asked to install MSDE. If you choose not to install the MSDE default
database, you must exit the wizard, install SQL Server and any other missing software, then rerun
the wizard again.
Note The MSDE database may be used; however, it is not recommended for a production
environment.
Software Requirements
Software
Description
Operating System
•
•
•
Windows 2003 Server
Windows 2000 Server SP2 or later (recommended)
NT Server 4.0 SP6a or later
SQL Database
•
•
•
Microsoft SQL Server 7 SP3 or later (recommended)
Microsoft SQL Server 2000 SP2 (recommended)
Microsoft MSDE (approved)
Microsoft Windows
Internet Information
Services (IIS)
•
Microsoft IIS 5.0 (requires the Web server to be hosted on
NTFS). This component is not installed by default with
Windows 2000 or later
Microsoft Windows
Internet Information
Services FTP Services
•
The FTP component is installed by default with Windows
2000 or later
Web Browser
•
Microsoft Internet Explorer 6.0 or later
UNIX Software Delivery Solution User Guide
12
Chapter 2: Setup and Installation
System Requirements
UNIX Computers
We recommend you meet the requirements for the supported systems and hardware listed below,
before installing the UNIX Software Delivery Solution, and the NS Agent for UNIX to the Notification
Server computer.
Operating System
The following table is a list of operating systems that are supported by the UNIX Software Delivery
Solution and the NS Agent for UNIX. The UNIX computers must meet these requirements before you
proceed with the installation of this solution.
Supported Systems
Operating System
Hardware
Version
HP-UX
HP-PA
11, 11i
IBM AIX
Power-PC / RS6000
4.3.3, 5.1, 5.2
Sun Solaris
Sparc
7, 8, 9
Red Hat Linux
x86
7.2, 7.3, 8, Advance Server 2.1
SuSE Linux
x86
8.0, 8.1 Enterprise Server 8
UnitedLinux
x86
1.0
Legacy System Support
Previously, UNIX Software Delivery Solution 5.5 supported older and different versions of UNIX
and Linux. The UNIX Software Delivery Solution 5.6 architecture is designed so that the 5.5 agents
can continue to work with the 5.6 solution. All versions of UNIX and Linux that were supported
under 5.5 will continue to be supported under 5.6, but without support for the new features of 5.6.
The following versions of UNIX and Linux are supported under this legacy definition.
Supported Legacy Systems
Operating System
Hardware
Version
HP-UX
HP-PA
10.10, 10.20, 10.30
IBM AIX
Power-PC / RS6000
4.1- 4.1.5, 4.2 - 4.2.1, 4.3 4.3.2
Sun Solaris
Sparc
2.51, 2.6
Sun Solaris
x86
2.6, 7, 8
Red Hat Linux
x86
5.2, 6.0, 6.1, 6.2, 7.0, 7.1
SGI Irix
SGI
6.0 - 6.5
Hardware
Minimum Requirements
Hardware
Description
Disk Space
30-50 MB
RAM
5-15 MB (depending on operating system)
UNIX Software Delivery Solution User Guide
13
Chapter 2: Setup and Installation
Security Information and Considerations
Software
Software Requirements
Software
Description
NS Agent for UNIX
The NS Agent for UNIX communicates with Notification Server
via HTTPS. From the Notification Server, you can configure the
NS Agent for UNIX to run at anytime and as often as you want. A
single Notification Server is able to handle the load of many
thousands of UNIX computers, if the agent is set to run no more
than once a day.
Note HTTPS is a session based protocol. The data collected by
the agent can be safely transmitted over heavy network traffic, as
well as low bandwidths. The data reported from most UNIX
computers is generally under 300 KB in size.
Security Information and Considerations
In this release of UNIX Software Delivery Solution, there are several new features to enhance the
security of the solution, and other areas where information regarding security implementation that
may be of interest. These areas include the Notification Server (NS) Console, Agent Installation
Security (user-level access and transport), Run Level Security in which the agent will run, and the
NS Server and NS Agent communication Security.
For more information about Notification Server Console Security and all other Notification Server
functionality, see the Altiris Notification Server User Guide located at http://www.altiris.com/
support/documentation.
Agent Installation Security
To install the NS Agent for UNIX onto a target UNIX computer, you need to have a root or root
equivalent user name and password. The NS Agent can be installed by various methods, including
Push the NS Agent from the NS console. When the agent is installed through the Push method, the
UNIX Software Delivery Solution will initially use SSH to connect to the target computer(s) to start
the installation process. If SSH fails it will try Telnet, which is not a secure protocol, then passes the
supplied user name and passwords as clear text across the network. If greater security is important
to your companies environment, and you have not already turned off Telnet, you may want to
consider doing so.
Note: The system supports SSH version 1 or 2, and utilizes the user name and password
authentication method. It does not support public and private key usage at this time.
If you want to use SSH to securely push the NS Agent out to the target UNIX computers, the
following must be done:
•
SSHD must be installed on the target UNIX computers
•
SSHD can be either V1 or V2
The username and password authentication must be enabled for a SSH based login on the UNIX
computers. When connecting via SSH, the implementation forces the selection of encryption
algorithms (for encAny value) in the following order:
1
SSH2 connection will first try to negotiate AES (any type) and if it fails, TripleDES will be used.
If TripleDES is not available, Blowfish is selected, and if that is not available, the connection
will be dropped. DES is not negotiated at all because most (new) servers do not support it
because it is not secure.
2
SSH1 connection will try to negotiation TripleDES algorithm and if that fails, it will try
Blowfish. If Blowfish is not available (by remote server), it will fallback to DES.
Note: The DES algorithm is declared as ‘insecure’, so avoid using it if possible.
UNIX Software Delivery Solution User Guide
14
Chapter 2: Setup and Installation
Step 1 – Get Notification Server Software
Run Level Security
The UNIX Software Delivery Agent is installed and runs as a root or root equivalent user. This is
required to probe and collect the various pieces of information that will be tracked for a particular
UNIX system.
NS Server and NS Agent Transport Security
The NS Agent can be configured to use HTTPS based communication with the Notification Server;
no additional components are required. OpenSSL 0.9.6 is used internally in the agent’s comm
modules. The internal version of OpenSSL is used regardless of the presence or absence of an
OpenSSL library on the UNIX computer.
To enable HTTPS based communication, the Notification Server must be configured to use HTTPS
(see the Altiris Notification Server User Guide located at http://www.altiris.com/support/
documentation). Additionally, the client.conf file must be edited so that the ns_url_format variable
is untenanted and changed to specify HTTPS. This can be done after the NS Agent is installed to
client UNIX computers by running a software delivery job.
NS Agent Listener
When a new UNIX Policy or Advertisement is created, there is an option under Client Notification to
notify clients immediately. If this option is selected, Notification Server will send out a UDP request
to the UNIX computer on port 6868. XINETD on that computer, as a part of the NS Agent for UNIX,
will be listening on that port and based on receiving the request, will spawn a process that forces the
computer to refresh its policies from the Notification Server. After this is done, the UNIX computer
finds that there is new software to be installed and will pull the packages and install the software.
This can be very useful if you want to install security updates or software patches, which often
requires immediate action.
The reason this is listed in the security section, is that under normal circumstances, all
communication in the Notification Server infrastructure comes from the agent. This limits the
security risks because all communication is sourced from a secure level on the system. In this case,
the UNIX computer is being notified or tickled to let it know that it has work to do. Many companies
may not want to expose port 6868 on their systems, or at least may want to configure the firewall on
the system to only allow communication on port 6868 to come only from the Notification Server.
Again, for those companies with strict security policies, we raise this for informational and
awareness purposes only.
Step 1 – Get Notification Server Software
Altiris® Notification Server™ is a web-based solution to help manage your network and nonnetwork resources. Altiris suites and solutions plug-in to Notification Server, which provide the
tools to manage a specific area of the IT technology lifecycle.
The UNIX Software Delivery Solution lets you deploy software programs and files to UNIX and
Linux computers on the network, and utilize features such as: Alert Manager, policies, collections,
and online reporting.
Notification Server and the UNIX Software Delivery Solution will install consecutively through the
use of an install wizard. When you unzip the downloaded file from Notification Server’s Web
Administration Console Solution Center, you will execute the AeXNSInstallHelper.exe file which,
will launch the Software Prerequisite Wizard. The wizard determines if the computer you are trying
to install to, meets all the software requirements. If needed, the Notification Server files will be
UNIX Software Delivery Solution User Guide
15
Chapter 2: Setup and Installation
Step 1 – Get Notification Server Software
downloaded and installed to the computer. After Notification Server is installed, the
AeXNSInstallHelper.exe file automatically begins the download to install the UNIX Software
Delivery Solution.
Note You can download the UNIX Software Delivery Solution on a computer other than the
designated Notification Server, which is helpful for those administrators and testers who want to
evaluate the product before installing or upgrading to a live production environment.
Before you start managing resources, you must first install the Notification Server software. Choose
one of the options below.
•
Option 1 - If you are a repeat customer and are using Notification Server and UNIX Software
Delivery Solution, go to “A - Software Prerequisite Wizard” on page 17.
•
Option 2 - If you are evaluating the UNIX Software Delivery Solution for the first time, go to
“Download Notification Server and the UNIX Software Delivery Solution” on page 16.
Download Notification Server and the UNIX
Software Delivery Solution
The zip file you download contains an executable file that will launch the Software Prerequisite
Wizard. The wizard will examine the computer where you want to install Notification Server and
the UNIX Software Delivery Solution.
To download Notification Server and the UNIX Software Delivery Solution
1
Go to the Altiris web site at www.altiris.com, click Download.
2
Click UNIX Software Delivery Solution from the drop-down list.
3
Enter your e-mail address, and then click Continue.
4
Enter the Personal Information in the form on the page, and then click Continue.
5
Enter the Business Information in the form on the page, and then click Continue.
6
Read the Evaluation License Agreement, and then click Yes, I Agree.
7
Click Save as, to save the file to a location on your computer.
8
Navigate to the location where you saved the unzip product files, and then go to “Install
Notification Server” on page 17.
Note The NS Agent is a base plug-in program to Notification Server. The UNIX Software Delivery
Solution adds files to the base NS Agent that resides on the Notification Server. After the solution is
installed, you will configure the setting for the NS Agent for UNIX, and then deploy it to UNIX
computers. If you install other Altiris UNIX or Linux suites or solutions, the files will automatically
plug-in to the base NS Agent.
UNIX Software Delivery Solution User Guide
16
Chapter 2: Setup and Installation
Step 1 – Get Notification Server Software
Install Notification Server
Notification Server must be installed before you can add other Altiris suites or solutions. Choose one
of the options below to begin the process of installing the Notification Server software followed by
the UNIX Software Delivery Solution.
Option 1 - Notification Server Is NOT Installed
If you currently do not have a server installed with Notification Server, go to “A - Software
Prerequisite Wizard” on page 17.
Option 2 - Notification Server Is Already Installed
If you already have Notification Server installed on a server, do the following.
a
b
Navigate to the location where you unzipped the installation files on the computer.
Click AXNSInstallHelper.exe to start the Altiris Notification Server Software Prerequisite
Wizard.
c
The wizard will make sure you are using the most current Notification Server software. Go
to “Step 4 – Install the UNIX Software Delivery Solution” on page 22 and continue with the
instructions.
A - Software Prerequisite Wizard
You must meet the hardware and software requirements before you can install Notification Server
to a designated computer. As part of the installation process, the Software Prerequisite Wizard
examines your computer to determine if all required software is present. If software components are
missing, you will be prompted to install the necessary files before you can proceed. The wizard will
display a confirmation message when all software requirements are met.
1
Click AeXNSInstallHelper.exe to start the Altiris Notification Server Software Prerequisite Wizard.
2
Click Next.
The wizard will ask if you want to install Notification Server on this computer.
3
If you are sure you want to install Notification Server on the computer; click Yes, and then Next.
4
If the wizard finds all prerequisite software present on the computer, the following confirmation
dialog box appears. Do the following.
a
Click Finish.
b
Go to “Step 2 - Install the Notification Server Software” on page 20 to continue with the
Notification Server software install.
UNIX Software Delivery Solution User Guide
17
Chapter 2: Setup and Installation
5
Step 1 – Get Notification Server Software
If the wizard finds the computer does not meet the software requirements, the dialog box will
display a list of missing software. Do the following.
a
Clear the Restart this wizard upon reboot check box to re-run the wizard manually after all
required software is loaded. If you are unsure of the requirements, you can click in the Help
column on the Details link for more information.
Note We recommend you leave the default check box selected. You must re-run the wizard
to ensure you have met all software requirements.
b
6
Click Next.
If it was determined that a SQL Server or MSDE database is not installed, the Download and
Install Microsoft Database Engine page appears. Do the following.
•
To download and install MSDE, click Yes and then Next. Go to “B - Install Microsoft
Database Engine (MSDE)” on page 19 for detailed help.
Note The MSDE database can be used for evaluation purposes, but it is not recommended
for a live production environment.
•
Install SQL Server. See the Microsoft SQL Server documentation.
UNIX Software Delivery Solution User Guide
18
Chapter 2: Setup and Installation
7
Step 1 – Get Notification Server Software
If the additional software requirements (other than MSDE) is not found on the computer, a dialog
box will appear displaying a list of missing software, then do the following.
a
Make a list of the missing software in the dialog box.
b
Click Finish to exit the wizard.
c
Go to “C - Install Additional Software Components” on page 20.
B - Install Microsoft Database Engine (MSDE)
You have selected to download and install the Microsoft Database Engine, do the following.
1
At the File Download dialog box prompt, do one of the following:
•
Internet Explorer 6 users with the current Microsoft updates, click Open.
•
Internet Explorer 6 users without the current Microsoft updates, click Save. The Save As
dialog box appears, navigate to a folder where you want to save the unixdbsetup.exe file, then
click Save. When the file download is complete, click Open.
2
When the WinZip Self-Extractor prompts you to Unzip the unixdbsetup[1].exe file, specify an
unzip folder or accept the default folder of c:\unixdbsetup.
3
Click Unzip to extract the files, and then click OK.
4
When the command box appears, wait for the MSDE installation to complete. The installation
may take a few minutes.
5
When the MSDE installation is complete, press any key.
6
If additional software is needed to meet the Notification Server requirements, go to “C - Install
Additional Software Components” on page 20.
7
If MSDE is the only installation needed to meet the software requirements for Notification
Server, you must re-run the Software Prerequisites Wizard. Go to “A - Software Prerequisite
Wizard” on page 17.
UNIX Software Delivery Solution User Guide
19
Chapter 2: Setup and Installation
Step 2 - Install the Notification Server Software
C - Install Additional Software Components
Important If you have been directed to this step, you need to install all missing software to the
computer before you can proceed with the Notification Server installation.
The following is an example of how to install Microsoft Internet Information Services (IIS), and the
File Transfer Protocol (FTP) to a Windows 2000 Server computer. Follow the instructions or
wizards from the software manufactures to install all missing software.
Install Microsoft Internet Information Services (IIS)
1
Click Start > Settings > Control Panel > Add/Remove Programs.
2
In the left pane, click Add/Remove Windows Components.
3
Select Internet Information Services (IIS) from the list of components.
4
Click Details.
5
Select the File Transfer Protocol (FTP) Server and the World Wide Web Server check boxes.
6
Click OK.
7
Click Next.
8
Follow the instructions on the screen to complete the Windows Components Wizard.
9
When all the missing software components have been installed, re-run the Software Prerequisites
Wizard again. Go to “A - Software Prerequisite Wizard” on page 17.
Step 2 - Install the Notification Server Software
1
Now that the Software Prerequisites Wizard is finished, a message dialog box appears telling you
that the Altiris Notification Server program download is about to begin. Click OK to proceed.
2
The Web browser opens to the http://www.altiris.com/support/documentation/ page, while the
File Download dialog box appears in the foreground. Click one of the options below to install
Notification Server.
•
Option 1 - Click Run this program from its current location to download from the online server.
When the file download is finished, go to step 3 on page 20.
•
Option 2 - Click Save this program to disk, and then click OK.
a
When the Save As dialog box appears, navigate to a folder where you want to save the
AeXNS_5_5.exe file, and then click Save.
Note Saving the file lets you copy it to removable media, so you can install Notification
Server to a computer that is not online.
b
Navigate to the location where you saved the file, AeXNS_5_5.exe.
c
Double-click AeXNS_5_5.exe.
3
The Altiris Packager Self-Extracting Executable dialog box appears, followed by the Windows
Installer dialog box. The Altiris Notification Server – Install Wizard will help you through the rest of
the Notification Server setup. Click Next to proceed.
4
Read the License Agreement. Click I accept the terms of the license agreement, and then click Next.
5
Enter the User Name and Organization. Select the option Install this application for, and then click
Next.
6
Click Complete as the Setup Type, and then click Next.
7
Click Install to begin the installation.
The Installing Altiris Notification Server dialog box displays the status of the files being installed
to the computer.
8
When the InstallShield Wizard Completed dialog box appears, click Finish.
UNIX Software Delivery Solution User Guide
20
Chapter 2: Setup and Installation
Step 3 – Configure Altiris Notification Server
The Notification Server program is now installed. There are three more tasks you must complete
before the Notification Server Web Administration Console can be used. Go to “Step 3 – Configure
Altiris Notification Server” on page 21 to complete these steps.
Step 3 – Configure Altiris Notification Server
Important If you have completed all of “Step 1 – Get Notification Server Software” on page 15
(including the sub-steps) and “Step 2 - Install the Notification Server Software” on page 20, you may
proceed.
You must configure a User Identity Setting, E-mail Information (optional), and SQL Server Information
before Notification Server becomes functional. The next three tasks will require your input.
A - User Identity Settings
1
Enter the User (domain\username).
Important The domain entry is the Domain Name in which the computer is associated with on the
network. If the computer is not attached to a network domain, enter the Workgroup name of the
computer. The user name must be a Windows user with local administrator rights.
2
3
Enter a valid Password for the user name you enter in Step 1.
Re-enter the password to Confirm entry.
Note You are not creating a new user account, rather, you are confirming that the password you
entered for an existing user account is correct.
4
Click Next.
B - E-mail Information (optional)
The e-mail information for this step can be entered at a later time, through the use of the Web
Administration Console > Configuration tab. If you choose to enter the information later, click Next to
continue. Go to “C - SQL Server Information” on page 21.
1
Enter a valid User name. The name must be a valid user allowed to login to the mail server.
2
Enter a Password for the user entered above.
3
Enter your SMTP Server. The DNS name or IP address of your SMTP server.
4
Enter an Administrator E-mail Address. Notification Server can send e-mail notices and alerts to
the administrator.
5
Click Send a Test E-mail. This is a test to ensure Notification Server is sending mail to the correct
address.
6
Click Next.
C - SQL Server Information
1
Select an option to log into the SQL Server database.
Important If you do not enter an account name and password with local administrative rights,
“sa” will be used as the default SQL user account. By using the default user account, the database
is less secure and at greater risk for unwanted users to access the data. We recommend you use
an assigned account name and password to access the SQL Server database.
2
Click Next.
3
The Database Setup dialog box appears. You must wait for the software to complete the setup
functions. If you do not wait for the Database Setup dialog box to close before performing any
other functions on the computer, it can result in an incomplete configuration of the database.
4
If the database setup process returns an error, and you are using MSDE, do the following:
a
Click Back.
b
Stop MSDE: Start > Programs > MSDE > Service Manager, and then click Stop.
UNIX Software Delivery Solution User Guide
21
Chapter 2: Setup and Installation
5
Step 4 – Install the UNIX Software Delivery Solution
c
The message “Are you sure you wish to STOP the MSSQL Server on \\servername?” appears,
click Yes.
d
Exit MSDE: Right-click the MSSQL Server icon in the lower right hand corner of the display,
and then click Exit.
e
Start MSDE: Click Start > Programs > MSDE > Service Manager, and then click Start.
f
On the database configuration page, click Next then repeat step 3 on page 21.
When the Web Administration Console opens to the Solution Center tab, go to “Step 4 – Install the
UNIX Software Delivery Solution” on page 22.
Step 4 – Install the UNIX Software Delivery Solution
If you are an Altiris customer already using an earlier version of the UNIX Software Delivery
Solution want to upgrade to this release, go to “Upgrade to UNIX Software Delivery Solution 5.6”
on page 23.
If you are a first time user of the UNIX Software Delivery Solution, and are trying to install the
product, the AeXNSInstallHelper.exe file you executed in “Step 1 – Get Notification Server
Software” on page 15, automatically starts the download and install process for the UNIX Software
Delivery Solution and the NS Agent for UNIX. If you received a “download failed” error message
at the bottom of the Web Administration Console page, you can restart the process again manually.
Follow the procedures to “Restart File Download” on page 22.
Restart File Download
The procedure below will guide you through the download and installation process for the UNIX
Software Delivery Solution, and the NS Agent for UNIX.
To install the UNIX Software Delivery Solution
1
Click Start > Programs > Altiris > Altiris eXpress > Notification Server > Web Administration Console.
2
Click the Solution Center tab.
3
Click NS Solutions, the topic category expands to display a list of available solutions. Click the
topic category again to hide the list.
4
Click UNIX Software Delivery Solution.
5
When the Suite Download and Installation dialog box appears, click Start. The Software Delivery
Solution will download and install to the Notification Server computer.
Note The download may take several minutes, and the files will install and configure
automatically. When the process is complete, the Web browser will return to the Solution Center
tab.
To install NS Agent for UNIX
1
Click Start > Programs > Altiris > Altiris eXpress > Notification Server > Web Administration Console.
2
Click the Solution Center tab.
3
Click NS Solutions.
4
Click NS Agent for UNIX.
5
When the Suite Download and Installation dialog box appears, click Start. The NS Agent for UNIX
will download and install to the Notification Server computer.
Note The download may take several minutes, and the files will install and configure
automatically. When the process is complete, the Web Administrator Console will return to the
tab.
Solution Center
UNIX Software Delivery Solution User Guide
22
Chapter 2: Setup and Installation
Step 5 - Install the NS Agent to Target UNIX Computers
Upgrade to UNIX Software Delivery Solution 5.6
If you are an Altiris customer who wants to upgrade to the UNIX Software Delivery Solution 5.6
release, you must do certain tasks and be aware of the following information:
•
Upgrading the UNIX Software Delivery Solution to 5.6 on the server is all that is required.
•
UNIX Software Delivery Solution 5.6 supports the existing 5.5 agents, however you will not be
able to reconfigure them or install the 5.5 agents to new UNIX computers from the Notification
Server, as the 5.5 installation pages will no longer be available when the 5.6 solution is installed.
•
You should make any changes to the 5.5 agents from the console before installing 5.6. After
installing the 5.6 solution, the only way to change the 5.5 agent’s configuration is through either
a manual edit of their configuration, or by using custom 5.6 software delivery jobs. Obviously,
this applies to the agents that will not be upgraded to the 5.6 agents due to their classification in
the Supported Legacy Systems table.
•
If you have many UNIX computers that fall into the legacy definition (see the Supported Legacy
Systems table), you might consider installing a separate NS 5.5 server with the 5.5 version of
UNIX Software Delivery Solution. This would allow you to change the client configuration or
push out the 5.5 agent. This 5.5 server could then be setup to forward its data to the NS server
that is installed with UNIX Software Delivery Solution 5.6.
Note: The 5.5 agents do not automatically recognize a more recent agent, nor do they
automatically update. The latest version of the 5.5 agents are installed and made available on the
NS server so you can install them onto legacy systems.
•
Software Delivery jobs and Collections are provided with this release so that the new NS Agent
for UNIX can be rolled out to supported 5.5 UNIX computers. These Collections can be found
in the Web Administration Console under the NS Agent for UNIX, Collections section. The
Collections target the specific platforms so that the NS Agent can be updated. The distribution
Policies are not enabled by default. This allows you to stagger the rollout of the NS Agent for
UNIX onto your UNIX and Linux computers on your own time table. You can also create new
collections to further sub-divide the systems for agent deployment.
•
Computers with the UNIX Software Delivery agent 5.5 can be updated from Notification Server
by enabling a Policy. Computers with the 5.5 agent that are only using the UNIX Software
Delivery Solution, will have to use the Agent ‘Push’ Installation, Agent ‘Pull’ Installation, or a
Manual Installation to upgrade to the new NS Agent.
Note: If you have a mix of UNIX computers using the older 5.5 agent and other computers using the
newer NS Agent for UNIX 5.6, be aware that the computers using the 5.5 agent will not be able to
take advantage of the new features UNIX Software Delivery Solution 5.6 offers, such as the security
or scalability features previously discussed.
You can now install the NS Agent to target UNIX computers. Go to “Step 5 - Install the NS Agent
to Target UNIX Computers” on page 23.
Step 5 - Install the NS Agent to Target UNIX Computers
The NS Agent for UNIX is a key component of the UNIX Software Delivery Solution. The NS Agent
is a compilation of files that reside on each UNIX computer within a network environment. The
agent collects hardware and software inventory information, then sends the data to the Notification
Server’s centralized database.
There are different methods of installing the NS Agent to UNIX computers. The options on the UNIX
Agent Installation page are as follows:
•
Remote Installation Setting - Configure
•
- This method is initiated from Notification Server’s Web
Administration Console. The Remote Installation Settings determine the connectivity and login
settings for the target computers. You can choose to install one computer at a time, or install
multiple computers in one session. The configuration settings (with exception to password
the communication protocol and login authentication
settings. These settings will be used to install the agent to UNIX or Linux computers. Go to
“Remote Installation Settings” on page 24.
Agent ‘Push’ Installation
UNIX Software Delivery Solution User Guide
23
Chapter 2: Setup and Installation
Step 5 - Install the NS Agent to Target UNIX Computers
information) you enter can be saved and used for future installs. Go to “Agent “Push”
Installation” on page 25.
•
Agent ‘Pull’ Installation - The “Pull” method requires a person, with root or root equivalent access
rights, to log on to the computer needing the agent. The user will go to a specific URL and “pull”
the agent from the Notification Server. Go to “Agent “Pull” Installation” on page 28.
•
Agent ‘Manual’ Installation - The NS Agent for UNIX can be installed to a target computer manually.
This lets you download the files to a computer and copy them to any removable media, which
can then be installed to a computer in a lab or test environment. Go to “Agent “Pull” Installation”
on page 28.
Remote Installation Settings
As part of the Push Installation, you must provide the settings for authentication and communication.
If you are doing bulk (multiple) installations onto many UNIX computers, setting the options in
Remote Installation Settings can be very helpful. These settings are not required because they can be
over-ridden by manually editing the table data directly.
1
From the Web Administration Console, click the Configuration tab.
2
In the left pane, click UNIX Agent Installation.
3
In the right pane, click Remote Installation Settings.
4
If you select the Use the same on all machines check box, the settings on this page will apply to
each target computer that you want to install the agent to. Choose the settings on the page using
the information table below as reference.
Remote Installation Settings
Setting Option
Action
Use the same on all machines
Select the check box to use the settings you choose on this
page for agents deployed to multiple target computers.
Private User Login
Enter a root or a root equivalent user account name.
Password
Enter the password for the user you entered above.
Multiple Passwords
The solution has the option to try multiple passwords
when attempting to login to the target UNIX computers.
The different user accounts chosen may be available on all
computers, but different passwords may be required to
login to each computer. The installation script will try the
next password in the list if login failure occurs.
Login first using unprivileged user
Select the check box to login as an unprivileged account.
User Login
Enter a valid login account. This is used when root is
disabled as a valid login over SSH or Telnet protocols.
After login, the user will switch user (SU) to the private
user for agent installation.
Installation Directory
Enter the directory path where you want the agent
installed. The default path is /opt/altiris/notification/
nsagent.
Use NS IP address
Select the check box to enter a static IP address.
IP address
If a UNIX or Linux computer does not have DNS
configured, you can enter the IP address of the
Notification Server. The target computer will look to this
IP address, in search for the appropriate agent.
Telnet Settings
Action
Login Timeout (secs)
Time duration that the install process will attempt to login
to a target UNIX computer. If the install script cannot
login to the remote host, an error message will indicate the
host is unreachable.
(Default 15)
UNIX Software Delivery Solution User Guide
24
Chapter 2: Setup and Installation
Step 5 - Install the NS Agent to Target UNIX Computers
Remote Installation Settings
Setting Option
Action
Command Timeout (secs)
(Default 120)
Time duration that each command of the script will
attempt to execute. If time expires and the command did
not execute, an error message will appear.
Agent Execution Timeout (secs)
This feature is not used in this release.
(Default 120)
Telnet user’s Prompt
(Default $)
Privileged user’s Prompt
(Default #)
5
Enter the prompt for unprivileged users. The installation
script uses the command line prompt to determine
successful state information. When it gets to a certain
point in the installation, it will check the prompt to
determine whether the current login for root or root
equivalent, or an unprivileged user has been successful.
Because many companies either customize their prompts,
or have no standards prompts in place, multiple prompts
can be listed by commas, for both types of users, in this
field.
Enter the prompt for root or root equivalent users. See note
above for Multiple Prompt usage.
Click apply at the bottom of the page to save the configuration settings you entered.
Agent “Push” Installation
You can install the NS Agent to a single target computer, or multiple target computers at once. The
Remote Installation Settings (page 24) let you configure the communication and authentication
settings, which can be saved and used to install multiple target computers at once. These settings
establish the communication protocol and the login authentication for the target computers.
The graphic below illustrates the process the NS Agent goes through, to push an installation from the
Notification Server to a target UNIX computer.
UNIX Software Delivery Solution User Guide
25
Chapter 2: Setup and Installation
Step 5 - Install the NS Agent to Target UNIX Computers
If you want to install the NS Agent to a single or limited number of target computers, follow the steps
below, and then go to “Option 1 - To get computer list from MS Excel file (Multiple target
computers)” on page 26.
The following procedure will install the NS Agent for UNIX from Notification Server’s Web
Administration Console to target computers.
To “Push” the NS Agent for UNIX
1
From the Web Administration Console, click the Configuration tab.
2
In the left pane, click UNIX Client Installation.
3
In the right pane, click Agent ‘Push’ Installation.
4
Click Load List of Computers and do one of the following options.
Option 1 - To get computer list from MS Excel file (Multiple target computers)
Import a list of computers into the table on the page, using the CSV file format. This option is
useful when you want to send the agent to multiple target computers.
The CSV file is a comma delimited text file that includes the computers names (DNS resolvable)
or IP address of the target computer where you want to push the agent. Each line in the CSV file
represents the data elements that will be imported into the install table for each computer; there
are 11 columns of data that can be filled in.
The following table shows the CSV file format with each column name and sample data that can
help you when creating your own CSV file. The last row in the table displays a single line item
of what the CSV file will look like.
CSV File Format
Column #
Item
Example
1
System Name or IP Address
172.19.5.34 or Solaris1.altiris.com
2
Root or Root Equivalent User
Root
3
Password for #2
A346d*
4
SU or use two-state login
0 means No, 1 means Yes
5
Unprivileged User Name
guest
6
Password for #5
guest
7
Installation Directory
/opt/altiris/notification/nsagent
8
Login Timeout
30
9
Command Timeout
60
10
Unprivileged User Prompt
$
11
Root or Root Equivalent Prompt
#
Example entry in a CSV file
172.19.5.24,root,A346d*,1,guest,guest,/opt/altiris/notification/nsagent,30,60,$,#
a
Click Load computer list from MS Excel CSV file.
b
Browse to the location of the CSV File, and then click Open.
c
Click the row from the list to select the target computers; use the Shift and Control keys to
select all rows or individual rows.
d
Click Install now to, a dialog box will show the progress.
e
When the “Push” is finished, click OK.
UNIX Software Delivery Solution User Guide
26
Chapter 2: Setup and Installation
f
Step 5 - Install the NS Agent to Target UNIX Computers
Review the Status values displayed in the table. See “Table Key” on page 28 for reference.
Option 2 - To manually edit the table list (Single or limited number of target computers)
You can edit the table on the page, entering the values below each column name. This option is
useful when you want to install the agent to a few select computers.
a
Click the field below the Computer Name column, and then enter the DNS computer name or
an IP address for the target computer. Use the Tab key to advance the cursor across the table,
entering all values.
b
When you reach the end of the first row, press Tab to advance down to the next row. If you
make a mistake, use the Arrow keys to move to the appropriate field and retype the value.
Press Delete to remove the row altogether.
c
Click the row from the list to select the target computers; use the Shift and Control keys to
select all rows or individual rows.
d
Click Install now to, a dialog box will show the progress.
e
When the “Push” is finished, click OK.
f
Review the Status values displayed in the table. See “Table Key” on page 28 for reference.
Option 3 - To get computer list from discovery table
This option is not available with this release
Option 4 - To load the computer list from Altiris Notification Collection
If you are currently using a previous version of the UNIX Software Delivery Solution, a
Collection of UNIX computers was created when you upgraded to version 5.6. This Collection
will identify those computers that can be upgraded with the new 5.6 NS Agent.
UNIX Software Delivery Solution User Guide
27
Chapter 2: Setup and Installation
Step 5 - Install the NS Agent to Target UNIX Computers
a
Click the drop-down arrow and select a Collection. The table list will populate with the
information from that Collection.
b
Click the row from the list to select the target computers; use the Shift and Control keys to
select all rows or individual rows.
c
Click Install now to, a dialog box will show the progress.
d
When the “Push” is finished, click OK.
e
Review the Status values displayed in the table. See “Table Key” on page 28 for reference.
Table Key
When the Agent “Push” Installation option is used, the progress of the install is displayed in the table
list of computers below the Status column. The table key is used to help you interpret the Status
results.
1
Click Table Key, the following is displayed.
•
Black - The computer does not have the agent installed, the agent is not being installed, or the
agent was installed by another method other than Push or Pull.
•
Yellow - The agent is being installed on these computers.
•
Green - The agent is successfully installed and functioning on the computer.
•
Red - The agent installation failed.
2
Click Refresh to see the latest status results.
Agent “Pull” Installation
UNIX Software Delivery Solution User Guide
28
Chapter 2: Setup and Installation
Step 5 - Install the NS Agent to Target UNIX Computers
You can install the NS Agent on a single computer by going to the physical location of the computer
and “pulling” the agent from Notification Server via HTTP or FTP. The NS Administrator can e-mail
the URL or FTP address, telling the UNIX Administrator where to get the agent.
It is assumed that Notification Server, UNIX Software Delivery Solution, and the NS Agent for UNIX
are installed and functioning.
To “Pull” the NS Agent for UNIX
1
From the Web Administration Console, click the Solutions tab.
2
In the left pane, click UNIX Agent Installation.
3
In the right pane, click Agent ‘Pull’ Installation.
From this page, the NS Administrator can cut and paste the URL for downloading the NS Agent
(based on the appropriate platform) in an e-mail or some other method, which provides
the information for pulling down and installing the agent. The person receiving this information
will access the URL and pull the NS Agent to the target UNIX computer.
for UNIX
4
Click the drop down arrow and select a platform.
5
If you want to view the process used by the UNIX Administrator, or provide more information
about the installation, the NS Administrator can click the Click Here to see this page link. A page
will display the instructions to manually download and install the NS Agent for UNIX.
The instruction page provides a link to download the bootstrap file, instructions for installing the
agent, and a link to pull down all of the agent files, if needed. It also provides the specific
command to execute the bootstrap file to initiate the agent installation so the UNIX
Administrator does not have to know the NS Server name. The UNIX Administrator can copy
and paste the command from the Bootstrap command and server name text box on this page.
When the aex-bootstrap command is run, the program will connect to the Notification Server and
download the full UNIX NS Agent Package, which will pass execution to the aex-setup script in
the Package.
The aex-setup script will then install, configure, and start the agent. In the event that the aexbootstrap program cannot contact the Notification Server, it will schedule itself to run again
using the at command.
The aex-bootstrap program will always try to contact the Notification Server using the HTTPS
protocol first. If the Notification Server is not configured to use HTTPS, it will try to the HTTP
protocol instead. You will see a warning message on the console if HTTP is used instead of
HTTPS; this is normal and ensures that the most secure communication protocol is always used.
To “Pull” and manually install the NS Agent for UNIX
1
Login to the target UNIX computer as root or a root equivalent user.
2
Open a browser and enter the URL that links to the bootstrap program for the appropriate
platform.
3
Right click and select Save as... from the browser’s menu, then choose a temporary directory to
save the bootstrap program; save it as aex-bootstrap.Z. Then follow the instructions below to
install the NS Agent.
UNIX Software Delivery Solution User Guide
29
Chapter 2: Setup and Installation
Step 5 - Install the NS Agent to Target UNIX Computers
a
Navigate to the directory where you saved the aex-bootstrap.Z file.Unpack the aexbootstrap.Z file with the command, uncompress aex-bootstrap.Z.
b
Use the command chmod u+x aex-bootstrap to ensure the aex-bootstrap can be
executed.
c
Run the command ./aex-bootstrap kathi-server2 (where kathi-server2, is the DNS
name or IP address of the Notification Server that you will connect to.
d
From the Manual Instruction page, click the link to take you to the directory where all the files
for the NSAgent (platform specific) are located. If you do not want to use the bootstrap
program, download the compressed agent and aex-setup files. Then, change the aex-setup
permissions to make it executable using the chmod command. Execute the file like you
would the bootstrap program, with the NS Server name or IP address as a command line
argument. Aex-setup will uncompress the agent Package and install and start the agent
process.
To use FTP to “Pull” and manually install the NS Agent for UNIX.
Another option for pulling the NS Agent for UNIX is via FTP. A UNIX Administrator may not have a
GUI and browser available on the UNIX system, so FTP access is another good option. Follow the
instructions below.
1
From the UNIX computer, FTP to the NS Server and login with an account that has access to the
server.
2
When the UNIX Solutions are installed, a mapped directory is created, but it cannot be seen in
the FTP root directory. If the user has the appropriate rights, you can access the NS Agent for UNIX
files by changing directories, use the command: ftp> cd aexns/nscap/bin/unixclient.
3
Navigate to the appropriate platform directory and, as stated previously, download either the
bootstrap file, or the compressed agent and the aex-setup files.
Important: Download the files in binary mode as the ASCII mode will corrupt the files.
4
Follow the instructions for manually installing the agent (see “To “Pull” and manually install the
NS Agent for UNIX” on page 29).
Using removable media to manually install the NS Agent for UNIX
You can redistribute the appropriate files by using removable media, such as, a floppy disk, CDROM, or any other media type that can be read and shared between the NS Server and the UNIX
Server.
1
From the NS Server, go to the nscap\bin\unixclient\<platform> directory.
2
Copy either the bootstrap file, or the compressed agent and aex-setup files on to any form of
removable media.
3
Go to the UNIX computer where you want to manually install the files, and then copy the files
into a directory or run them from the media.
4
Follow the instructions for manually installing the agent (see “To “Pull” and manually install the
NS Agent for UNIX” on page 29
UNIX Software Delivery Solution User Guide
30
Chapter 2: Setup and InstallationStep 6 - Enabling the Software Delivery Solution Component of the NS Agent for UNIX
UNIX Log
The UNIX log displays the session output of the target computer, and below the Apply and Cancel
buttons, messages are displayed to confirm the install process either failed or completed
successfully.
Step 6 - Enabling the Software Delivery Solution
Component of the NS Agent for UNIX
The UNIX Software Delivery Solution agent plugs into the NS Agent for UNIX architecture. By
default, after you install the solutions and ‘Push’ the NS Agent 5.6, the software delivery components
will follow. If you do not want the software delivery components to be installed immediately after
the NS Agent installation, or you do not want them Enabled, based on the default Collections for
systems based on their UNIX OS platform, then you will need to Disable the Policies prior to
installing the NS Agent onto target computers. This applies to the ‘Push’, “Pull’, or Manual Installation
methods.
Install Solution Licenses
Altiris solutions automatically install with a 7-day trial license. You must apply for a 30-day
evaluation license or purchased a full license from the Altiris web site to continue using this product.
To install a license
1
From the Notification Server computer, click Start > Programs > Altiris > Altiris eXpress >
Notification Server > Web Administration Console.
2
Click the Licensing tab. Altiris solutions that are installed to the Notification Server will display
information such as:
•
•
•
•
Product name
Number of licenses
The release and version number
The licensing expiration date
UNIX Software Delivery Solution User Guide
31
Chapter 2: Setup and Installation
Install Solution Licenses
The Notification Server will display a message when the solution license is expired.
3
In the left pane, click Install License.
By default, the Install from an email option is expanded. If the solution license (solution_name.txt)
file is stored in a different location other than e-mail, go to step 8 on page 32.
4
Copy and paste all lines of text from the e-mail license file (solution_name.txt) in the text box.
5
Click Install License.
6
The certificate will install and display a completed status, click OK.
7
Repeat steps 1- 6 to install additional solution licenses. If no other products need licensing, go to
step 9 on page 32.
8
If you did not use the Install from an email option to install a product license, select one of the
options below to complete the install process.
Option 1 - Install from a file
a
Click Browse for a license file.
b
Navigate to the location of the solution_name.txt file.
c
Select the license file, and then click Open.
d
Click Install License.
e
The certificate will install and display a completed status, click OK.
Option 2 - Install from a Folder
9
a
Click Browse for a license folder.
b
Navigate to the folder where the solution_name.txt file is located, and then click OK.
c
The certificate will install and display a completed status, click OK.
Confirm the license(s) installed successfully.
a
In the left pane, click License Status.
b
In the right pane, you will see the Solution Name, the Licenses in use, and the expiration date
for the type of license you installed, the Status should display OK.
For more information on product licenses and how to purchase other Altiris suites or solutions, see
the Altiris web site at http://www.altiris.com
UNIX Software Delivery Solution User Guide
32
Chapter 3:
Configuration
This section will help you understand how Notification Server and the UNIX Software Delivery
Solution work together to provide you the tools to deploy software files and packages. You will also
become familiar with the file structure and how to configure packages and policies.
Quick Links
UNIX Software Delivery
Description of the file structure for the UNIX
Solution and Notification Server Software Delivery Solution.
(page 34)
Collections (page 35)
Description of how to create Collections for
software package distribution.
Packages (page 36)
Description of how to create software Packages,
including the standard NS Agent packages.
Policies (page 38)
Description of how Policies impact software
delivery.
Reports (page 41)
Description of how to view Reports.
UNIX NS Agent Configuration
Solution (page 42)
Description of the file structure for the NS Agent
for UNIX.
Collections - NS Agent (page 43) Description of the NS Agent Collections
Packages - NS Agent (page 44)
Description of the NS Agent Packages
Policies - NS Agent (page 45)
Description of the NS Agent Policies
UNIX Software Delivery Solution User Guide
33
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
UNIX Software Delivery Solution and Notification Server
Notification Server uses Collections, Packages, Policies (also known as Advertisements), and Reports
to help you manage your infrastructure resources. The UNIX Software Delivery Solution is a plugin program to Notification Server and installs with the same folder structure as Notification Server.
The NS Agent for UNIX will install to the UNIX NS Agent Configuration Solution folder. There are no
reports associated with this solution, so a Reports folder will not install below the UNIX NS Agent
Configuration Solution folder. The contents of the Collections, Packages and Policies folders give you
the options to configure the agent that will be deployed to target computers. See “UNIX NS Agent
Configuration Solution” on page 42 for more details.
UNIX Software Delivery Solution User Guide
34
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
Collections
The results of data collected from UNIX and Linux computers are stored in the database and can be
viewed based on category groups called collections. The UNIX Software Delivery Solution does not
install with any default Collections. Data can be viewed in several default Collections that can be
found in the Altiris eXpress Configuration > Collections > Standard Collections folder. Two examples
would be the All UNIX Machines Collection, or the UNIX Solaris Machines Collection.
Collections can be one of two types, either dynamic or static. Collections that are dynamic, are based
on a SQL criteria, such as the predefined standard Collections in Notification Server. Static
collections are Collections obtained by manually selecting computers from the network, not from
data gathered in the Notification Server database.
You can create your own Collections to meet your specific needs, either under the Altiris eXpress
Configuration > UNIX Software Delivery Solution > Collections folder, or under the Altiris eXpress
Configuration > Collections folder. This can be helpful in managing network resources.
To view data collections
1
From the Web Administration Console, in the left pane, click Altiris eXpress Configuration >
Collections > Standard Collections.
2
Click on the collection you want to view. The results will appear in the right pane.
For more information about Collections and all other Notification Server functionality, see the Altiris
Notification Server User Guide located at http://www.altiris.com/support/documentation.
UNIX Software Delivery Solution User Guide
35
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
Packages
are a Collection of files or software programs grouped together, that will be deployed to
client computers where the NS Agent is installed. It is also possible to enable Package status events,
configure Package distribution methods, and specify software Packages to be replicated to Package
servers.
Packages
My UNIX Packages
The UNIX Software Delivery Solution lets you create your own packages consisting of individual
files, commands, and programs that can be deployed to target computers where the NS Agent is
installed. The My UNIX Packages folder is where you will store the Packages you create.
When the Packages are deployed, the software delivery agent files plug-in to the NS Agent already
installed.
NS Agent Architecture
The NS Agent for UNIX contains the following program objects, which manages the following
agent functionality:
•
•
•
•
•
•
Object Manager
Scheduler
Communication and Security
Policy Management
Event Queuing
Package Management
Each UNIX based solution will plug-in solution specific agents to the NS Agent, which provides the
functionality of the suite or solution you are using.
The agent files reside on client UNIX or Linux computers and run their assigned jobs when a
notification policy is sent to the client indicating that there is some function it must do.
UNIX Software Delivery Solution User Guide
36
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
Packages vs. Policies
The correlation between Packages and Policies is shown in the graphic below. The Packages are
deployable files to client computers, which run the executable files it receives, while Policies are the
notification to client computers of when to go retrieve the software delivery Packages from the
Notification Server.
To view the package programs
1
From the Web Administration Console, click the Solutions tab.
2
In the left pane, click UNIX SW Delivery Solution > Packages > My UNIX Packages.
3
Create a software package.
For more information about Packages and all other Notification Server functionality, see the Altiris
Notification Server User Guide located at http://www.altiris.com/support/documentation.
UNIX Software Delivery Solution User Guide
37
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
Packages - Execution Environment
The following steps describe how to set options for Packages, UNIX and Linux users must be aware
of the following exception.
1
From the Web Administration Console, in the left pane, click UNIX Inventory Solution > Packages
> UNIX Inventory Package.
2
Select a Package.
3
Click on Programs, in the upper right-hand corner of the page.
4
Click Execution Environment. You will see the following section appear
This section is not used by UNIX and the settings currently defined are ignored.
For more information about Packages and all other Notification Server functionality, see the Altiris
Notification Server User Guide located at http://www.altiris.com/support/documentation.
Policies
You can configure the standard Policies or create your own new Policies, so that when conditions
you define occur, the Notification Server will perform specific actions. You can also configure
Policies to use Event Handlers, which will perform actions when the Policy criteria is met.
You will notice in the Notification Server file structure, that each suite or solution will install with
its own Policies folder. The UNIX Software Delivery Solution installs with two policies folders, they
are; My UNIX Advertisements, see “My UNIX Advertisements” on page 39, and UNIX SWDelivery
Policy Group, see “UNIX SW Delivery Policy Group” on page 40.
UNIX Software Delivery Solution User Guide
38
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
My UNIX Advertisements
The My UNIX Advertisements folder is where you can create a New Notification Policy or a New UNIX
Advertisement, to run when and as often as you want.
To create a New Notification Policy or UNIX Advertisement
1
From the Web Administrator Console, click the Solutions tab.
2
Click UNIX SW Delivery Solution > Policies > My UNIX Advertisements.
3
Right-click on My UNIX Advertisements, then click New Notification Policy, or New UNIX
Advertisement.
For more information about Policies, Event Handlers and all other Notification Server functionality,
see the Altiris Notification Server User Guide located at http://www.altiris.com/support/
documentation.
UNIX Software Delivery Solution User Guide
39
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
UNIX SW Delivery Policy Group
The UNIX SW Delivery Policy Group folder contains Policies (also known as Advertisements) that will
notify UNIX or Linux client computers to send back software delivery information after packages
have been distributed. The table below describes the standard software delivery policies that install
with this solution.
SW Delivery Policies
Policy
Description
Advertisement completed
The policy will send e-mail notification when
a policy has run successfully, at least once, on
all targeted computers.
Advertisement expires in less than 7 days
The policy will send e-mail notification when
a policy is about to expire and not all of the
targeted computers have successfully run the
program.
Program execution failed
The policy will e-mail a web report summary
of failed program execution.
The SW Delivery Policy Group page from the Web Administration Console.
To view the UNIX Inventory Agent Policies List
1
From the Web Administrator Console, click the Solutions tab.
2
Click UNIX SW Delivery Solution > Policies > UNIX SW Delivery Policy Group.
3
Click one of the policies from the list.
For more information about Policies, configuring the settings, and all other Notification Server
functionality, see the Altiris Notification Server User Guide located at http://www.altiris.com/
support/documentation.
UNIX Software Delivery Solution User Guide
40
Chapter 3: Configuration
UNIX Software Delivery Solution and Notification Server
Reports
The UNIX Software Delivery Solution comes with many standard reports, designed to help you
analyze the data from UNIX and Linux client computers.
In the graphic below, you can see the Reports folder in the left pane with the category group folders
expanded. All the standard reports that install with this solution, will be categorized into these
folders. When you select a report group folder, it will expand and list the reports available for that
group. You can add your own report group folders and create your own custom reports by modifying
or adding the SQL Filters.
To view or run reports
1
From the Web Administrator Console, click the Solutions tab.
2
In the left pane, click UNIX SW Delivery Solution > Reports. The folder will expand showing the
folders for different report categories.
3
Click on a category folder. The folder will expand, showing you the standard reports available
for that category.
4
Click on the report you want. In the right pane, the Report Properties page will display the Name
and Description of the report you selected.
For more information about Reports and all other Notification Server functionality, see the Altiris
Notification Server User Guide located at http://www.altiris.com/support/documentation.
UNIX Software Delivery Solution User Guide
41
Chapter 3: Configuration
UNIX NS Agent Configuration Solution
UNIX NS Agent Configuration Solution
When the NS Agent for UNIX installs to the Notification Server file structure, a folder named UNIX NS
Agent Configuration Solution will appear in the right pane of the Web Administration Console.
The graphic below shows the file structure with the Collections, Packages, and Policies folders
expanded to show the contents of each folder. The remainder of this section will detail the
Collections, Packages, and Policies that are unique to the NS Agent for UNIX.
To view the UNIX NS Agent configuration solution folders
1
From the Web Administrator Console, click the Solutions tab.
2
In the left pane, click UNIX NS Agent Configuration Solution, the folder will expand showing the
sub-folders.
3
Click on the Collections, Packages or Policies folder. The folder will expand, showing you its
contents.
UNIX Software Delivery Solution User Guide
42
Chapter 3: Configuration
UNIX NS Agent Configuration Solution
Collections - NS Agent
When the NS Agent for UNIX is installed to the Notification Server, the install process will
automatically determine if there are pervious versions of the agent installed to client computers. The
computer names and location are compiled in a Collection, so you can view the computers requiring
an agent upgrade.
The UNIX NS Agent Rollout Jobs folder contains four standard Collection groups, they are as follows:
• AIX computers requiring UNIX NS Agent upgrade
• HP-UX computers requiring UNIX NS Agent upgrade
• Linux computers requiring UNIX NS Agent upgrade
• Solaris computers requiring UNIX NS Agent upgrade
If you select the Agent ‘Push’ Installation method to deploy the NS Agent to UNIX and Linux
computers, there is an option to Select a Collection, which will deploy the agent to computers listed
within a defined Collection. See “Step 5 - Install the NS Agent to Target UNIX Computers” on
page 23 for more details. These Collections can also be used with the Rollout Policies for computers
who have both UNIX Inventory and UNIX Software Delivery Solutions
installed
To view data Collections
1
From the Web Administration Console, in the left pane, click UNIX NS Agent Configuration
Solution > Collections > UNIX NS Agent Rollout Jobs.
2
Click on the collection you want to view. The results will appear in the right pane.
UNIX Software Delivery Solution User Guide
43
Chapter 3: Configuration
UNIX NS Agent Configuration Solution
Packages - NS Agent
The NS Agent for UNIX installs with five standard Packages to the Notification Server file structure.
See “UNIX NS Agent Configuration Solution” on page 42 for details on the file structure. Each
standard Package contains the base NS Agent files for the supported UNIX platforms.
The standard packages that install with the NS Agent are as follows:
• AIX NS Agent Package
• HP-UX NS Agent Package
• Linux X86 NS Agent Package
• NS Agent Uninstall Package
• Solaris Sparc NS Agent Package
These Packages are associated with the Polices for upgrading the NS Agent on existing UNIX
computers. If you use the ‘Push’ installation method, the bootstrap file will take care of the
installation. If you use the ‘Pull’ installation method, you will be required to pull the appropriate files
for installation, or just the bootstrap. See “Step 5 - Install the NS Agent to Target UNIX Computers”
on page 23 for more details.
To view the base NS Agent packages
1
From the Web Administration Console, click the Solutions tab.
2
In the left pane, click UNIX NS Agent Configuration Solution > Packages > UNIX NS Agent Rollout
Jobs.
3
In the left pane, click one of the NS Agent Packages.
It is possible to enable Package status events, configure Package distribution methods, and specify
software Packages to be replicate to Package Servers.
For more information about Packages and all other Notification Server functionality, see the Altiris
Notification Server User Guide located at http://www.altiris.com/support/documentation.
UNIX Software Delivery Solution User Guide
44
Chapter 3: Configuration
UNIX NS Agent Configuration Solution
Policies - NS Agent
The Policies folder for the NS Agent contains two sub-folders, their description and functions are
outlined below.
•
The UNIX NS Agent Configuration folder contains the NS Agent Settings policy, used to set general
configuration parameters for the NS Agent. See “UNIX NS Agent Configuration” on page 45 for
more details.
•
The UNIX NS Agent Rollout Jobs folder contains four standard Policies that are notifications to
client computers that the NS Agent needs upgrading. See “UNIX NS Agent Rollout Jobs” on
page 47 for more details.
UNIX NS Agent Configuration
NS Agent Settings Policy
The NS Agent Settings policy will effect the UNIX computers that already have the agent installed.
You can configure some general parameters that control the behavior of the agent, including how
the agent communicates with the Notification Server.
To configure the NS Agent
1
From the Web Administrator Console, click the Solutions tab.
2
Click UNIX NS Agent Configuration Solution > Policies > UNIX NS Agent Configuration > NS Agent
Settings.
Note By default, the Enabled check box is selected. This option means that after you save the
policy changes, they will go into effect on the Notification Server immediately.
3
Click Configure the UNIX Client in the upper right-hand corner of the page.
UNIX Software Delivery Solution User Guide
45
Chapter 3: Configuration
4
5
UNIX NS Agent Configuration Solution
Click NS Agent Communication, the following screen appears.
a
Click the drop-down arrow and select a slow connection threshold. The default is 50 kByte/
sec (recommended).
b
If a slow connection is detected, the agent will switch to this bandwidth utilization. Click the
drop-down arrow and select an alternate connection speed.
c
Click the drop-down arrow and select how often the agent should request new configuration
information.
d
Click the drop-down arrow and select how often the NS agent should send basic inventory
information to the Notification Server database.
Click Blockout and Disabled Periods, the following screen appears.
a
Select the check box to Disable the UNIX NS Agent software.
b
Click the drop-down arrow for each box and select the blockout hours when the agent will be
disabled. The time selection is in military hours.
c
Click the Blockout type:
Standard:
The NS Agent sends events and receives configuration information from the
Notification Server, but the agent will not download any software delivery packages during
this time. Events and configuration are typically small amounts of information and have
minimal impact on network traffic; however, packages can be large and could effect the
network load. This setting helps to minimize the agent’s impact on the network during highpeak business hours.
Total: There is no communication between the NS Agent and Notification Server during the
blocked out time period. All events from the agent are queued (on the agent) and will be sent
after the blockout. Software delivery packages will resume downloading after the blackout
period.
d
6
Click the drop-down arrow and select how long to disable configuration requests and sending
basic inventory at startup and after blockouts.
When the NS Agent Communication and Blockout and Disabled Periods selections have been made,
click Apply.
UNIX Software Delivery Solution User Guide
46
Chapter 3: Configuration
UNIX NS Agent Configuration Solution
UNIX NS Agent Rollout Jobs
his folder contains Policies used to upgrade UNIX Computers currently running the 5.5 agent. The
four standard Policies are as follows:
•
•
•
•
AIX computers requiring UNIX NS Agent upgrade
HP-UX computers requiring UNIX NS Agent upgrade
Linux computers requiring UNIX NS Agent upgrade
Solaris computers requiring UNIX NS Agent upgrade
You will notice that the Policy names are similar to the Collections and Packages folder contents. The
Collections folder tells you what computers need the NS Agent upgrade, and the Packages folder
contains the NS Agent Packages to be installed. By default, these Policies are not Enabled.
To configure the UNIX NS Agent rollout policies
1
From the Web Administrator Console, click the Solutions tab.
2
Click UNIX NS Agent Configuration Solution > Policies > UNIX NS Agent RolloutJobs.
3
Click on one of the standard agent upgrade policies.
4
Click the Enabled check box is on the page. This option means that after you save the Policy
changes, they will go into effect on the Notification Server immediately.
For more information about Policies and all other Notification Server functionality, see the Altiris
Notification Server User Guide located at http://www.altiris.com/support/documentation.
UNIX Software Delivery Solution User Guide
47
Chapter 3: Configuration
UNIX NS Agent Configuration Solution
Customize the UNIX NS Agent Configuration Policy
You can create your own UNIX NS Agent Configuration Policies, which provides you the flexibility to
ensure that each client computer receives the configuration you want it to have.
The graphic below shows that the NS Agent Settings Policy is currently configured to effect All UNIX
Machines; however, you can select a different Collection group by clicking the drop-down arrow and
selecting from the list. The Collection list that is displayed in the drop-down selection, is populated
from both the Notification Server and the UNIX Software Delivery Solution Collections folders.You
can also Clone the Policy as many times as you want to ensure that each UNIX computer gets the
blockout, update and bandwidth settings. You can create your own Collection groups for the UNIX
Software Delivery Solution. Go to “Collections” on page 35.
To customize the NS Agent policies
1
From the Web Administrator Console, click the Solutions tab.
2
Click UNIX NS Agent Configuration Solution > Policies > UNIX NS Agent Configuration.
3
Right-click on UNIX NS Agent Configuration, and then select New > UNIX Client Settings Policy.
For more information about Creating Policies and all other Notification Server functionality, see the
Altiris Notification Server User Guide located at http://www.altiris.com/support/documentation.
UNIX Software Delivery Solution User Guide
48
Chapter 4:
UNIX Agent Files, Settings, and Processes
This section will help you understand file structure, the settings, and processes for the NS Agent for
UNIX, and the UNIX Software Delivery Solution.
Quick Links
Agent Files (page 49)
NS Agent Configuration File
(page 51)
Manual Process (page 55)
Description of the NS Agent files their installation
directory, links, and files and processes.
Description of the configuration file for the NS
and the UNIX Software Delivery Solution.
Agent
Description of the files used to manually install the
NS Agent for UNIX.
Agent Files
There are several files that will be installed onto your UNIX system for use by the NS Agent and for
the UNIX Software Delivery Solution components
Installation Directory
The NS Agent can be installed to any directory on the UNIX computer; however, Altiris recommends
installing to the default directory location of /opt/altiris/notification/nsagent. This install location is
the base directory where all binaries, libraries, configuration files, and log files are stored.
The base install directory, which we will refer to as the agent’s directory or base directory, can also
be used to determine the location for other agents when their files need installing. For example, if
the NS Agent is already installed, then the Software Delivery Agent will install to the default base
directory of
/opt/altiris/notification/inventory, which is the same level as the NS Agent.
Through out this document, any time the reference The Agent’s bin Directory is made, it refers to
the subdirectory of the agent’s base directory, located at /opt/altiris/notification/nsagen/bin.
Additionally, a number of symbolic links are created in /usr/bin. All these links start with the
characters “aex-” and include key executables that may need to be accessed from the command line.
The only other files installed or modified outside the agent’s base directory, are the files required to
configure the aex-messagelistener. These executable files are launched by (x)inetd to enable instant
delivery of software delivery jobs. Be aware that the (x)inetd configuration file and the (x)inetd
directory may be changed by the agent installer
The following table is a summary of the directories that get created and the function they serve.l
File locations
The Directory
File Description
/opt/altiris/notification/nsagent
Default base directory for the NS Agent for UNIX.
/opt/altiris/notification/nsagent/bin/
UNIX NS Agent binaries and scripts.
UNIX Software Delivery Solution User Guide
49
Chapter 4: UNIX Agent Files, Settings, and Processes
Agent Files
File locations
The Directory
File Description
/opt/altiris/notification/nsagent/var
Directory where log files and downloaded
and jobs are stored, as well as
collected inventory data
Packages
/opt/altiris/notification/nsagent/var/Pkg_** Directory specific to a particular downloaded
Package.
/opt/altiris/notification/nsagent/var/queue
Directory where jobs are stored to be processed.
/opt/altiris/notification/nsagent/etc
Directory where configuration files are kept.
Files, Links and Processes
The following section discusses the use of symbolic links in conjunction with the NS Agent and
inventory binaries, and a description of the more important files that get installed.
Links
Links to agent executables are created in /usr/bin and point to files in the agent’s “bin” directory.
Other agents installed, like the Inventory Agent, may also create links.
Links will always be in the format “/usr/bin/aex-*”. In most cases these links will refer to the
runit.sh script and not to the matching binary in the agent’s bin directory. The are two reasons for
the aex-* links, they are as follows.
1
It allows executables that may be run at the shell level by a user, administrator, or the operating
system to be found using a normal PATH setting.
2
By linking to the runit.sh script, it allows the run environment for the agent’s executables to be
setup and specified. This is required so that the agent, or applications that use the agent, have the
required library paths set so the agent’s shared libraries can be found. It also sets an environment
variable called AEXCLIENT_CONFIG_FILE, that allows all agent’s executables and find the
client.conf file.
Files and Processes
The following is a list of files and their function or significance.
Files Description
Filename
Directory
Type of
File
Function
Aex-clientconfigupdate NS Agent Basedir/bin Process
The objects in this process, translate
configuration XML items into
settings in the client.conf file.
Aex-clientevent
NS Agent Basedir/bin Process
The objects in this process creates
and sends events to the Notification
Server. They will wrap the objects
in XML to identify where the
events came from, and queue events
in the case where the Notification
Server is not available.
Aex-clienttransport
NS Agent Basedir/bin Process
The objects in this process provide
low level communication services.
HTTPS, FTP, and Package
retrieval.
Aex-configure
NS Agent Basedir/bin Script
Aex-diagnostics
NS Agent Basedir/bin Executable
Aex-env
NS Agent Basedir/bin Script
UNIX Software Delivery Solution User Guide
50
Chapter 4: UNIX Agent Files, Settings, and Processes
NS Agent Configuration File
Files Description
Filename
Directory
Type of
File
Function
Aex-messagelistener
NS Agent Basedir/bin Process
Aex-monitor
NS Agent Basedir/bin Process
Aex-objectmanager
NS Agent Basedir/bin Process
The aex-objectmanager is the key
operating process for the NS Agent
and without it, nothing works. It
interacts with the object factories in
each of the other processes and
creates and deletes objects as
requested by other agent processes
(e.g. when a process requires a
ClientTransport object to make a
http connection, it asks the
objectmanager which will, if
required, start the aexclienttransport process.
Aex-policymanager
NS Agent Basedir/bin Process
The objects in this process manages
policy XML, refreshing it from the
Notification Server as required, and
notifying/creating agents as
required.
Aex-refreshpolicies
NS Agent Basedir/bin Executable
Aexsendbasicinventory
NS Agent Basedir/bin Executable
Aex-swdapm
NS Agent Basedir/bin Executable Script that queries NS for current
advertisements, and displays a pick
list of options that can be run
manually
Aex-swdclientagent
NS Agent Basedir/bin Process
The objects in this process
implement any SWD policies and
keep track of those that have run,
and require schedules etc.
Aex-taskscheduler
NS Agent Basedir/bin Process
The objects in this process manages
all scheduled tasks. This includes
periodic refreshing of policies, and
the schedules of active SWD jobs/
Agents.
Aex-uninstall
NS Agent Basedir/bin Script
Uninstall script for the NS Agent.
This script will also uninstall the
Inventory components as well,
assuming that without the NS Agent,
Inventory will not function.
Runit.sh
NS Agent Basedir/bin Script
See discussion regarding Links
NS Agent Configuration File
There are several configuration files that are used in conjunction with the NS Agent and UNIX
Software Delivery Solution. Client.conf will be discussed here, while filescan.rule and filescan.cfg
will be discussed in the next chapter.
The client.conf file contains the configuration settings for both, the NS Agent and the UNIX Software
Delivery Solution. The client.conf file is installed to a subdirectory of the default location for the NS
Agent install. The directory /opt/altiris/notification/nsagent/etc, is the central repository of all
configuration settings for the NS Agent and for any subagents, such as the Inventory Agent.
UNIX Software Delivery Solution User Guide
51
Chapter 4: UNIX Agent Files, Settings, and Processes
NS Agent Configuration File
At installation time, the agent installer will modify settings in the client.conf file specific to your
installation. For example, the installer will set the “installdir” value in the “[Notification
Servers]” section.
Below is a sample client.conf file. Each section and option has comments to help you understand
what the options mean. Under most circumstances, you would not have to edit this file directly.
Sample client.conf file
The sample file below is the same as the client.conf file installed to your UNIX computer; however,
it has been highlighted so you can easily find the descriptions for each section. The blue text denotes
description, while the black bold denotes the beginning of each section.
Important: Some descriptions tell you that certain sections cannot be edited as it will interfere with
internal program function.
client.conf
#
# This is the NS Agent primary configuration file.
#
# This file is broken into sections, delimited by the section headings
# enclosed
# in square brackets. Comment lines begin with a '#'.
#
# Some values below are commented out. This is to show the default setting
# for these optional values.
#
# Values with (read-only) in the description, are written to by the Agent
and # should not be edited.
# Values with (NS-Specified) in the description are replaced with values
# from policies, and
# can be changed for all UNIX Computers using the NS console GUI.
# Values used internally are marked “DO NOT EDIT”.
#
# Values which contain the string “%installdir%” in the right hand side,
# will have the “%installdir%” string replaced with the actual value of the
# installdir value. “installdir”
# is the only value that operates thus.
#
# This file contains the configuration setting for both the Agent and SWD
# and Inventory Solutions.
#
# The Configuration section contains the main settings used by the Agent
# and solutions.
#
[Configuration]
# The directory the Agent is installed to.
installdir=/opt/altiris notification/nsagent
# A location to be used for temp files.
tmpdir=/tmp
# The location where links to agent executables are created, should be in
the PATH of users.
binder = /usr/bin
# The Scenario GUID used for sending basic inventory, do not change.
scenario_guid_basicinv = BasicInventory
# The location where the UNIX Computer’s GUID (assigned by the NS) is
stored.
guid_guid_file = /opt/altiris/notification/nsagent/etc/host.GUID
# event_queue_dir is where the Inventory Solution's collector finds the
output of the
# inventory agents and regular events are queued
event_queue_dir = /opt/altiris/notification/nsagent/var/queue
# httppost_directory is where the Inventory Solutions's collector places
the results of the
# combined inventory agents
httppost_directory = /opt/altiris/notification/nsagent/var/queue
# This is the file extension used for NS events in the queue directory.
event_file_extension = .nse
# Task Scheduler storage path
task_storage_path = /opt/altiris/notification/nsagent/var/tasks
# Task Scheduler file extension
task_file_extension = .nst
# var directory used for log storage etc
var = /opt/altiris/notification/nsagent/var
# Location of the Agent's log file
debug_output=/export/home/altiris/notification/nsagent/var/aex-client.log
# Maximum size of the Agent's log file in Kilobytes
UNIX Software Delivery Solution User Guide
52
Chapter 4: UNIX Agent Files, Settings, and Processes
NS Agent Configuration File
debug_file_size=256
# Logging level for the agent. Possible values, from least to most logging,
are ERROR, WARNING, INFO.
debug_level=ERROR
# (NS-Specified) Download speed limit values. These values will be
overwritten by values specified
# in the Agent configuration page, communication section. When/if the
connection between the NS
# and the agent is detected to be below the lowwatermark value, the
speedlimit is applied.
speedlimit = 1K
lowwatermark=200k
# (NS-Specified) Value set to specify Package server network preferences.
pkgsvr_prefs =
# (readonly) Value set (on startup) to the detected OS Locale
os_locale =C
#
# Optional Configuration values, uncomment to change.
# This setting specifies the base URL used to communicate with an NS. The
value "%server%
# in the URL should be left as is because it is substituted by the Agent
internally.
#ns_url_format = http://%server%/AeXNS/
# Relative location of the NS page used to process events on an NS.
#ns_postevent_page = PostEvent.asp
# Relative location of the NS page used by the Agent to get a GUID for the
UNIX Computer.
#ns_createresource_page = CreateResource.asp
# Relative location of the NS page used by the Agent to get policies.
#ns_clientpolicies_page = GetClientPolicies.asp
# Directory in which the policy XML files are cached.
#policies_cache_dir = %installdir%/var/
# Location of the file uses to store the UNIX computer's GUID assigned by
the NS.
#guid_guid_file = %installdir%/etc/host.GUID
# If set to 1, the Agent will use domain values in /etc/resolv.conf as the
Unix computer's domain.
#basicinv_use_resolv_conf = 0
# Value set in DNS Server 3 if a DNS error is detected (i.e. if no NIC has
the
# IP returned by resolving the hostname of the Unix computer)
#basicinv_ip_error_return_value = NameServ Error
# DO NOT EDIT. GUID for basic Inventory
#basicinv_policy_guid = BasicInventory
# DO NOT EDIT. Post variable used in Event posting.
#httppost_var_name = XML
# Location where SWD Packages are downloaded to. A directory will be created
for
# Each package. Directories are named using the Package GUID.
#swd_temporary_dir = %installdir%/var/
#
# this parameter is for AIX systems. If the user wants to gather the patch
# information for the software inventory this variable can be set to several
# values. on non AIX systems this parameter does nothing.
# yes | full | all = do a full patch listing
# down = list all patches that are down level
# correct = list all patches that are at the correct level
# superseded = list superseded patches
# notinstalled = can you figure this one out?????
AIXPatchListing=yes
#
# This section contains specific setting for the Event Queue of the Agent.
#
[Event Queue]
# Queue backoff is used whenever events cannot be sent to the NS.
# Backoff uses the "levelX-delay" and "levelX-retries" settings (where X is
# the numbers 1,2,3,4 etc being the level of backoff) All levels between 1
and X
# must be present for X to be used). All values are in seconds. Default is
every
# 60 seconds for forever (not advisable) one the last level is reached it is
# used thereafter regardless of its retry setting.
#once per minute for 15 minutes
level1-delay = 60
level1-retrys = 15
#once every five minutes for an hour
level2-delay = 350
level2-retrys = 12
#once every 30 minutes for 4 hours
level2-delay = 1800
level2-retrys = 8
#once every 2 hours for 24 hours
level2-delay = 7200
level2-retrys = 12
UNIX Software Delivery Solution User Guide
53
Chapter 4: UNIX Agent Files, Settings, and Processes
NS Agent Configuration File
#once every 10 hours for ever
level2-delay = 36000
level2-retrys = 1
# (readonly) This value is the current backoff level.
backoff_level=1
# (readonly) This indicated the number of failed attempts to communicate
with the NS.
retry_count=0
# Set hold_queue to 1 to stop sending events.
#hold_queue = 0
#
# This section lists the name/IP of the notification server where the agent
gets its policy XML from
#
[Notification Servers]
# This is used by the policy manager, currently only the first server is
used
# (in the future that will be the default server)
Server-1=172.16.8.246
#
# This section contains the Agent Object Manager specific settings.
#
[Object Manager]
# Location of the IOR file (used by subagent and programs using the Agent
to find the Object Manager)
IORFilePath=/export/home/altiris/notification/nsagent/etc/om-ior
# This value, in minutes, specified how often the Object manager checks to
see which
# subagents have not been used and can unload.
checkperiod=1
#
# This contains Policy Manager sub agent settings.
#
[Policy Manager]
# (readonly) This contains the current Policy XML hash. Used to minimize
Agent->NS comms.
172.16.8.246_hash=28ToDJEvZ3aWzPfoJc6hkw==
# (NS-Specified) This is the frequency, in seconds, at which the Agent
checks for new/changed policies.
policies_request_interval=300
# (NS-Specified) This is the interval, in seconds, at which basic inventory
is sent to the NS
basicinv_send_interval = 86400
# (NS-Specified) This is the last time, seconds since the epoch, basic
inventory was sent
basicinv_last_sent =1057696358
# (readonly) True if a blockout is enabled.
blockout_enabled = false
# (NS-Specified) Max time after a blockout or start to wait before
commencing comms.
post_blockout_random_wait = 0
# (NS-Specified) Blockout values read by Agent subagent.
blockout_from =
blockout_until =
# (NS-Specified) Level of blockout (normal, total).
blockout_level = total
# (readonly) Current blockout wait value
#
# Values specific to the Software Delivery subagent.
#curr_post_blockout_wait=
last_reschedule_int=60
#
[SWD]
# 'nice' value for the low priority setting of the SWD Ad page of the NS
swd_lowpriority=10
# 'nice' value for the normal priority setting of the SWD Ad page of the NS
swd_normalpriority=
# 'nice' value for the high priority setting of the SWD Ad page of the NS
swd_highpriority=-10
# 'nice' value for the very high priority setting of the SWD Ad page of the
NS
swd_veryhighpriority=-20
#
# This section, along with the section names in the RHS of this section
(below)
# are used Internally by the Object Manager to map requests for a particular
# sub agent to the server that implements it.
# DO NOT EDIT
#
[Class Servers]
Altiris.AeXClientTransport=AeXClientTransport
Altiris.AeXNfySvrClientEvent=AeXNfySvrClientEvent
UNIX Software Delivery Solution User Guide
54
Chapter 4: UNIX Agent Files, Settings, and Processes
Manual Process
Altiris.AeXMachineID=AeXNfySvrClientEvent
Altiris.AeXPolicyManager=AeXPolicyManager
Altiris.AeXNSClientConfigUpdate=AeXNSClientConfigUpdate
Altiris.AeXTaskScheduler=AeXTaskScheduler
Altiris.SWD=AeXSWDClientAgent
Altiris.SWDAgent=AeXSWDClientAgent
Altiris.SWDTaskProcessor=AeXSWDClientAgent
[AeXClientTransport]
exe=/export/home/altiris/notification/nsagent/bin/aex-clienttransport
[AeXNfySvrClientEvent]
exe=/export/home/altiris/notification/nsagent/bin/aex-clientevent
[AeXPolicyManager]
exe=/export/home/altiris/notification/nsagent/bin/aex-policymanager
[AeXTaskScheduler]
exe=/export/home/altiris/notification/nsagent/bin/aex-taskscheduler
[AeXSWDClientAgent]
exe=/export/home/altiris/notification/nsagent/bin/aex-swdclientagent
[AeXNSClientConfigUpdate]
exe=/export/home/altiris/notification/nsagent/bin/aex-clientconfigupdate
# This section specified the Initial subagent startup order. DO NOT EDIT.
#
[Static Agents]
Altiris.AeXNfySvrClientEvent=AeXNfySvrClientEvent
Altiris.AeXPolicyManager=AeXPolicyManager
#
# Here can be Client Details section
#
# This section may contain:
#
# - Return Inventory status timestamp in GMT/UTC
#Default = 0
#status_time_as_gmt = 1
#
# - Filesystem types to filter out for DiskAgent. Can be a comma or space
separated.
#Default = ""
#fstype_ex_list =
#
# - Value to return if the hostname cannot resolve to an IP for an interface
on this box.
#Default = "NamServ Error"
#basicinv_ip_error_return_value = NamServ Error
#
# - Setting the following to 1 will cause the domain name reported to the
NS to be read
#from the /etc/resolv.conf file, overriding any value from the name
service.
#Default = 0
#basicinv_use_resolv_conf = 1
#
Manual Process
Manual Installation
A manual installation of the UNIX agent can be done one of two ways; either with the aex-bootstrap
files which will pull the rest of the files it needs down to the UNIX computer and work through the
installation, or by manually getting the compressed agent Package and the aex-setup file. See “Agent
“Pull” Installation” on page 29 for more information. The following information provides details for
the aex-bootstrap file, the aex-setup script, and how they work to install the agent and set up the
environment
The aex-bootstrap File
The aex-bootstrap file is used to manually install and configure the NS Agent for UNIX from a remote
client computer. When this file is run from the command line, using the name of the Notification
Server as its only argument, the client computer will connect to the Notification Server and
UNIX Software Delivery Solution User Guide
55
Chapter 4: UNIX Agent Files, Settings, and Processes
Manual Process
download the NS Agent Package and the aex-setup script. The aex-bootstrap script automatically runs
the aex-setup (see “The aex-setup File” on page 56) on the downloaded Package, passing in required
arguments such as, the Notification Server name and address.
There are two bootstrap file types but they are the same aex-bootstrap executable.
•
uu is an uuencoded version used for streaming out; it is also used during the Agent ‘Push’
process.
Installation
•
gzipped version is used when downloading. For example, using the wget utility.
The aex-setup File
After the aex-bootstrap (see “The aex-bootstrap File” on page 55) file has requested the NS Agent
the Notification Server to a client computer, the aex-setup script is
launch to complete the installation.
Package to be downloaded from
The aex-setup script is an installer script that performs the following tasks.
•
Unpack the binaries and library files, and sets up the appropriate links in "/usr/bin.
•
Creates some environmental setup files and configures client.conf for the specific installation,
such as the location, name of the NS, and more.
•
Configures the system so that when a system starts up, the appropriate rc. scripts are launched to
start the aex-objectmanager. It also modifies the (x)ined.conf file with information regarding the
aex-messagelistener. This is used when immediate software delivery is required, and the user
cannot wait until the next polling interval for the agent to run the software delivery job.
•
Uninstalls any old agents, migrating some settings into the new configuration files.
If you want to do a manual install, do the following:
1
Download the appropriate UNIX Package into a temporary directory, chmod the aex-setup file
to make it an executable.
2
Run the aex-setup file giving it the name of the NS as its only argument. This will unpack the
Package, configure, and start the agent correctly.
UNIX Software Delivery Solution User Guide
56
Chapter 5:
Troubleshooting
This section will help you resolve issues you may encounter when installing or using the UNIX
Software Delivery Solution. After the UNIX Software Delivery Solution gets installed and the NS
Agent is deployed, the system is very reliable. Most troubleshooting issues that could occur, usually
deal with the installation of the agents (Push from the Web Administration Console) and networking
problems.
Quick Links
Agent Installation (page 58)
Common errors when remotely Pushing the NS
Agent.
NS Agent Installation Errors
(page 58)
List of possible errors when installing the NS
Agent.
Additional Troubleshooting Tips List of network and network protocol errors.
(page 63)
Additional Troubleshooting Tips How to isolate subagents, and using the log file.
(page 63)
UNIX Software Delivery Solution User Guide
57
Chapter 5: Troubleshooting
Agent Installation
Agent Installation
When using the Push method to remotely install the NS Agent onto a UNIX or Linux computer, there
is potential for errors to occur. Common errors include: typing an incorrect user name or password,
and not understanding the system prompts on target computers. To minimize issues before installing
the NS Agent, review the following information:
•
System name or IP Address
•
Root or root equivalent user name and password
•
If pushing the NS Agent from the Web Administration Console, the system prompt for root or
root equivalent must already be known. If you are pushing to multiple computers, you may want
to use the multiple password and multiple prompt options in case the user accounts and
configurations are not consistent across UNIX computers.
•
If you are trying to connect to UNIX computers that do not allow root level access through SSH
or Telnet, you must be able to enter a user name and password as a second account, which allows
access to the computer. After accessing the UNIX computer, the installation process will switch
contexts to the root or root equivalent account.
NS Agent Installation Errors
NS Agent on WinNT Server Error
If you are running Windows NT Notification Server, it is possible to receive the following error at
first startup.
1
From the Web Administration Console, click the Configuration tab.
2
In the left pane, click UNIX Agent Installation. The following error message appears.
Note: This problem does not occur when running Windows 2000 Server and Windows 2003
Server.
3
If you are using Internet Explore 5.0, upgrade to 5.5 or the latest release available.
UNIX Software Delivery Solution User Guide
58
Chapter 5: Troubleshooting
NS Agent Installation Errors
NS Agent Errors
The following is a table list of possible errors that may occur during the NS Agent installation
process.
To view NS Agent installation errors
1
From the Web Administration Console, click the Configuration tab.
2
In the left pane, click UNIX Agent Installation.
3
After selecting a method for deploying the NS Agent and you have clicked the Install now to link,
if you received errors during the install, they will be listed at the bottom of the page.
NS Agent Install Errors
Issue
Wrong computer name or IP address
Installation Log
Connect via SSH.
Cannot connect via SSH.
Failed to connect using SSH protocol; trying Telnet.
Connect via Telnet.
Cannot connect via Telnet.
Failed to connect: Either the computer does not exist or the account is invalid.
Agent installation failed. Cannot connect to the UNIX computer.
Agent installed on 0 computer(s). Check list for errors.
Issue
No SSH, Telnet with wrong user password
Installation Log
Connect via SSH.
Cannot connect via SSH.
Failed to connect using SSH protocol; trying Telnet.
Connect via Telnet.
Cannot connect via Telnet.
Failed to connect: Either the computer does not exist or the account is invalid.
Agent installation failed. Cannot connect to the UNIX computer.
Agent installed on 0 computer(s). Check list for errors.
Issue
No Telnet, SSH with wrong user password
Installation Log
Connect via SSH.
Cannot connect via SSH. Disconnected from server, invalid user name or
password reported by server, or bad public key.
Failed to connect using SSH protocol; trying Telnet.
Connect via Telnet.
Cannot connect via Telnet.
Failed to connect. Either the computer does not exist or the account is invalid.
Agent installation failed. Cannot connect to the UNIX computer.
Agent installed on 0 computer(s). Check list for errors.
Issue
With SSH/Telnet, wrong user password
Installation Log
Connect via SSH.
Cannot connect via SSH. Disconnected from server, invalid user name or
password reported by server, or bad public key.
Failed to connect using SSH protocol; trying Telnet.
Connect via Telnet.
Connection succeeded. Login.
Login failure.
Failed to connect, either the computer does not exist or the account is invalid.
Agent installation failed. Cannot connect to the UNIX computer.
Agent installed on 0 computer(s). Check list for errors.
UNIX Software Delivery Solution User Guide
59
Chapter 5: Troubleshooting
Troubleshooting Network Problems
NS Agent Install Errors
Issue
With SSH/Telnet, wrong root password
Installation Log
Connect via SSH.
Connection succeeded. Login.
Attempting to 'su' to root.
Failed to change to root. Possible incorrect root password or root user name.
Solaris 7 on Sparc operating system detected.
Failed to connect using SSH protocol; trying Telnet.
Connect via Telnet.
Connection succeeded. Login.
Attempting to 'su' to root.
Failed to change to root. Possible incorrect root password or root user name.
Failed to connect, either the computer does not exist or the account is invalid.
Agent installation failed. Cannot connect to the UNIX computer.
Agent installed on 0 computer(s). Check list for errors.
Issue
With SSH/Telnet, not a root user
Installation Log
Connect via SSH.
Connection succeeded. Login.
Attempting to 'su' to root.
Failed to change to root. Possible incorrect root password or root user name.
Solaris 7 on Sparc operating system detected.
Failed to connect using SSH protocol; trying Telnet.
Connect via Telnet.
Connection succeeded. Login.
Attempting to 'su' to root.
Failed to change to root. Possible incorrect root password or root user name.
Failed to connect, either the computer does not exist or the account is invalid.
Agent installation failed. Cannot connect to the UNIX computer.
Agent installed on 0 computer(s). Check list for errors.
Troubleshooting Network Problems
The benefit of a remote management product is that the server and managed computer systems
communicate on a regular basis. If communications is impeded or inaccurately setup, then the
management application will not be able to run as designed. The network protocols to check are as
follows:
•
TCP/IP Validation - TCP/IP Validation (page 60)
•
SSH and Telnet Validation - SSH and Telnet Validation (page 61)
•
Domain Name System (DNS) Validation - Domain Name System (DNS) Validation (page 61)
•
HTTP Communication Validation - HTTP Communication Validation (page 62)
•
FTP Validation - FTP Validation (page 62)
TCP/IP Validation
Verify that the Notification Server (NS) can communicate with the UNIX computer over TCP/IP by
using the “ping” utility.
To verify TCP/IP is working correctly
1
From the Notification Server, click Start > Run.
2
In the Open text box, type cmd, and then click OK. The command session page appears.
UNIX Software Delivery Solution User Guide
60
Chapter 5: Troubleshooting
3
Troubleshooting Network Problems
From the command line, enter the IP address of the target UNIX computer by typing “Ping
xxx.xxx.xxx.xxx”, and then press Enter. This will ping the IP address of the UNIX computer,
which tests the network connection. You could receive one of the following messages:
•
Reply from the host - Indicates a valid TCP/IP route.
•
“Destination unreachable” - Indicates a bad configuration of TCP/IP or no response
from the host.
•
“Request timed out” - Indicates a bad configuration of TCP/IP or no response from the
host.
SSH and Telnet Validation
When deploying the NS Agent from the Notification Server, this release relies on the SSH or Telnet
utilities to establish a connection with the target UNIX computer. For security reasons, Telnet traffic
is often turned off or blocked by firewall software.
To verify SSH is working correctly
•
You can use a SSH utility, such as Putty, to verify it is working correctly.
•
Test the SSH connection from another UNIX computer.
To verify Telnet is working correctly
1
From the Notification Server, click Start > Run to open a command session.
2
In the Open text box, type “cmd”, and then click OK. The command session page appears.
3
From the command line, enter the IP address of the target UNIX computer by type “Telnet
xxx.xxx.xxx.xxx”, and then press Enter. You could receive one of the following messages:
4
•
“Connect Failed” - Telnet is disabled or the destination is unreachable.
•
Login prompt for the target UNIX computer - Telnet is working correctly.
Login to the UNIX computer by typing the user name and password.
If Telnet does not allow root access (Generally this is the default configuration) do the following:
a
Login using a secondary user name and password, and then note the system prompt for that
user.
b
From the command line, type “su root”, or a “root equivalent user name”, and then
press Enter.
c
Type the “root equivalent password”, and then press Enter.
Important: Be sure to note the command line system prompt, which is usually a “#”, but it
could be different because the prompt can be configured. The system command line prompt
for both root and root equivalent user accounts, are used to determine the current state of the
process when Pushing the NS Agent to target UNIX computers. If the system command line
prompts are incorrect, the installation will fail.
Domain Name System (DNS) Validation
DNS resolution is required if domain names are used in the configuration of the NS Agent software.
The configuration file, named client.conf, is located in the default directory /opt/altiris/notification/
nsagent/etc. The client.conf file contains references to the Notification Server in URLs using domain
names or IP addresses. If an IP address is listed and it is not the Notification Server’s IP address, the
system will not work. If domain names are being used, failure can occur if the DNS server cannot
resolve the domain name into an IP address.
To verify DNS is configured
1
On the target UNIX computer, login a root or root equivalent user name and password.
2
From the command line, type “cat/opt/altiris/notification/nsagent/etc/
client.conf | grep Server-” to determine if DNS is being used in the configuration of
the NS Agent.
UNIX Software Delivery Solution User Guide
61
Chapter 5: Troubleshooting
•
3
Troubleshooting Network Problems
The output result should be something like, Server-1=172.15.3.2.
If the output is an IP address, DNS is working correctly; no further action is required. If the
output is a DNS domain name, then do the following:
a
From the command prompt, verify that you can ping the NS server. Type “Ping
xxx.xxx.xxx.xxx”, the IP address of the Notification Server.
b
Call the DNS lookup (resolution) utility to see if DNS can resolve the name. Type
“nslookup ns-name.domain.com”, the full DNS name of the NS server.
c
The output will reflect the DNS server being queried: the name you entered, and the IP
address that is registered with the DNS server. If this is incorrect, you can edit the client.conf
configuration file and enter the IP address of the Notification Server in place of the DNS
name.
d
If you do not get a response, check the contents of the /etc/resolv.conf file. This determines
which DNS servers your computer is configured to communicate with. Ping the DNS servers
to see if you get a response.
HTTP Communication Validation
UNIX data is posted to the Notification Server via HTTPS, HTTP or FTP. One way to test that the
Internet Information Services (IIS) on the Notification Server is responding to an HTTP post request,
is to investigate the response from the IIS server.
To verify HTTP is working correctly
1
On the UNIX computer, in a command console (shell), run the following commands:
•
telnet xxx.xxx.xxx.xxx 80 (where xxx.xxx.xxx.xxx is the IP address of the NS server and 80
is the port utilized by HTTP).
The responses will be one of the following:
•
“Connection Refused” - The IP address (xxx.xxx.xxx.xxx) is not listening on port
80 (no HTTP services), which means there is a problem with IIS.
•
“Connected to xxx.xxx.xxx.xxx” - The server is listening on port 80 and is waiting
for further instructions.
2
If you received the “Connected to...” message, type the command:
•
GET http://xx.xx.xx.xx/AeXNS (where xxx.xxx.xxx.xxx is the IP address of the NS server)
The return response from the IIS server can vary; however, in most cases you will receive one of
the responses listed below, along with lots of data. The first line returned after the “GET”
command where to look for the response.
•
“HTTP/1.1 200 OK” - The system is listening and responding. The page requested exists and
the requestor has the appropriate rights to get access.
•
“HTTP/1.1 401 Access Denied” - This means that the either the page does not exist, or that
the requestor does not have the appropriate permissions to access the page. This would
necessitate investigation of the IIS server and services on the NS server for resolution.
FTP Validation
The FTP protocol can be used to pull down updated configuration files or software packages. To
verify that FTP is working correctly, determine the FTP user account and password being used, by
looking in the client.conf file. This information will help you test the FTP protocol.
To verify FTP is working correctly
1
On the UNIX system, in a command console (shell), run the following commands:
•
ftp xxx.xxx.xxx.xxx
Possible responses are as follows:
•
No route to host (can’t communicate over TCPIP)
UNIX Software Delivery Solution User Guide
62
Chapter 5: Troubleshooting
2
Additional Troubleshooting Tips
•
Connection Refused (Service is not running)
•
Connected to xx.xx.xx.xx (Connected and prompting for a name and a password)
Type the name and password you found in the config files.
Possible responses are as follows:
•
Login failed - The user does not exist, the password is incorrect, or both.
•
(User name) user logged in - Successful login.
If you have a successful login, the FTP protocol is working correctly.
Additional Troubleshooting Tips
When applicable, the following steps can help determine where problems may be happening.
The first thing to do is to make sure that the “debug level” is set to “info” in the client.conf.
This will provide as much information as possible on what is happening on the system at any given
time.
Isolating issues in the subagents
If the error is in aex-invagent-configuration, aex-invagent-hardware, or aex-invagent-software,
isolate the individual subagent causing the error by running each main agent’s subagents
individually. The names of each subagent can be found by using the “-?” switch on the main agent.
Instructions are given on how to run an agent and a subagent from the “-?” option. The following
commands illustrate how to determine the sub agents for the aex-invagent-configuration agent, so
that each sub agent can be run individually and examined for errors and issues. The aex-invagenthardware and aex-invagent-software agents would provide similar results.
To determine the sub agents
1
Run the following commands from a UNIX command prompt:
•
aex-invagent-configuration -? (Lists the subagents for the agent in question)
Output for -? will include usage information as well as a list of the subagents
•
2
Each main agent may have a number of sub agents, which are applicable only to particular
platforms. For example, the software agent’s “agentrpminfo” is only available on Linux
systems which have the rpm subsystem.
If you have isolated the subagent causing the error, it can often help to attach any system files or
the output of commands related to that agent. For example, if the “agentgroups” seems to be
in error, looking at the file /etc/group may help isolate the issue; for example, if the file was
corrupted.
Using the log file
Located in the /opt/altiris/notification/nsagent/var directory (or where ever you chose to install the
NS Agent for UNIX) is a file called aex-client.log. This is the primary file where information is
logged as different processes run and have output. When troubleshooting, there is a way to view the
log real-time, as your are trying to narrow down any problems.
To view the log
1
From the UNIX command line issue the command:
•
2
tail -f /opt/altiris/notification/nsagent/var/aex-client.log
This will output to the screen any log entries as they occur. From another console screen (or
session), you could then run any of the utilities, and watch their output to see what is occurring.
UNIX Software Delivery Solution User Guide
63
Appendix A:
Appendix
Step-by-step How to Distribute a Software Package
These step-by-step instructions will help you to understand the process required to distribute a
software package to target computers. The example will begin with downloading Acrobat Reader
from the Adobe System, Inc. web site, and end with checking the software package distribution
status after it has been sent to a group of UNIX computers.
Quick Links
Download Adobe Acrobat Reader How to download Adobe Acrobat Reader.
(page 65)
Unzip the .GZ file (page 65)
How to uncompress a .gz file, and then extract the tar files.
Create a Collection (page 70)
How to create a UNIX Collection.
Create a Package (page 73)
How to create a software Package.
Create a Policy or Advertisement How to create a software notification Policy.
(page 76)
Check the Policy or
Advertisement (page 78)
How to check if a Policy is assigned to a computer.
Verify Success or Fail of Software How to check if the Software Delivery Package installed
successfully.
Install (page 83)
Use Adobe Acrobat on the UNIX How to check if Adobe Acrobat is working correctly.
computer (page 86)
UNIX Software Delivery Solution User Guide
64
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Download Adobe Acrobat Reader
Adobe Acrobat Reader can view and print Adobe PDF files. Download the latest version available
for your platform from Adobe Systems, Inc.
To download the Adobe Acrobat Reader
1
Go to www.adobe.com/products/acrobat, and then click Get Adobe Reader on the page.
2
Step 1 of 2
3
Step 2 of 2 - The latest version of Adobe Acrobat Reader available for the Platform you chose will
be displayed along with the file size, click Download.
- Click the drop-down arrow to select a Language, Platform, and Connection Speed.
Unzip the .GZ file
Altiris recommends you do not use the WinZip program to unzip downloaded UNIX zip files. If you
use WinZip to unzip files, it will add a hard return symbol (^M) at the end of every line of the
INSTALL script, which will cause the script to fail when it tries to install the software package after
downloading to client UNIX computers.
Copy the .gz file you downloaded from Adobe Systems, Inc., to a directory on the UNIX computer
and use gunzip and tar to uncompress the archive. See “Uncompressing the .gz file” on page 66
for more details.
UNIX Software Delivery Solution User Guide
65
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Uncompressing the .gz file
The Adobe Acrobat Reader file you downloaded and saved to the hard drive, is a compressed .gz
file. The following instructions will guide you through uncompressing the .gz file.
To Uncompress the .gz file
1
Copy the .gz file to a new directory on the UNIX computer. The graphic below is using the file
transfer tool CuteFTP to FTP the .gz file to the UNIX computer. The file, solaris-505.tar.gz, is
being uncompressed on a Solaris Sparc computer.
The graphic shows the downloaded Acrobat Reader zip file has been transferred from the local
drive (left pane) to a UNIX computer (right pane).
2
From the shell console of the UNIX computer, navigate to the directory where you copied the.gz
file to, and then use the gunzip command to unzip the file.
UNIX Software Delivery Solution User Guide
66
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
3
When the file is unzipped, the .gz extension is dropped, leaving the filename with only the .tar
extension. A .tar file is a container consisting of several other files. Notice the result in the right
pane of the graphic.
4
From the shell console, use the tar command to untar the file and extract all files in the container.
5
When you untar the file, the extracted files will list in the directory where you executed the tar
command. The graphic below shows the list of extracted files in the right pane of the CuteFTP
program.
UNIX Software Delivery Solution User Guide
67
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
The same list of extracted .tar files shown from the shell console.
6
The package you will create later in the “Create a Package” on page 73 section, is defined with
a directory that contains all the files for the Adobe Acrobat Reader. When a package gets
distributed, all the files within the directory will try to download and install to the client UNIX
computers.
The .tar file is not needed on client computers, and because the file size is so large, it is best to
delete it before downloading the package. Delete the .tar file, solaris-505.tar now.
Removing the solaris-505.tar file from the shell console.
UNIX Software Delivery Solution User Guide
68
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
7
Download all the (Adobe Reader) unzipped files from the UNIX computer to the local directory
on the Notification Server, as shown in the left pane of the CuteFTP program. These locally
copied files will become the software package that is distributed to client UNIX computers.
8
You have completed all steps required to unzip, untar, and copy the extracted files from the
UNIX computer to the Notification Server. You are now ready to create a group of computers to
send the software package to, see “Create a Collection” on page 70 for more details.
UNIX Software Delivery Solution User Guide
69
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Create a Collection
You must first create a Collection (or group of UNIX computers) before you can download a software
package. The software package you create is associated to a Collection, which tells Notification
Server the group of client computers that are to receive the software package. Only the computers
defined within a Collection will receive the package download from Notification Server.
When you create a Collection, the group of computers you define must reside within the Notification
Server database. Altiris’ UNIX Inventory Solution collects inventory from your network resources,
and then automatically adds the data to the database. Creating a Collection requires you to search the
Notification Server database and group lists of computers together.
To create a collection
1
From the Web Administration Console, click UNIX SW Delivery Solution > Collections.
2
Right-click on Collections, and then select New Solution Group. The folder will add to the file
structure below Collections.
3
Click the New Solution Group, and then rename it to your own name. For this example, the folder
is named, UNIX Computers.
UNIX Software Delivery Solution User Guide
70
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
4
Right-click on the new folder you created, the example shows the folder UNIX Computers, and
then select New > Static Collection.
5
Enter a name for the Collection, such as SPARC.
6
In the right pane, click Add Resource.
A pop-up window will open, you will see a list of UNIX computers, previously inventoried by
the UNIX Inventory Solution.
7
Select the computers you want, then click Add. The example shows the sparc-utah computer was
added to the SPARC Collection.
UNIX Software Delivery Solution User Guide
71
Appendix A: Appendix
8
Step-by-step How to Distribute a Software Package
Click the Click here to refresh link in the right-pane, the computers you selected to add to the
SPARC Collection will appear on the page.
UNIX Software Delivery Solution User Guide
72
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Create a Package
The Package Servers option now supports UNIX packages. If you have Package Servers set up in
your environment, you can select these at this time.
A Package is distributed to one or several target UNIX computers, and may contain file updates,
shell scripts, or program files. Continuing on with our example, we will create a package that
contains the Adobe Acrobat Reader program files.
To create a software package
1
From the Web Administration Console, in the right pane, click UNIX SW Delivery Solution >
Packages.
2
3
Right-click on My UNIX Packages, and then select New > UNIX Package.
Enter a name for the package, such as SPARC - Acrobat Reader.
4
In the left-pane, the new package you named is listed below My UNIX Packages. The right pane
displays the Package Properties page.
5
Enter the values for the Version, Publisher, Language, and Description fields on the Package
Properties page.
UNIX Software Delivery Solution User Guide
73
Appendix A: Appendix
6
Step-by-step How to Distribute a Software Package
You do not need to enter values for Status Events; however, you will need to setup the
distribution method, click the option Package Distribution Method (Required). There are four ways
to distribute the Package, they are listed on the page.
a
Because you have the Package in a directory on the Notification Server, click the option
Access Package from a local directory on the Notification Server machine.
b
Browse to the directory where the Adobe Acrobat Reader program files reside, and then click
OK. The folder you selected will be appear in the Package Location field.
Important: Be sure all files within the directory you selected above are intended to be
distributed, as they will be added to the Package.
7
The Package Servers option is used with Windows Packages. When you are done entering the
setting for this page, click Apply.
8
Click the Programs link at the top of the page, the Program page appears.
9
Because you have not defined any programs within this package, the only option in the dropdown list is New Program. Click New and Delete to add or remove programs to this Package.
10
Click the Identification link.
11
Enter a Name for the package, a Description (optional), and a Command line path in the fields on
the page.
Note: Be sure to include a “./” in front of the program filename that is to execute (on the
Command line)
12
or it may not run after it is downloaded to the UNIX computer.
Enter the values as needed, for the following fields.
Working Directory - If this field is blank, the software package will download and install to the
directory path entered for the Command line field. If you enter a Working Directory value, when
the package downloads, it will change to the Working Directory path before it tries to install the
package to the directory path Command line.
Estimated Disk Space - The Software Delivery Solution can determine if the is enough disk space
to execute the Package installation as it downloads to each target computer. If the target
computer’s disk space is less than the value entered in this field, the Package distribution will bypass the computer, skipping the download altogether.
UNIX Software Delivery Solution User Guide
74
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Estimated Run Time - is there for calculation purposes so that in case you install this package
on multiple machines, you will be given an estimated time to run this package installation.
Anyway, your right-pane should look like the graphic below:
13
When you have entered all the settings for the Programs page, click Apply. The New Program
name in the drop-down list has now changed to the new name you defined in the Identification
section.
UNIX Software Delivery Solution User Guide
75
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Create a Policy or Advertisement
After you have created a Package, you must send a UNIX Advertisement to the targeted computers.
The Package is associated with a Collection, which contains a list of target computers. A Policy is a
notice that tells the target computer to “pickup” a Package from the Notification Server.
To create a Policy or Advertisement
1
From the Web Administration Console, click UNIX SW Delivery Solution > Policies > My UNIX
Advertisements.
2
Right-click on UNIX SW Delivery Solution, and then click New > UNIX Advertisement.
3
Enter a name for the Advertisement, such as Adobe Advertise.
The value you entered for the Advertisement name appears in the Name field, of the Identification
section on the Advertisement Properties page.
4
Select the Enabled check box.
5
The Package Type defaults to the UNIX Package, click the drop-down arrow to select a different
type.
6
Click the drop-down arrow and select a Package Name. In this example, the SPARC - Adobe
Acrobat Reader Package you created has been selected.
7
Enter a description for the Policy in the Description field.
8
Click the drop-down arrow and select the Priority.
9
Click the drop-down arrow next to the Applies to Collection option, select the solution where you
have created a Collection of computers to apply this Policy. The example shown selected UNIX
Software Delivery Solution.
10
Click the drop-down arrow and Select a Solution Group. The example shown selected UNIX
Computers.
UNIX Software Delivery Solution User Guide
76
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
11
Click the drop-down arrow and Select a Collection. The example shown selected SPARC.
12
Click Mandatory Assignments.
13
By default, the option Allow users to run this advertisement independently of mandatory
is selected. This option allows users to run the package manually from the console
of the UNIX computer.
assignments
In our example, we are creating a Policy (Advertisement) for the Adobe Acrobat Reader Package.
The Adobe program runs through a series of steps prior to installation, such as displaying the
license agreement, that the user must accept. Because of the interactive steps involved, it is best
that the user manually install the program at the UNIX console, instead of the Software Delivery
Solution installing it automatically after download.
14
Select the check box to either run the advertisement As Soon As Possible or on a schedule, and
then click Apply.
UNIX Software Delivery Solution User Guide
77
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Check the Policy or Advertisement
Because a Policy is assigned to a Collection, consisting of target computers, you may want to find out
what Policies or Advertisements are assigned to the target computers.
To check a Policy or Advertisement
1
From the Web Administration Console, click UNIX SW Delivery Solution > Collections > UNIX
Computers > SPARC.
2
Double-click on the UNIX computer, whose policies you want to view. (i.e., sparc-utah in my
case)
3
Click the Policy Config tab at the top of the page.
UNIX Software Delivery Solution User Guide
78
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Manually installing Adobe Acrobat at the Console
Now we can go to the UNIX box and run the installation program manually.
1
There is a script installed on the Unix box called “aex-swdapm” which stands for “Software
Delivery Advertised Package Manager”. This script is in charge of looking up on the NS any
advertised packages destined for this machine. To find it, change to the /usr/local/aex-swdsoln/
bin directory. To run it, type the command “./aex-swdapm” and Enter. You will see this:
2
To choose the package to install, simply type the “1” in front of the package and press Enter. This
will begin to download all package files from the NS server via FTP. Here is a sample of it
downloading:
UNIX Software Delivery Solution User Guide
79
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
3
You will then be presented with Adobe’s License Agreement. Press the Space Bar until the
complete license agreement scrolls to the end.
4
When done, you will be prompted to type “accept” or “decline”. I suggest you type “accept” and
Enter.
UNIX Software Delivery Solution User Guide
80
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
5
Next, you are informed that the installation will require 28MB of free space and the install will
ask you where to install the software. If you press Enter, it will default to /opt/Acrobat5. I suggest
you just press Enter.
6
It will pause to ask you if you want to create this directory since it doesn’t exist. Type “y” and
press Enter.
7
It will then go through the installation process and report on each operation. At the end the
message: “Command executed with exit code 0" will display signifying that the installation was
UNIX Software Delivery Solution User Guide
81
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
successful. The last step is that all downloaded files in the package are deleted from the Unix
box. Finally, the message: “Posting Events to the Notification Server” shows up.
8
You can verify that the application has been installed and all files copied to the /opt/Acrobat5
directory as shown:
UNIX Software Delivery Solution User Guide
82
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Verify Success or Fail of Software Install
Check to see if the software package you sent installed successfully on the target UNIX computer.
To check software delivery
1
From the Web Administration Console, click UNIX SW Delivery Solution > Collections > UNIX
Computers.
2
Highlight the SPARC collection.
UNIX Software Delivery Solution User Guide
83
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
3
In the right pane, double-click on the UNIX computer that you are targeting. This example shows
a sparc-utah computer.
4
Click the Event tab, and then click the AeX Unix SWDelivery link in the left pane. This will create
a table in the right pane showing the results of the installation as shown below.
UNIX Software Delivery Solution User Guide
84
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
5
Notice that there are two lines of information. The first line reports the results of the download
from the NS to the UNIX computer under the Action column heading. The Status column will
display Success, and the Exit Code column will report a zero (0).
6
Finally, the LogMessage column will give a description of the recorded results.
UNIX Software Delivery Solution User Guide
85
Appendix A: Appendix
Step-by-step How to Distribute a Software Package
Use Adobe Acrobat on the UNIX computer
To verify that the software package process worked, go to the target UNIX computer and try to run
the Adobe Acrobat Reader application.
To run Adobe Acrobat Reader
1
Open a console window, change directory to /opt/Acrobat5/bin.
•
2
Type “acroread”, and they press Enter.
The Adobe Systems license agreement will appear, click Accept.
UNIX Software Delivery Solution User Guide
86
Appendix A: Appendix
3
Click File, Open, and then Browse to /opt/Acrobat5/Reader then select the file “MapTypes.pdf”.
•
4
Step-by-step How to Distribute a Software Package
Click Open.
You have successfully installed Adobe Acrobat Reader on the UNIX computer.
UNIX Software Delivery Solution User Guide
87
Index
A
administration 49
Altiris
support 7
assistance 7
R
Requirements 13
Requirements, UNIX Operating
Systems 13
C
contact information 7
conventions for document 6
copyright 2
creation date of document 2
cross references 6
customer support 7
D
document
conventions 6
print date 2
S
Setup, Notification Server 15
support 7
contact information 7
System Requirements 12
T
technical support 7
trademark 2
troubleshooting 57
U
E
external documents 6
UNIX Operating Systems
requirements 13
UNIX System 13
UNIX System Requirements 13
G
getting help 7
V
version 2
I
Install Additional Software
Components 20
Install Microsoft Database Engine 19
Install Notification Server 17
L
legal notice 2
links 6
N
notice 2
Notification Server Setup 15
Notification Server, Install 17
Notification Server, Install Additional
Software Components 20
Notification Server, Install MSDE 19
O
operation 49
P
patent 2
product version 2
UNIX Software Delivery Solution User Guide
88
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement