Autodesk COMBUSTION-4 - Acad Full-seat Windows Version, Combustion 4 discreet Network Manual

11 March 2005

This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose.

AUTO DESK CA NADA CO ./AUTO DE SK, INC. MAKE S NO WAR RA NTY, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES, OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, REGARDING THESE MATERIALS AND MAKES SUCH MATERIALS AVAILABLE SOLELY ON AN “AS-IS” BASIS.

IN NO EVENT SHALL AUTODESK CANADA CO./AUTODESK, INC. BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING OUT OF PURCHASE OR USE OF THESE MATERIALS. THE SOLE AND EXCLUSIVE LIABILITY TO AUTODESK CANADA CO./AUTODESK, INC., REGARDLESS OF THE FORM OF ACTION, SHALL NOT EXCEED THE PURCHASE PRICE OF THE MATERIALS DESCRIBED HEREIN.

Autodesk Canada Co./Autodesk, Inc. reserves the right to revise and improve its products as it sees fit. This publication describes the state of this product at the time of its publication, and may not reflect the product at all times in the future.

Autodesk, Inc. Trademarks

The following are registered trademarks of Autodesk, Inc./Autodesk Canada Co. in the USA and/or other countries: 3D Props, 3D Studio, 3D Studio MAX, 3D Studio VIZ, 3DSurfer, 3ds max, ActiveShapes, ActiveShapes (logo), Actrix, ADI, AEC Authority (logo), AEC-X, Animator Pro, Animator Studio, ATC, AUGI, AutoCAD, AutoCAD LT, AutoCAD Map, Autodesk, Autodesk Inventor, Autodesk (logo), Autodesk MapGuide, Autodesk University (logo), Autodesk View, Autodesk WalkThrough, Autodesk World, AutoLISP, AutoSketch, backdraft, Biped, bringing information down to earth, CAD Overlay, character studio, Cinepak, Cinepak (logo), cleaner, Codec Central, combustion, Design Your World, Design Your World (logo), discreet, EditDV, Education by Design, fire, flame, flint, flint RT, frost, glass, gmax, Heidi, HOOPS, Hyperwire, i-drop, inferno, Inside Track, Kinetix, lustre, MaterialSpec, Mechanical Desktop, mountstone, NAAUG, ObjectARX, PeopleTracker, Physique, Planix, Powered with Autodesk Technology (logo), RadioRay, Revit, riot, river, smoke, Softdesk, sparks, stone, stream, Texture Universe, The AEC Authority, The Auto Architect, vapour, VISION*, Visual, Visual Construction, Visual Drainage, Visual Hydro, Visual Landscape, Visual Roads, Visual Survey, Visual Toolbox, Visual TugBoat, Visual LISP, Volo, WHIP!, and WHIP! (logo), wire.

The following are trademarks of Autodesk, Inc., in the USA and/or other countries: AutoCAD Architectural Desktop, AutoCAD Learning Assistance, AutoCAD LT Learning Assistance, AutoCAD Simulator, AutoCAD SQL Extension, AutoCAD SQL Interface, Autodesk Map, Autodesk Streamline, AutoSnap, AutoTrack, backburner, Built with ObjectARX (logo), burn, Buzzsaw, Buzzsaw.com, Cinestream, cleaner central, ClearScale, Colour Warper, Content Explorer, Dancing Baby (image), DesignCenter, Design Doctor, Designer's Toolkit, DesignProf, DesignServer, Design Web Format, DWF, DWG Linking, DXF, Extending the Design Team, GDX Driver, gmax (logo), gmax ready (logo), Heads-up Design, IntroDV, jobnet, lustre, MultiMaster Editing, ObjectDBX, onscreen onair online, Plans & Specs, Ppasma, PolarSnap, ProjectPoint, reactor, Real-time Roto, Render Queue, Visual Bridge, Visual Syllabus, and Where Design Connects.

All other brand names, product names, or trademarks belong to their respective holders.

Government Use

The software and documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the United States Government or any agency, department or instrumentality thereof is subject to the restrictions set forth in the Commercial Computer Software—Restricted Rights clause at FAR 52.227-19 or the Commercial Computer Software—Licensing clause at NASA FAR Supplement 1852.227-86. Manufacturer is Autodesk Canada Co./Autodesk, Inc., 10, Duke Street, Montreal, Quebec, Canada, H3C 2L7.

Titl e: combustion® 4 Network Administrator’s Guide for Microsoft® Windows®

Par t Numb er: NA

Software version: 4

Document version: 4.0

Date: 11 March 2005

1Requirements 1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Network Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Network Planning Concepts 5

Network Configuration Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

AdLM Network Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Installation 13

FLEXlm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Setting up the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Silently Installing combustion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 License Server Configuration 19

Obtaining the Server Host Name and ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Obtaining and Setting Up a License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuring the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 Administration 23

License Server Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Using the FLEXlm Configuration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Using the License Configuration Switcher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

iii

toc

Table of Contents

6 Networking Quick Start and Troubleshooting 27

FLEXlm Defined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Obtaining Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Identifying the Server Name and Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Handling the License File Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the FLEXlm Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Troubleshooting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

AGlossary 35

Requirements

Summary

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Network Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Requirements

The Network Administrator’s Guide gives you

the information you need to deploy

combustion® from a network location. This

chapter describes the system requirements and

network installation components required for

installing, authorizing, and configuring

combustion on a network.

System Requirements

Before you begin installing combustion on a

network using the Autodesk (AdLM), ensure your network, servers, and client workstations meet the minimum recommended requirements for network installation. Refer to the follow ing table for the server hardware and software requirements.

License Server

Hardware / Software

Operating system

Network interface card

Communication Protocol

Requirements Notes

Windows NT®, Windows 2000, or Windows XP

Compatible with current Ethernet network infrastructure

TCP/IP By default, AdLM

Licensing Manager

AdLM supports Ethernet network configurations only.

AdLM supports multiple network interface cards.

uses TCP packet types. Optionally, you can configure UDP packet types.

Refer to the following table for the client workstation minimum recommended hardware and software requirements.

Client Workstation combustion

Hardware / Software

Processor Intel® Pentium® III,

Operating system

Hard drive 20 GB main hard drive,

RAM 256 MB

Video Video display card

CD-ROM Any speed For installation only.

Network interface card

Web browser Microsoft Internet

Requirements Notes

Pentium 4, or AMD® Athlon™ XP

Microsoft 2000 or Windows XP

approximately 142 MB free space

Windows

CPU, 850 MHz or higher.

It is recommended that you install and run an on an English version of the operating system. You must have Administrator permissions to install Not assigning these permissions can cause and third-party applications to perform incorrectly. See Windows Help for information about assigning user permissions.

See the

Installation Guide

for details.

— —

with 32 MB of VRAM (1024x768 display with 24-bit color minimum required)

Compatible with current Ethernet network infrastructure

Required for installing and running network versions of

combustion

—

Explorer 6 or later

combustion

Network Installation Components

❚❘❘

Client Workstation combustion

Hardware / Software

Optional Modem or access to

Requirements Notes

—

an Internet connection

Network Installation Components

To de pl oy a n d c o nf i gu re combustion on a network, the following network installation components are required. These are included on the combustion 4 installation CD.

• Autodesk License Manager (AdLM)

