landesk asset lifecycle manager - download.ivanti.com · track, and manage assets in the context of...

LANDesk® Asset Lifecycle Manager

Installation Guide

INSTALLATION GUIDE

2

Copyright © 2011 LANDesk Software, Inc. and its affiliates. All rights reserved. LANDesk and its logos are registered trademarks or trademarks of LANDesk Software, Inc. and its affiliates in the United States and/or other countries. Other brands and names may be claimed as the property of others.

LANDesk Software, Inc. and its affiliates (“LANDesk”) do not warrant that this document is error free and retain the right to make changes to this document or related product specifications and descriptions at any time without notice. LANDesk does not assume any

obligation to update the information contained herein. This document is provided “AS IS” and without any guaranty, warranty, or license, express or implied, including but not limited to: fitness for a particular purpose, merchantability, non infringement of intellectual property, or other rights of any third party. Any LANDesk products referenced in this document are not intended for use in medical, life saving, or life sustaining applications. Third parties may have intellectual property rights relevant to this document and the technologies discussed herein.

LANDesk Asset Lifecycle Manager 5.0

Revision 1.0 (04/15/2011)

LANDESK ASSET LIFECYCLE MANAGER

3

Contents

Cover ..........................................................................................................................1 Contents .....................................................................................................................3 LANDesk Asset Lifecycle Manager ..............................................................................4

Upgrading from earlier versions ............................................................................. 4 Installation tasks ................................................................................................. 4

LANDesk Asset Lifecycle Manager overview .................................................................. 5 Important concepts and terms .............................................................................. 5 Console interfaces ............................................................................................... 5 Tools and features ............................................................................................... 5 Asset Content pack .............................................................................................. 6 User documentation ............................................................................................. 6

Proceeding with the installation .................................................................................. 6 Understanding and meeting system requirements .....................................................7

Selecting the ALM server ........................................................................................... 7 Server system requirements ................................................................................. 8

Selecting the console computer ................................................................................ 10 Console system requirements ............................................................................. 10

Requirements for computers accessing the Web console .............................................. 11 Selecting the database ............................................................................................ 12

Supported databases ......................................................................................... 12 SQL Server database system requirements ........................................................... 12

Continuing with the installation ................................................................................ 12 Preparing the database ............................................................................................13

Database configuration....................................................................................... 13 Microsoft SQL Server 2005 and 2008 database configuration guidelines ........................ 14 Example: Installing and configuring a Microsoft SQL Server 2005 database ................... 15 Reindexing your database........................................................................................ 17 LANDesk Customer Support and database issues ........................................................ 17

Installing LANDesk Asset Lifecycle Manager components ........................................18 Installing the server and console components ............................................................ 18

Completing the final setup tasks .......................................................................... 24 Installing the Design console on a remote machine ..................................................... 25 Integration issues with LANDesk Management Suite ................................................... 26

Activating the server ................................................................................................27 LANDesk Software license activation overview ........................................................... 27

Licensing options ............................................................................................... 28 Using the license activation utility ............................................................................. 29

Viewing your product licenses ............................................................................. 29 Activating a new server with a LANDesk Software account ...................................... 30 Activating a new server with a trial-use license ..................................................... 30 Updating an existing account .............................................................................. 30 Manually activating a server and verifying usage data ............................................ 30

Configuring required initial settings .........................................................................32 Required initial settings ........................................................................................... 32 Configuring initial settings ....................................................................................... 32 Additional settings .................................................................................................. 36

Starting the console .................................................................................................37

INSTALLATION GUIDE

4

LANDesk Asset Lifecycle Manager

Welcome to the Installation Guide for LANDesk® Asset Lifecycle Manager, or ALM.

This guide provides critical planning considerations and step-by-step instructions for installing and configuring LANDesk Asset Lifecycle Manager — an innovative and fully-integrated IT asset and process management solution.

NOTE: IMPORTANT Audience assumptions and disclaimers

This guide assumes you are familiar with Microsoft* Windows 2003 Server and Windows 2008 Server, or

Server 2008 R2 and that you are able to install the operating system with all of the necessary

prerequisites for a Microsoft SQL 2005 or SQL 2008 database. Obtaining licensing for Microsoft software

and distribution of the software are the responsibility of the customer installing the product.

Additionally, your network environment must have an Active Directory system configured with users that

can be assigned IT assets. Assets cannot be allocated to non-Active Directory accounts.

This guide covers all of the concepts and procedures necessary for completing prerequisites, installing the

product, configuring initial settings, and starting the administrator console. Database performance tuning

is NOT within the scope of this document and should be performed by a qualified database administrator.

Furthermore, this guide provides the information necessary for a base installation only. Implementation

questions regarding extraordinary data generation and related performance issues should be directed to

LANDesk Professional Services or LANDesk Customer Support.

Upgrading from earlier versions

If this installation is to upgrade Asset Lifecycle Manager from either version 3.5 or 4.0, you need to first install the latest Asset Lifecycle Manager service pack before proceeding with the installation. For assistance, contact LANDesk Technical Support or search on the LANDesk

