Script Logic Asset Manager 8 Quick Install Guide

1 | Asset Manager 8 Install Guide

Quick Install Guide

Asset Manager 8.0


© 2011ScriptLogic Corporation ALL RIGHTS RESERVED.

ScriptLogic, the ScriptLogic logo and Point,Click,Done! are trademarks and registered

trademarks of ScriptLogic Corporation in the United States of America and other

countries. All other trademarks and registered trademarks are property of their

respective owners.


Table of Contents

Implementing ScriptLogic Asset Manager ................................................................... 4

ScriptLogic Asset Manager Architecture .................................................................. 4

Default Port Used within Asset Manager System ..................................................... 4

System Requirements .............................................................................................. 5

ScriptLogic Asset Manager Server software requirements ......................................... 5

Small scale environment (less than 500 client PC’s) ................................................... 5

Mid scale environment (from 500 to 5,000 clients) ................................................... 5

Large scale environment (more than 5,000 clients) ................................................... 6

Client software requirements.................................................................................... 6

VMware integration requirements ............................................................................ 6

Browser requirements .............................................................................................. 6

Load on client computers .......................................................................................... 6

Before Installing the ScriptLogic Asset Manager Web Server Software ................... 7

Installation and Initial Configuration ........................................................................... 8

Installing the ScriptLogic Asset Manager Server Software ....................................... 8

Initial Configuration of ScriptLogic Asset Manager ................................................. 9

Installing Asset Manager Client ................................................................................. 15

Launching ScriptLogic Asset Manager Agent with Logon Script ........................... 16

SLAMAgent.msi: LWClient as Offline Agent ....................................................... 16

Service Installation of Asset Manager Agent .......................................................... 17

LWClient Parameters ............................................................................................. 18

Installing the Asset Manager Mac Agent (LWMacClient) ...................................... 18

Index ............................................................................................................................ 20

Implementing ScriptLogic Asset Manager



ScriptLogic Asset Manager Architecture The ScriptLogic Asset Manager software has client-server architecture.

The ScriptLogic Asset Manager Server uses Microsoft IIS Web server with .NET

Framework 3.5 SP1 and requires Microsoft SQL Server (local or remote) for storing all

collected data. Both IIS and .NET Framework 3.5 can be installed and (re)configured

during Asset Manager installation.

Default Port Used within Asset Manager System All communication within the Asset Manager system runs via HTTP / HTTPS. The

design of this protocol allows a customer to use any port, but the default ports are as

follows: HTTP default port: 80

HTTPS default port: 443

Ensure these ports are opened on every AM client computer and AM server.



System Requirements ScriptLogic Asset Manager requires a Microsoft Windows Server host (“ScriptLogic

Asset Manager Server”) and a Microsoft SQL database (“ScriptLogic Asset Manager

Database”).

While the ScriptLogic Asset Manager Server software prerequisites are always the same,

the ScriptLogic Asset Manager Server hardware requirements and ScriptLogic Asset

Manager Database system requirements depend on the environment - number of client

PC’s processed by Asset Manager. We define three types of environments:

Small scale – less than 500 client computers;

Mid scale – 500 to 5.000 client computers;

Large scale – more than 5.000 client computers.

The scale of the environment is important because more clients require more disk storage

and will put a heavier load on the server running ScriptLogic Asset Manager.

ScriptLogic Asset Manager Server software requirements

MS Windows Server 2003 SP 1 or higher (both x64 and x86 Editions)

MS Window Server 2003 R2 (both x64 and x86 Editions)

MS Windows Server 2008

MS Windows Server 2008 R2

Adobe Reader to view the Asset Manager guides

Small scale environment (less than 500 client PC’s) ScriptLogic Asset Manager Server hardware

2.0 GHz AMD/Intel CPU or higher

1 GB RAM or more (2 GB is recommended)

500 MB free disk space for installation of .NET and ScriptLogic Asset Manager server

Database server for data storage

Can be installed locally or via a remote server

Microsoft SQL Server 2005/2008 Express Edition

2005 Express Edition SP3 installer can be found within the ScriptLogic Asset Manager installation package or can be downloaded from www.microsoft.com. Please note that this edition is free and has a limit of 4 GB data storage.

Free disk space for data storage (the ScriptLogic Asset Manager database)

2 MB for each client is recommended (e.g. 500 clients = 1 GB)

Mid scale environment (from 500 to 5,000 clients) ScriptLogic Asset Manager Server hardware

