Third Party Trademarks

All other brand names, product names or trademarks belong to their respective holders.
Third Party Software Program Credits
ACIS Copyright 1989-2001 Spatial Corp. Portions Copyright 2002 Autodesk, Inc. AnswerWorks 4.0 1997-2003 WexTech Systems, Inc. Portions of this software Vantage-Knexys. All rights reserved. Copyright 1997 Microsoft Corporation. All rights reserved. Copyright 1988-1997 Sam Leffler. Copyright 1991-1997 Silicon Graphics, Inc. AutoCAD 2007 and AutoCAD LT 2007 are produced under a license of data derived from DIC Color Guide from Dainippon Ink and Chemicals, Inc. Copyright Dainippon Ink and Chemicals, Inc. All rights reserved. DIC and DIC Color Guide are registered trademarks of Dainippon Ink and Chemicals, Inc. International CorrectSpell Spelling Correction System 1995 by Lernout & Hauspie Speech Products, N.V. All rights reserved. InstallShield 3.0. Copyright 1997 InstallShield Software Corporation. All rights reserved. Macromedia and Flash are registered trademarks or trademarks of Adobe Systems Incorporated in the United States or other countries. PANTONE Colors displayed in the software application or in the user documentation may not match PANTONE-identified standards. Consult current PANTONE Color Publications for accurate color. PANTONE and other Pantone, Inc. trademarks are the property of Pantone, Inc. Pantone, Inc., 2002
Pantone, Inc. is the copyright owner of color data and/or software which are licensed to Autodesk, Inc., to distribute for use only in combination with certain Autodesk software products. PANTONE Color Data and/or Software shall not be copied onto another disk or into memory unless as part of the execution of this Autodesk software product. Portions Copyright 1991-1996 Arthur D. Applegate. All rights reserved. Portions of this software are based on the work of the Independent JPEG Group. RAL DESIGN RAL, Sankt Augustin, 2002 RAL CLASSIC RAL, Sankt Augustin, 2002 Representation of the RAL Colors is done with the approval of RAL Deutsches Institut fr Gtesicherung und Kennzeichnung e.V. (RAL German Institute for Quality Assurance and Certification, re. Assoc.), D-53757 Sankt Augustin. Typefaces from the Bitstream typeface library copyright 1992. Typefaces from Payne Loving Trust 1996. All rights reserved. Printed manual and help produced with Idiom WorldServer.

GOVERNMENT USE

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212 (Commercial Computer Software-Restricted Rights) and DFAR 227.7202 (Rights in Technical Data and Computer Software), as applicable.

Contents

Chapter 1
Quick Start to SAMreport-Lite. 1
How to Obtain a License File. How to Install Java Runtime Environment. How to Install SAMreport-Lite. How to Create and Set Up an Options File. How to Use SAMreport-Lite. How to Upgrade to SAMreport.2.2.3.3.4.5

Chapter 2

Introduction. 7
Intended Audience. About This Manual. What is License Management?. What is SAMreport-Lite ?.8.8.8.9

Chapter 3

Basics of Generating a Report. 11
Generate a Usage Summary Report. 12

Chapter 4

Usage Summary Report. 15
Usage Summary Report Output. 16 Output Arrangement and Detail. 18

Chapter 5

Report Input and Output. 21
Specifying Input Report Logs. Displaying Output to the Viewer Window. Navigating the SAMreport-Lite Viewer Window. Selecting Output Type and Output File Names. Output Formats. Format Specification:. Data Filters. Reports and Time Zones. Setting Start and End Dates for a Report.
. 22. 22. 22. 23. 24. 24. 25. 25. 26
Appendix A Enabling and Managing Report Logs. 27
How to Turn on a Report Log. Size of the Report Log. Flushing Data to a Report Log. Managing Report Logs. Finding the Version of the Vendor Daemon and lmswitchr. Rotating a Report Log with lmswitchr. Avoiding Corruption in Report Logs. 28. 29. 29. 29

. 30. 31. 31

Appendix B SAMreport-Lite Error Messages. 33
Runtime Error Messages. 34

Index. 37

vi | Contents
Quick Start to SAMreport-Lite

In this chapter

How to Obtain a License
This section gives you step-by-step instructions for installing SAMreport-Lite on your system. If you have any questions that are not addressed in this Quick Start section, consult the appropriate sections in this User's Guide.

How to Install Java

Runtime Environment

How to Install

SAMreport-Lite

How to Create and Set

Up an Options File

How to Use

How to Upgrade to

SAMreport

How to Obtain a License File
Before you install SAMreport-Lite, you must obtain a license file. SAMreport-Lite runs on any computer, but it can read only the report logs from the license server(s) where you obtain a license file. You will be asked for the location of this file during installation. To obtain a license file 1 On the server where you plan to manage licenses and report on them, click Start menu All Programs (or Programs) Autodesk Network License Manager LMTOOLS. 2 In LMTOOLS, click the System Settings tab. 3 Record the host ID, which is located in the Ethernet Address field. NOTE If your server has more than one Ethernet adapter, select one that corresponds to a physical network adapter. 4 Exit lmtools.exe. 5 Next, you need to request a license file from Macrovision Corporation. On the Internet, go to the following website: http://autodesk.globes.com 6 Follow the online instructions for requesting a license file. 7 After completing the online request for the license file, you will receive an email that contains the license information. Copy and paste the license information from the email into a text editor. Save the file with an extension of.lic or.dat. Make sure you note where you saved the file and what you named it. You will be prompted for the location of the license file during the SAMreport-Lite installation.

How to Install Java Runtime Environment
SAMreport-Lite requires Java Runtime Environment 1.4.2_04. To install Java Runtime Environment 1 Insert the Autodesk product CD into your CD-ROM drive. 2 On the Media Browser, click the Install tab. 3 Click Network Deployment.
2 | Chapter 1 Quick Start to SAMreport-Lite
4 On the Network Deployment tab, under Install Supplemental Tools, click SAMreport-Lite 3.4. 5 Click Install JRE 1.4.2, and follow the on-screen instructions.
How to Install SAMreport-Lite
To install SAMreport-Lite 1 Insert the Autodesk product CD into your CD-ROM drive. 2 On the Media Browser, click the Install tab. 3 Click Network Deployment. 4 On the Network Deployment tab, under Install Supplemental Tools, click SAMreport-Lite 3.4. 5 Click Install, and follow the on-screen instructions. NOTE During installation of SAMreport-Lite, you will be asked for the location of your license file. If you do not have a license file, follow the procedures in How to Obtain a License File on page 2 to obtain one.
How to Create and Set Up an Options File
To use SAMreport-Lite, you must configure your license server(s) to generate report logs. In the Network License Manager, you set up an Options file to enable SAMreport-Lite to create report logs. NOTE Complete instructions for setting up an Options file are located in the Autodesk Network Licensing Guide. You can access the guide from your product's Media Browser or in the Help system. To create and set up an Options file 1 In a text editor, create a file called adskflex.opt. 2 In the adskflex.opt file, enter the following syntax on a single line:
REPORTLOG [+] report_log_path REPORTLOG must be uppercase, as shown.
In the REPORTLOG syntax, [+] means that entries to the log file you create are appended rather than replaced each time the Network License
How to Install SAMreport-Lite | 3
Manager is restarted. (It is recommended that you use this option so that you retain a history of log entries.) Path names that contain spaces must be enclosed in quotation marks. For example, the syntax REPORTLOG + c:\My Documents\report.rl means that a report log named report.rl is located in the folder c:\My Documents. 3 Save the adskflex.opt file to the same location where your license file exists. 4 Stop and then restart the Network License Manager.