Technical Community website (http://community.landesk.com).

Installation tasks

Installation, configuration, and starting LANDesk Asset Lifecycle Manager is divided into the following main tasks, which should be performed in the order listed below. Each task is described in a corresponding section in this guide that walks you through that part of the installation process.

Read this guide to learn about:

See "LANDesk Asset Lifecycle Manager overview" on page 5

See "Understanding and meeting system requirements" on page 7

See "Preparing the database" on page 13

See "Installing LANDesk Asset Lifecycle Manager components" on page 18

See "Activating the server" on page 27

See "Configuring required initial settings" on page 32

See "Starting the console" on page 37


5

LANDesk Asset Lifecycle Manager overview

The integrated LANDesk Service Management Suite is comprised of two LANDesk product technologies: LANDesk Asset Lifecycle Manager and LANDesk Process Manager.

The combined functionality of these technologies lets IT asset managers proactively create, track, and manage assets in the context of their organization's unique process workflow requirements. IT asset management is a comprehensive set of business practices that join financial, contractual, and inventory functions to support asset life cycle management and strategic decision making for your IT environment.

With a powerful and flexible asset and process management tool, your organization can realize immediate and ongoing benefits in all key business areas, including: maximizing critical investments, demonstrable cost savings, increased end user productivity, and improved overall operational efficiency.

Important concepts and terms ALM server: The center of your asset and process management system. All the key

files and services for LANDesk Asset Lifecycle Manager are on the server. Your network requires only one ALM server. A dedicated machine is recommended for the ALM server.

ALM database: LANDesk Asset Lifecycle Manager requires a database to store asset and process workflow information. The database provides a structured asset repository, which is the core of the ALM system. A separate dedicated machine is recommended for the ALM database.

Design console: The Windows-based interface used by system administrators to perform asset and process management tasks, and to configure system settings. The Design console can be installed on the server and/or on multiple separate machines as

remote consoles.

Web console: The browser-based interface used by asset managers and regular end

users. This Web console URL can be accessed from any computer that has a supported browser.

Console interfaces

LANDesk Asset Lifecycle Manager includes two console interfaces with distinct operations:

Windows console: Resides on the server or on a separate machine as a remote console; allows system administrators to implement a custom IT asset management

infrastructure by creating asset definitions, designing processes, forms, schedules, and report views, and configuring system settings. In the user documentation, this console is referred to as the Design console.

Web console: Accessed by any computer with a supported browser; with available tools and features determined by assigned roles and rights; allows designated asset managers to enter, import, synchronize, track, and manage asset data; and allows end users to access and fill out asset request forms that initiate automated process

workflows.

Tools and features

With LANDesk Asset Lifecycle Manager, you can:

Create a variety of custom asset type definitions, including: hardware, software, office equipment, supporting resources such as contracts and invoices, etc.

Design asset data entry forms that asset managers use to add, edit, and delete asset instances in the database

INSTALLATION GUIDE

6

Track assets though the entire business lifecycle from procurement to disposal

Implement asset security and control across your enterprise

Create complex automated process workflows with an easy-to-use graphical tool

Assign and view asset dependencies and relationships

Search and sort asset inventory based on custom criteria

Synchronize and reconcile asset data from multiple external data sources

Import process workflows from existing LANDesk Process Manager systems

Enforce standardized processes and regulatory compliance

Conduct accurate and complete asset auditing

Create report views

Generate and print actionable reports and graphs

Design asset and service request forms

Provide request forms to end users via the Web console

Control access to the Web console interface and features based on specific assigned

roles

Asset Content pack

ALM also includes an extensive collection of ready-to-use asset definitions, workflows, and resources in the Asset Content pack. The content pack includes dozens of pre-designed forms, data views, reports, and supporting resources (asset forms, forms for contracts, vendors, purchase orders, warranties, etc.).

The Asset Content pack is designed to help you start putting the asset management system to work right away. It also gives you a model for how to set up and customize additional kinds of

asset records and supporting resources as your needs continue to evolve.

For information about the Asset Content pack, see the Asset Manager's Guide.

User documentation

LANDesk Asset Lifecycle Manager has a complete set of user documentation that describes the features and capabilities offered by the ALM tools. The documentation you consult depends on your role.

If you are the IT Administrator or individual assigned to design the asset management system, your primary resource is the Designers Guide, which describes how to use the

Design console.

If you are the Asset Manager, your primary resource is the Asset Manager's Guide, which describes how to use the Web console.

Proceeding with the installation

The first step in preparing to install LANDesk Asset Lifecycle Manager components is to make

sure you have the necessary hardware and that it meets minimum system requirements. For detailed information, proceed to "Understanding and meeting system requirements" on page 7.


7

Understanding and meeting system requirements

This section describes how to select and set up the appropriate hardware resources with the necessary software prerequisites prior to installing LANDesk Asset Lifecycle Manager components.

Read this section to learn about the following preliminary tasks:

See "Selecting the ALM server" on page 7

See "Server system requirements" on page 8

See "ALM port usage" on page 9

See "Selecting the console computer" on page 10

See "Console system requirements" on page 10

See "Requirements for computers accessing the Web console" on page 11

See "Selecting the database" on page 12

See "SQL Server database system requirements" on page 12

Selecting the ALM server

The ALM server is the center of your IT asset and process management system. All of the key LANDesk Asset Lifecycle Manager files and services reside on this server.

A dedicated machine for the ALM server is strongly recommended. Because of the traffic that must pass through the server to manage your assets and process workflows, LANDesk

strongly recommends that a server machine is dedicated to hosting the LANDesk Asset Lifecycle Manager software to ensure maximum performance.

Keep the following general guidelines in mind when selecting the ALM server:

ALM can be installed along with LANDesk Management Suite (LDMS) 9 in order to take advantage of the patch automation and/or Launchpad integration. In this case, ALM can reside on the same machine as LDMS. This is because in this context, ALM will not require the system resources that would be included with a full install. The full version

of ALM should only be run when it is installed on a dedicated server.

Don't install the ALM server component on a primary domain controller, backup domain controller, or Active Directory controller.

If you install other programs on the ALM server, you may experience short- and long-term resource issues.

Another separate dedicated machine is recommended to install and configure a

Microsoft SQL Server database for ALM data (see See "Selecting the database" on page 12).

NOTE: Install the same language versions

When setting up a LANDesk Asset Lifecycle Manager system, make sure to install the same language

version of the ALM components on matching native-language OS platforms. In other words, do not mix

different language versions of the ALM server, database, or console on different OS language machines.

INSTALLATION GUIDE

8

Server system requirements

As you consider which server you'll set up as your ALM server, review these system requirements and confirm that your server meets or exceeds them. The installation program automatically checks your system for the required components, reports any deficiencies to

you, and where practical, provides a link where you can download them.

NOTE: Component installation options are based on system prerequisites being met

If the machine doesn't meet the server OS or software/service prerequisites, the ALM server component

installation option is not available in the setup program. However, if the console system requirements are

met, you can install the ALM console component.

ALM server performance benchmarks

The hardware requirements for the ALM server are based on the number of process workflow actions to be performed on an hourly basis, as described below.

Up to 24 users working simultaneously at the following rates:

2 managers approving asset requests (500 approvals / hour)

2 IT managers approving asset requests (500 approvals / hour)

7 users requesting assets (400 new requests / hour)

3 asset managers editing assets (100 / hour) and adding assets (250 / hour)

2 report users running reports (20 each / hour)

Less than 250,000 assets in the database

400 process workflows per hour

The server machine should meet the following minimum hardware and software requirements.

Server hardware requirements

Core 2 Quad (2 x dual core processors) 2.66 MHz or higher

4 GB RAM

800 MB free disk space

Networked to a Gigabit network with the SQL Server

Server OS requirements

32-bit Server platforms

Windows Server 2003 Standard, SP2

Windows Server 2003 Enterprise, SP2

Windows Server 2003 R2 Standard, SP2

Windows Server 2003 R2 Enterprise, SP2



Windows Server 2008 R2 Standard

64-bit Server platforms



Windows Server R2 Standard

Windows Server 2008 R2 Enterprise


9

NOTE: The machine you set up as your ALM server must be installed as a standalone server, not on a

machine that also acts as a primary domain controller (PDC), backup domain controller (BDC), or Active

Directory controller. The user that installs the ALM server component must be logged in as a domain user

that has Administrator rights on the machine.

Console OS requirements

Windows XP Professional, SP2

Windows Vista Business, Enterprise, Ultimate (32-bit)

Windows Vista Business, Enterprise, Ultimate (64-bit), SP2

Server installed software/service requirements

Microsoft .NET Framework version 3.5

Microsoft Data Access Components (MDAC) version 2.8

Microsoft Web Services Enhancements (WSE) version 2.0 with SP3 or greater

Microsoft ASP.NET version 2.0

Internet Information Services (IIS) requirements

For Windows Server 2003, Internet Information Services (IIS) version 6.0 (To install, click Control Panel > Add/Remove Programs > Windows Components > Application Server > IIS)

For Windows Server 2003, the IIS Component: ASP.NET version 2.0 (allowed as a Web Service Extension)

For Windows Server 2008, Internet Information Services (IIS) version 7.0

For Windows Server 2008, the IIS Component: ASP.NET

For Windows Server 2008, the IIS Component: Static Content

For Windows Server 2008, the IIS Component: Windows Authentication

For Windows Server 2008, the IIS Component: IIS version 6.0 Management

Compatibility

ALM port usage

LANDesk Asset Lifecycle Manager uses the following ports:

Port 8092 needs to be open on the ALM server for remote consoles to obtain a license.

INSTALLATION GUIDE

10

Selecting the console computer

The LANDesk Asset Lifecycle Manager console computer runs the Windows (Design) console where the ALM Designer conducts management activities such as creating asset definitions, designing process workflows, defining end user request forms, creating report views, and other administrative and process management tasks.

When running the setup program, you can install the console component on the same machine as the ALM server or on a separate computer where it can be used as a remote console. If you plan to create, track, and manage a large number of IT assets and associated process

workflows and reports, we recommend installing the console component on a separate machine other than the ALM server.

NOTE: Remote console computers must be on the same domain as the ALM server

Make sure that any computer running the administrator console is on the same domain as the ALM server.

Console system requirements

If you plan to install the Design console on a separate computer, confirm that the computer

meets the following criteria.

Windows XP Professional with SP2

Windows Vista with SP1 (Ultimate and Professional Editions are supported)

Windows Server 2003 Standard or Enterprise edition with SP2

Windows Server 2008 Standard or Enterprise editions

NOTE: When you install a remote console, you must add domain users who will access the console interface to the Security tab on the Service Management directory and

assign them all rights, or they won't be able to log into the console. (Go to C:\Program Files\LANDesk, right-click the Service Management directory, click Properties > Security.)

Pentium 4 processor, 2.6 GHz, or higher

2 GB RAM

180 MB free disk space

Microsoft .NET Framework version 3.5

MDAC 2.8

NOTE: The user that installs the ALM console component must have rights to copy files, but does not need to be an Administrator user


11

Requirements for computers accessing the Web console

The LANDesk Asset Lifecycle Manager Web console provides the interface where designated asset managers use asset entry forms to add items to the database, import and synchronize asset data from external data sources, and view, generate, or print reports. The Web console is also where all end users access asset and service request forms created and configured using the ALM Design console.

Any Windows-based computer with a supported browser can access the Web console without requiring additional configuration. In order to view graphical report elements and other display

screens, you must have Adobe Flash Player installed. If you have an Internet connection, your browser should prompt you to download Adobe Flash Player.

In order to access and utilize the Web console URL, end user computers must meet the following basic requirements:

Supported browsers: Internet Explorer (IE) 6, 7, and 8 (32-bit version only); Firefox 3.x.

Adobe Flash Player version 10 or later.

INSTALLATION GUIDE

12

Selecting the database

LANDesk Asset Lifecycle Manager requires a database to store asset and process workflow information. This database provides the structured asset repository that is the core of the ALM system.

A separate dedicated machine is recommended for the database.

NOTE: Installing in a test lab environment

For a trial or demo installation, you can use the bundled Microsoft SQL Server 2005 Express database.

SQL Express database has a 4 GB database size limit. If you choose this default database option during

installation, the ALM database container is automatically set up and configured for you. The only

preparation necessary is to confirm that your ALM server meets the system requirements necessary to run

the database.

When you're installing in a production environment, you must use a supported enterprise-level

Microsoft SQL Server database to ensure LANDesk Asset Lifecycle Manager performs optimally.

Supported databases Microsoft SQL Server 2005 Express

Microsoft SQL Server 2005


SQL Server database system requirements 2 x dual core processors, 3.00 MHz, or higher

4 GB RAM

Data size requirements:

5-30 KB per asset

5-10 KB per request

20-30 KB per workflow instance

Minimum of 4 spindles for data segment (RAID 10); 2 spindles for master database and transaction log segment (RAID 1); and preferably have tempdb on a RAID 0 with 2+ disks or single drive

Networked to a Gigabit network with the ALM/LPM server

Continuing with the installation

The next step in the installation process is to create a database that stores asset, process workflow, forms, and reporting data. For information on installing and configuring the

database, see "Preparing the database" on page 13.


13

Preparing the database

LANDesk Asset Lifecycle Manager requires interaction with a database management system.

The database is an integral part of the IT asset and process management infrastructure. It handles all of the information LANDesk Asset Lifecycle Manager needs to track assets, process workflows, asset dependencies and relationships, data entry forms, end user request forms, reports, and so forth.

A dedicated machine is recommended for the database.

Read this section to learn about:

See "Database configuration" on page 13

See "Microsoft SQL Server 2005 and 2008 database configuration guidelines" on page

14

See "Example: Installing and configuring a Microsoft SQL Server 2005 database" on page 15

See "Reindexing your database" on page 17

See "LANDesk Customer Support and database issues" on page 17

Database configuration

The default installation installs a Microsoft SQL Server 2005 Express database on your ALM

server (see note below). Before installation, however, you need to create the separate container for the ALM asset data. This default database configuration is adequate for a test lab environment.

In a distributed production network environment, you need to install and configure a supported enterprise-level Microsoft SQL Server database before running the LANDesk Asset Lifecycle Manager Install program. During the installation procedure, you'll be prompted to

provide connection information to this database.

The following databases are supported:

Microsoft SQL Server 2005 Express (NOTE: If you accept this database option during installation, both the ALM database container and the licensing database container are automatically set up and configured for you.)



INSTALLATION GUIDE

14

Microsoft SQL Server 2005 and 2008 database configuration guidelines

The basic configuration guidelines are the same for both SQL Server 2005 database and SQL Server 2008 database.

The database needs the following parameters. These parameters will be configured by default if you use a typical installation for SQL Server 2005 or 2008 database.

SQL server configuration parameters

Microsoft SQL Server 2005 performs self-tuning. You shouldn't need to tune any parameters

manually.

Database parameters

Use the defaults.

A database container will need to be created for the ALM asset data repository before running the Install procedure.

Other settings

Specify the user "sa" (or another user with an alias into the database) when creating the database. The critical qualification for the user is that they must have full access rights to the database including create, update, delete, drop, etc.


15

Example: Installing and configuring a Microsoft SQL Server 2005 database

This section provides detailed steps for installing and configuring a specific database type and is provided as an example only. Keep in mind that your specific database type, as well as your

particular network environment, may necessitate some differences in the exact procedures. As mentioned above, for detailed installation instructions for each supported database type, refer to the LANDesk Support site.

Prerequisite: Installing Microsoft Internet Information Services (IIS)

To install IIS

1. Log on to the Windows 2003 Server as a member of the local Administrators group.

2. Click Start > Control Panel > Add or Remove Programs > Add/Remove Windows Components.

3. Select the Application Server component, and then click Details.

4. At the Application Server window, select the following components: Application Server Console, ASP.NET, and Internet Information Services (IIS).

5. Click OK to install the components.

6. Click OK to exit.

7. To verify IIS is installed, right-click My Computer, and then click Manage. Make sure IIS has been added to the list of installed components.

Installing a Microsoft SQL Server 2005 database

To install the database

1. Log on to the Windows 2003 Server as a member of the local Administrators group.

2. Insert the Microsoft SQL Server 2005 media. At the Microsoft SQL Server 2005 autorun window, click Install. (Or run SETUP.EXE from the root directory of the media.)

3. At the End User License Agreement page, read and accept the End User License Agreement, and then click Next.

4. Microsoft SQL verifies its prerequisites and installs them as necessary. Click Install.

5. When prerequisite installations are completed, click Next.

6. At the initial installation wizard page, click Next.

7. When the System Configuration Check verifies all prerequisites are complete, click Next.

8. At the Registration Information page, click Next.

9. Some versions might also request you to enter your 25-character product key. Enter your product key, and then click Next.

10. At the Choosing Microsoft SQL Server Components page, at a minimum select the

following components: SQL Server Database Services, Workstation Components, Books Online, and Development Tools. Click Next. NOTE: You can also select to use any of the other components at this time. Click Advanced to make other selections such as the location for installing the files.

11. At the Instance Name page, we recommend that you select Default instance, and then click Next.

INSTALLATION GUIDE

16

12. At the Service Account Settings page, select the Built-in system account of the local system. However, keep in mind that the objective of this setting is to fulfill the basic requirements of your own organization.

13. At the SQL Server Agent page, select to Start the SQL Server (because typically you will want your SQL Server and SQL Server Agent running most of the time), and then click Next. (NOTE: The SQL Server Agent allows you to automate backup procedures.)

14. At the Authentication Mode page, select Mixed Mode, and then click Next. (This allows

you to log in using either your Windows credentials or by using an “sa” password which you need to enter here.)

15. At the Collation page, select the following specific collation: dictionary order, case-insensitive, and the 1252 character set. Click Next.

16. Select whether you want to send reports to Microsoft, and then click Next.

17. At the Final Warning page, click Install.

18. When the installation is complete, click Next.

19. At the Completion Notification page, click Finish.

Checking for database service packs

At this point you should check the Microsoft Web site to see if there are any service packs that you need to install in order to update your product. Follow the directions provided in order to download and install any updates.

Creating and configuring a Microsoft SQL Server 2005 database

To create and configure the database

1. To add the TCP/IP listener for a Microsoft SQL Server 2005 database, click Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager.

2. In Configuration Manager, open the SQL Server Network Configuration object, and

select Protocols.

3. In the right-hand frame, double-click TCP/IP, select the Protocol tab, and then set enable to Yes.

4. Click the IP Addresses tab, and then enable both IP1 and IP2.

5. Click OK to save the settings.

6. Go to the Computer Management utility, and restart the SQL Server service.

7. Go to the Open SQL Server Management Studio.

8. Log in using Windows Authentication, or by choosing SQL Server Authentication and supplying your "sa" password.

9. To create the ALM database container, right-click the database tree, and then click New Database. (When installing the ALM server, you will point to this database container.)

10. Specify the database name, choose the creation options you want, and specify the path where you want the database MDF and LDF files.

11. Click OK to exit.

Once you've configured your database, the next step in the installation process is to install the actual LANDesk Asset Lifecycle Manager components and point to the database.

For complete instructions on running the LANDesk Asset Lifecycle Manager setup program, see See "Installing LANDesk Asset Lifecycle Manager components" on page 18.


17

Reindexing your database

Performing routine database maintenance such as re-indexing is important for keeping the database running at peak performance. When information is entered or modified in the database tables, indexes can become fragmented.

Index fragmentation can happen when the logical sequence of pages is disrupted or when an index page contains less than its maximum amount of data, creating a gap in the data page or index. As indexes become fragmented, data reads become inefficient when accessing tables, thus slowing database performance.

For more information on reindexing SQL databases, see the document "Reindexing LANDesk Databases" in the LANDesk Technical Community, at: http://community.landesk.com. Look under Systems Management > Inventory > Database.

LANDesk Customer Support and database issues

LANDesk Customer Support is committed to helping you resolve database issues. Some issues may require additional assistance from the database vendor or through an approved third party.

The database support that LANDesk Customer Support won't provide includes, but is not

limited to, the following:

Configuring the DBMS with additional parameters for performance or other reasons

Creating scripts

Configuring an existing DBMS installation to work with LANDesk Asset Lifecycle Manager

Restricting rights or perform other user maintenance

Backing up the databases

Repairing corrupt databases

If you call LANDesk Customer Support, support personnel will attempt to do the following:

Isolate the problem

Verify that the specified DBMS parameters are correct

Verify that LANDesk Asset Lifecycle Manager is working correctly

If the DBMS still doesn't work, you may need to either reinstall the DBMS or resolve the issue through other means.

INSTALLATION GUIDE

18

Installing LANDesk Asset Lifecycle Manager components

This section describes how to install the core components of LANDesk Asset Lifecycle Manager.

The instructions assume you've set up the necessary requirements for a successful installation. If you have not completed the prerequisites described in the system requirements

section, return to that section to make sure your system meets all of the hardware and software prerequisites. For details, see See "Understanding and meeting system requirements" on page 7.


See "Installing the server and console components" on page 18

See "Completing the final setup tasks" on page 24

See "Installing the Design console on a remote machine" on page 25

See "Integration issues with LANDesk Management Suite" on page 26

Installing the server and console components

The ALM server is the center of your IT asset and process management system. It contains all the key files and services required for LANDesk Asset Lifecycle Manager.

The Design console provides system administrators with a convenient interface where they can perform IT asset and process management tasks (creating asset definitions, process workflows, forms, and report views); configure system settings (mail, users/groups, LDMS

core server connections, third-party PIM integration, roles, and scopes); and launch the Web console.

To install Asset Lifecycle Manager, you must be logged on as an Active Directory domain user, with system administrator rights on the server as well as rights to create a container on the database.

NOTE: IMPORTANT: Turn off the User Account Control setting on Windows Server 2008 or

Windows Vista

If you're installing LANDesk Asset Lifecycle Manager components to a Windows Server 2008 or Windows

Vista device, you need to turn off the User Account Control. To do this, go to Settings > Control Panel

> User Settings, and set the User Account Control setting to Off. It is turned on by default. If you

don't change this setting to Off, you will be prompted for permission when each executable is run by the

setup program, and you won't be able to start the console. Once the installation has completed, you can

return to the User Settings dialog box and re-enable User Account Control.

To install the server and console components

1. At the Windows server you've selected to be your ALM server, insert the LANDesk Asset

Lifecycle Manager CD into the CD-ROM drive or run AUTORUN.EXE from your

installation image. The installation procedure begins and you are prompted to specify which component you want to install.


19

• LANDesk Service Management Server: Installs both the ALM server and the Design console.

• LANDesk Service Management Designer: Installs only the Windows (Design) console that system administrators will use to create asset definitions, process workflows, forms, and report views. The Design console can be installed and run on as many machines and remote consoles as you need.

2. Click the Install button for the installation option you want:

These instructions assume you will be selecting option 1 (both the server and the console).

3. After a few seconds, the Install Requirements page displays the result of the Prerequisite check.

INSTALLATION GUIDE

20

If the prerequisite checker displays "Prerequisite check failed", there are missing components that need to be downloaded and installed. Click the LANDesk Software link (or the Help me fix this link) to download any missing required components before continuing. When you have finished, click the Check again button when you are ready to confirm that all prerequisites are now installed and you're ready to proceed.

4. When the prerequisite check confirms successful installation of all prerequisites, you are ready to continue.,

5. Click Setup Database to configure Asset Lifecycle Manager to connect to the ALM core database.

6. For Database type, select either SQL Express or SQL.

7. Enter the login credentials for the database option you chose, and click Next. When the database configuration is complete, you are returned to the Install

requirements page, and the Prerequisite check passed message appears. You are

now ready to begin the installation.


21

8. Click Run Setup

9. At the Choose Setup Language dialog, select the installation language, and then click OK.

10. At the LANDesk Service Management setup wizard page, click Next.

11. At the License Agreement page, read the agreement, select I accept the terms in

the license agreement, and then click Next.

INSTALLATION GUIDE

22

12. At the Custom Setup page, select the components (features) you want to install, and click Next. (NOTE: If you want to change the default destination folder, click Change and browse

to the desired location. Remember to substitute the new path in any references to the install location you see in the documentation.)

13. At the Ready To Install page, click Install.


23

14. While setup is running, a progress dialog shows the installation and configuration status of various components and services.

INSTALLATION GUIDE

24

15. When setup successfully completes, click Close to exit the setup program.

You've now finished installing LANDesk Asset Lifecycle Manager components. The final step in the Setup process is to complete the license activation procedure.

Completing the final setup tasks

Before launching the console, complete these final setup tasks. For detailed instructions, proceed to:

See "Activating the server" on page 27

See "Configuring required initial settings" on page 32



25

Installing the Design console on a remote machine

If you want to install only the ALM Design console component on a separate machine other than the server, follow the steps below. You can install multiple remote consoles.

NOTE: If you install multiple consoles, keep in mind that the Design (Windows) console in LANDesk Asset

Lifecycle Manager only supports one language at a time. Thus, you should not install the Design console

on one machine in English and on additional consoles in Spanish; all consoles must be in the same

language.

To install the Design console on a workstation, you must have administrator rights on that workstation.

Make sure the computer meets the console system requirements. For details, see "Selecting

the console computer" in "Understanding and meeting system requirements".

To install the Design console on a remote machine

1. At the computer you've selected to be a remote console, insert the LANDesk Asset Lifecycle Manager CD into the CD-ROM drive or run AUTORUN.EXE from your

installation image.

2. At the Autorun page, click the Install button for ALM Design console.

3. At the Install Requirements page, the prerequisite check displays either passed or failed. If the prerequisite check displays passed, click Run Setup to begin the installation.

If the prerequisite check displays failed, you will need to download and install the required components before continuing.

4. At the Choose Setup Language dialog, select the language you want to install, and

then click OK.

5. At the LANDesk Service Management setup wizard page, click Next.

6. At the License Agreement page, read the agreement, select I accept the terms in the license agreement, and then click Next.

7. At the Custom Setup page, the server component is hidden, so you can simply click Next.

8. At the Ready To Install page, click Install.

9. While setup is running, a progress dialog shows the installation and configuration status.

10. When setup successfully completes, click Close to exit the setup program.

When you log in to the remote console, enter the name of the ALM server to which you want to connect.

INSTALLATION GUIDE

26

Integration issues with LANDesk Management Suite

If you're installing LANDesk Asset Lifecycle Manager in a network environment that already has LANDesk Management Suite installed, and where a LANDesk core server and database are used to manage your devices, you need to be aware of the following integration issues.

Synchronizing asset data

With LANDesk Asset Lifecycle Manager, you can import and synchronize asset data from external data sources, including LANDesk Management Suite. For information, refer to the Asset Manager's Guide.

Configuring LDMS component services to work with Asset Lifecycle Manager

For LANDesk Asset Lifecycle Manager to properly work with LDMS 8.8 (or above), three

LANDesk services must be configured with domain logon credentials.

The ALM/LPM service: Configure this service with the ALM Database Utility.

The LDMS Scheduler service: Configure this service on the LDMS core server with the LANDesk Configure Services utility. In the console, click Tools > Configure Services.

The LDMS COM+ LANDesk application: Configure this COM+ application on the

LDMS core server with the Windows Component Services utility. On the server, click Start > Programs > Administrative Tools > Component Services to open the tool window, click Component Services > Computers > My Computer > COM+ Applications > LANDesk, and then specify the user on the LANDesk application's Identity tab.

If you don't change the logon credentials for these services, the LDMS message-based SDK

won't be able to properly make call-backs to the ALM server.


27

Activating the server

This section provides information about activating your server with a valid LANDesk Software

license.


See "LANDesk Software license activation overview" on page 27

See "Using the license activation utility" on page 29

LANDesk Software license activation overview

LANDesk Software maintains a central licensing server to help you manage your server's

product license. To use LANDesk products, you must obtain from LANDesk a user name and password that will activate the server with an authorized certificate. Activation is required on

each server before you can use LANDesk products on that server. You can activate each server either automatically by the Internet or manually by e-mail. You may need to reactivate a server in the event that you significantly modify its hardware configuration.

On a periodic basis, the activation component on each server will generate data regarding:

Precise usage information

The non-personal encrypted hardware configuration

The specific LANDesk Software programs you're using

No other data is collected or generated by the activation.

The hardware key code is generated on the server using non-personal hardware configuration factors, such as the size of the hard drive, the processing speed of the computer, and so on. The hardware key code is sent to LANDesk in an encrypted format, and the private key for the

encryption resides only on the server. The hardware key code is then used by LANDesk Software to create a portion of the authorized certificate.

Each time the usage data is generated by the activation software on a server, you need to

send the data to LANDesk Software, either automatically by the Internet or manually by e-mail. If you fail to provide the usage data within a 30-day grace period after the initial usage verification attempt, the server may become inoperative until you provide LANDesk with the data. Once you send the data, LANDesk Software will provide you with an authorized certificate that will allow the server to work normally once again.

Each server must have a unique authorized certificate. Multiple LANDesk servers can't share

the same authorization certificate, though they can verify usage counts to the same LANDesk account.

Periodically, the server generates usage verification information in the "\Program Files\LANDesk\Authorization Files\LANDesk.usage" file. This file is sent periodically to the LANDesk Software licensing server. This file is in XML format and is digitally signed and encrypted. Any changes manually made to this file will invalidate the contents and the next

usage report to the LANDesk Software licensing server.

The server communicates with the LANDesk Software licensing server via HTTP. If you use a proxy server, click the utility's Proxy tab and enter your proxy information. If your server has an Internet connection, communication with the license server is automatic and won't require any intervention.

INSTALLATION GUIDE

28

Note that the license activation utility won't automatically launch a dial-up Internet connection, but if you launch the dial-up connection manually and run the activation utility, the utility can use the dial-up connection to report usage data. If your server doesn't have an Internet connection, you can activate the server and verify usage data manually via e-mail (see See "Manually activating a server and verifying usage data" on page 30).

Licensing options

After installing the server, use the license activation utility to activate it, either with a LANDesk account associated with the licenses you've purchased or with a 45-day evaluation license (on the server, click Start > All Programs > LANDesk Service Management > License

Activation).

