Autodesk COMBUSTION-4 - Acad Full-seat Windows... Installation and maintenance instructions

del
11 March 2005

© Copyright 2005 Autodesk Canada Co./Autodesk, Inc. All Rights Reserved.
This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose.
AUTODESK CANADA CO./ AUTODESK, INC. MAKES NO WARRANTY, 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, Multi-
Master 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.
Title: combustion® 4Network Administrator’s Guide for Microsoft® Windows®
Part Number: NA
Software version: 4
Document version: 4.0
Date: 11 March 2005

iii
Table of Contents
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

Table of Contents
toc
iv
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

1
Requirements
Summary
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Network Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Requirements
1
2
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
® Licensing Manager
(AdLM), ensure your network, servers, and client
workstations meet the minimum recommended
requirements for network installation. Refer to the
following table for the server hardware and software
requirements.
Refer to the following table for the client workstation
minimum recommended hardware and software
requirements.
License Server
Hardware /
Software
Requirements Notes
Operating
system
Windows NT ® ,
Windows 2000, or
Windows XP
AdLM supports
Ethernet network
configurations only.
Network
interface card
Compatible with
current Ethernet
network infra-
structure
AdLM supports
multiple network
interface cards.
Communication
Protocol
TCP/IP By default, AdLM
uses TCP packet
types. Optionally,
you can configure
UDP packet types.
Client
Workstation-
combustion
Hardware /
Software
Requirements Notes
Processor Intel® Pentium® III,
Pentium 4, or AMD®
Athlon™ XP
CPU, 850 MHz or
higher.
Operating
system
Microsoft
® Windows
2000 or Windows XP
It is recommended
that you install and
run combustion on
an on an English
version of the
operating system.
You must have
Administrator
permissions to
install combustion .
Not assigning these
permissions can
cause combustion
and third-party
applications to
perform incorrectly.
See Windows Help
for information
aboutassigning user
permissions.
Hard drive 20 GB main hard drive,
approximately 142
MB free space
See the combustion
4 Installation Guide
for details.
RAM 256 MB —
Video Video display card
with 32 MB of VRAM
(1024x768 display
with 24-bit color
minimum required)
—
CD-ROM Any speed For installation only.
Network inter-
face card
Compatible with
current Ethernet
network
infrastructure
Required for
installing and
running network
versions of
combustion .
Web browser Microsoft Internet
Explorer 6 or later
—

Network Installation Components
3
❚❘❘
Network Installation
Components
To d e p l oy a n d c o n f i g u r e 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
SAMreport-Lite, refer to the online samlite_ug.chm
file located on the combustion 4installation 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 configuration. 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’’.
Optional Modem or access to
an Internet
connection
—
Client
Workstation-
combustion
Hardware /
Software
Requirements Notes

Requirements
1
4
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
4installation 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: www.autodesk.com/
samreportlite.

5
Network Planning Concepts
Summary
Network Configuration Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
AdLM Network Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Network Planning Concepts
2
6
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:
• Autodesk License Manager (AdLM)
Installing, authorizing and starting the AdLM is
the first component of any network installation 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
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.
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
7
❚❘❘
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 lm_license_file environment
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 lm_license_file environment
variable to each client workstation is necessary if you
want to have license carryover. 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.
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 file and the
lm_license_file environment variable are both
used, the environment variable takes priority.
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 obtain licenses. If two servers
fail, client workstations cannot get licenses.

Network Planning Concepts
2
8
• 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
9
❚❘❘
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 networkprotocol 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.
If you use environment variables in a distributed or
redundant server environment, these variables take
precedence over the settings in the combustion.lic
file.
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 —A text file that has vendor-specific
license information.

Network Planning Concepts
2
10
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 Autodesk .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 r s i o n E x p i r a t i o n D at e Nu m b e r o f L i c e n s es \
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
Binds the license to a particular server.
VendorDaemon The name of the server-side Autodesk
license daemon.
portnumber Reserved and assigned for use only for
Autodesk products running the
Autodesk/FLEXlm vendor daemon.
IncrementName Name of the product.
Version The product release version.
ExpirationDate The amount of time the license is
available.
NumberofLicens-
es
Specifies the number of licenses (i.e.
seats) to be managed by a particular
server or redundant server pool.
VENDOR_STRING Defines the license configuration
settings, UsageType and License
Behavior.
SUPERSEDE Replace lines in a license file that have a
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.
DupGroup Defines how the server does or does
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.
IssueDate The date the license file was generated
by Autodesk.
ck= Can be used with the lmcksum utility to
help verify that the license information
has been entered correctly by the
license administrator.
SerialNumber The serial number of the Autodesk
product.
SIGN= The encrypted signature used to
authenticate the attributes of the
license file.

License Management
11
❚❘❘
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 andEDU/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 tothe 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
2
12

13
Installation
Summary
FLEXlm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Setting up the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Silently Installing combustion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installation
3
14
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 l i c e n s e s f o r m u l t i p l e Au t o d e s k
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
15
❚❘❘
To run the AdLM manually:
1. Insert the combustion 4program 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 4program 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 network share that is accessible by all
client workstations that require combustion.
1. Copy the contents of the combustion 4program
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 automatically
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 4on a network:
%Comspec% /c combustionSetup.exe -s
%Comspec% is an environment variable provided by
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
Files\Discreet\
combustion 4
combustion install
directory
LicenseType 1 1=standalone
license, 0=network
license
SerialNumber — Product serial
number
ShortDesktop 1 1 or 0 to install or not
a shortcut on the
desktop
InstallBackburner 1 1 or 0 to install or not
backburner
InstallHelp 1 1 or 0 to install or not
the Help files
InstallDirectX 1 1 or 0 to install or not
DirectX

Installation
3
16
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 Tar 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 protocoland
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 is the vise uninstaller
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.
C:\Program Files\discreet\combustion
4\uninstal.log is the path to the uninstal.log file
in the combustion 4installation 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.