AutoCAD® Civil 3D 2008

Network Administrator’s Guide

April 2007
 Copyright© 2007 Autodesk, Inc.
All Rights Reserved
This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose.
AUTODESK, INC., MAKES NO WARRANTY, EITHER EXPRESS 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, INC., BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES IN CONNECTION WITH OR ARISING OUT OF ACQUISITION OR USE OF THESE MATERIALS. THE SOLE AND EXCLUSIVE
LIABILITY TO AUTODESK, INC., REGARDLESS OF THE FORM OF ACTION, SHALL NOT EXCEED THE PURCHASE PRICE, IF ANY, OF
THE MATERIALS DESCRIBED HEREIN.
Autodesk, Inc., reserves the right to revise and improve its products as it sees fit. This publication describes the state of the product at the time
of publication, and may not reflect the product at all times in the future.

Autodesk Trademarks
The following are registered trademarks or trademarks of Autodesk, Inc., in the USA and other countries: 3DEC (design/logo), 3December,
3December.com, 3ds Max, ActiveShapes, Actrix, ADI, Alias, Alias (swirl design/logo), AliasStudio, Alias|Wavefront (design/logo), ATC, AUGI,
AutoCAD, AutoCAD Learning Assistance, AutoCAD LT, AutoCAD Simulator, AutoCAD SQL Extension, AutoCAD SQL Interface, Autodesk, Autodesk
Envision, Autodesk Insight, Autodesk Intent, Autodesk Inventor, Autodesk Map, Autodesk MapGuide, Autodesk Streamline, AutoLISP, AutoSnap,
AutoSketch, AutoTrack, Backdraft, Built with ObjectARX (logo), Burn, Buzzsaw, CAiCE, Can You Imagine, Character Studio, Cinestream, Civil
3D, Cleaner, Cleaner Central, ClearScale, Colour Warper, Combustion, Communication Specification, Constructware, Content Explorer,
Create>what's>Next> (design/logo), Dancing Baby (image), DesignCenter, Design Doctor, Designer's Toolkit, DesignKids, DesignProf, DesignServer,
DesignStudio, Design|Studio (design/logo), Design Your World, Design Your World (design/logo), DWF, DWG, DWG (logo), DWG TrueConvert,
DWG TrueView, DXF, EditDV, Education by Design, Extending the Design Team, FBX, Filmbox, FMDesktop, GDX Driver, Gmax, Heads-up
Design, Heidi, HOOPS, HumanIK, i-drop, iMOUT, Incinerator, IntroDV, Kaydara, Kaydara (design/logo), LocationLogic, Lustre, Maya, Mechanical
Desktop, MotionBuilder, ObjectARX, ObjectDBX, Open Reality, PolarSnap, PortfolioWall, Powered with Autodesk Technology, Productstream,
ProjectPoint, Reactor, RealDWG, Real-time Roto, Render Queue, Revit, Showcase, SketchBook, StudioTools, Topobase, Toxik, Visual, Visual
Bridge, Visual Construction, Visual Drainage, Visual Hydro, Visual Landscape, Visual Roads, Visual Survey, Visual Syllabus, Visual Toolbox, Visual
Tugboat, Visual LISP, Voice Reality, Volo, and Wiretap.
The following are registered trademarks or trademarks of Autodesk Canada Co. in the USA and/or Canada and other countries: Backburner,
Discreet, Fire, Flame, Flint, Frost, Inferno, Multi-Master Editing, River, Smoke, Sparks, Stone, Wire.

Third Party Trademarks

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

Third Party Software Program Credits