NOTE: The activation utility launches automatically if you haven't already activated the server when you

try to log on to the ALM console for the first time.

The 45-day evaluation period begins when you first activate a product on the server. If you

install other LANDesk products for evaluation on the server later in the 45-day period, that doesn't extend the initial 45-day evaluation period. All LANDesk products on a single server share the same evaluation license and the same 45-day evaluation period.

You can switch from a 45-day evaluation to a full-use account license at any time by running the license activation utility and entering your LANDesk Software user name and password.


29

Using the license activation utility

Use the license activation utility to:

Activate a new server with a LANDesk Software account

Activate a new server with a trial-use license

Update an existing account

View your current product licenses

Start the utility by clicking Start > All Programs > LANDesk Service Management > License Activation. The license activation dialog displays.

Viewing your product licenses

To view your current LANDesk Software licenses, click Licenses. The product licensing dialog displays. This dialog provides information about usage verification deadlines, and lists the

software product licenses you've purchased along with their expiration dates.

For more information about LANDesk Software licenses, contact your LANDesk reseller, or visit the LANDesk Web site at the URL provided in the licensing dialog.

INSTALLATION GUIDE

30

Activating a new server with a LANDesk Software account

Before you can activate a new server with a full-use license, you must have an account set up with LANDesk Software that licenses you for the LANDesk Software products you purchased. You will need the account information (contact name and password) to activate your server. If