• FLEXlm™ Tools

• combustion License Configuration Switcher

• SAMreport-Lite (optional); for information about

SAMrepor t-Lite, refer to the online samlite_ug.chm file located on the combustion 4 installation CD, in the Network Licensing\Manuals folder.

Autodesk License Manager

The Autodesk License Manager (AdLM) provides authorization for clients running combustion on a network. The AdLM also contains tools for network administrators that provide query and tracking capabilities. For authorizing combustion on a network, double-click setup.exe in the Network Licensing directory on the combustion 4 installation CD and follow the AdLM installer instructions on the screen.

See “License Management” in Chapter 2, “Network

Planning Concepts’’.

FLEXlm Tools

The AdLM uses FLEXlm technology from Macrovision® to manage network licenses. FLEXlm provides administrative tools that help simplify management of network licenses. You can use FLEXlm tools to monitor network license status, reset licenses lost to a system crash, troubleshoot license servers, and update license files on the fly.

See “Using the FLEXlm Configuration Tools” in

Chapter 5, “Administration’’.

combustion License Configuration Switcher

You use the combustion License Configuration Switcher (LicenseSwitcher.exe) located in the same directory as the combustion.exe to allow a workstation to use either a network license or a standalone license. For example, users running a network license of combustion on a network workstation can use the combustion License Configuration Switcher to switch their license configuration to a standalone configuration and take work on the road. When they return, they can switch back to a network license configur ation. With the combustion License Configuration Switcher, users can remain productive while their computer is detached from the network. Using the combustion License Configuration Switcher does not convert a network license to a standalone license. It only changes the method combustion uses to get its license. See “License Management” in Chapter 2,

“Network Planning Concepts’’.

See “Using the License Configuration Switcher” in

Chapter 5, “Administration’’.

Requirements

SAMreport

While not part of the network installation, a version of SAMreport called SAMreport-Lite™ is included in the Network Licensing folder on the combustion 4 installation CD to help you track network license usage. With SAMreport-Lite technology from Macrovision, you can monitor client usage for all software that uses FLEXlm to manage network licenses.

SAMreport-Lite generates usage reports in a variety of output formats, including HTML, text, and Report Interchange Format.

For more information about the SAMreport-Lite features and for instructions on installing SAMreport-Lite, see the online help file samlite_ug.chm included on the combustion 4 installation CD in the Network Licensing\Manuals directory.

For additional information about SAMreport-Lite, and for updates and fixes for this feature, visit the Autodesk website at:

samreportlite

www.autodesk.com/

Network Planning Concepts

Summary

Network Configuration Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

AdLM Network Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Network Planning Concepts

This chapter explains concepts related to

installing and operating combustion on a

network.

Network Configuration Models

Installing combustion on a network requires careful planning. The type of installation you choose to deploy can differ depending on your network infrastructure and requirements for client use. The network configuration model you choose to implement determines where the components that combustion requires for a network installation are installed in your network environment.

Before you choose the appropriate network configuration for your users, you must determine how you want to deploy combustion and which components you need to deploy on a network.

Most deployment types require two components:

the AdLM and the deployment on the same server or on separate servers.

The network server model you choose for your installation determines where each component resides on the network. The server model you choose is based on the structure of your network, the number of users, and your performance requirements. It can determine how well combustion performs in your network environment and the length of recovery time in the event of a network problem.

Another important aspect of a deployment to consider is data sharing. One of the key benefits of a deployment is that users can share data. When you plan a deployment, consider the requirements for sharing data and the network resources (such as shared folders) when choosing your deployment type and server model.

combustion supports the single server model, the distributed server model, and the redundant server model.

• Autodesk License Manager (AdLM)

Installing, authorizing and starting the AdLM is the first component of any network installat ion of combustion. The AdLM and related files (located on a network share) control available licenses used by combustion. A user can run combustion only if a license is available. The AdLM is required for all deployment types.

• Deployment location

Creating and installing the deployment is the second component of any network installation of combustion. A deployment is a shared network resource where a preconfigured combustion setup program resides. A user installs combustion from a deployment on the network onto each workstation. A deployment location is required for all deployment types. You can store

Single Server Model

With the single server model, all license management takes place on a single server. Since all license management takes place on a single server, this configuration requires the least amount of maintenance.

To create a deployment using the single server model, you run the AdLM on the server you want to configure and store the deployment on the same server.

Network Configuration Models

❚❘❘

Distributed Server Model

The distributed server model is the preferred method of installing combustion in a network environment. The distributed server model allows you to place (distribute) the AdLM on more than one server. This lets you split your software licenses between multiple servers. The servers can be located at different sites, if necessary.

The distributed server model gives you more network tolerance. Since the software licenses are split among multiple servers, licenses can still be granted should one of the servers fail or run out of licenses. In addition, a distributed server requires less system administration than a redundant server model. However, if a server fails, some licenses are not available. This drawback can be resolved by adding the variable to each client workstation.

To create a deployment using the distributed server model, you install the AdLM on each server you want to configure.

This model requires a unique license file for each server. See License File

Once the network installation is complete, you install combustion on each workstation. The client installation creates a combustion.lic file on the client workstation that identifies which license server the client communicates with to obtain a network license. The client workstation tries to obtain a network license only from the server that was configured when the AdLM created the deployment location from which the client was installed.

Adding the variable to each client workstation is necessary if you want to have license carr yover. This is a key strength of the distributed server model. It allows the client workstation to automatically obtain a license from another server in the distributed server pool if one server should fail or run out of licenses.

lm_license_file environment

For example, if you installed a distributed server pool of two servers, each server has a license file for five combustion licenses. You then create six client installations that use the default combustion.lic file pointing to the first server. If all the licenses on the first server are in use, the sixth workstation that tries to obtain a license from the server will be denied, even when the second server in the pool has five available licenses.

You have two options to get the sixth workstation a license:

• Edit the combustion.lic file so the sixth workstation looks exclusively to the second server for its license.

Note:

Using this method does not give you the

benefit of network tolerance.

• Add the lm_license_file environment

variable to all the workstations so the AdLM can access any available licenses on either server. See

License File Parameters

Note:

If the

combustion.lic

lm_license_file

used, the environment variable takes priority.

file and the

environment variable are both

Redundant Server Model

With the redundant server model, you must 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. If all three servers are active and functioning properly, all software licenses are available to client workstations. A redundant server model does have some drawbacks you need to consider:

• A redundant server model should be maintained by a dedicated system administrator.

• At least two servers must be functional in order for client workstations to obt ain licenses. If two servers fail, client workstations cannot get licenses.

Network Planning Concepts

• Since the redundant server model is more

susceptible to network failure, all servers must reside on the same subnet and have consistent network communications. All servers must be located on the same site.

• Slow, erratic, or dial-up connections are not recommended when using the redundant server model.

• The redundant server model does not support the UDP packet type.

To create a redundant server pool, run the AdLM installation on the initial server you want to configure, then repeat the AdLM installation for the other two servers. 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. For additional information, see “Obtaining the Server Host Name

and ID” in Chapter 4, “License Server Configuration’’.

Once all client workstations are installed and communicating with the license server, you must modify the combustion.lic file on each client workstation to include server information for each of the three servers. Following is an example of the contents of the combustion.lic file:

SERVER PC54321 210987654321

USE_SERVER

Following is an example of a combustion.lic file modified for a redundant server operation:

SERVER PC54321 210987654321 27005

SERVER PC12345 123456789012 27005

SERVER PC32154 321543210981 27005

USE_SERVER

The redundant server model requires a port number (the default is 27005) for each server.

The port number at the end of each SERVER line must also be included in the license file for the redundant server model only.

The redundant server model requires Windows 2000 Server Edition.

Note:

Windows 2000 Workstation edition is not

supported as license servers.

The redundant server model also requires that separate copies of the same license file, license manager daemon (lmgrd), and vendor daemon reside on each server; all are necessary to authenticate and release licenses.

If the redundant server configuration fails, it might be necessary for the system administrator to start the license server on each of the redundant server machines within a few minutes of one another.

AdLM Network Communication Protocol

Once you have chosen your preferred installation configuration, you have the option of using either the TCP/IP or UDP packet types. The AdLM uses the standard network protocol—Transport Control Protocol/Internet Protocol (TCP/IP) packets by default. TCP sends data between applications whereas IP communicates data between an application and the physical network.

There is a 10-connection TCP/IP limit with Windows 2000/Windows XP Professional editions. The Windows 2000 and Windows XP Server editions do not have the 10-connection limitation, so they are the preferred Operating systems. If you have more than 10 client workstations that need to access a single license server and you do not have a Server edition of Windows, then use UDP as the default packet type. UDP requires more extensive configuration at servers and clients.

License Management

❚❘❘

combustion does not support the redundant server model if you choose to use UDP as your primary packet type with UDP packet transmission.

To use UDP packets, you must set the environment variable FLEXLM_COMM_TRANSPORT UDP on each client workstation.

License Management

Rather than purchasing a single-user license for every combustion user or workstation, you can purchase a network license for a maximum number of concurrent users, and purchase additional licenses as needed.

combustion uses either TCP (default) or UDP packets to communicate with the AdLM. You can’t configure combustion to use both packet types simultaneously. The packet type you use depends on your network environment and the number of clients assigned to a specific server.

License Operation and Availability

When a user starts combustion, the application reads the combustion.lic file located on the client workstation to determine which server it should try to obtain a license from. combustion then sends a message to the AdLM server listed in the combustion.lic file through the network protocol and requests a license. If the number of available licenses has not exceeded, the AdLM assigns a license to the user. The combustion session then starts on the workstation, and the number of available licenses is reduced by one.

The client and server communicate at regular intervals to keep track of licenses in use and manage license availability.

When a user exits combustion, the AdLM frees a license for another user. Multiple sessions on an individual workstation use only one license. When the last session is closed, the license is freed.

The following three processes direct license management:

License manager daemon (lmgrd.exe)

•

Handles the original contact with the application, then passes the connection to the vendor daemon. Lmgrd is used to communicate with the vendor daemon only and does not authenticate or dispense licenses, it passes user requests on to the vendor daemons. By using this approach, a single lmgrd daemon can be used by many different software vendors to provide license authentication. Lmgrd starts and restarts the vendor daemons as needed.

•

Autodesk vendor daemon (adskflex.exe)

Contains the server process that releases licenses. The vendor daemon keeps track of the licenses that are checked out and which clients are using them. Each vendor has a unique vendor daemon to manage vendor-specific licensing. adskflex.exe is specific to Autodesk products only. If the vendor daemon terminates for any reason, all users lose their licenses until lmgrd restarts the vendor daemon or the problem causing the termination is resolved.

•

License file

license information.

—A text file that has vendor-specific

—

If you use environment variables in a distributed or redundant server environment, these variables take precedence over the settings in the combustion.lic file.

Network Planning Concepts

License File

The license file contains licensing information provided by Autodesk, including license type, behavior, and the number of seats available for use. You obtain license file data when you register combustion.

Save each file to the C:\Program Files\Autodesk License Manager\License folder. You can name the license file anything you like, although the name must have a .lic extension, or you can append the Increment information to a Auto desk .lic file on your license server.

The license file includes information about network server nodes and vendor daemons, and an encrypted digital signature created when Autodesk generates the license file. The following is a template for the contents of a license file:

SERVER ServerName HostID

USE_SERVER

VENDOR VendorDaemon port=portnumber

INCREMENT IncrementName VendorDaemon Ve rs i o n E xp ir at i on D a te Nu mb er of L ic en se s \

VENDOR_STRING=UsageType:LicenseBehavior

SUPERSEDE DUP_GROUP=DupGroup \

ISSUED=IssueDate ck= SN=SerialNumber SIGN=

License File Parameters

The following table provides a definition for each license file parameter.

Parameter Definition

ServerName and Host ID

VendorDaemon The name of the server-side Autodesk

portnumber Reserved and assigned for use only for

IncrementName Name of the product.

Version The product release version.

ExpirationDate The amount of time the license is

NumberofLicens-esSpecifies the number of licenses (i.e.

VENDOR_STRING Defines the license configuration

SUPERSEDE Replace lines in a license file that have a

DupGroup Defines how the server does or does

IssueDate The date the license file was generated

ck= Can be used with the lmcksum utility to

SerialNumber The serial number of the Autodesk

SIGN= The encrypted signature used to

Binds the license to a particular server.

license daemon.

Autodesk products running the Autodesk/FLEXlm vendor daemon.

available.

seats) to be managed by a particular server or redundant server pool.

settings, UsageType and License Behavior.

date earlier than the defined IssueDate. The Autodesk policy for modifying a license is to re-issue the license file. Since there can be multiple INCREMENT lines, the SUPERSEDE/ ISSUED parameters are used to replace any previous product or feature of the same name.

not handle the sharing of multiple license requests. The default for this behavior is Host, which allows for multiple copies on the same computer to share the same license.

by Autodesk.

help verify that the license information has been entered correctly by the license administrator.

product.

authenticate the attributes of the license file.

License Management

❚❘❘

License File Sample for a Single or Distributed Server Model

Following is an example of a completed license file for a single or distributed server model.

SERVER pc12345 123456789012

USE_SERVER

VENDOR adskflex port=6000

INCREMENT 40800COMBUSTION_4_0F adskflex

1.000 permanent 3 \

VENDOR_STRING=commercial:permanent SUPERSEDE DUP_GROUP=UH \

ISSUED=10-Mar-2005 ck=231 SN=399-99999999 SIGN=6E88EFA8D44C

If you are using a distributed server model, adding the LM_LICENSE_FILE environment variable to each client workstation enables them to get a license from another server, should the first server fail or run out of licenses.

License File Sample for a Redundant Server Model

Following is an example of a completed license file for a redundant server model.

SERVER PC54321 210987654321 27005

SERVER PC12345 123456789012 27005

SERVER PC32154 321543210981 27005

USE_SERVER

VENDOR adskflex port=6000

INCREMENT 40800COMBUSTION_4_0F adskflex

1.000 permanent 3 \

VENDOR_STRING=commercial:permanent SUPERSEDE DUP_GROUP=H \

ISSUED=10-Mar-2005 ck=231 SN=399-99999999 SIGN=6E88EFA8D44C

Note:

The redundant server model requires the addition of a port number (the default is 27005) for each server.