ACIS Copyright © 1989-2001 Spatial Corp.
Copyright © 1999-2000 The Apache Software Foundation. All rights reserved. This product includes software developed by the Apache Software
Foundation (http://www.apache.org) subject to its license terms and conditions (http://xml.apache.org/dist/LICENSE.txt).
Typefaces from the Bitstream® typeface library Copyright © 1992.
HLM © Copyright D-Cubed Ltd. 1996-2006. HLM is a trademark of D-Cubed Ltd.
AutoCAD® 2008 and AutoCAD LT® 2008 are produced under a license of data derived from DIC Color Guide® from Dainippon Ink and Chemicals,
Inc. Copyright © Dainippon Ink and Chemicals, Inc. All rights reserved. DIC and DIC Color Guide are registered trademarks of Dainippon Ink
and Chemicals, Inc.
Portions of this software are based on the work of the Independent JPEG Group.
Active Delivery™ 2.0 © 1999-2004 Inner Media, Inc. All rights reserved.
ISYS and the ISYS logo are registered trademarks or trademarks of ISYS® Search Software Inc.
Copyright © 1988-1997 Sam Leffler. Copyright © 1991-1997 Silicon Graphics, Inc.
Copyright © Lingea s.r.o. 2006.
The New Features Workshop contains Macromedia Flash™ Player software by Macromedia, Inc. Copyright © 1995-2005 Macromedia, Inc. All
rights reserved. Macromedia® and Flash® are registered trademarks or trademarks of Adobe Systems Incorporated in the United States or other
countries.
Copyright © 1996-2006 Macrovision Corporation. All rights reserved.
Copyright © 1996-2006 Microsoft Corporation. All rights reserved.
Copyright © 2002 Joseph M. O'Leary.
PANTONE® Colors displayed in the software application or in the user documentation may not match -PANTONE-identified standards. Consult
current PANTONE Color Publications for accurate color.
PANTONE® and other Pantone, Inc. trademarks are the property of Pantone, Inc. © Pantone, Inc., 2004.
Pantone, Inc. is the copyright owner of color data and/or software which are licensed to Autodesk, Inc., to distribute for use only in combination
with certain Autodesk software products. PANTONE Color Data and/or Software shall not be copied onto another disk or into memory unless
as part of the execution of this Autodesk software product.
Typefaces from Payne Loving Trust © 1992, 1996. All rights reserved.
RAL DESIGN © RAL, Sankt Augustin, 2004.
RAL CLASSIC © RAL, Sankt Augustin, 2004.
Representation of the RAL Colors is done with the approval of RAL Deutsches Institut für Gütesicherung und Kennzeichnung e.V. (RAL German
Institute for Quality Assurance and Certification, re. Assoc.), D-53757 Sankt Augustin.
This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/.
The Sentry Spelling-Checker Engine Copyright © 1994-2003 Wintertree Software, Inc.
Portions of this product include one or more Boost libraries. Use of the Boost libraries is subject to its license agreement
http://www.boost.org/LICENSE_1_0.txt.

GOVERNMENT USE
Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212 (Commercial Computer
Software-Restricted Rights) and DFAR 227.7202 (Rights in Technical Data and Computer Software), as applicable.
1 2 3 4 5 6 7 8 9 10
Contents

Chapter 1 Quick Start to Network Administration . . . . . . . . . . . . . . 1

How to Prepare for Deployment . . . . . . . . . . . . . . . . . . . . . . 2
How to Choose an Installation Type . . . . . . . . . . . . . . . . . 2
How to Choose a License Server Model . . . . . . . . . . . . . . . 3
Understanding Autodesk Vault Installation and
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
How to Set Up a License Server . . . . . . . . . . . . . . . . . . . . . . . 4
How to Install the Network License Manager . . . . . . . . . . . . 5
How to Install and Use the Network License Activation
Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
How to Configure Your License Server . . . . . . . . . . . . . . . . 8
How to Set Up and Distribute the Program . . . . . . . . . . . . . . . . 10
How to Create a Network Share . . . . . . . . . . . . . . . . . . . 10
How to Use the Installation Wizard to Set Up a
Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
How to Deploy This Program . . . . . . . . . . . . . . . . . . . . 17

Chapter 2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . 19

System Requirements for This Program . . . . . . . . . . . . . . . . . . 20
System Requirements for Autodesk Data Management Server . . . . . . 23

Chapter 3 Deploy the Program . . . . . . . . . . . . . . . . . . . . . . . . 25

Preliminary Tasks for a Network Deployment . . . . . . . . . . . . . . 26

v
 Minimize Chances of Installation Failure . . . . . . . . . . . . . . 27
Create Shared Folders for Your Deployments . . . . . . . . . . . . 28
Install and Activate Tools and Utilities . . . . . . . . . . . . . . . 29
Use the Installation Wizard to Set Up a Deployment . . . . . . . . . . . 29
Start the Deployment Process . . . . . . . . . . . . . . . . . . . . 30
Create a Deployment . . . . . . . . . . . . . . . . . . . . . . . . 30
Enter Personal Information . . . . . . . . . . . . . . . . . . . . . 31
Specify Log File Locations . . . . . . . . . . . . . . . . . . . . . . 32
Select a License Type . . . . . . . . . . . . . . . . . . . . . . . . 34
Select the Installation Type . . . . . . . . . . . . . . . . . . . . . 38
Define Search Paths and File Locations (optional) . . . . . . . . . 43
Install Additional Files (optional) . . . . . . . . . . . . . . . . . . 44
Specify User Preferences (optional) . . . . . . . . . . . . . . . . . 46
Include Service Packs (optional) . . . . . . . . . . . . . . . . . . 48
Configure InfoCenter Communication Center (optional) . . . . . 49
Configure InfoCenter Search Results (optional) . . . . . . . . . . 52
Allow Users to Access Online Resources (optional) . . . . . . . . . 52
Final Review and Complete Setup . . . . . . . . . . . . . . . . . 55
Register the Product . . . . . . . . . . . . . . . . . . . . . . . . . 58
Modify a Deployment (optional) . . . . . . . . . . . . . . . . . . 59
Point Users to the Administrative Image . . . . . . . . . . . . . . . . . 60
Uninstall the Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Appendix A Advertise a Deployment Using MSI . . . . . . . . . . . . . . . . 63

Advertise a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Appendix B Use Scripts to Deploy the Program . . . . . . . . . . . . . . . . 65

Create Scripts That Install Programs . . . . . . . . . . . . . . . . . . . 67
A Sample Installation Script . . . . . . . . . . . . . . . . . . . . . . . . 67
Use Switches and Flags in Scripts . . . . . . . . . . . . . . . . . . . . . 74
Scripts for Custom Installations . . . . . . . . . . . . . . . . . . . . . . 75
Run Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Appendix C Use Group Policies to Install a Deployment . . . . . . . . . . . 79

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Assign a Deployment Using Group Policies . . . . . . . . . . . . 80
Advantages and Disadvantages of Using Group Policies . . . . . . 81
Distribute a Deployment Through Group Policies . . . . . . . . . . . . 81
Assign a Deployment to Computers . . . . . . . . . . . . . . . . . . . 82
Verify the Installation of a Deployment . . . . . . . . . . . . . . . . . 85
Verify That the Program Is Assigned to a Computer . . . . . . . . 85

vi | Contents
Appendix D Use Microsoft Systems Management Server to Install a
Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Tasks for Deploying Autodesk Software with SMS . . . . . . . . . . . . 89
Create a Collection for Distributing Autodesk Software . . . . . . . . . 89
Create a Rule Using the Query Rule Properties Toolbar
Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Create a Rule Using the Direct Membership Rule Wizard . . . . . 91
Set Up a Source Directory Using the Deployment Wizard . . . . . . . . 92
Create the SMS Software Installation Package . . . . . . . . . . . . . . 93
Create an SMS Program . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Use the Deploy Executable Method to Create a Program . . . . . 95
Use the Windows Installer Method to Create a Program . . . . . . 97
Create an Advertisement . . . . . . . . . . . . . . . . . . . . . . . . . 100
Install Autodesk Software on the Client Computer . . . . . . . . . . . 102

Appendix E Distribute the Product Using Imaging Software . . . . . . . . 103

Use a Master Image to Distribute Multi-Seat Stand-Alone Products to
Multiple Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Use a Master Image to Distribute Network Licensed Products to
Multiple Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Restore the Master Image . . . . . . . . . . . . . . . . . . . . . . . . 106
Clean a Master System and Restore the Operating System . . . . . . . 107

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Contents | vii
viii
Quick Start to Network
Administration 1
Network deployment of this program requires careful planning In this chapter
and execution. This section gives you quick, step-by-step ■ How to Prepare for
Deployment
instructions about how to prepare for deployment, set up a
■ How to Set Up a License
Server
license server, and set up and distribute the program.
■ How to Set Up and
Distribute the Program
If you are not familiar with network administration and

deployment, you should read the entire Network Administrator's

Guide before you attempt to deploy and administer the

program over a network.

1
How to Prepare for Deployment
To prepare for a deployment, you need to choose an installation type and a
license server model.

How to Choose an Installation Type

When you set up your deployment, you need to choose the type of installation
to deploy. In the AutoCAD Civil 3D 2008 Installation wizard, you specify one
of the following installation types:
Network License installation With this type of installation, you install the
program to workstations with the files and registry entries that allow the
program to communicate with the Network License Manager. You also define
the configuration of the Network License Manager so that the licenses can be
accessed. Workstations running the program based on a network installation
do not require individual activation. Licensing of this program is managed
by at least one license server.
The main advantage is that you can install AutoCAD Civil 3D on more systems
than the number of licenses you have purchased (for example, purchasing 25
licenses but installing on 40 workstations). At any one time, AutoCAD Civil
3D will run on the maximum number of systems for which you have licenses.
This means you get a true floating license.

Multi-Seat Stand-Alone installation (Stand-Alone option) Choose this type

of installation for stand-alone installations where a single serial number is
used for multiple seats. Multi-seat stand-alone installations do not rely upon
a Network License Manager to manage product licenses; however, you can
still use the AutoCAD Civil 3D 2008 Installation wizard to create administrative
images and create deployments. Registration and activation is more automated
for multi-seat stand-alone installations. After the first activation using the
multi-seat stand-alone serial number, activation occurs automatically for all
workstations based on this deployment, as long as your systems are connected
to the Internet.

Stand-Alone installation (Stand-Alone option) Choose this type of

installation for stand-alone installations where a single serial number is used
for a single seat. Like a multi-seat stand-alone installation, you do not use the
Network License Manager to manage product licensing, but installation,
registration, and activation occurs on each workstation.

2 | Chapter 1 Quick Start to Network Administration

 If you choose one of the Stand-Alone installation types, you can proceed to
the section How to Set Up and Distribute the Program (page 10).

How to Choose a License Server Model

If you chose the Network Installation option, you need to decide which license
server model to use to distribute the product licenses.

TIP If you are deploying a stand-alone or multi-seat stand-alone installation type,

you do not use a license server model. Proceed to the How to Set Up and Distribute
the Program (page 10) section.

For the network installation, use one of the following license server models:

■ Single license server model. The Network License Manager is installed on

a single server, so license management and activity is restricted to this
server. A single license file represents the total number of licenses available
on the server.

■ Distributed license server model. Licenses are distributed across more than
one server. A unique license file is required for each server. To create a
distributed license server, you must run the Network License Manager on
each server that is part of the distributed server pool.

■ Redundant license server model. You use three servers to authenticate a

single license file. One server acts as the master, while the other two provide
backup if the master server fails. With this configuration, licenses continue
to be monitored and issued as long as at least two servers are still functional.
The license file on all three servers is the same. You must install the
Network License Manager on each server.

Each of these license server models is described in detail in the Network Licensing
Guide. It is strongly recommended that you read that guide before you deploy
the program. You can find the Network Licensing Guide by clicking the
Documentation link at the lower left corner of the AutoCAD Civil 3D 2008
Installation wizard and in the Help system.

How to Choose a License Server Model | 3

Understanding Autodesk Vault Installation and
Configuration
AutoCAD Civil 3D 2008 includes a data management feature that includes
client and server components. The client components consist of the Vault
Civil 3D Add-In and Autodesk Vault Explorer. The server component is called
Autodesk Data Management Server. Collectively, these components can be
referred to as Autodesk Vault.
The Autodesk Vault client components must be installed in order to use
AutoCAD Civil 3D 2008 project management features. The server components
can be installed on the network as a separate activity to create a shared server,
or a “local host” version can be installed on the client computer as a single-user
server.
There are several ways to configure a Vault installation. A single server
configuration is recommended. The server component (the Autodesk Data
Management Server) is installed on one system and the client component is
installed on any system that needs to communicate with that server. For best
performance, a dedicated server is recommended. You have flexibility to
choose a configuration that suits your requirements, based on criteria such as
the number of users who must share data, how your users are divided into
design teams, and the amount of project data you expect your users to generate.
For more details, see the Autodesk Data Management Server Implementation
Guide available on the Documentation page that can be accessed from the
Installation wizard.
You may choose whether or not to install Autodesk Vault components during
the AutoCAD Civil 3D 2008 installation.

How to Set Up a License Server

If you are planning to have users run the program using network licenses, you
need to use the Network License Manager and the Network License Activation
utility.
The Network License Manager helps you configure and manage license servers.
The Network License Activation utility helps you get licenses and register
them over the Internet.

4 | Chapter 1 Quick Start to Network Administration

How to Install the Network License Manager
The Network License Manager is used to configure and manage the license
servers.

To install your Network License Manager

1 In the AutoCAD Civil 3D 2008 Installation wizard, click Install Tools and
Utilities.

2 On the Welcome to the AutoCAD Civil 3D 2008 Installation wizard page,

click Next.

3 On the Select the Products to Install page, make sure Network License
Manager is selected and click Next.

4 Review the Autodesk software license agreement for your country or

region. You must accept this agreement to proceed with the installation.
Choose your country or region, click I Accept, and then click Next.

NOTE If you do not agree to the terms of the license and wish to terminate
the installation, click Cancel.

5 On the Review - Configure - Install page, click Configure.

6 Click the Network License Manager tab, if you selected multiple products
in step 3.

7 On the Select the Installation Location page, either accept the default
installation path (C:\Program Files\Autodesk Network License Manager) or
click the [...] button to specify a different path. If you enter a path that
does not exist, a new folder is created using the name and location you
provide. Click Configuration Complete.

WARNING Do not install the Network License Manager on a remote drive.

When you install the Network License Manager files, you must provide a path
to a local drive. You must specify the drive letter; the universal naming
convention (UNC) is not supported.

8 On the On Line Access Tools page, click Next to install the Network
License Manager and any other selected tools and utilities.

9 When the Installation Complete page displays, click Finish.

How to Install the Network License Manager | 5

How to Install and Use the Network License
Activation Utility
With the Network License Activation utility, you can obtain licenses over the
Internet, which saves time and effort in setting up a network-licensed version
of the program. In addition, you can register your product, get automated
support by email if you cannot obtain a license over the Internet, and save
and migrate license files automatically.

To install your Network License Activation utility

1 In the AutoCAD Civil 3D 2008 Installation wizard, click Install Tools and
Utilities.

2 On the Welcome to the AutoCAD Civil 3D 2008 Installation wizard page,

click Next.

3 On the Select the Products to Install page, make sure Network License
Activation Utility is selected and click Next.

4 Review the Autodesk software license agreement for your country or

region. You must accept this agreement to proceed with the installation.
Choose your country or region, click I Accept, and then click Next.

NOTE If you do not agree to the terms of the license and wish to terminate
the installation, click Cancel.

5 On the Review - Configure - Install page, click Configure.

6 Click the Network License Activation Utility tab, if multiple products

were selected in step 3.

7 On the Select the Installation Location page, either accept the default
installation path (C:\Program Files\Autodesk Network License
Manager\Network License Activation Utility\enu\) or click the [...] button
to specify a different path. If you enter a path that does not exist, a new
folder is created using the name and location you provide. Click
Configuration Complete.

8 On the Review - Configure - Install page, click Install to begin installing

the Network License Activation Utility and any other selected tools and
utilities.

9 When the Installation Complete page displays, click Finish.

6 | Chapter 1 Quick Start to Network Administration

To use your Network License Activation utility

1 On the Start menu (Windows), click All Programs (or Programs) ➤

Autodesk ➤ Network License Manager ➤ AutoCAD Civil 3D 2008
Network License Activation Utility.

2 On the Obtain a Network License page, review how this utility works and
the requirements for using it, and then click Next.

3 On the Server Information page, enter the product serial number.

NOTE If you are modifying an existing license file or obtaining a new license
for an existing product, your previously entered information might be
displayed. Make sure that the serial number that is displayed is the one you
want to license. If it is not, enter the correct product serial number.

4 In the License Server Model section, click a license server model. For more
information about each license server model, click the ? button.

5 In the Server Host Name box, enter a server host name or click the [...]
button to locate the name of each server you plan to use.

6 In the Host ID box, for each server host name you entered in the previous
step, click Lookup to have the utility automatically locate the host ID for
the server, or enter the host ID manually.

NOTE If your server has more than one network adapter, select the one that
corresponds to a physical network adapter. To determine which adapters are
physical, enter ipconfig /all at a Windows command prompt and view the
Description field above each physical address. If there is more than one
physical network adapter, you can use any one of them, as long as it was
listed when you ran ipconfig /all. Logical devices such as VPN adapters, PPP
adapters, and modems may be listed but are not usable for licensing.

7 If you chose Distributed Server in step 4, the Seats box is displayed. In

the Seats box, enter the number of seats for each license server, and then
click Next.

8 On the Confirm Server Information page, review the server information

you entered, and click Next.

9 If the Register and License Your Autodesk Product page is displayed, do

all of the following, and then click Next.
■ In the This Product is To Be Registered To option, select Company or
Individual.

How to Install and Use the Network License Activation Utility | 7

 ■ In the Select Country or Region section, select your country or region
of residence.

■ In the Is This an Upgrade section, select Yes or No.

10 If the Registration Information page is displayed, enter your registration

information, and then click Next.

11 If the Confirm Information page is displayed, review your registration

information, and then click Next.

12 If the Connecting page is displayed, click Next to connect to the Internet

to obtain your network license.

13 On the Licenses Received page, in the Save License File for [computer name]
dialog box, enter the location where you want to save your license file,
or click Browse to navigate to the location.

NOTE It is recommended that you save your license file to the location where
you installed the Network License Manager.

14 If you have an existing license file from another Autodesk product, select
one of the following options:
■ Insert the New License Information Into It. Adds the new license
information into the existing license file.

■ Overwrite the Existing License File. Replaces the entire contents of

the existing license file with the new license information. Select this
option only if you no longer require any part of the existing license
file contents.

15 Click Next.

16 On the License Activation Successful page, click Print to save a printed

copy of the license information, or click Done to complete the transaction
and exit the Network Activation utility.

How to Configure Your License Server

You configure a license server so that you can manage the Autodesk product
licenses that you received when you ran the Network License Activation utility.
Configure the license server with the lmtools.exe utility.

8 | Chapter 1 Quick Start to Network Administration

To configure your license server

You should be logged in with Administrator rights when working with the
LMTOOLS utility.

1 Do one of the following:

■ Click Start menu (Windows XP & 2000) ➤ All Programs (or Programs)
➤ Autodesk ➤ Network License Manager ➤ LMTOOLS.

■ Right-click the LMTOOLS icon (Windows Vista) on the desktop and

choose Run As Administrator.

2 In the Lmtools program, on the Service/License File tab, select the

Configure Using Services option.

3 Click the Config Services tab.

4 On the Config Services tab, in the Service Name list, select a service name
or do one of the following:
■ If a service name is selected, verify that it is the one you want to use
to manage licenses.

■ If no service name exists, enter the service name you want to use to
manage licenses.

NOTE If you have more than one software vendor using FLEXlm® for license
management, the Service Name list contains more than one option.

5 In the Path to Lmgrd.exe File box, enter the path to the Network License
Manager daemon (lmgrd.exe), or click Browse to locate the file.
By default, this daemon is installed in the \Program Files\Autodesk Network
License Manager folder.

6 In the Path to the License File box, enter the path to your license file, or
click Browse to locate the file.

7 In the Path to the Debug Log File box, enter a path to create a debug log,
or click Browse to locate an existing log file.

8 To run lmgrd.exe as a service, select Use Services.

9 To automatically start lmgrd.exe when the system starts, select Start Server
at Power Up.

10 Click Save Service to save the new configuration under the service name
you selected in step 4. Then click Yes.

How to Configure Your License Server | 9

 11 Click the Start/Stop/Reread tab.

12 On the Start/Stop/Reread tab, do one of the following:

■ If a service has not yet been defined for Autodesk, click Start Server
to start the license server.

■ If a service for Autodesk is already defined and running, click ReRead

to refresh the Network License Manager with any changes made to
the license file or Options file.
The license server starts running and is ready to respond to client
requests.

13 Close lmtools.exe.

How to Set Up and Distribute the Program

Once you have prepared for deployment and you have used the Network
License Manager and the Network License Activation utility, you are ready to
set up and distribute this program by using the AutoCAD Civil 3D 2008
Installation wizard and choosing a deployment method.

How to Create a Network Share

A network share is an installation folder that you make available to users'
computers on a network. You point users to this location to install the program.
Create a network share that will be used by the AutoCAD Civil 3D 2008
Installation wizard during the creation of a client deployment.

NOTE You must have Full Control permissions set for your shared folder when
you are creating your deployment images. Read permissions are necessary to
access the network share and administrative permissions on the workstation where
the program is deployed.

To create your network share

1 On the desktop of a network server, create a folder named Autodesk.

2 Right-click the Autodesk folder and click Sharing and Security (or Sharing).

3 In the <folder name> Properties dialog box, Sharing tab, select Share This
Folder.

10 | Chapter 1 Quick Start to Network Administration

 4 Specify a Share Name, such as Autodesk or MyDeployments, if necessary.

5 Click the Permissions button. In the Permissions dialog box make sure
Full Control is active. Click OK.
This is important when creating your deployment images.

6 Click OK to close the Properties dialog box.

7 For each product you plan to install, create a subfolder in the Autodesk
folder. Name each folder with the pertinent product name.

How to Use the Installation Wizard to Set Up a

Deployment
You can create a deployment directly from the AutoCAD Civil 3D 2008
Installation wizard. From the deployment, users can install the program on
their computers.

NOTE The following procedure illustrates just one of the ways you can set up a
deployment. This procedure details a single-server network deployment with a
Typical client setup type and no customizations. For further information about
setting up deployments, see Use the Installation Wizard to Set Up a Deployment
(page 29).

To use the Installation Wizard to create a default deployment

1 In the AutoCAD Civil 3D 2008 Installation wizard, click Create

Deployments.

2 On the Welcome to the AutoCAD Civil 3D 2008 Installation wizard page,

click Next.

3 On the Begin Deployment page, you need to specify the following: a

deployment location, a deployment name, and if you want the client
installation run in silent mode.
■ In the deployment location field, enter an existing shared network
location where you want to create an administrative image, or click
the [...] button to navigate to a location where there is a shared
network location. Users install the program from this location.

NOTE If you do not know how to create a network share, see How to
Create a Network Share (page 10).

How to Use the Installation Wizard to Set Up a Deployment | 11

 ■ In the deployment name field, enter the new deployment's name.
The name you enter here is the name of the shortcut your users will
access to install the product.

■ If you want to prevent users from changing your installation settings

when they install the product, select Client Installations Will Be Run
in Silent Mode.

Click Next.

4 On the Select the Products to Install page, choose the product you want
deploy and click Next.

5 Review the Autodesk software license agreement for your country or

region. You must accept this agreement to proceed with the installation.
Choose your country or region, click I Accept, and then click Next.

NOTE If you do not agree to the terms of the license and wish to terminate
the installation, click Cancel.

6 On the Personalize the Products page, enter your user information and
click Next.
The information you enter here is permanent and is displayed in the
AutoCAD Civil 3D window (accessed by using Help ➤ About) on your
computer. Because you can't change this information later without
uninstalling the product, make sure you enter the correct information
now.

7 On the Write to Log page, choose to create the following: a network log
and/or a client log.
■ When you choose to create a network log file, you also have to specify
where the log file is created by entering either a valid UNC (universal
naming convention) path or hard-coded path on your network. The
network log file is optional.

NOTE The folder where the network log resides must be a shared folder
where users who install the program have Change permissions. Otherwise,
successes or failures for user installations cannot be written to the log file.

■ Choose whether or not you want a client log file created.

For more information regarding log files, refer to Specify Log File Locations
(page 32).
Click Next.

12 | Chapter 1 Quick Start to Network Administration

 8 On the Review - Configure - Create Deployment page, click Create
Deployment.
By clicking Create Deployment, the wizard creates an administrative
image in the shared folder using the deployment options listed in the
Current Settings field.

9 On the Deployment Complete page, click Finish.

To use the Installation Wizard to create a configured deployment

1 In the AutoCAD Civil 3D 2008 Installation wizard, click Create

Deployments.

2 On the Welcome to the AutoCAD Civil 3D 2008 Installation wizard page,

click Next.

3 On the Begin Deployment page, you need to specify the following: a

deployment location, a deployment name, and if you want the client
installation run in silent mode.
■ In the deployment location field, enter an existing shared network
location where you want to create an administrative image, or click
the [...] button to navigate to a location where there is a shared
network location. Users install the program from this location.

NOTE If you do not know how to create a network share, see How to
Create a Network Share (page 10).

■ In the deployment name field, enter the new deployment's name.

The name you enter here is the name of the shortcut your users will
access to install the product.

■ If you want to prevent users from changing your installation settings

when they install the product, select Client Installations Will Be Run
in Silent Mode.

Click Next.

4 On the Select the Products to Install page, choose the product you want
deploy and click Next.

5 Review the Autodesk software license agreement for your country or

region. You must accept this agreement to proceed with the installation.
Choose your country or region, click I Accept, and then click Next.

How to Use the Installation Wizard to Set Up a Deployment | 13

 NOTE If you do not agree to the terms of the license and wish to terminate
the installation, click Cancel.

6 On the Personalize the Products page, enter your user information and
click Next.
The information you enter here is permanent and is displayed in the
AutoCAD Civil 3D window (accessed by using Help ➤ About) on your
computer. Because you can't change this information later without
uninstalling the product, make sure you enter the correct information
now.

7 On the Write to Log page, choose to create the following: a network log
and/or a client log.
■ When you choose to create a network log file, you also have to specify
where the log file is created by entering either a valid UNC (universal
naming convention) path or hard-coded path on your network. The
network log file is optional.

NOTE The folder where the network log resides must be a shared folder
where users who install the program have Change permissions. Otherwise,
successes or failures for user installations cannot be written to the log file.

■ Choose whether you want a client log file created.

For more information regarding log files, refer to Specify Log File Locations
(page 32).
Click Next.

8 On the Review - Configure - Create Deployment page, click Configure to

make changes to the administrative image.

9 On the Select the Installation Type page, you can choose to make the
following configuration changes:
■ Typical - Installs the most common application features and allows
you to make the following changes to optional tools:

Express Tools Contains AutoCAD Civil 3D support

tools and utilities.

14 | Chapter 1 Quick Start to Network Administration

 Materials Library Contains over 300 professionally built
materials to apply to a model.

■ Custom - Installs only the application features that you select from
the Select Features To Install list:

CAD Standard Contains tools for reviewing design

files for compliance with your stand-
ards.

Databases Contains database access tools.

Dictionaries Contains multilingual dictionaries.

Drawing Encryption Allows you to use the Security Options

dialog box to protect a drawing with
a password.

Express Tools Contains AutoCAD Civil 3D support

tools and utilities.

Fonts Contains program fonts. (True Type

fonts are automatically installed with
the program.)

Materials Library Contains over 300 professionally built

materials to apply to a model.

New Features Work- Contains animated demos, exercises,

shop and sample files to help users learn
new features.

Portable License Utility Contains a tool for moving a stand-

alone license between computers.

Reference Manager Allows you to view and edit the paths

of externally referenced files associated
with a drawing.

How to Use the Installation Wizard to Set Up a Deployment | 15

 Samples Contains various feature sample files.

Tutorials Contains product lessons.

VBA Support Tutorials Contains Microsoft Visual Basic for

Applications support files.

■ Product Installation Path - Specifies the drive and location where

AutoCAD Civil 3D will be installed.

Click Next to proceed with the configuration process.

10 On the Select the License Type page, select Network License and make
to following settings: the license server model and the server name where
the Network License Manager will run.
■ You can choose from one of three license server models, but for this
example leave it set to Single License Server.

NOTE For complete instructions on all installation and server types, see
Select a License Type (page 34).

■ Enter the name of the server that will run the Network License
Manager, or click the [...] button to locate the server.

Click Next.

11 On the Select Preferences page, make the following settings:

Choose a Default Text Editor. A text editor is used to edit text files such
as PGP and CUS dictionary files. You can accept the default text editor
or select one from the list of available text editors. You can also click
Browse to locate a text editor that is not listed.

Create a Desktop Shortcut. Choose whether or not to display the

AutoCAD Civil 3D shortcut icon on your desktop. A product icon is
created on your desktop by default. Clear the check box if you do not
want to display the shortcut icon.

Click Next.

12 On the Define Search Paths and File Locations page, click Next.

13 On the Install Additional Files page, click Next.

16 | Chapter 1 Quick Start to Network Administration

 14 On the Specify User’s Workstation Settings, enter a default profile name
and click Next.

15 On the Include Service Packs page, click Next.

16 On the Configure InfoCenter Communications Center page, click Next.

17 On the Configure InfoCenter Search Results page, click Next.

18 On the Configure Access to Online Resources page, click Configuration

Complete.

19 Click Create Deployment.

20 On the Deployment Complete page, click Finish.

How to Deploy This Program

You can choose from several methods of deploying the program. Network
sharing is the default method.

■ Network Share. Users launch the program using the shortcut that you
created with the Installation wizard, in step 3 of the procedure How to Use
the Installation Wizard to Set Up a Deployment (page 11) (for example:
\\Server1\Autodesk\deployment\AutoCAD Civil 3D 2008). The program is
installed on users' local computers, and a product icon appears on their
desktop.

NOTE Users must have Read permissions to access the network share and
administrative permissions on the workstation where this program is installed.

■ Scripting. See Use Scripts to Deploy the Program (page 65).

■ Group Policy Objects (GPOs). See Use Group Policies to Install a

Deployment (page 79).

■ Disk Imaging Software. See Distribute the Product Using Imaging Software
(page 103).

How to Deploy This Program | 17

18
System Requirements
2
This section contains the system requirements for the location In this chapter
of the administrative image that you create, the network ■ System Requirements for
This Program
license server, the client workstation, and the machine on
■ System Requirements for
Autodesk Data
which you install the optional Autodesk Data Management
Management Server
Server.

19
System Requirements for This Program
Before you begin installing the program on a network, make sure that your
servers and client workstations meet the minimum recommended hardware
and software requirements for a deployment.
See the following tables for administrative image, license server, and client
workstation system requirements.

Hardware and software requirements for the location of the administrative image

Hardware/Software Requirement Notes

Hard disk 5 GB free disk space recom- The location where you create the adminis-
mended for installation trative image must be a shared location so
that users can access the administrative
image.

Hardware and software requirements for the network license server

Hardware/Software Requirement Notes

Operating system Windows Server 2003 The Network License Manager sup-
Windows XP Professional, Service Pack ports Ethernet network configurations
2 only.
Windows 2000 Server Edition The redundant license server model
Windows 2000, Service Pack 4 is supported only on Windows 2000
Server Edition and Windows 2003
Server.

Computer/processor Pentium III or greater

450 Mhz (minimum)

Network interface card Compatible with existing Ethernet net- The Network License Manager sup-
work infrastructure ports multiple network interface
cards.

20 | Chapter 2 System Requirements

Hardware and software requirements for the network license server

Hardware/Software Requirement Notes

Communication pro- TCP/IP The Network License Manager uses

tocol TCP packet types.

Hardware and software requirements for client workstations

Hard- Requirement Notes

ware/Soft-
ware

Operating sys- (32-Bit) It is recommended that non-English lan-

tem Windows 2000, Service Pack 4, guage versions of AutoCAD Civil 3D be in-
Windows XP Professional, Service stalled on an operating system with a user
Pack 2 interface language that matches the code
Windows XP Home, Service Pack 2 page of the AutoCAD Civil 3D language. A
Windows 2000, Service Pack 4 code page provides support for character
Windows Vista Enterprise sets used in different languages.
Windows Vista Business
Windows Vista Ultimate
Windows Vista Home Premium
Windows Vista Home Basic
Windows Vista Starter

Web browser Microsoft Internet Explorer 6.0, You cannot install AutoCAD Civil 3D if Mi-
Service Pack 1 (or later) crosoft Internet Explorer 6.0 with Service
Pack 1 (or later) is not installed on the in-
stallation workstation. You can download
Internet Explorer from the Microsoft web-
site:
http://www.microsoft.com/downloads/

Processor Pentium 4 or greater, 3 GHz

RAM 2 GB

System Requirements for This Program | 21

Hardware and software requirements for client workstations

Hard- Requirement Notes

ware/Soft-
ware

Graphics card 1280 x 1024 VGA with True Color, ■ Requires a Windows-supported display
128 MB or greater Open GL®-com- adapter.
patible 3D video card
■ For graphic cards that support Hard-
ware Acceleration, DirectX 9.0c, or
better, must be installed.
■ Installing from the ACAD.msi file does
not install DirectX 9.0c, or later.
Manual installation of DirectX is re-
quired, in this circumstance, for Hard-
ware Acceleration to be configured.

Hard disk 5 GB free disk space for installation

Pointing device Mouse, trackball, or other device

DVD-ROM Any speed (for installation only)

drive

Optional hard- Printer or plotter

ware Digitizer
Modem or access to an Internet
connection
Network interface card

Additional recommendations for 3D use

Hard- Requirement Notes

ware/Soft-
ware

Operating sys- Windows® XP Professional, Service It is recommended that non-English lan-

tem Pack 2 guage versions of AutoCAD Civil 3D be in-
stalled on an operating system with a user
interface language that matches the code

22 | Chapter 2 System Requirements

Additional recommendations for 3D use

Hard- Requirement Notes

ware/Soft-
ware

page of the AutoCAD Civil 3D language. A

code page provides support for character
sets used in different languages.

Processor Intel Pentium 4, 3.0 GHz or greater

RAM 2 GB (or more)

Graphics card 128 MB or greater, OpenGL-cap- ■ For graphic cards that support Hard-
able workstation-class ware Acceleration, DirectX 9.0c, or
better, must be installed.
■ Installing from the ACAD.msi file does
not install DirectX 9.0c, or later.
Manual installation of DirectX is re-
quired, in this circumstance, for Hard-
ware Acceleration to be configured.

For more information about tested and

certified graphics cards, visit ht-
tp://www.autodesk.com/autocad-graphic-
scard/.

Hard disk 2 GB (in addition to the 750 MB

required for installation)

System Requirements for Autodesk Data

Management Server
If you plan to use the AutoCAD Civil 3D 2008 project management features,
you must install Autodesk Data Management Server (ADMS). Before you begin
installing the program on a network, make sure that you understand the
requirements for the machine that is to be used as your data management
server.

System Requirements for Autodesk Data Management Server | 23

 The ADMS components can be installed on the same computer as AutoCAD
Civil 3D 2008, if the computer meets the recommended ADMS system
requirements, or it can be installed on any other machine that meets these
requirements. For more information, see Understanding Autodesk Vault
Installation and Configuration (page 4).

Hardware and software requirements for Autodesk Data Management Server

Hard- Requirement Notes

ware/Soft-
ware

Operating Sys- Windows 2000, Service Pack 4 It is recommended that non-English lan-
tem Windows 2000 Server, Service Pack 4 guage versions of AutoCAD Civil 3D
Windows XP Professional Edition, Service 2008 be installed on an operating system
Pack 1 or 2 with a user interface language that
Windows XP Professional x64 Edition matches the code page of the AutoCAD
Microsoft Server 2003, Service Pack 1 or 2 Civil 3D 2008 language. A code page
Microsoft Server 2003 x64 Edition provides support for character sets used
in different languages.

Additional Microsoft IIS

Components (Internet Information Services) Web server

Processor Intel Pentium 4, 3 GHz

RAM 1 GB

Hard Disk 60 GB free disk space for installation

Pointing Device Mouse, trackball, or other compatible

pointing device

Web Browser Microsoft Internet Explorer 6.0, Service Pack

1 (or later)

DVD-ROM Any speed for installation only

Drive

24 | Chapter 2 System Requirements

Deploy the Program
3
In this section, you’ll find more detailed information about In this chapter
using the Installation wizard to create or modify deployments. ■ Preliminary Tasks for a
Network Deployment
■ Use the Installation Wizard
to Set Up a Deployment
■ Point Users to the
Administrative Image
■ Uninstall the Program

25
Preliminary Tasks for a Network Deployment
Installing this program on a network requires careful planning and execution.
The deployment checklist gives you a quick summary of the type of
information you should be familiar with during your deployments.

Deployment Checklist

You have reviewed the system requirements. You must make sure that your
network, servers, and workstations meet the system requirements. See System
Requirements for This Program (page 20).

If your deployment plan involves using imaging software to distribute your

program(s) to client workstations, you have reviewed the Distribute the Product
Using Imaging Software (page 103) section.

You have installed and activated any supporting tools and utilities. See Install
and Activate Tools and Utilities (page 29).

Identify where deployments will reside such as a shared folder for each program
you plan to deploy. See Create Shared Folders for Your Deployments (page
28).

You have closed all other programs and disabled anti-virus software. See Min-
imize Chances of Installation Failure (page 27).

Specify whether you want to create log files which contain deployment and
installation data. See Specify Log File Locations (page 32).

You understand the type of license you’ve purchased. If you plan a network li-
cense deployment, you should also be familiar with the type of license server
model you wish to use and the license server name(s). See Select a License Type
(page 34).

You have an idea whether you’ll perform a typical or custom installation. See
Select the Installation Type (page 38).

You may want to set search paths to custom files or file locations that may have
changed in this release of software. See Define Search Paths and File Locations
(optional) (page 43).

26 | Chapter 3 Deploy the Program

 Deployment Checklist

Additional files can be included with your deployment, such as drawing files,
AutoLISP® routines, or script files. See Install Additional Files (optional) (page
44).

You have checked for service packs that might be available for your product.
If a service pack is available, you’ve downloaded it and extracted an MSP file.
See Include Service Packs (optional) (page 48).

Live Update notifications let you know when product updates are posted and
configuring Communication Center lets users access technical information. See
Configure InfoCenter Communication Center (optional) (page 49) and Config-
ure InfoCenter Search Results (optional) (page 52).

You can allow users of the deployed product to access and participate in features
like DesignCenter Online, Subscription Center, Customer Error Reporting and
the Customer Experience Improvement Program. See Allow Users to Access
Online Resources (optional) (page 52).

Using consistent registration data is very important. Make sure you know how
you’re going to personalize the program(s) during registration. See Register
the Product (page 58).

When you have completed these tasks, you are ready to create a deployment
from the Installation wizard.

Minimize Chances of Installation Failure

The installation process of AutoCAD Civil 3D 2008 may stop if some
applications, such as Microsoft® Outlook® or virus protection programs, are
running when you are creating a deployment. Close all running applications
and temporarily disable virus protection utilities.

Minimize Chances of Installation Failure | 27

Create Shared Folders for Your Deployments
Shared folders are required for both network license and multi-seat stand-alone
methods of installation. The shared folder (network share) is created before you
run the Installation Wizard and is where product deployments are stored.
It is recommended that you name the network shared folder Deployments on
the desktop of the system where you want deployments stored. You can then
add subfolders inside the shared Deployments folder that clearly convey the
name of product you plan to deploy. This is also beneficial if you plan to
deploy multiple products. For example:

Any subfolders that are placed inside a shared folder are automatically shared.

TIP You must have Full Control permissions set for your shared folder when you
are creating your deployment images. Read permissions are necessary to access
the network share and administrative permissions on the workstation where the
program is deployed.

To create a shared folder

1 On a network server, create a folder named Deployments.

2 Right-click the Deployments folder. Click Sharing and Security (or Sharing).

3 In the Properties dialog box, Sharing tab, select Share This Folder.

4 In the Permissions dialog box, click the Permissions button. Make sure
Full Control is active. Click OK.
This is important when creating your deployment images.

5 Click OK to close the Properties dialog box.

6 For each product you plan to install, create a subfolder in the Deployments
folder. Name each folder with the pertinent product name.

28 | Chapter 3 Deploy the Program

Install and Activate Tools and Utilities
Several supporting tools and utilities are necessary if you plan to have users
run the program(s) with network licenses. Ancillary programs you might install
include:

■ Network License Manager

■ Network License Activation Utility

■ CAD Manager Tools

■ SAMreport Lite

Refer to the Network Licensing Guide for detailed information about how to set
up your license servers. The Network Licensing Guide is available on the
Documentation link of the Installation wizard and in the Help system.

Use the Installation Wizard to Set Up a

Deployment
The deployment process is initiated from the Installation Wizard. After
deployments are created, users can install the program on their computers.
You make choices during the deployment process to create various client
deployment images and deployment types that meet user requirements and
company needs.
The deployment process lets you do any of the following:

■ Create a deployment.

■ Apply a patch to a deployment.

■ Add customized files to a deployment.

■ Change search paths and file locations.

NOTE Because the deployment process provides you with numerous options for
creating and customizing your deployments, there are many deployment pages
you need to complete and choices you must make. You should set aside ample
time to complete the deployment process in one sitting.

When you initiate the deployment process, you can do the following:

Install and Activate Tools and Utilities | 29

Start the Deployment Process
Once you have started the Installation wizard, you initiate the deployment
process to set up a deployment.

To start the deployment process

■ In the AutoCAD Civil 3D 2008 Installation wizard, click Create

Deployments.

Create a Deployment
A deployment contains a Microsoft Transform (MST) file that modifies the
default behavior of the installation program. As you begin a deployment, you
need to select a deployment location, choose a deployment name, and specify
whether silent mode (page 30) is active for client installations.

Silent mode When silent mode is active and a user initiates the deployment,
the installation proceeds without any user input. No dialog boxes are presented
that require interaction from the user.

30 | Chapter 3 Deploy the Program

 To create a deployment

1 On the Begin Deployment page, enter a deployment location or click the

[...] button to browse your drive for a location.

NOTE The deployment location should be a shared network folder. To create

a shared folder, see Create Shared Folders for Your Deployments (page 28).

2 In the Specify the Deployment Name field, enter the new deployment's
name. The name you enter here is the name of the shortcut your users
will access to install the product.

3 If you want to prevent users from changing your installation settings

when they install the product, make sure Client Installations Will Be Run
in Silent Mode is active.

4 Click Next.

Enter Personal Information

The Personalize the Products page is used to personalize the program for your
company. The information you enter here is permanent and is displayed in
the About <product name> window (accessed by using Help ➤ About) on all
workstations that install your deployment. Because you can't change this
information later without uninstalling the product, make sure you enter the
correct information now.

Enter Personal Information | 31

 You must also enter your product serial number in order to run the product.
The product serial number is located on the product packaging. The serial
number must contain a three-digit prefix followed by an eight-digit number.

To enter your personal information and serial number

1 On the Personalize the Products page, enter the requested personalization

data.

NOTE Although it is required that you enter information in each box on this
page, you can enter any information that you want to convey to users who
install the deployment.

2 Enter your product serial number.

3 Click Next.

Specify Log File Locations

The program has two types of log files with which you can monitor
information about deployments and installations.

32 | Chapter 3 Deploy the Program

■ Network log. The network log file keeps a record of all workstations that
run the deployment. On the Write to Log page of the deployment process,
you choose whether or not to create a network log file. The log lists the
user name, workstation name, and the status of the installation. Refer to
this file for status information and details about problems that users may
have encountered during installation (for example, low disk space or
inadequate permissions). The network log is named with the same name
you chose for your deployment. You can specify where the log file is created
by entering either a valid UNC (universal naming convention) path or
hard-coded path on your network, for example
\\MyComputer\Autodesk\AutoCAD Civil 3D 2008.

NOTE The folder where the network log resides must be a shared folder where
users who install the program have Change permissions. Otherwise, successes
or failures for user installations cannot be written to the log file.

■ Client log. The client log contains detailed installation information for
each workstation. This information may be useful in diagnosing installation
problems. The client log is located in the \Temp directory of each client
workstation. The client log is named with the same name you chose for
your deployment.

To specify a log file location

1 While creating a deployment, on the Write to Log page, select the check
box next to the Create Network Log box. Enter the name of the folder
where you want the network log to be located.

Specify Log File Locations | 33

 2 If you want to create a client log, select the Create Client Log option.

3 Click Next.

Select a License Type

When you set up your deployment, you need to choose the type of installation
to deploy based on the type of software license you’ve purchased. You can
purchase one of three types of product licenses: network, multi-seat
stand-alone, and stand-alone.

Specify the license type to use during deployment

Network License With this type of installation, you install the program to
workstations with the files and registry entries that allow the program to
communicate with the Network License Manager. You also define the
configuration of the Network License Manager so that the licenses can be
accessed. Workstations running the program based on a network installation
do not require individual activation. Licensing of this program is managed
by at least one license server.
■ Choose Network License.

Multi-Seat Stand-Alone license (a single serial number for multiple

seats) Registration data is gathered on the Register Today pages. After the first
activation using the multi-seat stand-alone serial number, activation occurs
automatically for all workstations based on this deployment, as long as your
systems are connected to the Internet.
■ Choose Stand-Alone License.

Stand-Alone license (a single serial number for a single seat) You do not
use the Network License Manager to manage product licensing. For stand-alone
installation, you install, register, and activate the program on each workstation.
■ Choose Stand-Alone License.

To deploy a network license using a single license server model

1 While creating a deployment, on the Select the License Type page, select
the Network License option.

34 | Chapter 3 Deploy the Program

 2 Select Single License Server as the License Server Model you want to use
with the Network License Manager.
If you have already used the Network License Manager to create a license
server model, you must select the same license server model in this step.
If you have not yet used the Network License Manager to create a license
server model, make sure that you select the same settings in the Network
License Manager that you choose here.
For detailed information about license server models, see “License Server
Models” in the Network Licensing Guide, located in the Help system and
on the Documentation link of the Installation wizard.

3 Enter the server name of the server that will run the Network License
Manager, or click the [...] button to locate the server. Click Next.

To deploy a network license using a distributed license server model

1 While creating a deployment, on the Select the License Type page, select
the Network License option.

2 Select Distributed License Server as the License Server Model you want
to use with the Network License Manager.
If you have already used the Network License Manager to create a license
server model, you must select the same license server model in this step.
If you have not yet used the Network License Manager to create a license
server model, make sure that you select the same settings in the Network
License Manager that you choose here.
For detailed information about license server models, see “License Server
Models” in the Network Licensing Guide, located in the Help system and
on the Documentation link of the Installation wizard.

Select a License Type | 35

 3 Enter the name of one of the servers that will run the Network License
Manager, or click the [...] button to locate the server. Click Add to add
the server to the Server Pool. Once all the servers are added to the Server
Pool list, use the Move Up and Move Down buttons to arrange the servers
in the order you want them to be searched by a user's workstation. You
must enter at least two servers. Click Next.

To deploy a network license using a redundant license server model

1 While creating a deployment, on the Select the License Type page, select
the Network License option.

2 Select Redundant License Server as the License Server Model you want
to use with the Network License Manager.
If you have already used the Network License Manager to create a license
server model, you must select the same license server model in this step.
If you have not yet used the Network License Manager to create a license
server model, make sure that you select the same settings in the Network
License Manager that you choose here.

36 | Chapter 3 Deploy the Program

 For detailed information about license server models, see “License Server
Models” in the Network Licensing Guide, located in the Help system and
on the Documentation link of the Installation wizard.

3 In the First Server Name field, enter a server name of one server that will
run the Network License Manager, or click the [...] button to locate the
server. Enter the server names for the remaining two servers that you will
use in the redundant server pool. Click Next.

NOTE If you are not sure how to obtain the server host name, see “Plan Your
License Server Configuration” in the Network Licensing Guide. The Network
Licensing Guide is located in the Help system and on the Documentation link
of the Installation wizard.

To deploy a multi-seat stand-alone or stand-alone license

1 While creating a deployment, on the Select the License Type page, select
Stand-Alone Installation.

Select a License Type | 37

 2 Click Next.

Select the Installation Type

As part of making your deployment choices, you select the type of installation
that users receive when they install the program, choose which optional tools
or features get included, and specify where the product will get installed on
each workstation.

■ Typical. Installs the most common application features. This option is

recommended for most users.

38 | Chapter 3 Deploy the Program

■ Custom. Installs only the application features that you select.

You can also choose to include Express Tools and the Material Library with
this deployment.

■ Express Tools. Express Tools are available in their original form, in English
only, and are not supported. No updates have been made to the tools.
Double-byte characters are not supported.

NOTE Some Express Tools have been integrated into AutoCAD Civil 3D 2008.
For a full list of tools that have been integrated, see the FAQ section in the
Express Tools Help. You can also get help on each integrated command in the
product Help system.

■ Material Library. The Material Library contains over 300 professionally

built materials that you can apply to your models. The library is constructed
as a series of tool palettes.

You choose the location where program files are installed on the client
workstation in the Product Install Path. To help decide where the product is
installed, a chart of drives and disk space is provided.

To deploy a typical installation, choose optional tools and specify a

product location

1 During the deployment, on the Select the Installation Type page, select
the Typical option as the type of installation that you want.

Select the Installation Type | 39

 2 Clear the check box for the Express Tools option if you do not want to
include the tools in this deployment. Express Tools are installed by default.

3 If you want to install the Material Library, select the check box for the
Material Library option.
The Material library option is cleared by default.

4 Enter the path on the client workstation where you want to install the
program, for example C:\Program Files\AutoCAD Civil 3D 2008, or click
the [...] button to specify the install location.
The Disk Space Requirements chart lets you review available drives and
disk space.

5 Click Next.

To deploy a custom installation, choose optional tools and specify a

product location

1 During the deployment, on the Select the Installation Type page, select
the Custom option as the type of installation that you want.

40 | Chapter 3 Deploy the Program

2 From the Select Features To Install list, select the features that you want
to install.
Your choices are as follows:

CAD Standard Contains tools for reviewing design

files for compliance with your stand-
ards.

Databases Contains database access tools.

Dictionaries Contains multilingual dictionaries.

Drawing Encryption Allows you to use the Security Options

dialog box to protect a drawing with
a password.

Express Tools Contains AutoCAD Civil 3D support

tools and utilities.

Select the Installation Type | 41

 Fonts Contains program fonts. (True Type
fonts are automatically installed with
the program.)

New Features Work- Contains animated demos, exercises,

shop and sample files to help users learn
new features.

Portable License Utility Contains a tool for moving a stand-

alone license between computers.

Migrate Custom Set- Allows you to migrate custom settings

tings and files from previous releases. For
more information, see Migrate Custom
Settings.

Reference Manager Allows you to view and edit the paths

of externally referenced files associated
with a drawing.

Samples Contains sample files for various fea-

tures. Sample are part of a default in-
stallation. (Visual Lisp samples are not
installed by default.)

VBA Support Contains Microsoft Visual Basic for

Applications support files.

If, after making feature changes, you decide you want the original
selections, click the Restore Defaults button.

3 Enter the path on the client workstation where you want to install the
program, for example C:\Program Files\AutoCAD Civil 3D 2008, or click
the [...] button to specify the install location.
The Disk Space Requirements chart lets you review available drives and
disk space.

4 Click Next.

42 | Chapter 3 Deploy the Program

Define Search Paths and File Locations (optional)
On the Define Search Paths and File Locations page, you can modify the
default search paths and the location of some program files. You might want
to modify the default settings for the following reasons:

■ If your CAD environment uses a file (such as a customization file or

plug-ins) other than the default file that's installed with the program, you
can point to that file now and avoid having to add it at each workstation.

■ Some default file locations may have changed in this version of the
program. You can use this page if you have an earlier version of the
program, and you want to move the files to the same file location as your
earlier version of the program.

NOTE You can also modify the search paths and file locations for individual
workstations after you have installed the program. You do this by using the Options
dialog box. For more information, see Specify Search Paths and File Locations in
the User's Guide.

To use the default program settings for search paths and file locations

■ While creating a deployment, on the Define Search Paths and File Locations
page, click Next.

To modify the default program settings for search paths and file
locations

1 While creating a deployment, on the Define Search Paths and File

Locations page, in the Define Search Paths, File Names, and File Locations
list, click the plus sign (+) to the left of a search path or file location to
select and expand it.

Define Search Paths and File Locations (optional) | 43

 2 Select an item in the list and do any of the following:
■ To browse to a file location, click Browse.

■ To add a new entry to the currently selected search path or file

location, click Add.

■ To remove an entry from the currently selected search path or file

location, click Remove.

■ To move a selection up or down in the list, click Move Up or Move

Down.

NOTE The availability of these buttons depends on the item that you selected
in the previous step.

3 When you finish specifying search paths or file locations, click Next.

Install Additional Files (optional)

On the Install Additional Files page, when you click Browse, you can specify
additional files to include with a deployment. By default, these files are
installed in the program's installation directory on client workstations when
the deployment is run. You can install files to multiple directories if desired.

44 | Chapter 3 Deploy the Program

You can perform the following operations:

■ Specify additional files (such as drawing files, AutoLISP® routines, or script

files) to include with your deployment.

■ Install different types of files to different workstation directories.

■ Add subfolders under the installation folder (for example, a folder called
LSP to contain custom AutoLISP routines).

■ Add files to the same location as program files (for example, add sample
drawings for a project).

■ Add files to the root of the installation directory.

NOTE It is recommended that you install these files to a location within the
program's directory structure. You cannot install files with the same file name as
an installed program file. For example, you cannot add a file named acad.cui.

To install additional files

1 While creating a deployment, on the Install Additional Files page, set the
location where file will get installed.

Install Additional Files (optional) | 45

 2 Do any of the following:
■ Click [...] to open the Add Files dialog box, where you can select files
to add to the installation directory.

■ Click Add Folder to create a new folder in the installation directory.

■ Click Add Drive to create a new drive name in the installation

directory.

■ Click Remove to delete a file, folder, or drive from the installation

directory.

3 Click Next.

Specify User Preferences (optional)

On the Specify User Preferences page, you can specify whether installations
based on this deployment can proceed if Microsoft Internet Explorer is not
installed, specify a default profile name, choose to display the product shortcut
icon on the desktop, or create a custom desktop shortcut.

46 | Chapter 3 Deploy the Program

To specify user preferences settings

1 While creating a deployment, on the Specify User Preferences page, clear

the check box for the Internet Explorer option if you do not require
Microsoft Internet Explorer to be installed before AutoCAD Civil 3D is
installed.

2 In the Default Profile Name box, specify a default profile name that will
be current for all users who run the deployment.

3 Clear the check box for Create an AutoCAD Civil 3D 2008 Desktop
Shortcut if you do not want the product shortcut icon to appear on the
user's desktop.

4 If you want to create a custom desktop shortcut, specify a shortcut name

and any parameters, such as switches that will call profiles, startup scripts,
etc.

5 Click Next.

Specify User Preferences (optional) | 47

Include Service Packs (optional)
During the deployment process, you can choose to include service packs that
have been posted for your product.

When you include a service pack, you can also specify how it will be handled.
You can choose from the following;

■ Append the Service Pack onto the Deployment. When you append a service
pack, the service pack is applied to the current deployment only. Multiple
service packs may be appended to a deployment. The service pack file is
included in the deployment and the service pack is applied after the product
is deployed.

■ Merge the Service Pack into the Administrative Image MSI file. When you
merge a service pack, the service pack is merged into the administrative
image. Once merged, a service pack may not be removed from the admin
image. Multiple service packs may be included in a single admin image.

To extract an MSP file from a service pack

1 Download the service pack from the Autodesk product support site.

2 Review the service pack Readme file for information about patch usage.

48 | Chapter 3 Deploy the Program

 3 Open a Windows command prompt and enter the patch file name
followed by the /e switch and a target file name, such as:
ProductSP1.exe /e ./ProductSP1.msp
where <ProductSP1.exe> is the name of the downloaded patch and
<ProductSP1.msp> is the name of the extracted file. Using ‘./’ in front of
the extraction file name places the extracted file in the same folder as
the original executable.

NOTE To find out if a service pack is available, visit the Autodesk Product
Support page at http://support.autodesk.com/.

To include a service pack with the deployment

To include a service pack with a deployment, an MSP file must be extracted

from the downloaded service pack executable.

1 On the Include Service Packs page, click the [...] button.

2 In the Open dialog box, locate the service pack you want to include with
the deployment.

3 Select the MSP file and click Open.

4 Specify whether you want to Append the service pack on to the

deployment or merge the service pack into the administrative image.

5 Click Next.

Configure InfoCenter Communication Center

(optional)
The Communications Center is accessed through InfoCenter. Products are
updated with Live Update, which downloads patches to your product using
Communication Center. Beyond Live Update, other information channels
and feeds can be displayed by the Communication Center.

Configure InfoCenter Communication Center (optional) | 49

 The Communication Center settings you can make include

■ Enable Live Update. Users can use Live Update to check for updates when
a web connection is established. If a product patch is available, notification
of its availability is received on the program's status bar, and the patch can
be either downloaded directly from an Autodesk server or modified first
before being copied to users' workstations. If you don't want users to receive
updates or announcements, you can turn off Live Update.

NOTE You can also turn Live Update options on or off in the CAD Manager
Control utility. See How to Install and Start the CAD Manager Control Utility

■ Enable Information Channels. When active, information channels notify

users with various pieces of information such as subscription
announcements and product support information.

■ Enable CAD Manager Channels. Controls the display of the CAD Manager
Channels in InfoCenter. Aside from being able to toggle CAD Manager
Channels, you can also define the CAD Manager feed location and set the
display name for the CAD Manager Channel.

50 | Chapter 3 Deploy the Program

■ Enable RSS Feeds. Users can subscribe to any number of RSS feeds. Each
feed is contained within a discrete InfoCenter category. Additionally, you
can specify whether users can add RSS feeds.

To configure Communication Center

1 When creating a deployment, on the Configure InfoCenter

Communication Center page, make the following Live Update settings:
■ Enable Live Updates. Users can receive product updates or support
announcements from Autodesk servers.

■ Receive Live Updates from Autodesk. Users can receive product updates
and support announcements from Autodesk servers with Live Update.

■ Receive Live Updates from Internal Server. You can maintain a patch
list on a local server. If you select this option, the Local Patch List
Location box is available. Use the [...] button to locate the path to a
server location where you want a patch list to be located. More
information about how to use a local patch list is available by installing
Autodesk CAD Manager Tools 4.0, running the CAD Manager Control
utility, and then clicking Help in the CAD Manager Control utility
window.

NOTE You can name a file that will be used to enter the patch
information. By naming a file and using an .npl extension now, you are
creating a placeholder file, not creating the file itself. In the location that
you specify in the Local Patch List Location box, you must create a text
file with the same name you specify here.

2 Specify whether Information channels should be enabled.

3 Specify whether CAD Manager channels should be enabled. When active,

you can make the following settings:
■ Feed Location. Defines the location of the CAD Manager channel RSS
feed. RSS feeds are in XML format.

■ Display Name. Sets the display name of the CAD Manager channel.

4 Specify whether RSS Feeds are enabled and if users are allowed to add
feeds.

5 Click Next.

Configure InfoCenter Communication Center (optional) | 51

Configure InfoCenter Search Results (optional)
The Search Results tab of InfoCenter can be configured to display content
from various sources, such as the product Help system, CAD Manager
Channels, or the Internet.

You can specify whether users who install from the deployment can customize
access to their InfoCenter search locations.

To configure InfoCenter search results

1 When creating a deployment, on the Configure InfoCenter Search Results

page, specify whether users have the option to customize their InfoCenter
search locations.

2 Click Next.

Allow Users to Access Online Resources (optional)

The Configure Access to Online Resources page allows you to specify whether
users can access online resources such as DesignCenter and Subscription
Center. You can also determine whether users will receive notification from
Autodesk when reported errors are resolved and if they want to participate in
the Customer Involvement Program.

52 | Chapter 3 Deploy the Program

DesignCenter and Subscription Center

The DC Online tab in DesignCenter® provides access to previously drawn

content such as blocks, symbol libraries, manufacturers' content, and online
catalogs. This content can be used in common design applications to assist
users in creating drawings. If you turn off DC Online, the DC Online tab is
removed from all installations that are based on this deployment. The Enable
DC Online option is active by default.
Subscription Center provides Autodesk subscription members access to
resources such as e-Learning (self-paced, interactive lessons) and web support
(where customers can submit technical questions online to Autodesk support
staff).

You can determine whether users who are entitled to subscription resources
can access them by using Help and clicking a Subscription resource. Users

Allow Users to Access Online Resources (optional) | 53

 who do not have such access can still learn about subscription resources by
using the same option on the Help menu.

NOTE You can also enable or disable DesignCenter Online and Subscription Center
access from the CAD Manager Control utility.

Customer Error Reporting (CER)

If AutoCAD Civil 3D closes unexpectedly, users have the opportunity to send

an error report directly to Autodesk, which helps Autodesk to determine and
resolve the error. You can determine whether users can also receive notification
from Autodesk when their reported errors are resolved.

NOTE You can also turn Customer Error Reporting notification on or off in the
CAD Manager Control utility.

Customer Involvement Program (CIP)

If you choose to participate in the Customer Involvement Program, AutoCAD

will automatically send Autodesk information about what features you use
most, any problems that you encounter, and other information helpful to the
future direction of the product.
For more information regarding the CIP, see Join the Customer Involvement
Program.

NOTE You can enable or disable the Customer Involvement Program from the
CAD Manager Control utility.

54 | Chapter 3 Deploy the Program

 To configure access to online resources

1 While creating a deployment, on the Configure Access to Online Resources

page, do one of the following to configure DesignCenter Online:
■ To disable DesignCenter Online, make sure that the check box next
to Enable DC Online is cleared.

■ To enable DesignCenter Online, select the check box next to Enable

DC Online.

2 To allow access to the Subscription Center, select or clear the check box
next to Allow Access to Subscription Center from Within the Autodesk
Product (Recommended). This option is enabled by default.

3 If you want to receive notification of problem resolutions, do the

following:
■ Select the check box next to Allow Users to Receive Notification of
Resolution so that users are made aware of resolutions to issues and
can download applicable updates provided by Autodesk. This option
is enabled by default.

NOTE Users must have administrative permissions to install an update

provided by Autodesk.

■ Select the check box next to Include Computer Name to include the
user’s computer name in error reports. The computer name is included
in notifications to the user and in reports available to subscription
administrators. This option is disabled by default.

4 If you want to participate in the Customer Involvement Program, make

sure the check box next to Allow Users to Participate in the Autodesk CIP
Program is enabled.

5 Click Configuration Complete.

Final Review and Complete Setup

To complete your deployment setup, confirm the settings you selected.

Final Review and Complete Setup | 55

 To confirm and complete the setup of a network deployment

1 After making all your deployment settings, on the Review - Configure -

Create Deployments page, scroll the list of current settings and verify
your installation selections.

2 If you want to change any selections you made for the deployment, click
the Configure button.

3 If you want a hardcopy of the installation information displayed on this

page, click the Print button.

4 If you are ready to complete the deployment, click Create Deployment.

5 On the Deployment Complete page, click Finish.

56 | Chapter 3 Deploy the Program

To confirm and complete the setup of a multi-seat stand-alone
deployment

1 After making all your deployment settings, on the Review - Configure -

Create Deployments page, scroll the list of current settings and verify
your installation selections.

2 If you want to change any selections you made for the deployment, click
the Configure button.

3 If you want a hardcopy of the installation information displayed on this

page, click the Print button.

4 If you are ready to complete the deployment, click Create Deployment.

5 On the Deployment Complete page, click Register Products Online.

Final Review and Complete Setup | 57

 Registration at this stage ensures that consistent data is being used to
streamline product activation. When a user installs from this deployment
and runs the product, registration data is automatically referenced and
the product gets activated. See Register the Product (page 58).

6 Click Finish.

You have created an Autodesk product deployment with precise options that
are specific to your group of users. You can now inform those using this
deployment where the administrative image is located so that they can install
the program.

Register the Product

It is very important that the registration data (for example, your company
name and contact information) you supply when registering and activating
your products is consistent across all Autodesk products that you install. If
you enter this data incorrectly or inconsistently, you can run into activation
problems.
The way products are registered depends upon the type of license you selected
while creating the deployment. In order to receive an activation code, your
product must be registered.

To register a network licensed deployment

1 On the Start menu (Windows), click All Programs (or Programs) ➤

Autodesk ➤ Network License Manager ➤ AutoCAD Civil 3D 2008
Network License Activation Utility.

2 On the Obtain a Network License page, review how this utility works and
the requirements for using it, and then click Next.

58 | Chapter 3 Deploy the Program

 3 Follow the on-screen instructions to complete the registration and
activation.

To register a multi-seat stand-alone licensed deployment

1 On the Deployment Complete page, click Register Products Online.

The Register Today page is displayed. You complete Register Today at

this point so that all users have the same default registration information.

2 In the Register Today wizard, follow the on-screen instructions to

complete the registration.

NOTE This process only registers the product. If users are connected to the Internet,
activation will occur automatically when the product is started.

Modify a Deployment (optional)

After a deployment is created, it may be necessary to modify the deployment
for some client workstations. You can apply a patch or select various custom
files that are not part of the base administrative image. You can also perform
modifications such as changing the installation directory from drive C to drive
D.

To modify a deployment

1 Open the shared network folder where you originally chose to place your
product deployment.

2 Double-click the Modify <deployment name> shortcut in the shared folder.

This re-opens the Installation wizard.

3 Click through the deployment pages and make the necessary changes.

Modify a Deployment (optional) | 59

 4 After all the modifications have been made, click Create Deployment.

Point Users to the Administrative Image

When you have completed the deployment process, you are ready to have
users install the newly created or modified deployment. You need to notify
your users of the shortcut that was created in the administrative image. The
shortcut is the same name that you chose in Create a Deployment (page 30).

To point users to the administrative image

■ The simplest method of notifying users how to install the deployment is

to email them with instructions about using the shortcut. At a minimum,
the instructions need to include the location of the deployment and
instructions about double-clicking the shortcut to the deployment.

NOTE For more advanced ways of using the shortcut and installing the
deployment, see Use Scripts to Deploy the Program (page 65), Use Group Policies
to Install a Deployment (page 79), or Use Microsoft Systems Management Server
to Install a Deployment (page 87).

Uninstall the Program

When you uninstall AutoCAD Civil 3D 2008, most of the AutoCAD Civil 3D
components are removed. This means that even if you have previously added
or removed components, or if you have reinstalled or repaired the program,
uninstalling removes all program installation files from your system.

IMPORTANT Autodesk products that are add-ons to AutoCAD Civil 3D, such as
Autodesk Design Review, Autodesk Vault, and Autodesk Data Management Server
are not uninstalled when you uninstall AutoCAD Civil 3D. To uninstall these
applications, you must use the Windows Add or Remove Programs utility.

NOTE If you plan to modify an administrative image at a later date (for example,
by adding a patch to it), do not remove that image.

To uninstall the program

1 In Control Panel (Windows), click Add or Remove Programs.

60 | Chapter 3 Deploy the Program

2 In the Add/Remove Programs window, select AutoCAD Civil 3D 2008,
and then click Change/Remove.

3 In the AutoCAD Civil 3D 2008 Installation wizard, click Uninstall.

4 Click Next to remove AutoCAD Civil 3D from the system.

5 If prompted, click Yes if you want to restart your system, or No if you

prefer to do it later.

6 If you chose to restart later, click Finish.

7 Repeat steps 1 to 3 to uninstall any other Autodesk applications from

your system.

Uninstall the Program | 61

62
Advertise a Deployment
Using MSI A
Advertising is a deployment method that you use to provide In this appendix
access to a centralized program from a workstation. You create ■ Advertise a Deployment

an administrative image in a central location and then set up

each workstation to have a shortcut to the program. When

you click the shortcut, the program is installed on the

workstation.

In order for AutoCAD Civil 3D to run properly, the following

software must be installed on the computer where the program

is being installed:

■ Microsoft Internet Explorer version 6.0 Service Pack 1 or

later. (You can download Microsoft Internet Explorer from

the Microsoft website by visiting www.microsoft.com).

■ Microsoft Installer Package (MSI) 3.1

63
Advertise a Deployment
After you create an administrative image on a shared directory, you can set
up a shortcut to make the program accessible to users. The program name is
added to the Start menu (Windows) and to the Add/Remove Programs list.

To advertise a deployment using MSI 3.1

1 On the user's workstation, on the Start menu (Windows), click All

Programs (or Programs) ➤ Accessories ➤ Command Prompt.

2 At the Windows command prompt, enter the following to set up a

shortcut:
msiexec /jm \\[servername]\[sharename]\AdminImage\acad.msi /t
\\[servername]\[sharename]\AdminImage\[deploymentname].mst

This program is now advertised. To install this program on the workstation,

the user clicks a program shortcut in the Start menu (Windows). This method
installs the program on the workstation with minimal prompts for the user.

64 | Appendix A Advertise a Deployment Using MSI

Use Scripts to Deploy the
Program B
A script executes a command or a set of commands. Scripts In this appendix
are similar to batch files but are more flexible. Installation ■ Create Scripts That Install
Programs
scripts are most useful for stand-alone installation of programs
■ A Sample Installation Script
on computers that are connected to a network. Scripts are also ■ Use Switches and Flags in
Scripts
useful for installing service packs, extensions, and object
■ Scripts for Custom
Installations
enablers on a network.
■ Run Scripts
In order for AutoCAD Civil 3D to run properly, the following

software must be installed and prerequisites met on the

computer where the program is being installed:

■ Microsoft Internet Explorer version 6.0 Service Pack 1 or

later (You can download Microsoft Internet Explorer from

the Microsoft website by visiting www.microsoft.com)

■ Microsoft Scripting Engine

The sample scripts in this section are based on Microsoft
Scripting Engine 5.6, which works with both VBScripts
and JavaScript. If you don't have the scripting engine

65
 installed, you can download it for free from the Microsoft
website at www.msdn.microsoft.com/scripting. Sample scripts
and Help files are also available there for download.

■ Administrative permissions

66 | Appendix B Use Scripts to Deploy the Program

Create Scripts That Install Programs
You create a script by using a text editor such as Notepad and then saving it
in ASCII format in a file with the file extension .vbs. The script consists of one
or more commands, as well as command switches that specify options, and
flags that modify the options. An installation script also contains path names.
An installation script points to the location of the product's setup.exe file. You
must point to the setup.exe file on your product DVD. For example:
AutoCAD Civil 3D 2008 DVDROM1\setup.exe

A Sample Installation Script

The sample script in this section installs the program in a typical configuration.
To make it easy to copy this sample script and substitute your own information,
the same names are used throughout for variable items. The log file name is
based on the product being installed. You can either use the log file name in
the script or change it to something else.
Serial number prefix: 123
Serial number: 12345678
First name: Your First Name
Last name: Your Last Name
Organization: Your Company Name
A sample script for a silent installation of this program uses the syntax shown
in this section.

Create Scripts That Install Programs | 67

 Scripted installation for AutoCAD Civil 3D 2008

' Scripted installation for AutoCAD Civil 3D 2008

option explicit
'

' Create variables

dim x64bit
dim shell
dim productType
dim featuresToInstall
dim strADSKFirstName
dim strADSKLastName
dim strADSKOrganization
dim strADSKSercirity
dim strADSKSerialIsvalid
dim strADSKAccept
dim strADSKEula
dim strADSKReInstall
dim strADSKRemove
dim strADSKSNPrefix
dim strADSKSNNumber
dim strInstallLevel
dim strACADStandaloneNetworkType
dim strADSKLicenseServerType
dim strADSKLicenseType
dim strADSKServerFmtPath
dim strADSKServerPath
dim strADSKServerHostID
dim strADSKPath
dim strSourcePath
dim strAdditionalStuff
'

' Script initialization

Set shell = CreateObject("WScript.Shell")
x64bit = false ' change to true if this is AutoCAD Civil
3D 2008 x64
productType = "acad"
strInstallLevel=3 ' 5 installs everything 3 installs typical
'

68 | Appendix B Use Scripts to Deploy the Program

' Name and Organization information
strADSKFirstName = "Your First Name"
strADSKLastName = "Your Last Name"
strADSKOrganization = "Your Organization Name"
'
' Serial Number information
strADSKSNPrefix = "123"
strADSKSNNumber = "12345678"
'

' Source to install from (e.g. D: is assumed to be Install Media)

strSourcePath = "d:\"
'
' Destination to install to
strADSKPath = Shell.ExpandEnvironmentStrings("%ProgramFiles%") +
"\AutoCAD Civil 3D 2008"
'

A Sample Installation Script | 69

 ' Features to install
' ACS - AutoCAD Civil 3D Samples
' CADStandards - CAD Standards
' Database - Database (DBCONNECT)
' DCS - DesignCenter Samples
' DigSig - Digital Signatures
' Dictionaries - Dictionaries
' DrawingEncryption - Drawing Encryption
' Express_Tools - Express Tools
' Fonts - Fonts
' Impression - Autodesk Impression Toolbar (NOT in AutoCAD Civil
3D 2008 64 bit)
' Materials - Materials Library
' Migrate - Migrate Custom Settings
' NFW - New Features Workshop
' PLM - Portable License Utility
' RefMan - Reference Manager
' System_Files - Required system files (installed by default in
this script)
' TM - Texture Maps
' VBA - Visual Basic for Applications
' VLS - Visual LISP Samples
' VLT - Visual LISP Tutorials
'
' Sample is below - Note the leading comma
featuresToInstall = ",DigSig,TM,CADStandards,Database,Dictionar
ies,DrawingEncryption,Express_Tools,Fonts,NFW,Migrate,Ref
Man,Samples,ACS,DCS,VBA,Materials,PLM,VLS,VLT"
if not x64bit then
' To add Autodesk Impression to the install
featuresToInstall = featuresToInstall & ",Impression"
strAdditionalStuff = "ACADSHOWIMPR=" & """" & "1" & """"
end if