you don't have this information, contact your LANDesk Software sales representative.

To activate a server

1. Click Start > All Programs > LANDesk Service Management > License Activation.

2. Click Activate this server using your LANDesk contact name and password.

3. Enter the Contact name and Password you want the server to use.

4. Click Activate.

Activating a new server with a trial-use license

The 45-day trial-use license activates your server with the LANDesk Software licensing server. Once the 45-day evaluation period expires, you won't be able to log in to the server, but you won't lose any existing data in the database. During or after the 45-day trial use license, you can rerun the Server Activation utility and switch to a full activation that uses a LANDesk Software account. If the trial-use license has expired, switching to a full-use license will

reactivate the server.

To activate a 45-day evaluation


2. Click Activate this Asset Lifecycle Manager for a 45-day evaluation.

3. Click Activate.

Updating an existing account

To update an existing account, launch the activation utility and enter the new contact name and password. This will change a server from a trial-use license to a full use license.

To update an existing account


2. Click Update this server using your LANDesk contact name and password.

3. Enter the Contact name and Password you want the server to use. If you enter a name and password that's different than the one used to originally activate the server, this switches the server to the new account.

4. Click Activate.

Manually activating a server and verifying usage data

If the server doesn't have an Internet connection, the license activation utility won't be able to send usage data. You'll then see a message prompting you to send activation and usage verification data manually through e-mail. E-mail activation is a simple and quick process. When you see the manual activation message on the server, or if you use the license activation utility and see the manual activation message, follow these steps.