3.0 GHz AMD/Intel CPU or higher

2 GB RAM or more (3 GB is recommended)

500 MB free disk space for installation of .NET and the ScriptLogic Asset Manager server


Can be installed locally or remotely

Microsoft SQL Server 2005/2008 Standard Edition


2 MB for each client is recommended (e.g. 5.000 clients = 10 GB)

http://www.microsoft.com/



Large scale environment (more than 5,000 clients) ScriptLogic Asset Manager server

3.0 GHz dual AMD/Intel CPU or higher

4 GB RAM

500 MB free disk space for installation of .NET and the ScriptLogic Asset Manager server


Should be a remote and dedicated SQL database server.

Microsoft SQL Server 2005/2008 Standard/Enterprise Edition


2 MB for each client PC is recommended (e.g. 10.000 clients = 20 GB)

Client software requirements The ScriptLogic Asset Manager Client can be installed on computers or virtual machines

running the following operating systems:

Microsoft

Microsoft Windows Server 2008/2008 R2

Microsoft Windows Server 2003

Microsoft Windows Server 2003 R2

Microsoft Windows XP

Microsoft Windows Vista

Microsoft Windows 7

Apple

Mac OS X Leopard (version 10.5)

Max OS X Snow Leopard (version 10.6)

VMware integration requirements You can choose to implement integration with VMware. ScriptLogic Asset Manager can

communicate with the following VMware products:

ESX 3.5 and 4.0

ESXi3.5 and 4.0

vCenter 3.5 and 4.0

Browser requirements The ScriptLogic Asset Manager Administration portal can be accessed and configured via

the following browsers:

Internet Explorer 7.0 and above

Load on client computers When the ScriptLogic Asset Manager system is installed, it is necessary to have an agent

program running on the clients. The size of the agent is 200 KB. It collects data and

transfers it to the ScriptLogic Asset Manager system. When this agent (the LWClient.exe

process) is running, it will use approximately 7 – 8 MB of RAM.

When the client computer logs on to the network, the agent starts collecting data (with an

adjustable delay before any scans are started). The list of installed software can, for

example, be scanned at every log on and in just a few seconds be available in the



ScriptLogic Asset Manager system. Hardware and file scans can be set up in the same

way (every login, daily, monthly, etc.).

Before Installing the ScriptLogic Asset Manager Web Server Software When installing the ScriptLogic Asset Manager it is necessary to:

1. Log on the ScriptLogic Asset Manager server as a system administrator in order to install the software and perform its configuration.

2. If using an external MS SQL database server, log on as administrator to

the database server and create the database and users for the Asset Manager system. The ScriptLogic Asset Manager system can create its database by itself if the username and password is known for an “SQL Authentication user” inside the MS SQL server or an Active Directory (AD) user on the network that is added to the MS SQL server with the necessary rights for creating databases.

3. Make ScriptLogic Asset Manager agent start automatically on the clients. This is usually done with the users’ login script. An administrator with knowledge of the company’s login scripts is needed for applying the ScriptLogic Asset Manager command to the login script.


Installation and Initial Configuration To start using ScriptLogic Asset Manager, you have to:

1. install ScriptLogic Asset Manager server software; 2. perform ScriptLogic Asset Manager server initial configuration (done via Asset Manager

Configuration); 3. The database must be installed or the ScriptLogic Asset Manager must be configured to

use an existing database. 4. launch the Asset Manager agent on client PC’s.

Normally, you will be prompted to perform steps 1 through 3 during the unified process

of Asset Manager installation and initial configuration.

Be sure to install ScriptLogic Asset Manager on a system that meets the necessary

requirements.

Installing the ScriptLogic Asset Manager Server Software

During Asset Manager installation, the Command

Prompt window will open to show the Asset Manager messages.

Step 1 Start installation and automatic configuration.

Log on to the server as a system administrator, unzip the ScriptLogic Asset Manager archive, and execute the Setup.bat file.

(For Windows 2008), the installation needs to run with Elevated permissions (right-click the setup file and start installation by running the file as Administrator).

The installer will automatically begin to extract the necessary files and tune your server settings and configure Internet Information

Services.

Step 2 (If asked) Reboot the server, and then restart the installation.

Upon completing the IIS server configuration, reboot the server when asked, and then restart the installation file. The ScriptLogic

Asset Manager Setup wizard will open. Click Next to continue.

Installation and Configuration