The license file is required for using combustion on a network. As a result, the license file must be located on a network share that is accessible to every user that runs combustion from a network installation.

License Types

combustion deployment on a network supports two license types: Commercial and EDU/Institution (designed for educational institutions). Both license types enable permanent use of combustion.

combustion Communication with the License Server

When combustion is running, it sends a communication signal to the license server at regular intervals. If the communication signal is missed, the server tries to reconnect. If it cannot, it sends a message to the user indicating the license error.

Once the user acknowledges the message, the user can save the work in progress and can inform the systems management of the problem.

When combustion stops working because it lost a connection to the server, the user must shut down combustion and restart the program. If the problem causing the original loss of the communication signal is resolved and there are available licenses on the server, the program starts working again.

Note:

If you are using the redundant server model, the communication signals are passed between redundant servers.

Network Planning Concepts

Installation

Summary

FLEXlm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Setting up the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Silently Installing combustion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installation

This chapter provides information for installing

and configuring combustion and the Autodesk

License Manager on a network.

FLEXlm

The Autodesk License Manager (AdLM) that uses the FLEXlm license management technology must be fully registered and functional before clients can obtain licenses.

If there is another Autodesk FLEXlm product installed on the workstation where you intend to install AdLM, stop the FLEXlm service before installing the AdLM files and tools and proceed with the following guidelines.

There is no grace period when using the FLEXlm license manager.

Using combustion with other FLEXlm Network Products

Yo u c a n s e r v e li c en se s fo r m u lt ip l e A ut od e sk products from one workstation. However, only one FLEXlm service can run at any given time on any given license server.

To allow a single FLEXlm service to read multiple license files:

1. If there is a FLEXlm service running, stop it via

the Windows Services utility.

2. Place all the license files in the ...\Autodesk

Network License Manager\License\ folder.

3. Go to the Start menu and choose Programs |

Autodesk License Manager | Tools | LMTOOLS.

4. Click the Service/License File tab and click

Configuration Using Services.

5. Click the Config Services tab and in the Path to

the license file field, enter a license path (for example, ...\Autodesk Network License Manager\License\) instead of a license filename (for example, ...\Autodesk Network License Manager\License\licname.lic).

6. Restart the FLEXlm service.

Note:

You can serve licenses for other FLEXlm products. Non-Autodesk products licensed via FLEXlm utilize unique vendor daemon/license files/ NT License Services. In this case, you may have two or more FLEXlm services running on any given license server.

Setting up the Network

The type of combustion installation you choose to deploy can differ depending on your network infrastructure and requirements for client use.

To plan for a network installation:

1. Ensure your network, servers, and workstations

meet the recommended basic system requirements. See “System Requirements” in

Chapter 1, “Requirements’’.

2. Choose a network installation that works best for

your users. See “Network Configuration Models”

in Chapter 2, “Network Planning Concepts’’.

3. Contact Discreet to receive a license file. See

“Obtaining and Setting Up a License File” in Chapter 4, “License Server Configuration’’.

4. Configure the License Server. See Chapter 4,

“License Server Configuration’’.

5. Create a network share to hold the deployment

image files and ensure to provide read/write access to all users who will install combustion from this share.

Silently Installing combustion

❚❘❘

To run the AdLM manually:

1. Insert the combustion 4 program installation

CD into the CD-ROM drive.

If AutoPlay is enabled on your system, the combustionSetup.exe begins automatically.

2. Hold down the Shift key or right-click to prevent

AutoPlay from starting the installation of combustion. If AutoPlay is not enabled, proceed to the next step.

3. On the combustion 4 program installation CD,

go to the Network Licensing folder and run the setup.exe to install the AdLM.

Yo u c a n r u n t h e setup.exe as necessary to create varied client deployment images to meet user requirements and company needs.

Creating a Deployment Image

Creating a deployment image enables you to deploy combustion on a network. Deployment images must be located on a networ k share t hat is acce ssible by a ll client workstations that require combustion.

1. Copy the contents of the combustion 4 program

installation CD to a shared folder.

2. Create a combustion Settings.ini file and copy it

to a shared folder. See the information after the next table.

3. Inform the users that the network deployment is

complete and provide them with instructions.

4. Do one of the following:

• Ask each user to run the combustionSetup.exe file from the shared folder.

• Create a script to install combustion automatica lly on all machines. See the next section.

Silently Installing combustion

You can choose to silently deploy combustion on a network using the command-line interface.

The following command silently installs combustion 4 on a network:

%Comspec% /c combustionSetup.exe -s

%Comspec%

is an env iro nme nt v ar iab le pr ovi ded b y Windows. It points to the command interpreter, cmd.exe.

/c is a switch passed to cmd.exe telling the shell to

wait until the command completes before proceeding. Without this switch, the shell executes subsequent commands before the current command finishes.

combustionSetup.exe is the combustion installer.

-s instructs the installer to run silently, without user

interface.

You can specify options by using an .ini file. By default, the combustion installer looks for the

Settings.ini file located in the same directory as the combustionSetup.exe file.

Following are the properties and their default values. If a property is not set, the installer uses the default values.

Options Default Values Description

TargetDir C:\Program

LicenseType 1 1=standalone

SerialNumber

ShortDesktop 1 1 or 0 to install or not

InstallBackburner 1 1 or 0 to install or not

InstallHelp 1 1 or 0 to install or not

InstallDirectX 1 1 or 0 to install or not

Files\Discreet\ combustion 4

—

combustion install directory

license, 0=network license

Product serial number

a shortcut on the desktop

backburner

the Help files

DirectX

Installation

For example, if you want to set a new directory for installing combustion, and use a network license with the serial number 123-12345678, you need to make three entries to the Settings.ini file in the variables section:

[Variables]

0=TargetDir||c:\Program Files\

discreet\newDirectory

1=LicenseType||0

2=SerialNumber||123-12345678

If the combustion.lic file is present in the same directory as the combustionSetup.exe file, the combustion.lic file is copied to the Ta r g e t D i r folder.

The combustion.lic file is required for combustion to find the network license. combustion sends a message to the AdLM server listed in the combustion.lic file through the network protocol and requests a license. See “Obtaining and Setting Up a

License File” in Chapter 4, “License Server Configuration’’.

If combustion is already installed, invoking

combustionSetup.exe -s reinstalls

combustion 4.

Silently Uninstalling combustion

The following command silently removes combustion 4:

%Comspec% /c %Windir%\unvise32.exe -s C:\Program Files\discreet\ combustion 4\uninstal.log

%Windir%\unvise32.exe

which is copied to the %Windir% ( c:\Windows or c:\WINNT) when combustion is first installed.

-s instructs the installer to run silently, without user

interface.

is the vise uninstaller

C:\Program Files\discreet\combustion 4\uninstal.log

is the path to the uninstal.log file

in the combustion 4 installation folder.

Sample Batch File to Install combustion

If you share the CD-ROM drive or a copy of the image on a networked PC, you can use the same batch file for all the workstations on your network. For example, if your workstation name is pc1 and you copied the entire contents of cd1 to a folder you shared as \\pc1\combustion 4disc1

In that folder you can create in the \\pc1\combustion 4disc1 folder the Settings.ini file and set the options you want.

The installation batch routine would look like:

REM Combustion 4