How to Use SAMreport-Lite
To use SAMreport-Lite to generate a report 1 Click Start menu (Windows) All Programs (or Programs) SAMreport SAMreport. 2 In the SAMreport-Lite window, click the Browse button. 3 In the Report Log dialog box, locate and specify your report log file. By default, the Report Log dialog box lists only files named with a.rl file name extension. If your report log file has a different extension, such as.log, open the Files of Type list and select All Files to list all the files. 4 In the SAMreport-Lite window, in the Output File box, specify the folder location and file name for your report output files. You do not need to specify the file name extension; the extension is automatically added to the name you supply based on the output formats you select. For example, if you select HTML and Text output formats and specify c:\my documents\report in Output File, the following report files are generated: c:\my documents\report.html c:\my documents\report.txt NOTE Be sure to specify the full path name for your output files. If you don't, output files are written to the current working directory, which may be the Windows desktop. Specifying a full path name ensures that your report files are saved in the folder you choose. 5 On the Report menu, click Generate. 6 The report you specified is generated.
4 | Chapter 1 Quick Start to SAMreport-Lite
For more information about generating reports, see Basics of Generating a Report on page 11 and Usage Summary Report on page 15.
How to Upgrade to SAMreport
The full-featured SAMreport product provides additional types of reports and options, and includes additional features such as command line batch processing. Upgrading to the full version of SAMreport does not require a new installation, just a new license file. To learn about the full-featured version of SAMreport, go to the Macrovision Corporation website at: www.macrovision.com
How to Upgrade to SAMreport | 5

Introduction

Intended Audience About This Manual What is License
This chapter contains introductory information about license management, a description of SAMreport-Lite and explanatory information about this guide.

Management?

What is SAMreport-Lite

Intended Audience

SAMreport-Lite and this manual are intended for use by system administrators, system analysts, and managers who use FLEXlm license management to produce usage reports for your software.

About This Manual

This manual is divided into five chapters and two appendixes: Quick Start to SAMreport-Lite on page 1 provides quick instructions for installing and using SAMreport-Lite. This chapter defines license management and introduces SAMreport-Lite. Basics of Generating a Report on page 11 contains instructions for generating a Usage Summary report from the SAMreport-Lite interface. Usage Summary Report on page 15 describes the Usage Summary report, and describes how to arrange report output. Report Input and Output on page 21 shows how to specify input files and describes output formats. Enabling and Managing Report Logs on page 27 provides guidelines for enabling and managing report logs. SAMreport-Lite Error Messages on page 33 lists some errors that you might get while running SAMreport-Lite.
What is License Management?
License management is a set of technologies that monitors the use of software. In some cases, it may also limit use of a product or record usage of a product. Most software companies have legal agreements that detail the obligations of the manufacturer and user to each other. These agreements are often referred to as licenses. Some companies also include license management technology to simplify the legal use of their products. Throughout this documentation, the term license refers to a token obtained through some electronic technology, not the legal agreement between a customer and a software vendor. License management is embedded into a software product by the software vendor.
8 | Chapter 2 Introduction

What is SAMreport-Lite ?

SAMreport-Lite, a member of the GLOBEtrotter family of Software Asset Management (SAM) Solutions, is a report generator that helps you monitor the usage of applications that use FLEXlm. SAMreport-Lite complements FLEXlm by providing a graphical user interface (GUI) from which to run usage reports. SAMreport-Lite can help you make better decisions about your software assets. SAMreport-Lite generates reports based on the license usage activity recorded in FLEXlm report logs. FLEXlm report logs are produced by vendor daemons and maintain a record of the activity of the vendor daemon. Enabling and Managing Report Logs on page 27 describes how to start and manage report log files. The SAMreport-Lite report generator comes with a predefined report type, which allows you to quickly start generating reports. The report summarizes data from your report logs into categories. SAMreport-Lite processes the data from one or more report log files and writes the results to a file and/or displays results on the screen. The Usage Summary report produces a textual output that summarizes the usage statistics of each feature. The output of this report can be saved to files in text, HTML, or Report Interchange Format (RIF). RIF can be used to export report data to another software program, such as a spreadsheet.

What is SAMreport-Lite ? | 9
Basics of Generating a Report

Generate a Usage

This chapter shows you how to generate a Usage Summary report using the SAMreport-Lite user interface. You'll find a detailed explanation of the report in Usage Summary Report on page 15.

Summary Report

Generate a Usage Summary Report
Using SAMreport-Lite you can generate a network license-usage report, called Usage Summary, for Autodesk software that uses FLEXlm licensing technology. To generate a Usage Summary report from the SAMreport-Lite interface 1 Start SAMreport-Lite. 2 Select Usage Summary from the Report Type list. 3 Specify one or more report log files. 4 Using one of the following two methods, specify the location of each of the report logs you want to run with SAMreport-Lite. Type the path to the report log in the text field to the right of the Browse button. Press Enter. Repeat this process for each report log that you want to add. Click the Browse button and use the report log file browser to select a report log from your system. Double-click the report log file. You can repeat this process to select more than one report log from the browser. After you select a report log, the report log file name appears in the text box above the Remove button. To remove a report log from the list, click to highlight the report log, then click the Remove button. There is no fixed limit on the size of a report log that you run through SAMreport-Lite, but the execution time of a report is proportional to the amount of report log data that is processed. 5 Specify an output format and/or an output file name base. A Usage Summary report is displayed on the screen from a file. Therefore, if you want to display a Usage Summary report on the screen, you must specify an output file format and output file name base. Unavailable output formats are grayed out. All reports written to files require an output file name base and at least one output format selection. The file name base can be entered using one of two methods: Type the path and file name base in the text field to the right of the Output File button. If no path is specified, the files are written to the current working directory.
12 | Chapter 3 Basics of Generating a Report