31

To manually activate a server and verify usage data

1. When the server prompts you to manually verify the usage data, it creates a data file in the: \Program Files\LANDesk\Authorization Files folder; or when installed on a

64-bit machine, the files will be saved at \Program Files

(x86)\LANDesk\Authorization files folder. The data file is named with the following

syntax: en-activate.2010-02-14-13-25-56.txt, with your server's language abbreviation, the current date, and a unique number code.) Attach this file to an e-mail message and send it to [email protected]. The message subject and body don't matter.

2. LANDesk Software will process the message attachment and reply to the e-mail address you sent the message from. The LANDesk Software message provides instructions and a new attached authorization file (<servername>.auth).

3. Save the attached authorization file to the: \Program Files\LANDesk\Authorization

Files folder. The server immediately processes the file and updates its activation

status. Then it places the file (either servername.success or servername.rejected) in the: \Program Files\LANDesk\Authorization Files folder.

4. After the authorization file is processed, you must restart your ServiceManagement Web site. To do this, you can either reset the IIS service entirely, or reset the ServiceManagement application under the "Default Web Site" in IIS Manager.

If the manual activation fails or the server can't process the attached activation file, the

authorization file you copied is renamed with a .rejected extension and the activation utility logs an event with more details in the Windows Event Viewer's Application Log.