70 | Appendix B Use Scripts to Deploy the Program

'''''' Uncomment the relevant version of your installation - De
fault is Standalone
' For Standalone
RunStandaloneInstall()
'
' For Single Network License Server
'RunSingleLicenseServerInstall()
'
' For Redundant Network License Servers
'RunRedundantLicenseServerInstall()
'
' For Distributed Network License Servers
'RunDistributedLicenseServerInstall()
'

' End of Script

Wscript.quit()
'

Function RunStandaloneInstall
shell.run DefaultCommand(),2,1
end function
'

Function RunSingleLicenseServerInstall
' Update with the correct information for the license server
strACADStandaloneNetworkType = "3"
strADSKLicenseServerType = "Single Server License"
strADSKLicenseType = "Network License"
strADSKServerPath = "myFlexServer"
' HOSTID or MAC address
strADSKServerHOSTID = "001122334455"
'
' Consolidate the two values
strADSKServerPath = strADSKServerPath & " " & strADSKServerHOSTID

shell.run MakeCommand(),2,1
end function
'

A Sample Installation Script | 71

 Function RunRedundantLicenseServerInstall
' Update with the correct information for the license servers
strACADStandaloneNetworkType = "3"
strADSKLicenseServerType = "Redundant Server License"
strADSKLicenseType = "Network License"
'
' Format is SERVERNAME1 MACADDR1 PORT1;SERVERNAME2 MACADDR2
PORT2; SERVERNAME3 MACADDR3 PORT3; - Only 3 permitted for redund
ant servers
strADSKServerPath = " myFlexServer 001122334455 27005; myFlex
Server2 006622334455 27005;"
shell.run MakeCommand(),2,1
end function
'