Step 3 Install pre-requisite components.

Follow the wizard's prompts to proceed with the setup and install

the following components (if they are not already installed on your server):

.Net Framework 3.5 SP1,

Microsoft Visual Studio 2010 Report Viewer,

Microsoft SQL Server System CLR Types (x86),

Microsoft SQL Server 2008 Management Objects (x86).

Step 4 Proceed to install ScriptLogic Asset Manager Server.

Click Next to start the installation of ScriptLogic Asset Manager

Server.

After accepting the license agreement, use either the default, %PROGRAMFILES%\ScriptLogic Corporation\ScriptLogic Asset

Manager or %PROGRAMFILES(x86)%\ScriptLogic

Corporation\ScriptLogic Asset Manager, location or choose

another location for the ScriptLogic Asset Manager Server software.

Select whether or not other users (on this server) may access the ScriptLogic Asset Manager software (“Everyone” or “Just me“). Click Next to continue the installation.

Step 5 Exit the wizard.

When the software has been successfully installed, click Close to exit the setup and proceed to configure the software via the Asset Manager Configuration wizard that will start automatically. (For the next steps, see Initial Configuration of ScriptLogic Asset Manager)

Now your ScriptLogic Asset Manager Server is installed and requires initial

configuration to adjust Asset Manager to your needs.

Initial Configuration of ScriptLogic Asset Manager After the Asset Manager installation, the ScriptLogic Asset Manager Configuration

wizard will start automatically to help you perform some initial configurations of Asset

Manager: setup the Asset Manager database or instruct ScriptLogic Asset Manager to use

an existing one, launch the Asset Management agent on the computers on your domain,

and etc.

Step 1 (If required) Start the Asset Manager Configuration wizard.

(Log on to the server as a system administrator, if necessary.) Click Start All Programs ScriptLogic Corporation -> ScriptLogic Asset Manager Asset Manager Configuration.

(For Windows Server 2008) Launch the wizard by clicking the Asset Manager Configuration shortcut within the Start menu.



Step 2 Provide the license key.

Enter a valid ScriptLogic Asset Manager license key in the License

key field of the Asset Manager Configuration wizard.

Step 3 Select the type of configuration to perform.

Express Configuration helps set up all the necessary components to ensure functioning of the basic features of ScriptLogic Asset Manager:

setup a database;

setup synchronization with Active Directory

enable default hardware and file scans

enable Software Patterns Identification Service to send/receive data to an external web service for the purposes of quick software metering.

With Advanced Configuration you proceed to the Asset Manager Configuration console detailed in the Asset Manager Installation Guide. The Advanced Configuration allows you to configure all components of the Express Configuration plus all other system services: integration with SMS/SCCM, Citrix, and VMware systems, deploying Asset Manager in a multi-domain environment, etc.

While in the Asset Manager Configuration console, to return back to the Asset Manager Configuration wizard, click the Wizard button in the bottom of the Configuration Console screen.

Step 4 Specify/install the database.



Select between the available options to install SQL Server 2005 Express version database or instruct Asset Manager to connect to an existing database. (Consult the System Requirements section to

help you decide what option to choose.)

When installing or creating an AM database, ensure

that the user account specified is granted the DBCREATOR server role.

Choose Install Local SQL Server (SQL Server 2005 Express

SP3) max. database size 4 GB to install and use a local database instance. If the Asset Manager Server doesn’t have MS SQL 2005 Express SP3 installed, this option will install SQL Server 2005 Express SP 3 locally on the Asset Manager server.

Please note that this database can fit only small-scale environments (see Small scale environment system requirements (less than 500 client PC’s)).

1. Set the values within the dialog fields as necessary to:

enable/disable Network Protocols;

change the database instance name and installation directory;

SQL server authentication mode; (If Use Windows Authentication Security Mode is set to False) Within the Security section, specify

the Sysadmin Password for the “sa” user. It is recommended to use a strong password (at least 6 characters long and containing a-z, A-Z, 0-9).

2. Click Install to install and configure the database. It may take a moment to install.

3. When the installation has been completed successfully, click OK.

Choose Use existing database server if you would like Asset Manager to use an instance of SQL Server already installed on your network.

1. Choose a database instance that is available on your network or computer.

2. Set the authentication type supported by your SQL Server. 3. You may change the database instance name ( “SLAM” by default) used

to store ScriptLogic Asset Manager data. 4. Setup will create a database with the selected instance name on the target

