AUTODESK CIVIL 3D CAD MANAGER’S GUIDE
7
• The addition of user-defined or third-party add-ons
In addition to the benefits at the time of initial deployment, network installations make it
easy to add updates, service packs, and extensions to the original image when creating
new deployments.
It is important to note that you can also use the Network Installation wizard to create
installation images for use in stand-alone installations. This is called a multiseat stand-
alone deployment. In these environments, the client workstations won’t use the license
manager but can still take advantage of the benefits listed previously.
IT Coordination
After you have determined what software to install, and which machines that software will
be installed on, you need to coordinate the installation with your IT department (if this
involves personnel other than yourself). Items to consider include the following:
• What operating system are you using on the client and server? Only Microsoft
®
Windows
®
systems are supported (Novell
®
, Unix
®
, and Linux
®
systems are not
supported).
• Who will perform the installation? The CAD manager or the IT department?
• Who will authorize the software (obtain licenses, activate software, and so forth)?
• Who will download and install updates and service packs?
• Do you have administrator access to the workstations?
• Do you have administrator access to the server?
• Can you reboot the server (if installing FLEXlm
®
license management software)?
• When will the installation take place? After hours? On weekends?
• How long will the installation take?
• Will the software be installed in stages or simultaneously to all users?
• What must happen before the installation? Hardware upgrades, new computers,
and so forth?
• Do you have antivirus software? Can you temporarily disable it?
• Has your key data been backed up, and risk to data minimized?
Single-Site and Multisite Issues
Your organization may have multiple locations where Civil 3D is to be used. There are
generally no problems with this type of configuration, unless you have specific needs,
such as employees from multiple offices working on the same project at the same time. A
multisite configuration may experience poor system performance, legal issues, or both,
relating to which license structure you choose. Whether you have a single site, multiple
individual sites, or multiple sites that act as one, you need to consider the following:
• Will you share licenses between sites?
• Do you have enough licenses to meet all users’ needs in all offices?
• Do you require licensing reporting (SAMreport)?
• Do you want to create license restrictions?