Function RunDistributedLicenseServerInstall
' Update with the correct information for the license servers
strACADStandaloneNetworkType = "3"
strADSKLicenseServerType = "Distributed Server License"
strADSKLicenseType = "Network License"
'
' Format is @SERVERNAME1;SERVERNAME2;SERVERNAME3;
strADSKServerPath = "@ myFlexServer;@ myFlexServer2;@ myFlexServ
er3;"
'
shell.run MakeCommand() & "ACAD_LICENSESERVER_DISTRIBUTED=1",2,1

end function
'

72 | Appendix B Use Scripts to Deploy the Program

Function DefaultCommand
dim retString
' /q for silent install ' /c [key] override parameters for the
key
retString = strSourcePath & "\setup.exe /t /q /c " & productType
& ": "
retString = retString & "INSTALLDIR=" & """" & strADSKPath &
"""" & " "
retString = retString & "ACADSERIALPREFIX=" & strADSKSNPrefix &
" "
retString = retString & "ACADSERIALNUMBER=" & strADSKSNNumber &
" "
retString = retString & "ACADFIRSTNAME=" & """" & strADSKFirst
Name & """" & " "
retString = retString & "ACADLASTNAME=" & """" & strADSKLastName
& """" & " "
retString = retString & "ACADORGANIZATION=" & """" & strADSKOr
ganization & """" & " "
retString = retString & "InstallLevel=" & strInstallLevel & " "