database server.

If you encounter any problems setting up the database for the Asset Manager, please refer to the Using the Database Tab chapter of the Asset Manager Installation Guide.

Click Next to continue.

Step 5 Provide the service account.



Provide the Service account for background services that will run on the Asset Manager server. This account should be:

1. A local admin on the Asset Manager server

2. Should have Database Administrator (dbo) role on the Asset Manager database

3. (if planning to use Asset Manager Citrix Connector) local admin on the Citrix server)

If the Asset Manager server uses the proxy server to connect to the Internet, check in the Use proxy server check box and then specify the proxy server address and port in the fields that will show.

Step 6 (Optional) Connect to Active Directory.

1. Select the Use Active Directory checkbox to connect to Active Directory and automatically import user names and available organizational units from the Active Directory service. This operation may be performed at a later time if necessary (see Asset Manager Administration Guide).

2. Enter the credentials of the Active Directory user account with at least read access to the Active Directory via LDAP. Use the following syntax to specify the user name: User1@domain1.

3. In the Domain field, the ADSI root path is detected for you automatically.

Step 7 Accept configuration settings and start using the program.

Wait for the wizard to apply configuration, and then click Finish to exit the wizard. The ScriptLogic Asset Manager Administration Console will start automatically.

(For Windows Server 2003 that connects to a remote AM database) If you receive an error shown on figure below, you have to update the Service account (see Step 5) to access Active Directory. To achieve this, perform the requested steps. Contact your system administrator if necessary.



1. On your domain controller, install Windows Support Tools

for the operating system your domain controller is running (you can find the installer on the Windows Installation CD)

2. Run SUPTOOLS.MSI (eg. <CD>:\SUPPORT\TOOLS\SUPTOOLS.MSI)

3. Open Command Window to run successively the following

commands:

cd “c:\Program Files\Support Tools”

Setspn.exe –A HTTP/<Servername> <Full Domain\Accountname>

Setspn.exe –A HTTP/<Servername.Domain.com> <Full Domain\Accountname>

Replace <Servername> and <Servername.Domain.com> with the actual name of your AM server in the required format.

Replace <Accountname> with the actual account name of the Service account.

4. Restart both Asset Manger-specific application pools (SLAMAppPoolSLAM and SLAMAppPoolSLAMClientRequestHandler)

Now you are done with basic Asset Manager configuration during which:

1. The Asset Manager web server has been setup and configured to ensure proper work of the Asset Manager Web Console.

2. The Asset Manager database has been installed.



3. (If requested during setup) connection to the Active Directory service has been established to build the default Segment group, called AD, that will display your Active Directory structure of organizational units and to add your Active Directory users into the Users section of the Asset Manager Web Console (see Asset Manager Administration Guide for details).

4. The Software Patterns Identification Service has been enabled to send/receive data to an external Asset Manager software identification web service to start the software metering of your environment in no time (see Asset Manager Administration Guide for details).

5. The 2 software scan rules (Program Files and Program Files (x86)) have been created and run (see Asset Manager Administration Guide for details).

What’s next: Launch the Asset Manger Agent on the Windows PC’s on your network to

collect data from them (see Launching ScriptLogic Asset Manager Agent with Login Script for reference).

(If necessary) Install the Asset Manger Mac Agent on every Apple Mac

device to collect data from them (see Installing the Asset Manager Mac Agent (LWMacClient) for reference).

Refer to the the Asset Manager Installation Guide for further Asset Manager tuning: to implement integration with SMS/SCCM system,

to implement integration with Citrix system,

to implement integration with VMware system,

to deploy Asset Manager in a multi-domain environment, etc.



Installing Asset Manager Client The ScriptLogic Asset Manager Agent (LWClient.exe) is the special ScriptLogic Asset

Manager agent that runs on each client PC and delivers all the necessary data to the Asset

Manager system. For systems running MAC OS, there is a LWMacClient that is a

modification of the LWClient. The LWMacClient is almost the full substitute for the

LWClient running on Windows OS's. The agent performs the following tasks: scanning

PC’s for software, hardware, files, and WMI (Windows Management Instrumentation).

Furthermore, the agent can perform actions such as blocking the execution of unwanted

applications, limiting the execution of unwanted applications, or notifying the

ScriptLogic Asset Manager system, when specific applications are executed.

The LWClient agent is small (about 200 KB) and therefore quick to start up both the first

time and the following times on the client PC's. The matrix below shows the some