Click the Output File button to open a file selection browser. Find and double-click the directory in which you want to save the output file. Type the file name base in the file selection browser. Click the Save button. NOTE Do not type a file extension (such as.txt). SAMreport-Lite adds the appropriate file extension based on the file type that you chose. 6 Specify how you want the report data summarized and arranged. 7 Specify the start and end dates for the report output. Use these fields to limit the date range of data to include in a report. To include data from the entire report log(s) in your report, leave these fields blank. See Setting Start and End Dates for a Report on page 26. 8 Select Report Generate or click the Generate Report button. A SAMreport-Lite Viewer window will appear and the report progress indicator moves from 0-100% as the report runs. Status messages, including any errors that occurred during report processing, are written in the Status History pane. You should see a status message indicating whether a report was produced. Even if a report was generated, there may be warnings or errors that are displayed here. If you want to stop generating a report, click the Stop button on the toolbar or select Report Stop. After a report is generated, the SAMreport-Lite Viewer window contains one or more pages of the report output.
Generate a Usage Summary Report | 13

Usage Summary Report

Usage Summary Report
A Usage Summary report produces textual output that summarizes the usage statistics of each feature in the report log(s).

Output

Output Arrangement and

Detail

Usage Summary Report Output
The output of a Usage Summary report can be saved to files in HTML, text, or RIF format. The header of a Usage Summary report provides a summary of information about the report log and the parameters of the report: FLEXIm License Usage Report date time Produced by SAMreport-Lite
Input Report Log: Output File Name: Report Log(s) Start: Report Log(s) End: Report Start Date: Report End Date: Uptime: Vendor: Breakdown by: Filter Start Date: Filter End Date: Event Filters: Time Period Filters: Features With Usage:

Version

List of input report log(s) Name of report output file Earliest start date in any report log Latest end date in any report log Date to begin reporteither a filter start date or the starting date of the earliest report log Date to end the reporteither a filter end date or the ending date of the latest report log Duration in real clock time between the report start and end dates that a license server was up Vendor daemon name(s) Report breakdown categories, if any Date set to start report, if any Date set to end report, if any List of event filters for the report, if any List of time period filters for the report, if any List of features in the scope of this report (that is, not filtered out) that have license activity displayed in the report List of features in the scope of this report (that is, not filtered out) that do not have license activity displayed in this report

Features Without Usage:

A Usage Summary report with default settings contains one line per feature and 11 columns per line. From left to right in the report, the columns are:
16 | Chapter 4 Usage Summary Report

Category

Available

Column Heading

max hours

Description

Maximum number of available licenses. Includes overdraft licenses. Number of available hours of license usage. Total number of license requests. Number of licenses requests fulfilled. Number of license requests queued. Number of license requests denied. Number of license requests not fulfilled because the feature is unsupported. Percent of license requests that were denials. Maximum number of licenses used simultaneously. Includes overdraft licenses. Number of available license hours used. Percent of available license hours used.

License Requests

total used que den unsup %den

max hours %hrs

Usage Summary Report Output | 17
Possible explanations for denials in reports where the maximum available number of licenses were never used include: The number of available licenses changed during the report period. For example, you start your report log when you have 10 licenses of FeatureA, then a few months later, still writing to the same report log, you add 10 more FeatureA licenses. Your report might show the max available licenses = 20, max used licenses = 18, and denials. Remember that the denials may have occurred when you only had 10 licenses available. Licenses are reserved for particular users. Even though all licenses for a feature are not checked out, they are not available to all users. If someone outside the reservation group tries to check out a reserved license, that user will be denied a license. License reservations are set in a vendor daemon's options file. Users are excluded from the group of users who can check out a license. Even though all licenses for a feature are not checked out, a particular user may be excluded from using a license and gets a denial when trying to check out a license. Exclusions are set in a vendor daemon's options file.

Output Arrangement and Detail
The Usage Summary report shows license usage by feature. To create a report that shows more detail about the nature of license usage, you can use a combination of: Summary period
18 | Chapter 4 Usage Summary Report
Breakdown category Sort order specification Feature description Using these controls, you can decompose the usage of each feature into useful groupings according to your particular reporting requirements. You may use the Summary choice lists in the SAMreport-Lite main window, which provide easy access to the Feature, User Name, and User Host Name breakdown categories. You will notice that changing the breakdown settings automatically changes the sort order to defaults that correspond to your breakdown settings. If you specify multiple breakdown categories, the resulting report shows use of features by each unique combination of breakdown categories.
Output Arrangement and Detail | 19

Report Input and Output

Specifying Input Report
You can create reports using one or more report logs from one or more FLEXlm vendor daemons, as long as each report log is written by a single vendor daemon running on a single host. (Each redundant vendor daemon must write to its own report log.)

Displaying Output to the

Viewer Window

Navigating the

SAMreport-Lite Viewer Window

Selecting Output Type

and Output File Names
Output Formats Data Filters Reports and Time Zones Setting Start and End

Dates for a Report

Specifying Input Report Logs
The only valid input files are FLEXlm report logs. These report logs may have been produced by redundant license servers or distributed license servers, or they may simply be archived report logs from one or more license servers. Report logs must be accessible to SAMreport-Lite. Enabling and Managing Report Logs on page 27 describes how to start and manage report log files. You must specify at least one report log before running a report. You must specify the location of each of the report logs you want to run with SAMreport-Lite using one of the following two methods. Type the path to the report log in the text field to the right of the Browse button. Press Enter. Repeat this process for each report log that you want to add. Click the Browse button and use the report log file browser to select a report log from your system. Double-click the report log file. You can repeat this process to select more than one report log from the browser. After you select a report log, the report log file name appears in the text box above the Remove button. To remove a report log from the list, click to highlight the report log, then click the Remove button. There is no fixed limit on the size of a report log that you run through SAMreport-Lite, but the execution time of a report is proportional to the amount of report log data that is processed.

Displaying Output to the Viewer Window
All reports generated in the SAMreport-Lite interface are displayed on the screen in a SAMreport-Lite Viewer window, even if you specify one or more output files.
Navigating the SAMreport-Lite Viewer Window
The SAMreport-Lite Viewer window is divided into two sections. A list of the titles of individual pages of a report or a list of output formats is displayed in the left side of the SAMreport-Lite Viewer. A textual page of a report is displayed in the right side of the Viewer. If the displayed page is longer than the display space (often the case with textual report output), you can read the rest of the
22 | Chapter 5 Report Input and Output
page by moving the scrollbar at the right margin of the Viewer. A navigation toolbar and report progress indicator are displayed at the top of the Viewer. You can display different pages or output formats of a report in one of three ways: Click the page name in the left side of the window. Click the Back and Forward buttons in the toolbar. Select Next or Previous from the Page menu.
Selecting Output Type and Output File Names
Different output formats are available; unavailable output formats are grayed out. All reports written to files require an output file name base and at least one output format selection. The file name base can be entered in one of two methods: Type the path and file name base in the text field to the right of the Output File button. If no path is specified, the files are written to the current working directory. Click the Output File button to open a file selection browser. Find and double-click the directory in which you want to save the output file. Type the file name base in the file selection browser. Click the Save button. The appropriate file name extension is automatically appended to a file name base, depending on the files's output format: Output Format
HTML Text Report Interchange Format See a description of RIF in Output Formats on page 24.

