AUTODESK CIVIL 3D CAD MANAGER’S GUIDE
6
Chapter 2: Deployment
Considerations and Options
Installation Issues
This chapter covers planning issues related to the deployment of Autodesk Civil 3D
software. Issues to consider include what software needs to be installed, how the
installation will be performed (network deployment or individual machines), and who will
perform the installation (you or an outside consultant).
Software to Be Installed
The first consideration is to determine what software to install. In the civil/survey sector,
software could include the following:
• Autodesk Civil 3D/Autodesk
®
Survey add-ons (Trimble
®
Link, Leica
®
X-Change,
Carlson Connect)
• Autodesk Vault and Autodesk Vault Explorer
• Autodesk
®
Land Desktop Companion/Survey Extensions (Trimble Link, Leica X-
Change, Carlson Connect)
• Autodesk
®
Civil Design Companion
• Autodesk
®
Raster Design
• Autodesk service packs, updates, and fixes
• Third-party applications that run on top of Civil 3D or Land Desktop
• Autodesk
®
DWF™ Viewer; DWG TrueView™
• Autodesk Express Tools
New Autodesk Civil 3D users may want to install Land Desktop Companion, Civil Design
Companion, or both. These applications can be installed in a manner similar to that used
for Autodesk Civil 3D, either stand-alone or as a network deployment.
Once you have determined what to install, document the order in which the software
needs to be installed. Be sure to document any patches, service packs, or fixes installed.
Finally, document what machines the software will be installed on. This documentation
helps you determine hardware requirements in the next section.
Autodesk Civil 3D includes a Network Installation wizard. This wizard enables you to
create either a multiseat stand-alone or network deployment file so you can push the
installation to the workstations rather than use the installation CD at each machine. This
wizard drastically reduces installation time if you need to install on multiple machines.
Network installations provide many benefits, especially for large deployments, including
the following:
• Flexibility in how the application is delivered to the workstations (either “pushed”
from the server or “pulled” by the workstation)
• Standardization of the initial application settings, such as user interface and
support path configuration