functionality differences between the LWClient versus the LWMacClient.

Functionality LWClient LWMacClient

Software scan/identification from ”Add and

remove Programs”

Hardware scan from WMI

Detailed software identification from WMI

Data from Mac

System Profiler is

used.

File scan – (files can be used for software

identification)

Blocked files – (prevent unwanted application

start-up)

Passive metering – (historical usage of

software)

Active metering – (real time usage of software

+ limitation of concurrent usage of software) N/A

“Offline metering” -

“Offline launch of agent – (useful for VPN

users)

The Asset Manager Client can be installed in the following way:

Windows-based: Launching ScriptLogic Asset Manager Agent with Logon Script

SLAMAgent.msi: LWClient as Offline Agent

Service installation of Asset Manager Agent

Apple-based Installing the Asset Manager Mac Agent (LWMacClient)



Launching ScriptLogic Asset Manager Agent with Logon Script The ScriptLogic Asset Manager agent is launched with a start-up command added to the

logon script of the users. The ScriptLogic Asset Manager start-up command consists of

two parts: an executable file and a path to the website resource.

The ScriptLogic Asset Manager start-up command will look similar to this: \\AM-S1\SLAMClient\LWPreloader.exe http://AM-

S1/SLAMClientRequestHandler

\\AM-S1\SLAMClient is the server name and share where the client files

are located. By default it will be the location where the ScriptLogic Asset Manager Server is installed (C:\Program Files\ScriptLogic Corporation\ScriptLogic Asset Manager\Client or C:\Program

Files (x86)\ScriptLogic Corporation\ScriptLogic Asset

Manager\Client).

LWPreloader.exe copies/upgrades the client files to the client PC and

starts the LWClient.exe, which is the actual ScriptLogic Asset Manager agent.

AM-S1/SLAMClientRequestHandler is a website serving as gateway

between the ScriptLogic Asset Manager Server and the client PC’s.

The login script method has the following advantages and disadvantages:

Advantages:

It starts automatically, and the agent (LWClient) is automatically updated.

Disadvantages:

It cannot start offline. In other words, no login script means no start-up of agent. Instead,

it is possible to use the SLAMAgent.msi that will install the LWClient and start up

without login script; please refer to the following section LWAgent.msi: SLAMClient as

Offline Agent.

SLAMAgent.msi: LWClient as Offline Agent Apart from the client files (by default located on the ScriptLogic Asset Manager Server

share %ProgramFiles%\ScriptLogic Corporation\ScriptLogic Asset

Manager\Client or %Program Files (x86)%\ScriptLogic

Corporation\ScriptLogic Asset Manager\Client), there is also a file

named SLAMAgent.msi. If this file is installed on the client PC’s, the ScriptLogic

Asset Manager start-up command is added to the Windows Registry, and the client can

then start up without login script and connection to the ScriptLogic Asset Manager

Server. This is useful for mobile users using laptops and seldom being directly connected

to the local network where the ScriptLogic Asset Manager Server is installed. When

mobile users open for instance a VPN connection (Virtual Private Network) this client

will begin transmitting all the data it has collected while the mobile user was offline.

The SLAMAgent.msi method has the following advantages and disadvantages:

Advantages:

It can start offline (useful for mobile VPN user being 'out in the field').

Disadvantages:

It must be installed manually and requires local administrative rights for installation. The

LWClient is not updated automatically as no login script and LWPreloader are executed.

http://am-s1/SLAMClientRequestHandler

http://am-s1/SLAMClientRequestHandler



The LWPreloader handles copying and updating LWClient. The LWPreloader cannot

start without being connected to the ScriptLogic Asset Manager Server.

Service Installation of Asset Manager Agent The SLAMAgentService.msi is a service installation which runs the LWClient at a

scheduled time. The SLAMAgentService.msi is used for server installations because

the normal LWClient needs a user login.

The SLAMAgentService.msi is required to run the Software scans, Hardware scans

and File scans but not the Metering and Blocked files functionalities.

The SLAMAgentService.msi is placed in the MSI folder on the Asset Manager server

and can be copied to the server for being executed. (By default, the file is located in %Program Files%\ScriptLogic Corporation\ScriptLogic Asset

Manager\MSI or %Program Files (x86)%\ScriptLogic

Corporation\ScriptLogic Asset Manager\MSI)

To run the service installation of the Asset Manager Agent:

On Microsoft Vista and Server 2008 and higher