File Name Extension

.html.txt.rif
SAMreport-Lite will not warn you if the output file that you are defining already exists and that you are about to overwrite it.
Selecting Output Type and Output File Names | 23

Output Formats

Usage Summary reports are available in the following formats: Text. This format is suitable for printing and reading, but not for parsing. HTML. This format is suitable for posting textual reports to a web page. Report Interchange Format (RIF). This format is a simple, flexible, plain text format that is designed to pass tabular information between the report generator and another program, such as a spreadsheet. Fields are delimited by multiple spaces. Textual reports are written to a single RIF file; each page of a multipage graphical report is written to a separate RIF file. Sequential numbers (starting with 0) are appended to the file name base of the RIF files and they have the extension.rif. A Table of Contents RIF file is generated for each RIF report and is named output_filename_base _toc.rif.

Format Specification:

#BEGIN HEADER header lines #END HEADER #cols [#rows] name of dataset column labels [rows] // These lines contain // info for the first // table.
If you break down data by more than one category in a Usage Summary report written in RIF, each of the categories is presented in its own column. More than one table may be contained in a RIF file. The #rows entry is not present if the file contains rows from only one table. If the #rows entry is missing, read all of the rows until the end of the file. If there is more than one table in the RIF file, the table-specific portion of the format is repeated for each additional table.
#cols [#rows] name of dataset column labels [rows] // These lines contain // the first table. //
24 | Chapter 5 Report Input and Output

Data Filters

Some of the information contained in the report log is subject to filtering. Two filters can be specified for a Usage Summary reportfeature and user. Multiple filter categories for one report are applied with a Boolean AND operationall the specified conditions must be satisfied. If a report is filtered on user==User1 and feature==Feature2, the resulting report contains usage of Feature2 by User1. Multiple instances of a single filter category are applied with a Boolean OR operation. If a report is filtered on user==User1 and user==User2, the resulting report contains usage of features by either User1 or User2. Multiple filter values for the same filter category can be specified on the same line separated by a space or on separate lines. For example, user==User1 User2 is equivalent to user==User1 and user==User2.

Reports and Time Zones

Timestamps in a report log are determined by the clock on the license server machine. The times are converted from the time zone of the license server machine and stored in the report log in Greenwich Mean Time (GMT), also known as Universal Time (UTC). Therefore, the data in a report log is insensitive to time zones, and you can run a report using report logs that were written on machines in different time zones without compensating for time differences. Reports, on the other hand, show time using the time zone set on the machine where the report was generated. SAMreport-Lite translates times in UTC from the report log using the offset for the time zone of the machine on which SAMreport-Lite is running. For example, if you have an event in a report log that was written at 1pm by a vendor daemon running on a license server in the US Eastern time zone, its timestamp in the report log would be written as 6pm GMT. If an event in a report log was written at 10am by a vendor daemon running on a license server in the US Pacific time zone, its timestamp would also be written as 6pm GMT. If those two report logs were used to generate a report in the US Pacific time zone, those two events would both be reported at 10am. If the same report were generated on a computer in the US Eastern time zone, the events would both be reported at 1pm. Possible causes for the times in reports that are different than you expect are: The time zone on the license server machine is set incorrectly. If the time zone is not set correctly, and the system clock has been set to show local

Data Filters | 25

time, an error is introduced into the UTC timestamps recorded in the report log. The time zone on the machine where SAMreport-Lite is running is set incorrectly. Even if the clock time looks correct, the time zone may not be set correctly.
Setting Start and End Dates for a Report
Start and end dates for report output can be set in text fields in the middle portion of the SAMreport-Lite main window. Times can be included. If no start and end dates are set, the report is generated with data from the entire report log. If no time is specified, days begin at midnight, 00:00:00. The following formats are accepted for 3:30 pm on January 31, 2007:
MM/dd/yyyy HH:mm:ss MM/dd/yyyy HH:mm MM/dd/yyyy yyyyMMdd HHmmss yyyyMMdd HHmm yyyyMMdd MMM dd, yyyy HH:mm:ss MMM dd, yyyy HH:mm MMM dd, yyyy 1/31/2007 15:30:00 1/31/2007 15:30 1/31/Jan 31, 2007 15:30:00 Jan 31, 2007 15:30 Jan 31, 2007
HH is measured by a 24-hour click (0-23). MMM can be either the three-letter abbreviation for the name of a month or the full name of the month (Jan, January, jan, january, JAN, JANUARY).
26 | Chapter 5 Report Input and Output
Enabling and Managing Report Logs

How to Turn on a