' retString = retString & "ADSK_LAUNCH_MODE=Standalone" & " "

if strInstallLevel = 3 then
retString = retString & "ADDLOCAL=" & """" & "System_Files"
& featuresToInstall & """" & " "
end if
retString = retString & strAdditionalStuff ' Specifically for
Impression Toolbar
DefaultCommand = retString & " "
end function
'

Function MakeCommand
dim retString
retString = DefaultCommand() & " "
retString = retString & "ACADSTANDALONENETWORKTYPE=" & """" &
strACADStandaloneNetworkType & """" & " "
retString = retString & "ACADLICENSESERVERTYPE=" & """" &
strADSKLicenseServerType & """" & " "
retString = retString & "ACADLICENSETYPE=" & """" & strADSKLi
censeType & """" & " "
retString = retString & "ACADSERVERPATH=" & """" &
strADSKServerPath & """" & " "
MakeCommand = retString
end function

A Sample Installation Script | 73

Use Switches and Flags in Scripts
The following table lists all of the switches and flags that are relevant to
installation.

NOTE You must set the installation switch to INSTALLDIR=. If this is not done,
programs that run outside AutoCAD Civil 3D (such as the Portable License utility)
are not installed.

Switches in Installation Scripts

Switch Description

INSTALLDIR= Specifies the location to install the product.

ACADSERIALPREFIX= Specifies the numbers that precede the hyphen

in the serial number.

ACADSERIALNUMBER= Specifies the serial number.

INSTALLLEVEL= Specifies the type of installation: 3=Typical

ACADFIRSTNAME= Specifies the first name personalization.

ACADLASTNAME= Specifies the last name personalization.

ACADORGANIZATION= Specifies the company name.

ADDLOCAL= Used for customized installations where you des-

ignate specific features to install.
See Scripts for Custom Installations (page 75).

User Interface Flags

Flag Description

q Designates that the installation is performed in silent mode.

74 | Appendix B Use Scripts to Deploy the Program

Scripts for Custom Installations
To create a script for a custom installation, use the syntax ADDLOCAL=".....".
The following example shows how component flags are used in the
DefaultCommand section of a script.
Function DefaultCommand
dim retString
' /q for silent install ' /c [key] override parameters for the
key
retString = strSourcePath & "\setup.exe /t /q /c " & productType
& ": "
retString = retString & "INSTALLDIR=" & """" & strADSKPath &
"""" & " "
retString = retString & "ACADSERIALPREFIX=" & strADSKSNPrefix &
" "
retString = retString & "ACADSERIALNUMBER=" & strADSKSNNumber &
" "
retString = retString & "ACADFIRSTNAME=" & """" & strADSKFirst
Name & """" & " "
retString = retString & "ACADLASTNAME=" & """" & strADSKLastName
& """" & " "
retString = retString & "ACADORGANIZATION=" & """" & strADSKOr
ganization & """" & " "
retString = retString & "InstallLevel=" & strInstallLevel & " "

' retString = retString & "ADSK_LAUNCH_MODE=Standalone" & " "

if strInstallLevel = 3 then
retString = retString & "ADDLOCAL=" & """" & "Sys
tem_Files,ACS,Impression,NFW" & featuresToInstall & """" & "
"
end if
retString = retString & strAdditionalStuff ' Specifically for
Impression Toolbar
DefaultCommand = retString & " "

The table below lists all the component flags you can use.

Component Flags

Flag Component

ACS AutoCAD Civil 3D Samples

Scripts for Custom Installations | 75

 Component Flags

Flag Component

CADStandards CAD Standards

Database Database (DBCONNECT)

DCS DesignCenter Samples

DigSig Digital Signatures

Dictionaries Dictionaries

DrawingEncryption Drawing Encryption

Express_Tools Express Tools

Fonts Fonts

Materials Materials Library

Migrate Migrate Custom Settings

NFW New Features Workshop

PLM Portable License Utility

RefMan Reference Manager

Samples Sample files