INSTALLATION GUIDE

32

Configuring required initial settings

Now that you've completed the installation of LANDesk Asset Lifecycle Manager, and activated

the server with a valid LANDesk Software license, you need to configure some initial settings before you can launch the administrator (Design) console and start using the application.


See "Required initial settings" on page 32

See "Configuring initial settings" on page 32

See "Additional settings" on page 36


Required initial settings

The following settings must be defined before you can log on to the Design console:

Messaging: Define SMTP mail server information and a valid e-mail address in order to send notifications during process workflows.

Users/Groups: Define user and group information (for an Active Directory domain) in order to identify users that can be assigned or associated with assets.

Configuring initial settings

LANDesk Asset Lifecycle Manager setup creates a new program group in the Windows Start menu called LANDesk Service Management. This program group contains shortcuts to the

Administrator Console, the Configuration Options tool, and the License Activation utility.

To configure initial settings

1. At the server, click Start > All Programs > LANDesk Service Management > Configuration Options.

2. At the login screen, make sure the server name or (or server IP address) is correct, and then click Login to sign in as the current user. You can also click Sign is as a different user, enter the user name and password, and then click Login.

3. The first time the console is launched, the Settings dialog appears. (NOTE: This dialog can be accessed later from the console; click Tools > Settings.)

4. Click the General tab. Use the options on this tab to configure workflow notification settings. Enter a valid SMTP mail server name (or IP address), and a valid e-mail