%Comspec% /c combustionSetup.exe -s

Deploying combustion on a Network

Now that you have a batch routine that you tested on your local workstation, you are ready to install combustion on all the other network rendering workstations.

Instead of going to each workstation and run your batch routine

\\pc1\myshare\install_combustion4. bat

enter

At \\pc2 4:30 /INTERACTIVE \\pc1\myshare\install_combustion4.ba t

to install combustion on workstation pc2.

If y ou st ill have ma ny wor kst atio ns to set up, you can break out a scripting language with some kind of for loop and… enter

Silently Installing combustion

❚❘❘

foreach (3..100)

system qq(At \\pc${_] 4:30 / INTERACTIVE \\pc1\myshare\install_combustio n4.bat

}

{

Another way to do it would be to copy the batch file to each workstation startup folder, and when a user logs in, the batch file runs, and soon thereafter the user runs combustion 4.

Installation

License Server Configuration

Summary

Obtaining the Server Host Name and ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Obtaining and Setting Up a License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

License Server Configuration

This chapter provides information for

configuring the FLEXlm license server and for

modifying a license server configuration.

Obtaining the Server Host Name and ID

There are three steps for configuring the license server. You obtain the server host name and ID, set up a license file, and configure the server.

Configuring the license server requires a thorough understanding of the network configuration model you plan to deploy. See “Network Configuration

Models” in Chapter 2, “Network Planning Concepts’’.

To obtain the host name and ID, you must run the lmtools.exe installed by the AdLM Setup.exe.

To obtain the host name and ID:

1. Do one of the following:

• Choose Start | Programs | Autodesk Network License Manager and select LMTOOLS.

• Go to the directory where you installed the AdLM (the default path is C:\Program Files\Autodesk Network License Manager) and select lmtools.exe.

2. Click the Systems Settings tab.

3. Do one of the following:

• Write down the Computer/Hostname and the Host ID (Ethernet Address).

• Click Save HOSTID Info to a File.

4. In the Network Setup wizard, enter this

information on the Server Configuration page.

5. Click Next to continue.

Obtaining and Setting Up a License File

The license file identifies important licensing information, including license type, and the number of seats available for use.

To obtain a license file:

1. Obtain the following information:

• Product serial number(s).

• Servername.

• Host ID number.

• An email address where Discreet can send the

license file.

2. Provide the information to the Discreet

Registration and Authorization office.

Refer to the “Read This First” card for information about contacting the Discreet Registration and Authorization office.

The Registration and Authorization office will email you the license file in text format.

To set up a license file:

1. Copy the contents of the license file (you received

from Discreet via e-mail) to a text editor.

2. Save the file to the AdLM default directory

C:\Program Files\Autodesk Network License Manager\License or in the License folder in the

directory where you installed the AdLM.

3. Save the file as combustion.lic file.

Note:

If your server has more than one Ethernet adapter, select one that corresponds to a physical network adapter.

5. Choose File | Exit.

Note: You can name the license file anything you

like. However, the name must have a .lic or .dat extension.

The combustion.lic file is used to configure the server.

Configuring the Server

❚❘❘

Configuring the Server

You configure the license server with the lmtools.exe utility.

To configure the License server:

1. Do one of the following:

• Choose Start | Programs | Autodesk Network License Manager and select LMTOOLS.

• Go to the directory where you installed the AdLM (the default path is C:\Program Files\Autodesk Network License Manager) and select lmtools.exe.

2. Click the Service/License File tab.

3. Click Configuration using Services.

4. Click the Config Services tab.

5. In the Service Name drop-down list, verify that

the service you want to use to manage combustion licenses is selected.

Note:

If you have more than one software vendor using FLEXlm for license management, this dropdown list will have more than one option.

6. Enter the path to the license manager daemon

(lmgrd.exe). The default path where this daemon is installed is C:\Program Files\Autodesk Network License Manager folder.

Note:

If you are using distributed servers, the location of the license manager daemon and the license file can vary depending on your configuration.

9. To st a rt lmgrd.exe automatically when the system

starts, enable Start Server at Power Up.

10.To r un lmgrd.exe as a Windows 2000 service,

enable Use Services.

11.Click Save Service to save the new configuration

under the service name specified in step 5.

12.Click the Start/Stop/Reread tab.

13.Click Start Server to start the license server.

The license server is running and ready to respond to client requests.

If there are multiple service names, you must click the Service/License File tab, click the Config Services tab, then select the service name. For each service name, perform steps 12 and 13 to start the service.

Note:

When using the lmtools options to start the server or stop the server, the status line displays "Starting server" or "Stopping server" and does not change.

14.To confirm that the action has been successfully

completed, use the Windows Task Manager.

Note:

If you stop the license server and start up a

different license server, you must provide a new

combustion.lic

a new dialog box is displayed. If you choose Specify The License Server,

file for each client. If you don’t provide

combustion.lic

file, the FLEXlm License Finder

combustion

fails.

7. Enter the path to the license file. See Obtaining

and Setting Up a License File.

8. Enter the path where you want the debug log to be

located.

Note:

This file is not created by default, so create a

text file if you wish to use this option.

License Server Configuration

Administration

Summary

License Server Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Using the FLEXlm Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Using the License Configuration Switcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Administration

This chapter provides information for

maintaining a combustion installation on a

Note:

When using the lmtools options to start the server or stop the server, the status line displays "Starting server" or "Stopping server" and does not change.

network.

License Server Failure

If a license server fails, current sessions of combustion continue to run for a period of time, but new sessions cannot be started until the server is restored.

If combustion cannot continue because a license server is unavailable, when the user acknowledges the loss of connection to the license server, the user is given the opportunity to save the work-inprogress.

If a file was opened from a network drive and the network drive is no longer available, combustion cannot save the file.

To start the license server manually:

1. Do one of the following:

• Choose Start | Programs | Autodesk Network License Manager | Tools and select LMTOOLS.

• Go to the directory where you installed the AdLM (the default path is C:\Program Files\Autodesk Network License Manager) and select lmtools.exe.

2. Click the Service/License File tab.

3. Click Configuration using Services.

4. Click the Config Services tab.

5. In the Service Name drop-down list, verify that

the service you want to use to manage combustion licenses is selected.

6. Click the Start/Stop/Reread tab.

7. Click Start Server to start the license server.

8. To confirm that the action has been successfully

completed, use the Windows Task Manager.

See Chapter 4, “License Server Configuration’’.

See “Troubleshooting Problems” in Chapter 6,

“Networking Quick Start and Troubleshooting’’.

Using the FLEXlm Configuration Tools

FLEXlm provides two utilities, lmtools.exe and lmutil.exe, for managing the license server. These tools are located in the C: \Program Files\Autodesk Network License Manager folder. lmtools.exe

provides a Windows graphical interface for managing the license server. lmutil.exe provides a set of command-line options for managing the license server.

You can use lmtools.exe and lmutil.exe to perform the following server-management tasks:

• Start, stop, and restart the server.

• Configure and update the license file.

• Diagnose system or license problems.

• View server status, including active license status.

For additional information about using FLEXlm configuration tools, see the online FLEXlm information located in the C:\Program

Files\Autodesk Network License Manager\Docs\FlexUser.

Using the License Configuration Switcher

❚❘❘

Creating an Options File

Another useful component of FLEXlm is the Options file. This file is created by the network administrator to set configuration options specific to the operating environment. You can use the Options file to set parameters for the following server-related features:

Report Log File

•

encr ypted fi le that generate s accurate usa ge reports on license activity for use by SAMreport-Lite.

•

License Server Groups

servers to work concurrently and share license pools.

•

License Timeout

inactive license is reclaimed by the combustion vendor daemon. This setting allows the license server to releases licenses automatically after a set period of inactivity.

If you set up an Options file to generate a report log, the path to the report log file must not contain spaces unless you enclose the path name in quotation marks. If the path name does contain spaces, the log file may be created in the root folder (for example, C:\Program Files), and the license manager service wil l fa il to st ar t. I f th is h appe ns, del ete the root fol der fi le c reate d (for exa mple , "Program Files" at C:\). You can then set the path with quotation marks or without spaces.

—To create a compressed,

—To configure license

—To set the time after which an

Using the License Configuration Switcher

The default combustion configuration is the standalone configuration. With the License Configuration Switcher, you can “switch” the combustion configuration to use a standalone license or a network license through the use of an initialization file.

If an initialization file is found in the combustion 4 program installation CD in the Network Licensing folder and contains a line stating the type of licensing to use, the installer will create a registry key telling combustion which licensing scheme to use.

To switch from a network license to a standalone license:

1. Go to the directory C:\Program

Files\Discreet\combustion 4\ and double-click the LicenseSwitcher.exe.

2. In the combustion License Manager Setting

dialog, click Standalone and click OK.

The change will take effect the next time you launch combustion.

Note:

The syntax used in setting up a FLEXlm

Options file is case-sensitive.

For additional information about creating an Options file, see the online FLEXlm information located in the C:\Program Files\Autodesk Network License Manager\Docs\FlexUser.

Administration

Networking Quick Start and Troubleshooting

Summary

FLEXlm Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Obtaining Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Identifying the Server Name and Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Handling the License File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the FLEXlm Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Troubleshooting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Networking Quick Start and Troubleshooting

This chapter provides information on installing

a network license manager for combustion, and

on troubleshooting problems that may arise.

FLEXlm Defined

FLEXlm is developed by GLOBEtrotter Software, Inc. It is the technology for the network license manager used by the combustion 4 product. FLEXlm provides utilities that make the management of network licenses much easier. combustion and FLEXlm are separate applications. The Autodesk implementation of FLEXlm works via a Windows Service.

The network license manager is supported only on the following operating systems:

• Windows 2000 Professional

• Windows 2000 Server

• Windows 2000 Advanced Server

• Windows NT Workstation

• Windows NT Server

• Windows XP Professional

• Windows XP Server

• Windows XP Advanced Server

Obtaining Authorization

Before you can begin using the AdLM software, you need to email Autodesk the registration information so the license can be installed on the server.

Note:

There is no grace period that will allow you to run AdLM while you’re waiting for your FLEXlm license.

To obtain a valid license for running AdLM, you need to send Autodesk information about your software and system. You will need to send the following information:

• Product serial number(s). The serial number is

located on a sticker on the combustion product box.

• Server name (system name).

• Host ID number (Ethernet Address).

• An e-mail address where Autodesk can send the

license file.

• Registration information (Name, Address, Phone).

When you have all the necessary information, contact the Autodesk Registration and Authorization office. The Autodesk Registration and Authorization office can be reached at the following:

E-mail: authcodes@autodesk.com

Phone: 1.415.507.4690

Internet: http://www.autodesk.com/register

Note:

Requesting an authorization code via email is the preferred method.

Identifying the Server Name and Host ID

❚❘❘

Identifying the Server Name and Host ID

To g et a l ic en se fo r combustion, two pieces of data you need to provide the Server Name and Host ID. You can find your system’s server name and host ID by using the lmtools utility.

To obtain the host name and ID:

1. Do one of the following:

• Choose Start | Programs | Autodesk Network License Manager | Tools and select LMTOOLS.

• Go to the directory where you installed the AdLM (the default path is C:\Program Files\Autodesk Network License Manager) and select lmtools.exe.

2. Click the Systems Settings tab.

3. Do one of the following:

• Write down the Computer/Hostname and the Host ID (Ethernet Address).

• Click Save HOSTID Info to a File.

Note:

If your server has more than one Ethernet adapter, select one that corresponds to a physical network adapter.

5. Choose File | Exit.

4. Copy and paste the Computer/Hostname and the

Host ID (Ethernet Address) into your email for obtaining authorization.

Handling the License File Information

After you send your system information to Autodesk Registration and Authorization, you will receive license file information as part of an email. The FLEXlm server reads the license file information from a file on the hard disk, so you need to copy the information from the email and save it in a file.

Copy the contents of the license file (from the email) to a text editor such as Notepad.

sample contents:

SERVER mysystem 0012b59bb36a

USE_SERVER

VENDOR adskflex port=2080

INCREMENT 42100COMBUSTION_5_0P adskflex 1.000 permanent 100 \

VENDOR_STRING=educational SUPERSEDE DUP_GROUP=h \

ISSUED=09-oct- option=142 SIGN=33BDF7945532

5. Save this file in the AdLM default directory

C:\Program Files\Autodesk Network License Manager\License or in the License folder in the

directory where you installed the AdLM.

6. Save the file as combustion.lic file.

Note: You can name the license file anything you

like. However, the name must have a .lic or .dat extension.

The combustion.lic file is used to configure the server.

▲

Do not use a product such as Microsoft Word for editing the license file information because it may introduce formatting that will cause the license to become invalid to LMTools.

Configuring the FLEXlm Server

After you have a license file saved, you need to configure your FLEXlm server.

1. Do one of the following:

• Choose Start | Programs | Autodesk Network

License Manager | Tools and select LMTOOLS.

• Go to the directory where you installed the AdLM

(the default path is C:\Program Files\Autodesk Network License Manager) and select lmtools.exe.

2. Click the Service/License File tab.

3. Click Configuration using Services.

Networking Quick Start and Troubleshooting

4. Click the Config Services tab.

5. In the Service Name drop-down list, verify that

the service you want to use to manage combustion licenses is selected.

Note:

If you have more than one software vendor using FLEXlm for license management, this dropdown list will have more than one option.

By default, the service is named “FLEXlm Service 1”. All Autodesk products will have to use the same service, so consider naming the service something recognizable and sensible to you, like “Autodesk Product Licenses.” Whatever the name, simply type it in this field.

6. Enter the path to the license manager daemon

(lmgrd.exe). The default path where this daemon is installed is C:\Program Files\Autodesk Network License Manager folder.

Note:

If you are using distributed servers, the location of the license manager daemon and the license file can vary depending on your configuration.

7. Enter the path to the license file. The default path

where the license file is saved is C:\Program Files\Autodesk Network License Manager\License

or in the License folder in the directory where you installed the AdLM.

8. (Optional) Enter the path where you want the

debug log to be located. You will first have to create a text file to contain logging information.

9. To s ta r t lmgrd.exe automatically when the system

starts, enable Start Server at Power Up.

Note:

Use Services must be active before you can turn on Start Server At Power Up.

10.To ru n lmgrd.exe as a Windows 2000 service,

enable Use Services.

11.Click Save Service to save the new configuration

under the service name specified in step 5.

12.Click the Start/Stop/Reread tab.

13.Click Start Server to start the license server.

After a few seconds, the license server will be running and ready to respond to client requests.

14.Ensure each client workstation can connect to the

server, and that each client workstation has a copy of combustion configured to look for network licenses.

Troubleshooting Problems

This section presents suggestions for avoiding and troubleshooting installation and startup issues that may arise when you install or start combustion from a network or client deployment image.

This document is arranged by network issues divided into two categories: License Management and Program Execution. In each category, a description of how the program is designed to function is provided as well as possible problems and their resolutions.

This information applies to all Autodesk products that use AdLM with FLEXlm technology. For simplicity, the chapter refers to, but is not limited to, combustion.

License Management

combustion uses the new Intel port of the AdLM. AdLM is a software-based TCP/IP dependent license management system. This means that no external authentication devices are required, and that Microsoft TCP/IP must be installed and configured on all combustion workstations and license servers.

Once the AdLM has been installed, the following steps must be performed in a specific order before it will be available to issue licenses to combustion workstations.

Troubleshooting Problems

❚❘❘

Configure TCP/IP before proceeding, then follow the steps in Configuring the FLEXlm Server

The AdLM runs diagnostics and then goes online. The diagnostics may take as long as three minutes to run. When the network version of combustion is started on a workstation, combustion responds by first sending a broadcast to the local network segment to look for a license server with a free combustion license. If a license server is found, a license is checked out from the server, and combustion will start on the workstation. If a license server resides in a different network segment from the workstation, the license server will not be found unless the ACADSERVER environment variable is set to include the license server’s hostname on each combustion workstation. A workstation may be restricted to pulling licenses from specific license servers by the prefix symbol @ to the hostname listed in the ACADSERVER value. Using the @ symbol effectively disables the broadcast method of finding a license server. Following are potential problems that can occur and their solutions:

• The License Manager Service does not start.

Cause Solution

The AdLM is run on the wrong platform.

Microsoft TCP/IP is not installed or is improperly configured.

The AdLM was not launched from the Start/ Stop/ Reread panel of lmtools.exe.

The AdLM requires Windows 2000 or Windows NT running on an AMD or Intel-compatible processor running 300 MHz or higher.

The AdLM requires TCP/IP to operate. Verify the TCP/IP configuration by using the PING command at a DOS command prompt.

Start lmtools.exe, go to the Start/Stop/ Reread tab, and press “Start server”.

• AdLM will not issue licenses for three minutes after

startup.

Cause Solution

The default diagnostic time setting for the AdLM is three minutes; it does not issue licenses during this time.

This is normal operation. While it is possible to set the diagnostic time to a shorter time period, Discreet does not recommend it.

• AdLM is running but combustion cannot find a

license server.

Cause Solution

TCP/IP name resolution is not configured.

The system date and time are incorrect.

The license server is in a different subnet from the workstation.

Try using the PING command at a DOS prompt. The syntax of the PING command is ping <hostname>. If you cannot successfully "ping" the license server from a and "ping" the workstation from the license server, the AdLM will not work. Name resolution may be accomplished in a variety of ways on a Microsoft TCP/ IP network. The simplest method to provide name resolution is to create a hosts file with entries for all workstations on the network, and copy it to the \winnt\system32\drivers\etc folder on Windows 2000 and NT systems. Windows 2000 and Windows NT come with a sample hosts file located in the proper destination folder for that operating system.

Verify that the date and time are correct on all workstations, and that they are synchronized with the AdLM station. The AdLM will not issue a license to a workstation that has an invalid date.

Set the ACADSERVER environment variable value to contain the hostname of the license server so that can connect to a license server on another subnet. To set ACADSERVER to multiple license servers, separate each hostname with a semicolon. Consult your operating system documentation on how to properly set an envi ronment variable. The value of an environment variable can be confirmed by typing set |more at a DOS command prompt.

combustion

workstation

combustion

Networking Quick Start and Troubleshooting

Cause Solution

The key code was obtained prior setting up TCP/IP.

The "@" symbol prefix limits the license server search.

The AdLM server(s) is(are) out of licenses.

A license resource file may be preventing a workstation or user from obtaining license access.

Network routers are not configured for TCP/IP.

A server code generated by the AdLM Admin program prior to TCP/IP setup will be invalid. Key codes generated with invalid server codes will also be invalid. Regenerate the server code after TCP/IP configuration and obtain a new key code.

If the license server hostname is prefixed with an @ symbol (for example: @paradise), only poll that license server for a license. You can specify a list of hosts names, each prefixed with @ and separated with a semicolon, to create an exclusive group from which a workstation can pull licenses. For example, if ACADSERVER is set to @ paradise; @island; @birdcage,

combustion

licenses from the AdLM servers running on paradise, island, or birdcage even if there are other AdLM servers running on the same subnet.

If all licenses authorized on an AdLM server are in use, it will not allow additional workstations to start

combustion

or AdLM Report to view license utilization on AdLM servers.

To check if a license resource file is in use for a particular AdLM server, double-click the AdLM icon in Windows Control Panel and click the Settings button. If a license resource file is in use, the file name and path will be listed in the Settings dialog box.

Routers must be configured to route or bridge IP packets and pass UDP/TCP port data. AdLM uses UDP and TCP port number 1422. If routers are configured to route IP packets, the ACADSERVER environment variable setting is required on workstations residing on the remote side of the router.

combustion

will only be able to pull

. You can use AdLM Query

will

Cause Solution

The TCP/IP gateway is not set.

The server code has changed.

If routers are used, their TCP/IP addresses must be entered as a gateway on the IP Address tab in the Microsoft Control Panel TCP/IP Setup dialog box on all workstations, file servers, and AdLM servers. If you cannot ping any systems on the remote side of a router, it is an indication that the router has not been entered as a gateway.

AdLM authorization codes are tied to the server code that is displayed when you run AdLM Admin. You must generate the server code on the machine that is the license server as t he code will be unique to each machine. Hardware or network changes can cause the server code to change on a machine. If a new network card is installed or the system board is changed, check the server code for change. Updating the hostname or IP address of an AdLM server can also cause the server code to change. If the Se rv er c od e ch an ges , y ou mus t o bta in a new network authorization code from the Autodesk Registration and Authorization office, based on the new server code.

Troubleshooting Problems

❚❘❘

Executing combustion

Once the AdLM is configured and a deployment is installed to a workstation, you can start combustion by double-clicking the combustion icon placed on your desktop during the deployment installation. combustionwill automatically configure itself on initial startup if it does not find a configuration file. Following are potential problems that can occur and their solutions:

• combustion will not start.

Cause Solution

combustion

on the wrong platform.

combustion

to run in standalone mode.

is run

combustion

Windows XP running on an AMD or Intel-compatible processor running 850 MHz or higher.

is set

Go to C:|Program Files\Discreet\ combustion 4 and double-click the LicenseSwitcher.exe. Verify that the “network” radio button is selected. If prompted for a network license server, enter the hostname of the license server you want to use for that client.

requires Windows 2000 or

Troubleshooting License Errors

Following are some quick troubleshooting steps to execute at the client side or server side in the event that a license is not obtained. At the end of this section there is a brief list of common client-side errors.

• At the client: Start a command prompt and type

ping -t license [server name].

For example, type

ping -t combustionlicenses

This tests simple TCP/IP hostname resolution between the client and server.

• At the client: Check that the client is in fact looking for a license from the correct server. Start the Registry Editor,

HKEY_LOCAL_MACHINE > SOFTWARE > FLEXlm License Management.

Verify that the ADSKFLEX_LICENSE_FILE data matches the correct license file. Then verify that the server listed in the license file is the correct server.

• At the client and server: Ensure that any difference between date/time properties at the client and server is no greater than 24 hours.

• At the server: Ensure that the FLEXlm service is started, and that its type is set to "automatic." By default, the FLEXlm service is named "FLEXlm service 1".

• At the server: Start Menu | Programs Files | Autodesk Network License Manager | Tools | LMTOOLS. In the Service/License File tab, choose Configuration Using Services. In the Server Status tab, click Perform Status Inquiry. From the information in the status report, the following five lines indicate that licenses are being served:

license server name: license server UP (MASTER) v7.1

Vendor daemon status (on license server name):

adskflex: UP v7.1

Feature usage info:

Users of 40800COMBUSTION_4F: (Total of 5 licenses available)

Common Client Errors

Following is a list of common client errors.

[1.5.-4] Licensed number of users already reached.

[1.5.-10] Feature has expired.

[1.5.-18] License server does not support this feature.

[1.5.-21] License file does not support this version.

[1.5.-34] Clock difference too large between client and server.

Networking Quick Start and Troubleshooting

Glossary

adsflex.exe

The Autodesk vendor daemon used with the FLEXlm license technology. The adsflex.exe keeps track of the licenses that are checked out and the workstations that are using the licenses.

ADSKFLEX_LICENSE_FILE

In a distributed license server configuration, the environment variable used to point a client workstation to the distributed license servers.

client deployment

Also called a thick-client installation, an installation in which combustionSetup.exe resides on the client workstation.

combustion.lic

The client installation creates a combustion.lic file on the client workstation that identifies which license server the client communicates with to obtain a network license. In b oth single and redundant ser ver configurations, the combustion.lic file is used to point the client workstation to the FLEXlm license server. combustion sends a message to the AdLM server listed in the combustion.lic file through the network protocol and requests a license. The combustion.lic file is located in the root installation folder.

daemon

A process that runs in the background of a computer, doing automated processing. combustion uses two daemons: the vendor daemon (adeskflex.exe) and the master daemon (lmgrd.exe).

debug log file

A file used with FLEXlm to log connection activity (such as license failure or starting and stopping) between the AdLM and the client workstation.

deployment

The files and folders created on a server and used by client workstations to install combustion. The deployment must be located on a network share that all client workstations can access.

distributed server

The distributed server model is the preferred method of installing combustion in a network environment. This license server configuration option allows several servers to manage license distribution. Each distributed license server has a unique license file and a fixed number of licenses. If one distributed license server fails for any reason, the other servers are still able to distribute their licenses.

Ethernet address

The unique hardware address of a network adapter. Also known as Host ID.

Glossary

❚❘❘

FLEXlm

The GLOBEtrotter Software license management technology implemented in combustion. FLEXlm provides administrative tools that help simplify management of network licenses.

Host ID

The Host ID is a hardware address that uniquely identifies each node of a network. It is also referred to as the Ethernet Address. This information is used when creating the combustion.lic file, which resides on the client workstation and identifies the AdLM server from which the client will obtain a network license.

Host name

The TCP/IP name associated with a computer. FLEXlm technology uses the host name as a parameter and must be distinguished from the NetBIOS (server) name.

license server

A server that contains the AdLM. The License Server is configured with the lmtools.exe utility.

lmgrde.exe

The license manager daemon, it handles the original contact with combustion, and then passes the connection to the vendor demon adskflex.exe. Lmgrd.exe is used to communicate only with the vendor daemon and does not authenticate or dispense licenses. It passes user requests on to the vendor daemons.

lmtools.exe

One of two FLEXlm utilities used for managing the license server. Lmtools.exe provides a graphical user interface utility used to administer the FLEXlm license technology on the license server. (Lmutil.exe is the command-line version of this utility.)

lmutil.exe

One of two FLEXlm utilities used for managing the license server. A command-line utility used to administer the FLEXlm license technology. (Lmtools.exe is the graphical user interface version of this utility.)

license file

The License File is used with FLEXlm and it controls the number of seats available for use. The license file contains licensing information provided by Autodesk. You obtain license file data when you register combustion. This file must be in plain ASCII text format.

master daemon

One of two daemons used by combustion. The master daemon (lmgrd.exe) handles the original contact with combustion, then passes the connection to the vendor daemon. The master daemon is used to communicate with the vendor daemon only and does not authenticate or dispense licenses, it passes user requests on to the vendor daemons.

Glossary

network deployment

An installation in which combustionSetup.exe resides on a server.

Network License Manager

The technology used by Autodesk for network license management.

Options file

The file used by the FLEXlm to control license manager parameters such as reserving licenses and creating report logs used with SAMreport-Lite. This file is created by the network administrator to set configuration options specific to the operating environment.

SAMreport-Lite

A version of GLOBEtrotter’s SAMreport reporting tool. It is included on the combustion 4 installation CD. Using SAMreport-Lite, you can generate a network license-usage report for Discreet software that uses FLEXlm licensing technology.

server name

The NetBIOS computer name. It is often the same as the computer’s host name.

vendor daemon

One of two daemons used by combustion. The vendor daemon keeps track of the licenses that are checked out and the workstations that are using the licenses. See also, adeskflex.exe.

redundant server

A license server configuration option in which three servers are used to administer licenses. The redundant servers share a license file and a pool of licenses. The redundant server pool remains functional as long as two of the three servers are running.

report log file

Used with FLEXlm and SAMreport-Lite. The Report Log File provides information about network license usage.

Autodesk COMBUSTION-4 - Acad Full-seat Windows Version, Combustion 4 discreet Network Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Table of Contents

Requirements

System Requirements

Network Installation Components

Autodesk License Manager

FLEXlm Tools

combustion License Configuration Switcher

SAMreport

Network Planning Concepts

Network Configuration Models

Single Server Model

Distributed Server Model

Redundant Server Model

AdLM Network Communication Protocol

License Management

License Operation and Availability

License File

License File Parameters

License File Sample for a Single or Distributed Server Model

License Types

combustion Communication with the License Server

Installation

FLEXlm

Using combustion with other FLEXlm Network Products

Setting up the Network

Silently Installing combustion

Creating a Deployment Image

Silently Uninstalling combustion

Sample Batch File to Install combustion

Deploying combustion on a Network

License Server Configuration

Obtaining the Server Host Name and ID

Obtaining and Setting Up a License File

Configuring the Server

Administration

License Server Failure

Using the FLEXlm Configuration Tools

Using the License Configuration Switcher

Creating an Options File

Networking Quick Start and Troubleshooting

FLEXlm Defined

Obtaining Authorization

Identifying the Server Name and Host ID

Handling the License File Information

Configuring the FLEXlm Server

Troubleshooting Problems

License Management

Executing combustion

Troubleshooting License Errors

Common Client Errors

Glossary