System_Files Required system files

TM Texture Maps

Tutorials Tutorials

76 | Appendix B Use Scripts to Deploy the Program

 Component Flags

Flag Component

VBA Visual Basic

VLS Visual LISP Samples

VLT Visual LISP Tutorials

Run Scripts
After creating a script, you move it to a server or use a mapped drive letter or
a UNC (universal naming convention) path. If you place it on a server for
users to run, create a share on the server, and then add users to the share with
the rights they need. Because all that users need to do is run the script, provide
read-only access to the share directory.
Next (on the same server or on a different server), create a directory for each
product you want to install. Choose a location for this directory that won't
be changed so that you can point to the MSI files in your scripts. Copy the
product DVD to that directory. You may also want to create directories for
service packs, extensions, and your own customization tools.
You can use any of the following methods to run an installation script:

■ Run the script manually at each individual workstation. To run the

installation, paste the script into the Run dialog box or run it from the
Windows command prompt.

■ Send an email with the UNC path to each user who should run the script.
To run the script, the user follows your instructions.

■ Email the script to each user with instructions for use.

■ Set up the script so that it runs on login.

Run Scripts | 77
78
Use Group Policies to
Install a Deployment C
With group policies, you can advertise this program by In this appendix
assigning the deployment to computers. ■ Introduction
■ Distribute a Deployment
In order for AutoCAD Civil 3D to run properly, the following Through Group Policies
■ Assign a Deployment to
software must be installed on the computer where the program
Computers
is being installed: ■ Verify the Installation of a
Deployment
■ Microsoft .NET 2.0 (available on the product DVD)

■ Microsoft Internet Explorer version 6.0 Service Pack 1 or

later (You can download Microsoft Internet Explorer from

the Microsoft website by visiting www.microsoft.com).

■ Microsoft Installer Package (MSI) 3.1

■ Macromedia Flash™ Player 9.0

■ Autodesk Design Review® 2008

79
Introduction
With group policy objects, this program can be advertised to any computer
that is part of Windows 2000, Windows XP and Windows 2003 Server Active
Directory environments.

Assign a Deployment Using Group Policies

Assign a deployment that was created during the deployment process by the
Installation wizard to a computer. Assigning a deployment to a computer
installs the program the next time the computer is restarted.
A deployment that is assigned to a computer can be used by any user of that
computer. Generally, you should assign the program to a computer if the
computer is used by a large number of users.

NOTE Autodesk products are designed to be installed on a computer so that any

user who logs on to the computer can run the software. If you attempt to assign
this program for a specific user rather than a computer, you may encounter
problems when a second specified user tries to install or uninstall a copy of the
program.

80 | Appendix C Use Group Policies to Install a Deployment

Advantages and Disadvantages of Using Group
Policies
The following table outlines the advantages and disadvantages of using group
policies.

Advantages and disadvantages of group policies

Advantage Disadvantage

■ Works well with the deployment ■ Cannot pass command-line parameters to

functionality of the Installation MSI executable. The solution is to use
wizard. scripts.

■ Easy to add custom files through ■ Cannot customize application settings

the deployment functionality of other than what is set while creating a
the Installation wizard. deployment with the Installation wizard.
■ Deployed to workstation.

■ Simple to implement.

Distribute a Deployment Through Group

Policies
There are three main steps to distributing this program through group policies.

1 Create an application distribution share point. The application

distribution share point is created using the Deployment wizard. Follow
the steps outlined in Use the Installation Wizard to Set Up a Deployment
(page 29) to create a deployment.

2 Assign the program to a computer.

3 Verify the installation. Make sure that the program has been correctly
installed.

Advantages and Disadvantages of Using Group Policies | 81

Assign a Deployment to Computers
When the program is assigned to a computer, it is available to all users of the
computer. The following procedures must be run from the server that has
access to the Windows 2003 Server, Windows XP or Windows 2000 Active
Directory for assigning this program to computers.

To assign a deployment to a computer

1 On the Start menu (Windows), click All Programs (or Programs) ➤

Administrative Tools ➤ Active Directory Users and Computers.

2 In the Active Directory Users and Computers window, right-click the

organizational unit where you want to create the group policy object.
Then click Properties.
The Properties dialog box for the organizational unit you selected is
displayed.

NOTE In order for the group policy object to take effect, the computer objects
must be located in the organizational unit you have selected.

3 In the Properties dialog box, on the Group Policy tab, click New. Enter
a name for the group policy object. For example, enter AutoCAD Civil 3D
Computer Assigned Installation.
The group policy is created and is added to the Group Policy Object Links
list.

4 In the Group Policy Object Links list, click the policy you just created,
and then click Edit.

5 Do one of the following:

■ For Windows 2003 Server: In the Group Policy Object Editor window,
under Computer Configuration, click the plus sign (+) next to the
Software Settings folder to expand it.

■ For Windows 2000 Server: In the Group Policy window, under

Computer Configuration, click the plus sign (+) next to the Software
Settings folder to expand it.

6 Under Software Settings, right-click Software Installation, and then click

Properties.

82 | Appendix C Use Group Policies to Install a Deployment

 7 In the Software Installation Properties dialog box, on the General tab,
click Browse.

8 In the Browse for Folder dialog box, locate the application distribution
share point created in the Deployment wizard, and select the AdminImage
folder. Then click OK.
The Software Installation Properties dialog box displays (in UNC format)
the default package location, the server name, the shared folder that you
selected, and AdminImage. For example:
\\server123\Deployment\AdminImage

9 Do one of the following:

■ For Windows 2003 Server: On the General tab, under New Packages,
click Advanced to specify a method to be used when a new package
is created. This method also allows the transform file created by the
Deployment wizard to be selected.

■ For Windows 2000 Server: On the General tab, under New Packages,
click Advanced Published or Assigned to specify a method to be used
when a new package is created. This method also allows the transform
file created by the Deployment wizard to be selected.

10 Click OK to close the Software Installation Properties dialog box.

11 Do one of the following:

■ For Windows 2003 Server: In the Group Policy Object Editor dialog
box, under Software Settings, right-click Software Installation, and click
New ➤ Package.

■ For Windows 2000 Server: In the Group Policy dialog box, under
Software Settings, right-click Software Installation, and click New ➤
Package.

12 In the Open dialog box, make sure the Windows Installer Packages file
(acad.msi) is selected, and click Open. This default selection is the
application distribution share point that you set earlier.
If you created the administrative image in a location different from the
application distribution share point, find the administrative image
location, and click acad.msi.

13 In the <product name> Properties dialog box, click the Deployment tab.
Under Deployment Type, verify that Assigned is selected.

14 On the Modifications tab, click Add.

Assign a Deployment to Computers | 83

 15 In the Open dialog box, click the transform package file (.mst) created
by the Deployment wizard, and then click Open.
If you created the administrative image in a location different from the
application distribution share point, find the administrative image
location and select the transform package file (.mst).

16 In the <product name> Properties dialog box, on the Modifications tab,

the transform package you selected is added to the Modifications list.
Click OK.

NOTE You must select the transform package file created by the Deployment
wizard when you created the group policy object. You cannot add or remove
transform package files after the group policy object has been created. If you
fail to select a transform package file, the program cannot be installed on the
client computer.

17 Do one of the following:

■ For Windows 2003 Server: In the Group Policy Object Editor window,
under Computer Configuration, click Software Installation. The newly
created program package is displayed in the right pane.

■ For Windows 2000 Server: In the Group Policy window, under

Computer Configuration, click Software Installation. The newly created
program package is displayed in the right pane.

18 Do one of the following:

■ For Windows 2003 Server: Close the Group Policy Object Editor
window and any other open Active Directory windows.

■ For Windows 2000 Server: Close the Group Policy window and any
other open Active Directory windows.

This program is assigned to all computers that are members of the

organizational unit for which the group policy object has been created. The
next time a computer in the organizational unit is restarted, the program will
be installed and will be available for all users of the computer. See Verify the
Installation of a Deployment (page 85) to validate that the group policy has
been created correctly.

84 | Appendix C Use Group Policies to Install a Deployment

Verify the Installation of a Deployment
As a computer is restarted, the operating system displays messages about group
policy, generally just before or after the Windows Login dialog box is displayed.
These messages include the following:

■ Windows starting up

■ Applying computer settings

■ Installing managed software <application>

■ Applying software installation settings

■ Loading your personal settings

■ Applying your personal settings

From a Windows XP or Windows 2000 workstation, users log in under the

organizational unit or computer for which the group policy has been created.

NOTE If problems arise, an entry is logged in the system's Event Viewer under
Applications.

Verify That the Program Is Assigned to a Computer

To verify that this program has been correctly assigned to a computer, restart
a computer that is in the organizational unit for which the group policy was
created. The program is installed before the login prompt is displayed. After
logging in, double-click the program icon on the desktop. A second-time
installation begins. At the completion of the installation, the program starts.

Verify the Installation of a Deployment | 85

86
Use Microsoft Systems
Management Server to
Install a Deployment
D
This appendix provides details for deploying Autodesk software In this appendix
using Microsoft Systems Management Server (SMS). The ■ Introduction
■ Tasks for Deploying
benefits of using SMS to deploy software include software
Autodesk Software with
SMS
distribution to target computers that are dynamically evaluated
■ Create a Collection for
based on a set of administrator-defined rules, and hardware Distributing Autodesk
Software
and software that is inventoried to verify that target computers
■ Set Up a Source Directory
meet setup requirements. Using the Deployment
Wizard
■ Create the SMS Software
In order for AutoCAD Civil 3D to run properly, the following
Installation Package
software must be installed on the computer where the program ■ Create an SMS Program
■ Create an Advertisement
is being installed:
■ Install Autodesk Software
on the Client Computer
■ Microsoft .NET 2.0 (available on the product DVD)

87
■ Microsoft Internet Explorer version 6.0 Service Pack 1 or

later (You can download Microsoft Internet Explorer from

the Microsoft website by visiting www.microsoft.com).

■ Microsoft Installer Package (MSI) 3.1

■ Macromedia Flash™ Player 8.0.22.0

■ Autodesk Design Review® 2008

88 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

Introduction
To deploy Autodesk® software, you must have SMS 2.0 with Service Pack 1 or
later. You should also be familiar with the SMS 2.0 software distribution
process. You can find more information about this topic in the following
resources:

■ Microsoft® Systems Management Server Administrator's Guide

■ Microsoft Systems Management Server 2.0 Administrator Help

■ Microsoft Systems Management Server 2003 Administrator’s Companion

■ Microsoft Systems Management Server Resource Guide

Tasks for Deploying Autodesk Software with

SMS
To deploy Autodesk software with SMS, you must complete the following
tasks:

1 Create a collection for distributing Autodesk software.

2 Set up a source directory using the Deployment wizard.

3 Create the SMS software installation package.

4 Create an SMS program.

5 Create an advertisement.

6 Install the Autodesk software on the client computer.

Create a Collection for Distributing Autodesk

Software
A collection is a set of administrator-defined rules that determine which
computers Autodesk software can be installed on. You can use SMS to create
and maintain collections. Collections gather resources into logical, manageable
groups in ways that help you manage your SMS site. Collections can reflect
the structure and organization of your network by putting resources in groups

Introduction | 89
 such as users, clients, and routers. SMS uses collections as targets during
software distribution to clients.

To create a collection for distributing Autodesk software

1 On the Start menu (Windows), click All Programs (or Programs) ➤ System
Management Server ➤ SMS Administrator Console.

2 In the SMS console window, in the Tree pane, click the Systems
Management Server folder, and then click the plus sign (+) next to the Site
Database folder.

3 In the Tree pane, click the Collections folder.

The Name pane displays all the collections that are currently defined.

4 Right-click the Collections folder. On the shortcut menu, select New ➤

Collection.

5 In the Collection Properties dialog box, on the General tab, enter a name
for the collection; for example, Autodesk software computers. In the
Comment box, enter any comments you want to add.

You now need to create rules to define what resources will be included in the
collection. You can do this by using either the Query Rule Properties toolbar
button or the Direct Membership Rule wizard.

Create a Rule Using the Query Rule Properties

Toolbar Button
The Query Rule Properties toolbar button adds to a collection all resources
that match a set of criteria specified by the query.

To create a rule using the Query Rule Properties toolbar button

1 In the Collection Properties dialog box, on the Membership Rules tab,

click the Query Rule Properties toolbar button.

2 In the Query Rule Properties dialog box, click Browse (next to the Name
box).
A list of available queries is displayed.

3 Select the appropriate query. Start by selecting All Windows Systems, and
then click OK.

90 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

 In the Query Rule Properties dialog box, you can create or modify a query
statement by clicking Edit Query Statement. Under Collection Limiting,
you can limit the queries assigned to a collection by clicking Limit to
Collection.

4 Click OK.

Your new rule is displayed in the Rules list in the Collection Properties dialog
box.

Create a Rule Using the Direct Membership Rule

Wizard
The Direct Membership Rule wizard helps you create direct membership rules
for your collection. In contrast to query-based membership rules, which add
all resources that match a set of criteria, the direct membership rules add
specific resources to the collection. To create direct membership rules, you
locate and select the resources you want to add as direct members of the
collection.

To create a rule using the Direct Membership Rule wizard

1 In the Collection Properties dialog box, on the Membership Rules tab,

click the Create Direct Membership Rule Wizard toolbar button.

2 In the Create Direct Membership Rule Wizard dialog box, click Next.

3 In the Search for Resources dialog box, in the Resource Class list, select
System Resource. In the Attribute Name list, select Operating System
Name and Version. In the Value box enter Microsoft Windows
%Workstation%. Click Next.

4 In the Collection Limiting dialog box, click Browse. A list of available

collections is displayed. Select your collection and click OK.

5 In the Collection Limiting dialog box, click Next.

6 In the Select Resources dialog box, a list of all the resources that meet the
criteria of the collection is displayed. Click Select All or select the resources
you want to include. Future resources that meet the criteria of the
collection will be added. Click Next.

7 In the Completing the Create Direct Membership Rule Wizard dialog

box, click Finish.

Create a Rule Using the Direct Membership Rule Wizard | 91

 The new rule is displayed in the rules list in the Collection Properties
dialog box.

Now you must set the start time for the collection.

To set the start time for the collection

1 In the Collection Properties dialog box, on the Membership Rules tab,

click Schedule.

2 In the Schedule dialog box, set the start time for the collection and select
the Recurrence Pattern that will be supplied. Click OK.

3 In the Collection Properties dialog box, click Apply to apply the settings.
Click OK.

4 In the SMS console window, select the Collections folder in the Tree pane.
The new collection is displayed in the Name pane.

Set Up a Source Directory Using the

Deployment Wizard
When you use SMS to deploy Autodesk software, you set up the source
directory using the Deployment wizard. Using the Deployment wizard is an
easy way to create a source directory, and it also ensures that you can upgrade
the setup package in the future. The Deployment wizard creates an
administrative installation image that is used by SMS to deploy the Autodesk
software to the client computers. It also creates a transform file, also known
as the deployment, which must be used during the installation of AutoCAD
Civil 3D® and AutoCAD Civil 3D-based products on any client computers.
In SMS, the location where you perform the administrative installation
becomes the location of the package source directory. When using the
Deployment wizard to create the source directory, you can include additional
files, such as template files, AutoLISP routines, and custom menus. The
Deployment wizard also installs the Deploy executable file (Deploy.exe) that
is used to deploy the software.
To learn more about setting up the source directory for Autodesk software,
see Use the Installation Wizard to Set Up a Deployment (page 29).
It is strongly recommended that you test the deployment created by the
Deployment wizard before trying to configure SMS to deploy the program. By

92 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

 testing the deployment created by the Deployment wizard, you ensure that
there are no problems with the administrative image and deployment.

To test the Deployment wizard deployment

1 Log on to a Windows 2000 or a Windows XP Professional workstation

as a user who has administrative privileges.

2 Navigate to the source directory where the deployment was created. Use
Windows Explorer or Start ➤ Run.

3 Double-click the deployment shortcut created by the Deployment wizard.

The program is installed or an error is written to the network log file.

Create the SMS Software Installation Package

After creating the source directory using the Deployment wizard, you create
the SMS software installation package. An SMS package contains the files and
instructions that SMS uses to distribute the program to SMS clients. The
Deployment wizard creates the files and instructions, but SMS must be
configured to use these files.

To create a software installation package

1 On the Start menu (Windows), click All Programs (or Programs) ➤ System
Management Server ➤ SMS Administrator Console.

2 In the SMS console window, in the Tree pane, click the Systems
Management Server folder, and then click the plus sign (+) next to the Site
Database folder.

3 In the Tree pane, click the Packages folder.

The Name pane now displays all the installation packages that are
currently defined.

4 Right-click the Packages folder. On the shortcut menu, click New ➤

Package.

NOTE On the shortcut menu, you cannot select Package from Definition
because the program is not creating a package definition file (PDF or SMS
files).

Create the SMS Software Installation Package | 93

 5 In the Package Properties dialog box, on the General tab, enter the
following information:
■ In the Name box, enter a name for the SMS package; for example,
AutoCAD Civil 3D.