versions it might be necessary to run the program as Administrator.

1. Double-click the SLAMAgentService.msi file to start the installation wizard.

2. When the wizard Welcome screen opens, click Next to proceed with the installation. 3. Check the box to indicate if the Service has to update automatically when a new Asset

Manager version is installed on the Asset Manager Server. The box is checked for using the LWpreloader by default.

4. Set time for starting the LWpreloader.exe/LWClient.exe. Default is 01:00. 5. Click Next. 6. Accept the default folder or use the Change button to enter a new path. 7. Click Next. 8. Click Install to start the installation. 9. Click Finish to end the installation.

After the installation of the SLAMAgentService.msi process, the service starts

scanning immediately. Afterwards the SLAMAgentService.msi process starts as

scheduled.

To ensure the running of SLAMAgentService check the Task Manager in Windows.

It is possible to start the SLAMAgentService.msi in silent mode. The construction of

the string can be created this way: msiexec /i “SLAMAgentService” /passive

Because of the UAC security on Microsoft Vista and

Windows Server 2008 and versions above, it is only possible to run the silent installer in passive mode.



LWClient Parameters The LWClient can be started with different parameters.

To add a parameter, do as follows:

With no parameters specified, the ScriptLogic Asset Manager start-up command looks

like this: \\AM-S1\SLAMClient\LWPreloader.exe AM-

S1/SLAMClientRequestHandler

A parameter can be added to the command, for example -D, and then it will look like this: \\AM-S1\SLAMClient\LWPreloader.exe AM-

S1/SLAMClientRequestHandler -D

Here is a list of available parameters:

Parameter Hostname in

ScriptLogic Asset

Manager Example Comment

(Nothing) Ordinal case -S Can be used on Servers. Will only run Login tasks and Scheduled

task one time and then the LWClient will stop running. -D Use for debugging. Create a log-file in %temp% folder

Installing the Asset Manager Mac Agent (LWMacClient) To get the wanted data from Apple Mac devices into the Asset Manager system, an Asset

Manager Mac agent (LWMacClient) is required on each Mac devices. The tasks of the

agent include for instance scanning of the PC for software, hardware, files. Furthermore,

the LWMacClient can also perform actions such as blocking the execution of unwanted

applications, or notifying the Asset Manager system when specific applications are

executed (Metering).

The installation file for the LWMacClient is found in the folder on the LicenseWatch

server as a zip file –(\\<servername>\AssetManagerServer\MSI\LWMacClient.zip).

1. The administrator has to e-mail the LWMacClient.zip file to all involved clients including a description of how to unzip the file. The client downloads the LWMacClient.zip file to a certain place on the computer. Unzip the file by double clicking the LWMacClient.zip file. The unzipped file LWMacClient has to be copied into the Applications folder on the Apple Mac computer. Run the LWMacClient file by double clicking the file. The LWMacClient icon will expand very quickly but nothing more.

From now on the LWMacClient starts automatically when the Apple Mac computer is

turned on. During the start up sequence an icon of an eye shortly bounces on the task bar.

It is possible to monitor the LWMacClient process running on the Mac computer by

entering the utility Activity Monitor on the Mac computer.

LWMacClient Parameters

The LWMacClient can be started with different parameters.

Here is a list of available parameters:

Parameter Example/explanation

(Nothing) Normal case

-tcp_nodelay (disable “delayed ACK”)



-d Only for debug. A debug log file

(LWClientlog-<user name> can be found in

“tmp” folder for the current user (CD

/tmp).

Example for start the LWMacClient in a Mac Terminal window: ./LWMacClient http://<AMSERVER>/LWClientRequestHandler

Replace the <AMSERVER> with the fully qualified domain name of the Asset Manager

server, e.g. AMserver.domain.com

Index


Index

A

Asset Manager Configuration · 9

L

Launching ScriptLogic Asset Manager Agent · 16 LWClient Parameters · 18 LWClient.exe · 15 LWMacClient · 18

LWPreloader.exe · 16

M

MAC Client · 15

O

Offline Agent · 16

S

ScriptLogic Asset Manager Agent · See LWClient.exe ScriptLogic Asset Manager Architecture · 4 ScriptLogic Asset Manager license key · 10 SLAMAgent.msi · See Offline Agent

SLAMClientRequestHandler · 16

Start-up command · 16 System Requirements · 5

Documents

Script Logic Asset Manager 8 Quick Install Guide