The DriveWorks installer supports numerous command line parameters that modifies or alters how it runs.
The installation command must be prefixed with the name of the installation file in quotes, for example:
|Uninstall||Specified that DriveWorks should be uninstalled, this is the equivalent to right clicking and selecting "Uninstall" in Programs & Features in Windows.||/uninstall|
|Silent||s||Same as Quiet.1||/silent /repair|
|Repair||Specifies that the current installation should be repaired. This is the equivalent to right clicking and selecting "Repair" in Programs & Features in Windows.||/repair|
|Quiet||q||Specifies that no UI should be shown for the installer. The installer will automatically take the appropriate action, considering other specified arguments.||/quiet /uninstall|
|NoRestart||Specifies that the installer should not prompt to restart the computer, if a restart is deemed necessary by the installer.||/norestart|
|Modify||Specifies that the current installation should be modified. This is the equivalent to right clicking and selecting "Modify" in Programs & Features in Windows.||/modify|
|Log||l||Specify the path to the log file the installer will create.||/log C:\Temp\MyInstallLog.txt|
|Layout||Prepares the installation, and downloads any required files to the given optional path. Note that DriveWorks currently does not need to download anything, rendering this command pointless. The result therefore will be the same as running /install||/layout D:\DriveWorks\PreparedInstaller|
|Install||Performs a normal installation (This is the default).||/install|
|Force||f||Forcibly close all application that prevent setup from running (This is required If you have the live synchronization server running, and want to perform a silent installation).||/force|
|Extract||x||Extracts the bundled Windows Installer MSIs from the bootstrapper to the given directory, or the same directory as the bootstrapper if no path was specified. This is only required for advanced deployment scenarios where MSIs are required. All users are encouraged to use the combined bootstrapper whenever possible.||/x C:\Temp\DWExtracted|
|Schedule||Will allow installation to resume after a reboot.
This is useful if your DriveWorks installation required the .NET framework to be installed.
If this happened your PC would likely require a reboot before continuing the DriveWorks installation.
Right click on the command prompt launcher and select Run as administrator.
The table below shows which features are installed when using the specified installation command.
|DriveWorks Pro (Clients)||DriveWorks Pro (Network)||Common Components|
|Installation Command||Administrator||User||3D Workshop||Autopilot||License Manager||Live||Pro Server||Data Management Tool||Documentation||License Management Tool||3D Export for SOLIDWORKS|
See Examples below for more information.
|"InstallDriveWorksPro-[version].exe" /silent /install||Installs Admin, User, 3D Workshop, Data Management, Group Upscale, License Manager.|
|"InstallDriveWorksPro-[version].exe" /silent /install /schedule||Installs Admin, User, 3D Workshop, Data Management, Group Upscale, License Manager.
Will continue the installation after rebooting if .NET has been installed during the first install.
|"InstallDriveWorksPro-[version].exe" /uninstall||Uninstalls DriveWorks|
|"InstallDriveWorksPro-[version].exe" /install installfeatures=driveworksadministrator||Installs Admin, Data Management, Group Upscale, License Manager.|
|"InstallDriveWorksPro-[version].exe" /install installfeatures=driveworksadministrator|driveworkslive||Installs Admin, Data Management, Group Upscale, License Manager and Live.|
|"InstallDriveWorksPro-[version].exe" /silent /uninstall /force||Uninstalls DriveWorks silently and forcibly closes any applications that prevent it running.|
|"InstallDriveWorksPro-[version].exe"/install installfeatures=* /log c:\DWLog\InstallAll.txt||Installs all DriveWorks modules and creates a log file.|
|Knowledge Base Article Ref:||KB16071802|