address from which messages can be sent. NOTE: The other options on this tab are not required during this initial configuration to be able to log in to the console, although you can specify them now if you like. For

detailed information on the remaining options on the General tab, see "Configuring general settings" in the Designer's Guide.


33

5. (Optional) The Web server URL field is automatically filled in with the server's Web service address. If you've moved the Web server, you can enter the new URL here. You can enter either an IP address or a DNS hostname.

6. (Optional) The Service impersonation user field is automatically filled in with the currently logged-in user. Use this option to specify the user that the LANDesk Service Management service runs as. This is important when the service is trying to access files on different servers for data synchronization, attachments, or certain workflow actions

such as the execute script action. If this field is empty, the service runs by default as Network Service, which can access local files only. If access to files on other machines is necessary, make sure this user has access rights to resources on those servers.

7. (Optional) If you don't want workflow participants who must approve an action or event to be able to specify certain conditions with their approval, check the Hide approve with conditions checkbox. This option controls whether or not approval can include

conditions that must be satisfied before approval is granted and the process workflow

can continue. In other words, when this option is checked, approvers will have only the ability to approve or deny requests that are part of a workflow.

8. (Optional) If you want to require that approvers include comments and a time deadline for a workflow action, check the Require comments and time to complete manual task checkbox.

9. (Optional) If you want to allow Web console users to be able to delete multiple asset