■ In the Version box, enter the version of the product you are installing;
for example, 2007.

■ In the Publisher box, enter Autodesk, Inc.

■ In the Language box, enter the language of the product you are
installing; for example, English.

■ In the Comment box, enter any comments that are specific to your
environment.

6 Click the Data Source tab.

7 On the Data Source tab, select the This Package Contains Source Files
option. Click Set.

8 In the Set Source Directory dialog box, select the Network Path (UNC
Name) option.

9 Click Browse. Navigate to the source directory created in the Deployment

wizard. Click OK.
The server name and shared folder that you selected are displayed in the
source directory.

NOTE The administrative image you created with the Deployment wizard
should be displayed in the source directory.

10 In the Set Source Directory dialog box, click OK.

11 In the Package Properties dialog box, click OK.

12 In the Tree pane, click the Packages folder.

The Name pane displays the package you created.

Although the package to install the program on SMS client computers has
been created, it still cannot be installed. You must first create the SMS program
for the package.

94 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

Create an SMS Program
This section details the configuration options you must use when you create
an SMS program for your Autodesk software. Program configuration options
for deploying software are specified in the Program Properties dialog box in
SMS.
There are two methods for defining the Program configuration options with
Autodesk software. The first method uses the Deploy executable file created
by the Deployment wizard for AutoCAD Civil 3D and AutoCAD Civil 3D-based
products. The second method uses Windows Installer.

Use the Deploy Executable Method to Create a

Program
The Deployment wizard used to create the administrative image and source
directory for deploying Autodesk software contains an executable file called
Deploy.exe in the AdminImage folder under the Deployment wizard share.
Deploy.exe is a wrapper for Windows Installer (an executable file that performs
the checks before Windows Installer starts), but it also performs several other
important checks and functions for installing AutoCAD Civil 3D and AutoCAD
Civil 3D-based products. Deploy.exe checks the operating system to ensure
that it meets the minimum requirements for installing AutoCAD Civil 3D.
Deploy.exe also checks to ensure that Windows Installer is version 3.1. If it is
not, Windows Installer 3.1 is installed on the client computer. Deploy.exe is
also responsible for writing successful installations and failures to the network
log file specified in the Deployment wizard. It is strongly recommended that
you use this method when deploying AutoCAD Civil 3D or AutoCAD Civil
3D-based products to SMS client computers.

NOTE The Macromedia Flash Player 8 plug-in (which is installed with AutoCAD
Civil 3D 2008) may cause the SMS 2003 installer to hang.

To create a program using Deploy.exe

1 On the Start menu (Windows), click Programs ➤ System Management

Server ➤ SMS Administrator Console.

Create an SMS Program | 95

 2 In the SMS console window, in the Tree pane, click the Systems
Management Server folder, and then click the plus sign (+) next to the Site
Database folder.

3 In the Tree pane, click the plus sign (+) next to the Packages folder to
expand it. The defined packages are displayed in the Tree pane. Click the
package you created earlier. In the Name pane, the Access Accounts,
Distribution Points, and Programs folders are displayed.

4 In the Name pane, right-click the Programs folder. On the shortcut menu,
click New ➤ Program.

5 In the Program Properties dialog box, on the General tab, enter the
following:
■ In the Name box, enter a name for the program. The name of the
program must be unique because it is used when defining
advertisements. On client computers, the name is displayed in the
Control Panel (Windows), in the Advertised Programs folder.

■ In the Comment box, enter any comments you want to add. Text in
the Comment box is displayed on client computers in the Advertised
Programs Monitor dialog box, or in the Advertised Programs wizard
Control Panel applets.

■ For the Command Line box, click Browse. Navigate to the source
directory where the deployment was created by the Deployment
wizard. Right-click the deployment shortcut and click Properties. On
the Shortcut tab, in the Target box, select all of the text. Right-click
and click Copy. Click Cancel to exit the Deployment Properties dialog
box. Click Cancel to exit the Open dialog box. In the Program
Properties dialog box, in the Command Line box, right-click, and click
Paste. Your text is displayed.

■ In the Run list, select Normal.

■ In the After Running list, select No Action Required.

6 Click the Requirements tab. In the Estimated Disk Space box, specify at
least 750 MB. Select the This Program Can Run Only on Specified
Platforms option. Select the following platforms from the list:
■ All x86 Windows 2000 clients

■ All x86 Windows XP Professional clients

■ x86 Windows 2000 original release clients

96 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

 ■ x86 Windows 2000 Service Pack 1 clients

■ x86 Windows 2000 Service Pack 2 clients

7 Click the Environment tab. In the Program Can Run list, select Only
When a User Is Logged On (In SMS 2.0, you then select the User Input
Required option). Under Run Mode, select the Run with Administrative
Rights option if your users do not have administrative privileges on their
computer. Under Drive Mode, select Runs with UNC Name.

8 Click Apply, and then click OK. In the SMS console window, in the Tree
pane, click the Programs folder to see your new program in the Name
pane.

Use the Windows Installer Method to Create a

Program
When using the Windows Installer method to configure general program
options for Autodesk software, you must specify command line syntax. The
executable program that interprets packages and installs products is Msiexec.exe.
When using the Windows Installer, no entry is written to the network log
file.

NOTE Before you can deploy Autodesk software on your client computers, you
must ensure that the Windows Installer program (Msiexec.exe) is version 3.1 or
later. The Windows Installer 3.1 setup program is included on your Autodesk
product DVD.

In Windows Installer, in the Program Properties dialog box, on the General

tab, enter the following on the command line:
msiexec options < package> .msi

For AutoCAD Civil 3D, <package> is c3d.msi. The following table lists several
command-line options you will use when deploying the AutoCAD Civil 3D
package (c3d.msi). The command-line options are case sensitive. For a complete

Use the Windows Installer Method to Create a Program | 97

 list of options, together with their explanations, consult Microsoft Windows
Installer Help.

Windows Installer Command-line Options

Option Action

/I Installs or configures a product.

/x Uninstalls a product.

/lev Logfile Specifies the path to log file. The flags indicate which informa-
tion to log. e - All error messages v - Verbose output

/qb- Sets the user interface level.

qb - Basic UI

For example, for AutoCAD Civil 3D use the following syntax: msiexec /I c3d.msi
In addition to using the command-line options, you must use Windows
Installer properties. Properties are global variables used during an installation.
You will need to use the TRANSFORMS property to take advantage of the
transform file created by the Deployment wizard. When used, properties must
be specified as follows:
msiexec options <package>.msi PROPERTY=VALUE

The following table lists several command-line properties. The command- line
options are case sensitive. For a complete list of properties and an explanation
of each, see Microsoft Windows Installer Help.

Windows Installer Command-line Properties

Property Action

TRANSFORMS= List of transforms to be applied to the installation

database (acad.msi).

ACAD_SILENT_LICENSE=YES Silent License Agreement.

INSTALLDIR=

98 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

For AutoCAD Civil 3D, use the following syntax for command-line options
and properties:
msiexec /I <path>\c3d.msi TRANSFORMS=<path>\<transform name>.mst /qb-

To use Msiexec.exe to deploy AutoCAD Civil 3D packages

1 On the Start menu (Windows), click All Programs (or Programs) ➤ System
Management Server ➤ SMS Administrator Console.

2 In the SMS console window, in the Tree pane, click the Systems
Management Server folder, and expand the Site Database folder.

3 In the Tree pane, expand the Packages folder. The defined packages are
displayed in the Tree pane. Click the package you created earlier. In the
Name pane, the Access Accounts, Distribution Points, and Programs folders
are displayed.

4 In the Name pane, right-click the Programs folder. On the shortcut menu,
click New ➤ Program.

5 In the Program Properties dialog box, on the General tab, enter the
following:
■ In the Name box, enter a name for the program. The name of the
program must be unique because it is used when defining
advertisements. On client computers, the name is displayed in the
Control Panel (Windows), in the Advertised Programs folder.

■ In the Comment box, enter any comments you want to add. Text in
the Comment box is displayed on client computers in the Advertised
Programs Monitor dialog box, or in the Advertised Programs wizard
Control Panel applets.

■ In the Command Line box, enter a command using Windows Installer

command-line syntax. For AutoCAD Civil 3D, use the following
syntax:

Msiexec /I <path>\c3d.msi TRANSFORMS=<path>\<deployname>.mst/qb-

Replace <path> with the source directory or location of your
administrative image that you created with the Deployment wizard. You
must use the UNC naming convention. Replace <deployname> with the
name of the deployment you created with the Deployment wizard. You
must use the .mst file extension.

Use the Windows Installer Method to Create a Program | 99

 6 Click the Requirements tab. In the Estimated Disk Space box, specify at
least 750 MB. Select the This List Can Run Only on Specified Platforms
option. Select the following platforms from the list:
■ All x86 Windows 2000 clients

■ All x86 Windows XP Professional clients

■ x86 Windows 2000 original release clients

■ x86 Windows 2000 Service Pack 1 clients

■ x86 Windows 2000 Service Pack 2 clients

7 Click the Environment tab. In the Program Can Run list, select Only
When a User Is Logged On. Under Run Mode, select the Run with
Administrative Rights option if your users do not have administrative
privileges on their computer. Under Drive Mode, select Runs with UNC
Name.

8 Click Apply, and then click Close. In the SMS console window, in the
Tree pane, click the Programs folder to see your new program in the Name
pane.

The package program has now been created. Next, you must create an
advertisement for the package.

Create an Advertisement
SMS uses advertisements to distribute SMS programs to SMS client computers.
You create and maintain advertisements by using the SMS Administrator
console window.

To create an advertisement for the package

1 On the Start menu (Windows), click All Programs (or Programs) ➤ System
Management Server ➤ SMS Administrator Console.

2 In the SMS console window, in the Tree pane, click the Systems
Management Server folder, and expand the Site Database folder.

3 In the Tree pane, click the Advertisements folder.

The advertised programs are displayed in the Name pane.

100 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

 4 In the Tree pane, right-click the Advertisements folder, and on the shortcut
menu, click All Tasks ➤ Distribute Software.

5 On the Welcome to the Distribute Software Wizard page of the Distribute

Software wizard, click Next.

6 On the Package page, select the Distribute an Existing Package option (in
SMS 2003, select the Select an Existing Package option), and then, in the
Packages list, select AutoCAD Civil 3D. Click Next.

7 On the Distribution Points page, under Distribution Points, select the

server(s) where the package will be distributed from, and then click Next.

8 On the Advertise a Program page, under Do You Want to Advertise a

Program to a Collection, select Yes, and then verify that the program you
created earlier is displayed in the Programs list. Click Next.

9 On the Select Program to Advertise page, under Programs, select a

program, and then click Next.

10 On the Advertisement Target page, select Advertise the Program to an

Existing Collection, and then click Browse. In the Browse Collection
dialog box, select the collection you created earlier, and then click OK.
On the Advertisement Target page, click Next.

11 On the Advertisement Name page, in the Name box, enter a name for
the advertisement. In the Comment box, enter any comments you want
to add. The name and comments are displayed on the client computer.
Click Next.

12 On the Advertise to Subcollections page, you can specify whether the

advertisement should also be applied to subcollections. Select the option
for your advertisement, and then click Next.

13 On the Advertisement Schedule page, select Yes or No, depending on

whether or not you want the advertisement to expire. Select the expiration
date and time, if applicable. Click Next.

14 On the Assign Program page, select Yes or No, depending on whether

you want to assign the program. An assigned program runs automatically
if it has not already been run on the SMS client. If you select Yes, you
must enter a date and time for when the program becomes assigned. Click
Next.

15 On the Completing the Distribute Software Wizard page, click Finish. In

the SMS console window, in the Tree pane, click the Advertisements folder
to see your new program in the Name pane.

Create an Advertisement | 101

 The Autodesk software is ready to be installed on an SMS client computer.

Install Autodesk Software on the Client

Computer
To install the Autodesk software, log on to a computer with the SMS client
software installed. The computer must be part of the domain being serviced
by the SMS server. If you did not select Run with administrative rights when
creating the program, you need to log on to the computer as an administrator.
You can verify that the computer has the SMS client software installed by
checking for three Control Panel applets: Systems Management, Advertised
Programs, and Advertised Programs Monitor.

NOTE In Windows XP, you will not see these applets until you switch Control
Panel to Classic View.

To install the program on the SMS client computer

1 On the Start menu (Windows), click Control Panel.

2 In the Control Panel, double-click Advertised Programs.

The Advertised Programs wizard is started.

3 On the Welcome to the Advertised Programs Wizard page, click Next.

4 On the Select Programs to Run page, under Advertised Programs, select

the advertised Autodesk program, and then click Next.

5 On the Run Programs Now or Later page, select the Run the Selected
Program Now option, and then click Next.

6 On the Completing the Advertised Programs Wizard page, click Finish.

The Autodesk software program has been installed with SMS. To explore other
methods for installing Autodesk software using SMS, and to read more about
the advanced features of SMS, consult the SMS documentation.

102 | Appendix D Use Microsoft Systems Management Server to Install a Deployment

Distribute the Product
Using Imaging Software E
The following information is provided for those who use disk In this appendix
imaging software, such as Norton Ghost, to create a master ■ Use a Master Image to
Distribute Multi-Seat
image to distribute Autodesk products. Once created, the Stand-Alone Products to
Multiple Systems
master image is then replicated to other computers throughout
■ Use a Master Image to
your facility. Distribute Network
Licensed Products to
Multiple Systems
Care needs to be taken since the use of imaging software can
■ Restore the Master Image
result in: ■ Clean a Master System and
Restore the Operating
System
■ Conflicts with the product licensing

■ Incomplete installations and problems with activation

NOTE If you are experiencing licensing instability in a SATA

RAID environment, using imaging software to distribute

Autodesk products can cause product activation problems,

such as “Activation code limit exceeded” when you attempt

to activate.

103
104 | Appendix E Distribute the Product Using Imaging Software
 Use a Master Image to Distribute Multi-Seat
Stand-Alone Products to Multiple Systems
You can distribute the product using a master image for a multi-seat
stand-alone product.

NOTE When using Norton Ghost, you must use the -ib switch to include the boot
sector in your master image. Consult your imaging software for more details on
including the boot sector as part of the master image.

Master images should not be created if you’ve previously run Autodesk products
on the master computer. Cleaning the system may be necessary. See Clean a
Master System and Restore the Operating System (page 107).

To distribute a multi-seat stand-alone product to multiple computers

using a master image

1 Create a network deployment for a multi-seat stand-alone product. For

more information, see Use the Installation Wizard to Set Up a Deployment
(page 29).

2 Install the Autodesk product from the deployment onto the master
computer.

3 Do one of the following on the master computer:

■ Create a master image, including the boot sector. Test the product on
a machine other than the master computer before distributing the
product. Launch the product on the other machine, and register and
activate it. Users have a 30-day grace period to register and activate
the product on their machines.

■ Launch and customize the product as necessary. Create a master image

and distribute it to users. If users’ computers are connected to the
Internet, the product is automatically activated. Users whose
computers are not connected to the Internet have a 7-day grace period
to register and activate the product.

4 Apply the master image to the target computers.

Use a Master Image to Distribute Multi-Seat Stand-Alone Products to Multiple Systems | 105
Use a Master Image to Distribute Network
Licensed Products to Multiple Systems
You can distribute the product using a master image for a network licensed
product.

To distribute a network licensed product to multiple computers using

a master image

1 Create a network deployment for a network licensed product. For more

information, see Use the Installation Wizard to Set Up a Deployment
(page 29).

2 Install the Autodesk product from the deployment onto the master
computer.

NOTE A license server must be running, and each computer must be

connected to the network in order for the product to obtain a license.

3 After the Autodesk product has been installed, use imaging software to
create a master image of the system's hard drive.

4 Apply the master image to the target computers.

Restore the Master Image

The following procedure assumes that you have saved a copy of each
workstation’s Software Licenses folder (and Product Licenses folder, if present)
to either another workstation or a DVD before you reformat the workstation.

To restore a product using a master image

1 Exit the application. Do not run the application again until after you
have completed this procedure.

2 In Windows Explorer, copy the Software Licenses folder from the

appropriate path shown below to a location other than the disk that will
be restored.
C:\Documents and Settings\All Users\Application Data\Autodesk\Software
Licenses

106 | Appendix E Distribute the Product Using Imaging Software

 3 Reformat the workstation and restore the master image.

NOTE Do not perform a low-level format of the hard drive.

4 Copy the Software Licenses folder that you created in step 2 to its original
workstation and location on that workstation.

NOTE When you restore the disk image, any files that were altered are put back
in their original state and ready to use again. The license files are preserved, and
no reactivation of products is necessary.

Clean a Master System and Restore the

Operating System
If you have already run the Autodesk product on the master computer, the
master computer should be properly cleaned first.

To clean a master computer and restore the operating system

1 Clean the hard drive, including the boot sector.

For example, if you use Norton’s GDISK utility, use the following
command:
gdisk 1 /diskwipe
Where 1 is the hard disk that is being wiped.

NOTE If you use a utility other than Norton Ghost, make sure that it cleans
the boot sector; otherwise, you will not be able to activate Autodesk products.

