2010
Table Of Contents
- Contents
- Welcome to Autodesk Navisworks Simulate 2010
- Installation
- Quick Start to Stand-Alone Installation
- Prepare for Installation
- Install and Run Autodesk Navisworks Simulate 2010
- Move to Autodesk Navisworks from a Previous Release
- Install Autodesk Navisworks for Multiple Users
- Quick Start to Network Administration and Deployment
- Set Up a Deployment
- Installation Troubleshooting
- General Installation Issues
- How can I check my graphics card driver to see if it needs to be updated?
- When performing a Typical installation, what gets installed?
- Why should I specify the Project Folder and Site Folder?
- How do I share the Autodesk Navisworks settings on a site and project basis?
- Where are my product manuals?
- How do I register and activate Autodesk Navisworks?
- Deployment Issues
- Licensing Issues
- Networking Issues
- Uninstall and Maintenance Issues
- When adding or removing features, how can I tell what features get installed by default?
- Is it possible to change the installation folder when adding or removing features?
- When should I reinstall the product instead of a repair?
- Do I need my original disk to reinstall my software?
- When I uninstall my software, what files are left on my system?
- General Installation Issues
- Quick Start to Stand-Alone Installation
- Quick Start
- Get a Whole-Project View
- Work with Files
- Native File Formats
- Compatible CAD Applications
- Use File Readers
- 3DS File Reader
- ASCII Laser Scan File Reader
- Bentley AutoPLANT File Reader
- CIS2 File Reader
- DWG/DXF/SAT File Reader
- DWF File Reader
- DGN File Reader
- Faro Scan File Reader
- IFC File Reader
- IGES File Reader
- Inventor File Reader
- JTOpen File Reader
- Leica Scan File Reader
- MAN File Reader
- PDS File Reader
- Riegl Scan File Reader
- RVM File Reader
- SketchUp SKP File Reader
- STEP File Reader
- STL File Reader
- VRML File Reader
- Z+F Scan File Reader
- Use File Exporters
- Manage Files
- Explore Your Model
- Control Model Appearance and Render Quality
- Review Your Model
- Use Viewpoints and Sectioning Modes
- Record and Play Animations
- Work Within a Team
- Share Data
- Work with Files
- Animate Objects
- Create Photorealistic Visualizations
- Simulate Construction Scheduling
- Autodesk Navisworks Reference
- File Options Dialog Box
- File Units and Transform Dialog Box
- New Link Dialog Box
- Edit Link Dialog Box
- Edit Viewpoint Dialog Box
- Options Editor
- Default Collision Dialog Box
- Collision Dialog Box
- Convert Object Properties Dialog Box
- Culling Options Dialog Box
- Customize Dialog Box
- Customize Keyboard Dialog Box
- Edit Key Frame Dialog Box
- Publish Dialog Box
- Background Settings Dialog Box
- QTVR Object Movie Settings Dialog Box
- Export Rendered Image Dialog Box
- Image Export Dialog Box
- Animation Export Dialog Box
- Glossary
- Index
If I choose to create a log file, what kind of information does the log file contain?
There are two types of log files that can be generated that monitor information about deployments and
installations.
■ The Network log file keeps a record of all workstations that run the deployment. 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.
■ The Client log file 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.
What is an administrative image (MSI) file?
An administrative image is a collection of shared file resources created during the deployment process and is used
by deployments to install the program to networked workstations. An.msi file is a Microsoft Installer file.
What is the impact of selecting all products to be included in the administrative
image?
If you elect to include all products in your deployment, the administrative image will be larger.
You should select all products only when you create multiple deployments from this image and prefer not to
use the installation disk. If there are products you rarely or never use, and you do not expect to create additional
deployments, you should only select a subset of products.
You can still create a deployment at a later date, and include additional products, but you need to create a new
administrative image. You need the installation media to do so.
Uninstall and Maintenance Issues
This section outlines common issues and their solutions with regards to adding and removing features, reinstalling
or repairing your installation, and uninstalling products.
When adding or removing features, how can I tell what features get installed
by default?
To quickly see what gets installed during a typical, default installation, click the Restore Defaults button on the
Add/Remove Features page.
Is it possible to change the installation folder when adding or removing
features?
Once your product is installed, you cannot change the installation path from the Add/Remove Features page.
Changing the path while adding features results in program corruption, so it is not an option.
When should I reinstall the product instead of a repair?
You should reinstall your product if you accidentally delete or alter files that are required by the program. Missing
or altered files adversely affect the performance of your product and cause error messages when you try to execute
a command or find a file.
If an attempt to repair an installation fails, reinstalling is the next best option.
50 | Chapter 3 Installation