instances at the same time (instead of only one-by-one), check the Allow deletion of multiple assets in the Web console checkbox.

INSTALLATION GUIDE

34

10. Click the Users/Groups tab. Use the options on this tab to enter directory service information needed to contact your organization’s Active Directory users. This information is used to discover and identify users that can be assigned assets.

11. Click Add, select the directory service, and then click OK. IMPORTANT: You must enter information for the currently logged-in user or you will

not be able to log into the console. The machine must be connected to the domain and the currently logged-in user must be an Active Directory domain user.

12. At the Active Directory Settings dialog, enter a display name (any name you want), the domain name, the LDAP path, the user name and password, and then click OK. You should click Test in order to confirm a successful connection to your Active Directory.


35

NOTE: The Active Directory dialog also includes options to configure advanced Active Directory connection information. Very few installations will require the advanced settings to be completed. Contact your LANDesk Professional Services consultant or

LANDesk Support if you have questions about these advanced settings.

13. Click OK to save the settings and close the dialog.

You've now completed configuration of the required initial settings, which is the final step of installing and configuring LANDesk Asset Lifecycle Manager.

INSTALLATION GUIDE

36

Additional settings

In addition to the required initial settings described above, the Configuration Options utility includes the following system settings:

Integration servers: Configure PIMs (Process Integration Modules) including LANDesk Management Suite core server, LANDesk Service Desk, Avocent Mergepoint Infrastructure Explorer (AMIE), BMC Remedy, or a VMWare server, in order to access external data sources.

Barcode: Configure the e-mail address that barcode scanners send messages to.

Roles: Create roles to control user access to the asset and process features in the Web console based on individual responsibilities. (NOTE: This tab is hidden during initial configuration, but is available after you log on to the console for the first time.)

Scopes: Create scopes to control user access to resources in your organization based

on criteria such as geographical location or organizational structure. (NOTE: This tab is hidden during initial configuration, but is available after you log on to the console for the first time.)

All assets: Change the display columns for the All assets data list in the Web console. These display columns are searchable in the Web console.

None of these settings need to be defined during this initial configuration task. You will be able to configure these settings, and change the messaging and user/group settings, at any time in the console (click Tools > Settings). Refer to the "Configuring Settings" section in the Designer's Guide and the online help for detailed information about all of the settings.


37

Starting the console

Congratulations! You've completed the installation, activation, and basic configuration of

LANDesk Asset Lifecycle Manager.

You can now log in to the ALM Design console and begin using this business management tool. You'll be able to perform tasks such as create asset types and supporting resources, design and implement process workflows, design and make forms available to asset managers and regular end users, prepare report views, define lifecycle states, and so on.

To log in to the console

1. At the server, click Start > All Programs > LANDesk Service Management > Administrator Console.

2. Enter your user credentials, and click Login.

LANDesk Asset Lifecycle Manager includes a complete set of user documentation. For information about IT asset and process management concepts, and step-by-step instructions on how to use all of the tools, consult the Designer's Guide and the Asset Manager's Guide, as

well as the online help available from each console.

landesk asset lifecycle manager - download.ivanti.com · track, and manage assets in the context of...

Documents