To use SAMreport-Lite, you need one or more report log files that are accessible to SAMreport-Lite. Each report log must be written by a single vendor daemon on a single host. (Vendor daemons running on more than one server must each write to their own report logs.) SAMreport-Lite cannot produce reports from debug log files (lmgrd's standard output).

Report Log

Size of the Report Log Flushing Data to a Report
Managing Report Logs Avoiding Corruption in

Report Logs

How to Turn on a Report Log
SAMreport-Lite can read report logs that are accessible to the machine where SAMreport-Lite runseither by being located on the machine where SAMreport-Lite runs or via a network share. After you enable report logging with the following method, your vendor daemon will be writing a report log from which you can generate a report with SAMreport-Lite. Depending on your license usage, you should wait a few hours or a few days before generating a report from this report log. The options files and license files for each license server in a redundant license server configuration must also be set up in order for report logging to continue when the master changes. If a master license server goes down, the new master will read its license and options files and write to its own report log. To enable report logging for one of your Flexlm vendor daemons 1 Create an options file for the vendor daemon, if one doesn't already exist. The options file is a plain text file with any name (we recommend an.opt extension). For example, for a vendor daemon called vend, the options file could be: C:\Program Files\Autodesk Network License Manager\vend.opt 2 In the options file, enter a line of the following form:

Rotating a Report Log with lmswitchr
This method of rotating a report log is recommended if you are not using SAMsuite. 1 Start lmtools. In the Service/License File tab, select the license server whose report log you want to rotate. Click the Switch Report Log tab. Type the Vendor Name and the New Report Location. Be sure to specify a new file name (do not reuse the old file name) for the new report log. Click the Switch Report Log button. 2 Edit the options file with the new report log path and file name. If the license server goes down and comes back up, the vendor daemon will read its options file and will continue to write to the new report log. For redundant license servers, update each of the three options files. 3 Move the closed report log to where it can be accessed for reporting and storage. You will move one report log for a single license server and up to three report logs for a redundant license server. 4 Eventually you will not need to run reports on some of your old report logs. Those report logs can be compressed and archived to a location that does not necessarily need to be accessed by SAMreport-Lite.
Avoiding Corruption in Report Logs
Flexlm has been improved from version to version to make report logging more robust. Nevertheless, particularly in older versions of the vendor daemon, corruption can occur in the report log. Follow these guidelines to avoid corrupt report log files: In pre v 5.1 vendor daemons, rereads, and shutdowns could possibly introduce corruption, particularly if the server is busy. With these older vendor daemons, the best policy is to issue reread or shutdown when no licenses are checked out, if possible.
Rotating a Report Log with lmswitchr | 31
Issuing an lmdown command while the server is shutting down can cause corruption. Don't move, copy, or edit the report log file while the server is running. Never configure more than one license server to write to the same report log file. In the case of a redundant server, each vendor daemon must write to a distinct file, preferably one which is local to the server machine. Even if the report log is not corrupted, SAMreport-Lite will not run a report using a report log that has been written by a vendor daemon running on more than one license server machine. Never configure different vendor daemons to write to the same report log file. Even if the report log is not corrupted, SAMreport-Lite will not run a report using a report log that has been written by more than one vendor daemon. Do not use lmswitchr or -switchlog to switch the report log to an existing report log file. Switch to a file with a new name. Never hand-edit a report log or combine report logs together into the same file. If you change a server host name, make sure you stop the license manager and create a new report log when the name change is complete.

AutoCAD 2006
Questions and Answers AutoCAD 2006 Network Licensing
In the AutoCAD 2002 software release, Autodesk introduced a new network license manager, FLEXlm from Macrovision Corporation. The license manager has improved with each release, and continues to evolve with the release of AutoCAD 2006 software. Autodesk continues to enhance the capabilities of this license management software by enhancing the license borrowing capability with the latest FLEXlm version. In addition, AutoCAD 2006 includes a Network License Activation Utility.
This document provides an in-depth look at the FLEXlm features in AutoCAD 2006 software and reviews the basic FLEXlm technology and how it works. At the end of this paper is a section for users who are making the transition from the older lan network licensing software used with AutoCAD 2000i and earlier releases. CONTENTS General Information. 1 License Borrowing. 3 FLEXlm Basics.. 4 Host ID..5 FLEXlm Versions. 5 License File Locations. 7 License File Contents. 7 Using FLEXlm. 8 How FLEXlm Works.. 10 FLEXlm Versus lan.. 11

1. General Information

1.1 Can I have a back-up license server? Autodesk does not allow backup servers. However, Autodesk supports Distributed or Redundant server models that allow failover in case your active server stops working. Distributed license server model: Licenses are distributed across more than one server. A unique license file is required for each server. To create a distributed license server pool, you must run the Network License Manager on each server that is a member of the distributed server pool. The number of licenses available for a given product is the sum of licenses for that product across all distributed server pool members. If one server goes down, users can use the licenses on the remaining servers. Redundant license server model: Three servers authenticate a single license file. One server acts as the master, while the other two provide backup if the master server 1
AutoCAD 2006 White Paper Network Licensing Questions and Answers
fails. With this configuration, licenses continue to be monitored and issued as long as at least two servers still work. You must install the Network License Manager on each server. 1.2 If my server goes down, can I get another license file for my new server? Yes, Autodesk provides a temporary license to run until your primary server comes back up. If your primary server is permanently disabled, Autodesk reissues a new, permanent license for the new server. 1.3 Can I first deploy my Autodesk licenses on a test server, and then move them to another production server? Yes. To do this, contact the Autodesk registration and activation team so they can issue you a license file that works for 30 days. 1.4 I have a network license system at work that allows me to run Autodesk products while on the network. Am I allowed to run a copy of the products on my home computer, and how do I do this? The Autodesk Software License Agreement permits an additional installation only on a computer that is owned or controlled by the licensee. This provision is intended to allow employees to work while away from their usual work location. It is not intended to allow employees to install a product on their personal computer over which the licensee has no control. You have two options: Use the License Borrowing utility to check out a license from the network license server on a computer owned by the licensee. Your license is automatically returned to the license server at the end of the day on the return date you set when you borrowed the license. You can also return a license early. If you have a VPN (Virtual Private Network) connection into your company, dial up and run the application remotely on a computer owned by the licensee. You do not have to borrow a license from the server. 1.5 I am a customer with a network license, but I want to move two licenses and deploy them as stand-alone. How is this done? If you are a current subscription customer, contact the Autodesk Business Center at customercare.abc@autodesk.com and ask to create a new group for that product family with a stand-alone deployment for two seats. The network license is decremented by the number of stand-alone licenses requested. There is no charge, and you can merge all licenses back into one group in the future when you are ready. In EMEA, you sign a software removal form for network license reduction. If its for a certain period, Autodesk provides a temporary code. If it is a perpetual license that is not on subscription, you can get a new license created for two stand-alone seats. Place an order with the Autodesk Business Center at customercare.abc@autodesk.com. The network license is decremented by the number of stand-alone licenses requested. In EMEA, you sign a software removal agreement for this. New products with new deployment type settings and new serial numbers are issued. You can change back again, if necessary (there is a charge to do so). Ask the Autodesk Business Center at customercare.abc@autodesk.com for the specific cost in your region. Another option is to exchange two network licenses for two new stand-alone licenses for one seat each (there is a charge to do this). Ask your Autodesk Business Center at customercare.abc@autodesk.com for the cost in your region. As part of this transaction, Autodesk also ships you any necessary media or boxes

www.autodesk.com/autocad

1.6 If I am on subscription, how do I run part of my network on the prior release of a product and another part of the network on the current release? Firstly, you must have owned the prior release. Then, you must request a new network license through Autodesk Business Center customercare.abc@autodesk.com for the number of licenses you wish to run on each version. The license total will not exceed the total number of purchased licenses. If you are not on subscription, Autodesk allows you to do this for 120 days after you have installed the new Autodesk product.

2. License Borrowing

2.1 What is license borrowing? License borrowing was first introduced in AutoCAD 2004 and allows licenses that normally reside on the license server to be bound to a users workstation for a fixed period. License borrowing was enhanced in AutoCAD 2006, and is now part of the AutoCAD application. During a borrowing period, maintaining a license does not require any communications with the license server. At the end of the license borrowing period, the license is automatically disabled on the users workstation, and the license is automatically added back into the server pool of available licenses. A user may also return a license to the server pool early. A common use of license borrowing is for a user who is taking a laptop on a trip where access to the license server is not available. In this case a license is borrowed from the license pool on the server for a specified period, and then resides on the laptop until the borrowing period expires, or the license is returned by the user when they next connect to the server. License borrowing is integrated in AutoCAD 2006, and users can borrow a license from within AutoCAD. By integrating license borrowing into AutoCAD 2006 there is no longer a need for a separate utility or to use LMTOOLS utility from Macrovision. The LMTOOLS utility allows administrators to control the use of license borrowing by users. 2.2 How do I control my users borrowing of licenses? Since borrowing removes a license from your servers license pool, you may want to restrict how many licenses can be borrowed and who is allowed to borrow them. These restrictions are controlled by editing the Options file on the license server. There are three key options file controls that you can use to control license borrowing. BORROW_LOWWATER sets the maximum number of licenses that can be borrowed (per product) on a license server. INCLUDE_BORROW and EXCLUDE_BORROW enable you to specifically include or exclude individual users, groups of users, and specific workstations. 2.3 What is the maximum period my users can borrow licenses? The Autodesk license file sets a maximum borrowing period that is available for the software. You can then set the borrowing period to any value up to the maximum using the ADLM_BORROWMAX environmental variable (described in the Autodesk Network Licensing Guide). You, as a user, can then select your own desired borrow period up to the limit set by the administrator. This borrowing period is set in days so that the license is always deactivated on the individuals workstation at midnight on the last day of the borrowing period.

2.4 Can users return their licenses early? Yes, using the license borrowing utility, a user can return a license early. A user must be connected to the license server to return the license. 2.5 How do users borrow a license? In AutoCAD 2006, licenses are borrowed directly from within the application using the Tools > License Borrowing menu option. 2.6 How does a user know that a license has been successfully borrowed? When you launch the application, you are notified through the Communication Center balloon notification that you are running under a borrowed license. The notification informs you that the license has been borrowed and indicates the number of days left until the license expires. 2.7 Can users borrow licenses again if they are traveling and their previous licenses have expired? You, as a user, must be able to connect to the network to acquire licenses from the appropriate license server. If you have configured your network to allow remote access (for example, through VPN on a dial-up connection, or a local office that is connected by a WAN back to your office), then you will be able to borrow subsequent licenses in exactly the same way you did at the home office. 2.8 Does AutoCAD 2006 support the timeout feature? Yes. The timeout feature is supported through the Options file. Timeout defines the maximum time a license may be idle before the license server reclaims it. Administrators can use the timeout to enforce the return of licenses to the license pool when they are not being used. The behavior of a license reclaimed by the timeout setting is the same as that exhibited by a license that loses communication with the license server.

3. FLEXlm Basics

3.1 How does FLEXlm work? FLEXlm is a client-server application. The software client (the software application) requests a license from the license server and is either granted or denied a license by the license server.
The main FLEXlm components are
Lmgrd.exe referred to as the Vendor daemon a small monitoring application that runs all the time on the server A License file (or files, for some configurations) License administration applications (lmutil, lmdiag, lmstat, and so forth) The user installs lmgrd.exe and the vendor daemon on the computer specified in the license file. Once the license file(s) and the daemons are in place, the only requirement is to start lmgrd. The daemon is typically started when the machine boots (on Microsoft Windows as a system service) but can also be started manually. When the AutoCAD 2006 network version is started, a request for a license is sent to the FLEXlm license server. If a license is available, it is granted, and the AutoCAD 2006 application starts on the workstation. Once a license has been granted, a communication (called a heartbeat) is established between the AutoCAD session and the license server. The frequency of the heartbeat (communication) is approximately once per minute. When www.autodesk.com/autocad 4

the AutoCAD session ends, the license is returned to the server and the communication is terminated. The FLEXlm license server is passive in that it does not communicate itself, and thus it does not generate unnecessary network traffic. 3.2 What are the components of the FLEXlm license server? The following terms are used to describe FLEXlm concepts and software components: FeatureAny functionality requiring licensing. The meaning of a feature depends entirely on how it is used by each application. For example, a feature could represent any of the following: An application software system consisting of hundreds of programs A single program (regardless of version) A specific version of a program A part of a program A piece of data ClientAn application program requesting or receiving a license. DaemonA process (program) that must continuously run in the background and is often designed to respond to requests from other processes across a network. On Microsoft Windows, daemons are called services. When services respond to requests, they are known as the server half of a client/server architecture. Vendor DaemonThe daemon or service that dispenses licenses for the requested features. This daemon is built by a software provider with FLEXlm libraries supplied by Macrovision Corporation. The Autodesk vendor daemon name is adskflex. LmgrdThe daemon process, or license server, that directs client processes to the correct vendor daemon. The same lmgrd can be shared by all applications from all vendors, because this daemon neither authenticates nor dispenses licenses. Lmgrd processes few user requests on its own but forwards these requests to the vendor daemons. License FileA file distributed with software that enables and restricts the usage of specified features and behaviors. The three principal components of the FLEXlm network licensing system are the master daemon, the vendor daemon, and the license file. These components can be configured and managed with a GUI interface tool, lmtools.exe, or a command-line interface, lmutil.exe. At the option of the administrator, FLEXlm is capable of writing a debug log file and report log file. The administrator can create a vendor-specific options file to control license access and specify report log placement. A single instance of the master daemon is run on the license manager system, regardless of how many products or even software vendors are being served. When an application such as AutoCAD software sends a request for a license, it first contacts this master daemon, which directs the request to the proper vendor daemon. Once the master daemon passes a license request to the vendor daemon, all license interactions occur between the application (AutoCAD) and the vendor daemon (adskflex). Adskflex authenticates requests against the license file that contains information about the number of licenses authorized for each product feature and is tied to the license server by the network interface cards Ethernet MAC address. If the administrator elects to create a vendor-specific options file, license access can be reserved or denied based on workstation host name, user login name, or IP address. The options file also enables an administrator to reserve licenses for a user. Administrators specify report log creation in the options file to be used by the SAMreport-Lite tool. www.autodesk.com/autocad 5

4. Host ID

4.1 How is the host ID used? The host ID is used to communicate between the license manager and the AutoCAD 2006 software. The license manager uses the host ID to distinguish itself from other computers running license managers, and the AutoCAD application uses the host ID to identify which computer to request a license from. 4.2 How do I get the system host ID? When you create deployments, the Deployment Wizard prompts you for the server host name and server host ID. The server host name is the name of the computer running FLEXlm, and the server host ID is the MAC address of the network card from the host server. The Deployment Wizard can look up the server host ID of the computer specified under server host name. If the Deployment Wizard is unable to look up the server host ID it can be obtain by running lmtools.exe from the computer where FLEXlm is installed. LMTOOLS can be installed from the AutoCAD 2006 Media Browser. Installing the Network License Manager is step 2 on the Network Deployment option. The server host ID is the Ethernet address found on the System Settings tab in the LMTOOLS window. The server host ID is the identification key used to bind the license file to a particular license server machine. The Deployment Wizard also creates a license file (licpath.lic) from the information supplied, telling AutoCAD 2006 software where to find the license manager.

5. FLEXlm Versions

5.1 How can I tell which version Im using? Use the lmutil lmver command, or you can run lmtools.exe. When using lmtools, go to the Utilities tab, navigate to the FLEXlm file, and click the Find Version button. 5.2 I have products from several companies at various FLEXlm version levels. Do I have to worry about how these versions work together? If youre not combining license files from different vendors, the simplest thing to do is to run them separately, making sure you use the tools (especially lmgrd and the vendor daemon) that are shipped by each vendor. Newer versions of lmgrd always support older versions of vendor daemons and applications. If you have combined license files from two vendors, you must use the latest version of lmgrd. If youve received two versions of a product from the same vendor, you must use the latest vendor daemon. An older vendor daemon with a newer client may cause communication errors. 5.3 Ive received a new copy of a product from a vendor, and it uses a new version of FLEXlm. Is my old license file still valid? Yes. Older FLEXlm license files are always valid with newer versions of FLEXlm.

6. License File Locations
6.1 My AutoCAD program cannot seem to find the license file. What can I do? For Autodesk products using FLEXlm, the license files reside on the license server and are used by the master daemon and vendor daemon to distribute licenses. Created with the deployment and installed with each application to the client workstation is a file named licpath.lic, which contains the path information to the license server. Note: Distributed server configurations do not use licpath.lic. Instead an environment variable ADSKFLEX_LICENSE_FILE is set which specifies the server search order. Based on the error code displayed, you can reference the specific error in the FLEXlm documentation to resolve why AutoCAD cannot retrieve a license. 6.2 I have received FLEXlm license files from two different companies. Do I need to combine them? You dont need to combine license files. You can have any number of separate license files, with different lmgrd server processes supporting each file. Moreover, because lmgrd is a lightweight process, running separate license files is often the simplest way to proceed for sites without systems administrators. 6.3 When is it recommended to combine license files? Many systems administrators, especially for larger sites, prefer to combine license files to ease administration of FLEXlm licenses. Its purely a matter of preference. Autodesk recommends running separate license files between different companies software. Autodesk recommends combining Autodesk license files.

7. License File Contents

7.1 What are the components of a license file? The license file contains licensing information provided by Autodesk. You obtain license file data when you authorize the Network License Manager. The license file contains information about network server nodes and vendor daemons, and an encrypted digital signature created when Autodesk generates the license file. The following is an example of the contents of a license file: SERVER ServerName HostID USE_SERVER VENDOR VendorDaemon port=portnumber INCREMENT IncrementName VendorDaemon Version Expiration NumberofLicenses \ VENDOR_STRING=UsageType:LicenseBehavior BORROW=### SUPERSEDE DUP_GROUP=DupGroup ISSUED=IssueDate SN=SerialNumber SIGN=nnnnnnnnnnnn
The following table defines each license file parameter. Parameter ServerName and HostID VendorDaemon Portnumber Definition Binds the license to a particular server and network adapter. The name of the server-side Autodesk license daemon (adskflex). Reserved and assigned for use only for Autodesk products running the Autodesk/FLEXlm vendor daemon. By default port 2080. Name of the product or feature. Internal version number. The date when the license expires. Specifies the number of licenses to be managed by a particular server or redundant server pool. Defines the license configuration settings, UsageType and LicenseBehavior. Keyword allows license borrowing. Replaces existing lines in a license file that have a date earlier than the defined IssueDate. The Autodesk policy for modifying an existing license is to reissue the entire license file. Because there can be multiple INCREMENT lines, the SUPERSEDE/ ISSUED parameters are used to replace any previous product or feature of the same name. Defines how the server handles the sharing of multiple license requests. The default for this behavior is Host, which allows for multiple sessions on the same computer to share the same license. The date the license file was generated by Autodesk. The serial number of the Autodesk product. The encrypted signature used to authenticate the attributes of the license file.

IncrementName Version ExpirationDate NumberofLicenses VENDOR_STRING BORROW SUPERSEDE

DupGroup

IssueDate SerialNumber SIGN=
Following is an example of a completed license file for a single or distributed server model issuing 3 licenses: SERVER NLMSVR1 000476e5cb3d USE_SERVER VENDOR adskflex port=2080 INCREMENT 46300ACD_2006_0F adskflex 1.000 permanent 3 \ VENDOR_STRING=commercial:permanent BORROW=720 SUPERSEDE \ DUP_GROUP=UH ISSUED=10-MAR-2004 SN=341-01234567 SIGN=1FBC 0A61 9D93 AA5E A581 BFB3 AAE5 17D6 08EC 2814 E51C 5072 638D"
Following is an example of a completed license file for a redundant server model issuing 10 licenses: SERVER NLMSVR1 0002008B5DBSERVER NLMSVR2 00020086FCSERVER NLMSVR3 00020086FCUSE_SERVER VENDOR adskflex port=2080 INCREMENT 46300ACD_2006_0F adskflex 1.000 permanent 10 \ VENDOR_STRING=commercial:permanent BORROW=720 SUPERSEDE \ DUP_GROUP=UH ISSUED=13-Mar-2004 SN=341-01234567 SIGN="0D6B \ 36CE B604 BC6E5 EC24 BA3F 549F 81B5 D5DD EB90 3497" Note: The redundant server model requires the addition of a port number (the default is 27005) for each server.

8. Using FLEXlm

8.1 How do I obtain and set up the FLEXlm license file? New to AutoCAD 2006 is the Network License Activation Utility. Install the utility and run the application to obtain your license file. The utility is available for installation from the Network Deployment option of the Media Browser. The license file identifies important licensing information, including license type and behavior, and the number of licenses available for use.
To obtain a license file manually:
1. Obtain the following information: Product serial number(s) Server name Host ID number An email address where Autodesk can send the license file Contact the Autodesk Registration and Authorization office and provide all required information specified in the previous step.
The Autodesk Registration and Authorization office will email you the license file in text format, usually as an attachment to an email. To set up a license file: Copy the attachment to the \Autodesk License Manager\license folder. You can name the license file anything you want; however, the name must have a.lic or.dat extension. 8.2 How do I configure and start the FLEXlm license server? You configure the license server with the lmtools.exe utility. LMTOOLS is installed as part of the Autodesk Network License Manager. For specific steps see the technical white paper, Installing the Autodesk Network License Manager for AutoCAD 2006 or other Autodesk Products. 8.3 If my client application exits abnormally, does the server free the license? Yes, unless the clients entire system crashes. The license is freed immediately when the computer is still able to communicate with the license manager. If the entire system crashes, then the license is not freed, and you should use the lmremove option of lmutil.exe to free the license or fix the problem and restart AutoCAD on the computer that

crashed. You can also create an options file, setting a timeout value where a license is released if communication is lost between the client application and the license server. 8.4 What happens when the server stops? AutoCAD software continues running and checks for a period to see if the license server has been restored and is available again. After that, if the license server is still not available, users on each client workstation receive a warning that their licenses have been lost and are prompted to save their work before exiting.

9. How FLEXlm Works

9.1 What prevents me from changing a license file? Each feature line in the license file has a 12- or 20-character hexadecimal license key. If anything significant is changed, the key becomes invalid, and the license wont work. 9.2 How fast does a check-out occur? Check-out speed depends on the operating system and the system or network load. Some tests show that a typical system performs check-outs in about 1/50 second (20 ms). 9.3 Does FLEXlm licensing impose a heavy load on the network? No. A typical check-out request requires five messages and responses between client and server, and each message is less than 150 bytes. When a server is not receiving requests, it requires virtually no CPU time. 9.4 Does FLEXlm work with ATM, ISDN, token ring, and so on? These are not officially supported, but, in general, they have no impact on FLEXlm. Because FLEXlm requires TCP/IP, as long as TCP/IP works, FLEXlm will work. 9.5 Does FLEXlm work with subnets, fully qualified names, multiple domains, and so forth? Yes. 9.6 We are using FLEXlm over a wide-area network. What can we do to improve performance? Setting up your license configuration as a distributed server model improves performance over a wide-area network.

10. Redundant Servers

10.1 What are redundant servers? With a redundant server model, you use three servers to authenticate a single license file. One server acts as the master, while the other two provide backup if the primary server fails. Using this configuration, the system continues to monitor and issue licenses as long as at least two servers are functional. If you use the redundant server model, all servers must reside on the same subnet and have consistent network communications. (Slow, erratic, or dial-up connections are not recommended.) This model does not support the User Datagram Protocol (UDP) packet type.
To create a redundant server pool, install the network license manager on all three servers that make up the redundant server pool. To get proper license authorization, you must obtain the host ID and server name for each server in the redundant server pool before contacting Autodesk. Redundant servers require a quorum of two servers to be up, or no licenses are served. 16.2 How do I start redundant servers? The redundant server model requires Microsoft Windows 2000 Server or Windows 2003 Server. Windows NT , and 2000 Workstation editions are not supported. To start the redundant servers, use LMTOOLS.exe on each server and start each server within three minutes. Note: The redundant server model requires that separate copies of the same license file, the license manager daemon (lmgrd), and the vendor daemon reside on each server; all are necessary to authenticate and release licenses.

11. FLEXlm Versus lan

11.1 Why has Autodesk changed its network license manager to FLEXlm? FLEXlm is a more reliable and robust network licensing tool. In addition, it is already in wider use than the previous license manager. 11.2 Will the FLEXlm license server coexist with an existing lan installation? Yes, the two license managers can coexist; however, lan cant be used to manage licenses for AutoCAD 2002, 2004, and 2006, and FLEXlm cant be used to manage licenses for AutoCAD 2000i and earlier. 11.3 Does FLEXlm support Novell networks? You can still deploy and run the AutoCAD application in a Novell network environment using the FLEXlm license manager. However, the license manager itself must reside on a supported Microsoft Windows operating system, and the TCP/IP protocol must be configured and running on your network. This configuration does not support the IPX/SPX protocol or Novell Loadable Modules of FLEXlm. 11.4 How do I generate usage reports with FLEXlm? Autodesk includes SAMreport-Lite with FLEXlm. You can use SAMreport-Lite to generate summary reports on software usage. A copy of the SAMreport-Lite Users Guide is available for download from the Network Deployment option of the AutoCAD 2006 Media Browser. You need to obtain a license for SAMreport-Lite before you can start reviewing log files. The procedure to do this is explained in the guide. 11.5 Does Autodesk still provide a Network Setup wizard? No, in AutoCAD 2006 the Network Setup wizard has been replaced by the Deployment Wizard. The Deployment Wizard was first introduced in AutoCAD 2004 and replaces the older Network Setup wizard. 11.6 How do FLEXlm and the Autodesk License Manager from lan compare? AutoCAD 2002, 2004, and 2006 users see no difference using FLEXlm compared to earlier versions of AutoCAD software that use the Autodesk License Manager provided by lan. AutoCAD requests alicense from the license manager, and that request is either granted or denied. When the user is finished using the software, the license is returned to the license manager. www.autodesk.com/autocad 11
11.7 What are the FLEXlm equivalent tools when compared to lan? lan uses five program files to control, distribute, and report on license activity. FLEXlm uses only three program files. Following is a comparison of the lan tools with their FLEXlm counterparts lan Tools AdLM Admin Key Directory Host Name Key (Authorization Code) Feature Code: Licenses AdLM Control Servers Clients Bury Client Zero Log Find Log Dump Log FLEXlm Tools lmtools Configure Services:Path to license file System Settings:Computer/Hostname License file obtained from Autodesk Server Status:Perform Status Enquiry lmtools and lmutil.exe Server Status:Server Name Server Status:Perform Status Enquiry lmutil lmremove Switch Report Log Configure Services:Path to Debug Log Config Services:View Log and Close Log provide similar functionality.

AdLM Query Servers Clients Environment
lmtools Server Status:Server Name:Perform Status Enquiry Server Status:Perform Status Enquiry System Settings Server Status:Perform Status Enquiry

Feature

Server Status:Individual Feature:Perform Status Enquiry
AdLM Report AdLM Control Panel Applet Start/Stop Settings
SAMreport-Lite lmtools Start/Stop/Reread Configure Services Options file
AdLM equivalent No equivalent No equivalent
lmtools Utilities Server Diagnostics
Besides the initial program files, both the FLEXlm and lan license managers use support files. Following is a list of each file and its default installation location and equivalent.
lan.\key\<feature number>.lic One.lic file must exist for each application.\log\adlm.log
FLEXlm.\license\<file_name>.lic or.dat Multiple Autodesk product license files can be combined into a single file for easier management.\log\<file_name>.log
lan Resource file Set in control panel applet and created by user
FLEXlm Options file Created by user and specified in license file
11.8 Does FLEXlm use a server code and authorization code? FLEXlm has an equivalent for both the server code and authorization code. In FLEXlm the server code is equal to the Ethernet address reported on the System Settings tab in lmtools. The FLEXlm equivalent of the authorization code is the license file that Autodesk emails you when you authorize AutoCAD software. 11.9 Will FLEXlm work with AutoCAD 2000 and AutoCAD Release 14? No. FLEXlm cannot distribute licenses for AutoCAD 2000/2000i or AutoCAD Release 14. FLEXlm can coexist with the AdLM from lan. The lan license manager administers AutoCAD 2000/2000i and AutoCAD Release 14 licenses. 11.10 Will lan administer AutoCAD 2002, 2004 and 2006 licenses? No. lan cannot distribute licenses for AutoCAD 2002, 2004 and 2006. lan can coexist on the same computer running the FLEXlm license manager. The FLEXlm license manager will administer the AutoCAD 2002 licenses.
Occasionally, Autodesk makes statements regarding planned or future development efforts for our existing or new products and services. These statements are not intended to be a promise or guarantee of future delivery of products, services, or features but merely reflect our current plans, which may change. Purchasing decisions should not be made based upon reliance on these statements. The Company assumes no obligation to update these forward-looking statements to reflect events that occur or circumstances that exist or change after the date on which they were made. Autodesk is not responsible for typographical or graphical errors that may appear in this document. Autodesk and AutoCAD are trademarks or registered trademarks of Autodesk, Inc., in the USA and/or other countries. FLEXlm is a registered trademark of Macrovision Corporation. All other brand names, product names, or trademarks belong to their respective holders. 2005 Autodesk, Inc. All rights reserved.