2 Create a new partition and use the restore CD or product CD to install

the operating system.

Clean a Master System and Restore the Operating System | 107

108
Glossary

activate Part of the Autodesk software registration process, it allows you to

run a product in compliance with the product's end-user license agreement.

Active Directory A directory service from Microsoft that is part of Windows

2000 and Windows 2003 Server.

administrative image A collection of shared file resources created by the

Deployment wizard and used by deployments to install the program to network
workstations. Service packs (patches) can be applied to an administrative image
using the Deployment wizard.

advertising A pull technology that notifies users of an updated software

product that is available for installation. Users typically double-click a shortcut
(or do a similar operation) to complete the installation of the advertised
product.

AutoCAD Civil 3D startup accelerator (acstart17.exe) A runtime process that

can accelerate the initial startup of AutoCAD Civil 3D.

deploy Install an Autodesk product to one or more computers on a network.

deployment A link to a unique MST (Microsoft Transform) file that serves as

a basis for an installation. Using the Deployment wizard, administrators can
create multiple deployments that result in different types of installations for
users.

directory service A network service that identifies all resources on a network

and makes them accessible to users and applications. Resources include email
addresses, computers, and peripheral devices such as printers. Ideally, the
directory service should make the physical network topology and protocols
transparent so that a user on a network can access any resource without
knowing where or how it is physically connected. Virtually all directory services
are based on the X.500 ITU standard.

FLEXlm License management technology from Macrovision Software, Inc.

FLEXlm provides administrative tools that help to simplify management of
network licenses. FLEXlm can be used to monitor network license status, reset

Glossary | 109
 licenses lost to a system failure, troubleshoot license servers, and update
existing license files.

group policy Microsoft server technology that provides a way to do push

installations and advertising-based installations using standard Microsoft 2000
Server administration components.

installation image A deployment that consists of an MSI file, any associated

transforms, additional user-specified custom files, and profile and registry
settings.

MSI Microsoft installer that supports a variety of parameters that can be

scripted.

MSP Microsoft patch file (see also patch).

MST Microsoft transform file. Modifies the components installed by the MSI
file. For example, the Deployment wizard creates an MST file with the settings
that you specify. The deployment created by the Deployment wizard uses the
MST file in conjunction with the MSI file and MSIEXEC to install the program
on local workstations.

multi-seat stand-alone installation A type of installation where multiple

stand-alone seats of the program are installed using a single serial number.

partial profile A profile that contains partial registry information

corresponding to a subset of the options available from the Files tab of the
Options dialog box.

patch A software update to an application.

power user A user with rights to access and write to the Program Files folder
and the HKEY_Local_Machine folder of the registry.

pull technology An installation technology that requires user interaction to

complete the installation.

push technology An installation technology that installs files to a remote

desktop without any user interaction.

scripting The process of using scripting languages such as VB Script to facilitate

the deployment of software packages.

service pack An Autodesk term for an application patch (see also patch).

silent installation An installation that proceeds without any explicit user

input. No dialog boxes are presented that require interaction from the user.

110 | Glossary
SMS Microsoft Systems Management Server. A tool that helps administer
networked machines by allowing remote configuration, push deployments,
and user administration. SMS is an expensive technology that must be
purchased as an additional server.

transform See MST.

Glossary | 111
112
Index
A Autodesk products 7, 11, 20, 31–32, 49,
51, 58, 60
acstart17.exe file 109 advertising. See advertising
activation 2, 34 deployments
multi-seat stand-alone deployments of. See deployments of
installations 2 Autodesk products
of stand-alone installation types 34 enabling/disabling updates 49, 51
stand-alone installations 2 network registration 7
Active Directory 109 personalizing 31–32
additional files 44–45 registering 7, 58
installing 44–45 serial numbers 11
administrative images 11, 13, 20, 48, system requirements 20
60, 63, 109 uninstalling 60
creating 11, 13 AutoLISP (LSP) applications 92
defined 109 installing 92
file for. See acad.msi file
in deployment 63
merging service packs into 48
C
MSI files. See acad.msi file CAD Manager Channel 52
pointing users to (deployment CAD standards (custom feature for
shortcut) 60 stand-alone installation) 15, 41
system requirements 20 cleaning computer hard drives 107
advertising deployments 63–64, 80, client computers. See client workstations
100, 109 client installations 11, 13, 38–40, 67,
administrative images and 63–64 110
defined 109 setup types (feature
process 64 configurations) 38–40
SMS packages 100 silent installations 67, 110
using group policies 80 specifying location 11, 13, 39
applications See also network installations
advertising. See advertising client log file 32–33
deployments location 32–33
assigning. See assigning deployments client workstations 20, 63–64, 80, 82,
publishing. See publishing 85, 109
deployments advertising deployments on 63–64,
assigning deployments using group 109
policies 80, 82, 85 assigning deployments to 80, 82,
to computers 80, 82, 85 85
verifying assignments 85 installing the program on. See network
to users 80 installations
system requirements 20

Index | 113
collections (of Autodesk software setting up deployments 11, 29–30
distribution rules) (SMS) 89–92 deployments of Autodesk products 2,
creating 90 11, 30–31, 48–49, 55–57, 59, 63–
direct membership rules 91 64, 80–81, 85, 92–93, 100, 109
resource definition rule 90 advertising 63–64, 80, 100, 109
start time for 92 SMS packages 100
communication protocols 20–21 using group policies 80
system requirements 20–21 assigning. See assigning deployments
computers. See client workstations using group policies
configuring 8, 13 confirming setup information 55–
installation with Installation 57
wizard 13 creating (setting up) 2, 11, 30–31
license servers 8 distributing, through group
custom installations 31, 38, 40, 75 policies 81
feature choices 40 to dynamically evaluated computers.
scripts for 75 See SMS (Systems
creating 75 Management Server)
selecting 31, 38 file for. See MST (Microsoft Transform)
custom menus 92 files
installing 92 including service packs 48–49
Customer Error Reporting installing
notification 54–55 via advertising 64
Customer Experience Improvement via group policies. See group
Program participation 54 policies
customizing 13 via RIS. See RIS (Remote
installation 13 Installation Services)
via scripts. See installation scripts
via SMS. See SMS (Systems
D Management Server)
database access tools 15, 40–41 See also network installations
installing 15, 40–41 modifying 59
DC Online tab (DesignCenter) 53, 55 to remote computers. See RIS (Remote
access to online resources 53 Installation Services)
turning DesignCenter Online shortcuts to 63–64
on/off 55 starting 30
Deploy.exe file 92, 95 testing 92–93
deploying Autodesk products 20, 109 verifying group policy deployment
defined 109 installations 85
system requirements 20 DesignCenter Online 52–53, 55
deployment of Autodesk products 10, accessing content 52
17 DC Online tab 53
distributing deployments 10 turning on/off 55
methods 17 desktop shortcut icon 16, 46
network shares and 17 installing 16, 46
Deployment wizard 2, 11, 29–30, 92
creating deployments 2

114 | Index
dictionaries for spelling checker 15, 40– folders 1, 44–45, 92, 109
41 Active Directory 109
installing 15, 40–41 adding or deleting during
Direct Membership Rule wizard 91 installation 44–45
direct membership rules (for SMS source directory 1, 92
collections), creating 91 subfolders 44–45
directory services 109 fonts 15, 40, 42
distributed license server model 3, 35 installing 15, 40
defined 3 program fonts 15, 42
selecting 35
distributing deployments through group
policies 81
G
distributing the Autodesk program 107 GPOs. See group policy objects
Drawing Encryption utility 15, 40–41 graphics adapters 22
installing 15, 40–41 system requirements 22
drives 107 group policies 80–82, 85, 110
cleaning 107 advantages and disadvantages 81
advertising deployments using 80
E assigning deployments using 80,
82, 85
error reporting (to Autodesk) 54–55 to computers 80, 82, 85
Customer Error Reporting (CER) 54– to users 80
55 creating group policy objects 82
Ethernet network configurations 20 defined 110
Express Tools 14–15, 39–41 distributing deployments
installing 14–15, 39–41 through 81
optional installation 39 editing group policy objects 82
extracting 48 installation messages 85
MSP files 48 verifying deployment
installations 85
F
H
file locations 43
modifying 43 hard disks 20, 107
modifying defaults 43 cleaning 107
using defaults 43 system requirements 20
files 30, 44–45, 51, 83–84, 92, 110 See also drives
installing additional files 44–45, 92 hardware requirements 20
MSI files. See acad.msi file administrative images 20
MSP files 110 client workstations 20
MST files 30, 83–84, 92, 110 license servers 20
naming text files for patches 51 Help 52
flags (in installation scripts) 75 InfoCenter search settings 52
components flags 75 host ID (license server) 7
FLEXlm tools 109 entering 7

Index | 115
I via group policies. See group policies
via RIS. See RIS (Remote Installation
imaging software 105–107 Services)
InfoCenter 52 via scripts. See installation scripts
configuring search results 52 via SMS. See SMS (Systems
installation directory 44–45 Management Server)
adding or deleting files 44–45 See also client installations
adding or deleting folders 44–45 See also network installations
installation images 110 installing programs (stand-alone) 107
defined 110 cleaning computers before 107
installation information 11, 13, 56–57 imaging software 107
log files 13 installing utilities 5–6
saving 11, 56–57 Network License Activation utility 6
installation messages about group Network License Manager 5
policies 85 Internet (Web) 52
installation packages. See software searching 52
installation packages Internet Explorer (Microsoft) 20–21, 46,
installation scripts 65, 67–68, 74–75, 63, 65
77, 110 modifying defaults 46
components flags 75 Service Packs 21
creating 67, 110 system requirements 20, 63, 65
for custom installations 75
creating 75
running 77
L
sample scripts 65, 67–68 license files 7–8
silent installations 67 insert new file options 8
typical installations 68 modifying 7
switches 74 overwriting existing file options 8
uses 65 save location 8
See also scripts license servers 3, 8–9, 20, 34–36
installation switch 74 See also network license installations
installation types 2 configuring 8
Installation wizard 11, 13 models 3, 34–36
configured installations 13 saving configurations 9
setting up deployments 11, 13 system requirements 20
installing 26, 39–40, 44–45 Live Update 49, 51
additional files 44–45 enabling/disabling Autodesk product
feature choices 40 updates 49, 51
optional tools 39–40 lmgrd.exe (license manager daemon) 9
preliminary tasks 26 path to 9
installing files 92 running as a service 9
additional files 92 starting on system startup 9
installing programs (network) 64, 107 log files 32
cleaning computers before 107 types 32
imaging software 107 See also client log file
via advertising 64 See also network log files

116 | Index
M multi-seat stand-alone installations 2–
3, 34, 37, 105, 110
master images 105–106 imaging software 105
Materials library 39–40 license server model 3
installing 39–40 registration data 34
Materials Library 15 selecting 2, 37
installing 15
messages, group policy installation
messages 85
N
Microsoft .NET 63, 65 naming 51
system requirements 63, 65 text files for patches 51
Microsoft Installer (MSI) files 83, 97, 110 network adapters 7, 20
command line options 97 network interface cards 20
defined 110 selecting 7
selecting 83 network administration, Quick Start 1
Microsoft Internet Explorer 20–21, 63, network deployments. See deployments of
65 Autodesk products
Service Packs 21 network installations 2, 11, 20, 25–26,
system requirements 20, 63, 65 34–36, 55–57, 64, 67, 110
Microsoft Patch (MSP) files 110 confirming setup 55–57
defined 110 to dynamically evaluated computers.
Microsoft Scripting Engine 65 See SMS (Systems
Microsoft Systems Management Server. See Management Server)
SMS (Systems Management preliminary tasks 26
Server) to remote computers. See RIS (Remote
Microsoft Transform (MST) files 30, 83– Installation Services)
84, 92 saving installation information 11,
Microsoft Windows. See Windows 56–57
(operating system) silent installations 67, 110
Migrate Custom Settings utility 40, 42 system requirements 20
installing 40, 42 types 2, 34–36
modifying 30, 59 selecting 2, 34–36
deployments 30, 59 See also network license
MS Advertising. See advertising installations
MSI (Microsoft Installer) files 110 via advertising 64
Msiexec.exe file 97, 99, 110 via group policies. See group policies
deploying SMS packages 99 via scripts. See installation scripts
MSP (Microsoft patch) files 48, 110 See also client installations
defined 110 network interface cards 20
extracting 48 system requirements 20
MST (Microsoft Transform) files 83–84, Network License Activation utility 6–7
92, 110 installing 6–7
See also deployments of Autodesk network license installations 2, 34–36,
products 106
MST (Microsoft Transform) files, in imaging software 106
deployments 30 license server models 34–36

Index | 117
 selecting 2, 34–36 Portable License utility 15, 40, 42
Network License Manager 5, 20, 34 installing 15, 40, 42
installing 5 power users 110
stand-alone installation types processors 20
and 34 system requirements 20
system requirements 20 products. See Autodesk products
network license servers. See license servers profiles 46, 110
Network Licensing Guide, accessing 3 default names 46
network log files 11, 32–33 partial profiles 110
location 11, 32–33 pull technology 110
network shares 10, 17, 92 See also advertising
creating 10, 92 push technology 110
deploying Autodesk products
with 17
New Features Workshop 15, 40, 42
Q
installing 15, 40, 42 Query Rule Properties toolbar button 90
notification 54–55 Quick Start 1
resolved errors 54–55 network administration 1

O R
OpenGL drivers 20 RAM 20
system requirements 20 system requirements 20
operating systems 20, 107 redundant license server model 3, 36
client workstation requirements 20 defined 3
license server requirements 20 selecting 36
restoring 107 Reference Manager 15, 40, 42
system requirements 20 installing 15, 40, 42
optional tools 39–40 Register Today pages (Deployment) 58
completing 58
P registering and activating Autodesk
products 7, 58
partial profiles 110 Remote Installation Services. See RIS
patches (service packs) 21, 48–49, 51, (Remote Installation Services)
110 reporting errors 54–55
extracting 48 resolving reported errors 54–55
including in deployment 48–49 restoring 106–107
naming text files for 51 installation from master images 106
system requirements 21 operating systems 107
personal information 11, 13, 31–32 rules. See collections (of Autodesk software
entering 11, 13, 31–32 distribution rules) (SMS)
physical network adapters 7
selecting 7
pointing devices 20
S
client workstation requirements 20 sample files 16, 42

118 | Index
saving 11, 56–57 software installation packages. See SMS
installation information 11, 56–57 packages
screen display 20 SMS packages 93, 95, 97, 99–100
client workstation requirements 20 advertising 100
scripts 65 creating 93
system requirements 65 deploying 99
See also installation scripts installation program for,
search paths 43 creating 95, 97
modifying defaults 43 software installation packages 30, 83–
using defaults 43 84, 92, 110
searching 52 MSI files. See acad.msi file
InfoCenter settings 52 MST files 30, 83–84, 92, 110
serial numbers (for Autodesk SMS. See SMS packages
products) 11 software patches. See patches (service
entering 11 packs)
servers source directories (network shares) 92
license. See license servers creating 92
SMS. See SMS (Systems Management stand-alone installations 2, 37, 58, 65
Server) registering 58
service packs. See patches (service packs) scripting 65
setup.exe files 67 selecting 2, 37
location 67 See also client installations
shortcut icons 16, 46 starting 9
desktop shortcut icon 16 lmgrd.exe license manager daemon
silent installations 67, 110 on system startup 9
defined 110 startup accelerator 109
sample script 67 definition 109
single license server model 3, 34 subfolders 44–45
defined 3 Subscription Center 52–53, 55
selecting 34 accessing 52
SMS (Systems Management Server) 87, turning on/off 53, 55
89, 102, 111 system requirements 20, 63, 65
benefits 87 administrative images 20
collections (of rules) for. See client workstations 20
collections (of SMS Internet Explorer 20, 63, 65
deployment distribution license servers 20
rules) network installations 20
collections. See collections (of scripts 65
Autodesk software Systems Management Server. See SMS
distribution rules) (Systems Management Server)
defined 111
information resources 89
installation packages. See SMS
T
packages TCP/IP protocol 21
installing the program with 102 testing 92–93
preliminary tasks 89 deployments 92–93

Index | 119
text editors (multiline text) 16 VBA Support tutorials 16
default 16 VBS (installation script) files 67
text files 51 verifying group policy deployment
naming for patches 51 installations 80, 85
textures 39–40 video cards 22
installing 39–40 system requirements 22
transform files (MST files) 30, 83–84, video display. See screen display
92, 110
TRANSFORMS property (Windows
Installer) 98
W
transforms. See MST (Microsoft Transform) Web browsers 20
files client workstation requirement 20
tutorials 16 Windows (Microsoft) 20–21
typical installations 38–39, 68 Service Packs 21
scripts for 68 system requirements 20
sample script 68 Windows Installer 97–98
selecting 39 command-line options 97
command-line properties 98
U creating an SMS package installation
program 97
uninstalling 60 TRANSFORMS property 98
programs 60 wizards 13
users, assigning deployments to 80 Installation wizard 13
workstations, client. See client
workstations
V
VBA support 40, 42
installing 40

120 | Index