We have received inquires about script installations, silent installations, and the like. Below are excerpts from actual questions asked of us:
"I'm preparing e-SPECS for installation and am in the planning process with several colleagues for a firm-wide roll-out of e-SPECS for Revit. The number if installations will be in the hundreds. With the number of installations we are facing and the process in which we typically deploy applications I would like to know from you anything you can provide regarding large scale deployments with silent installation configurations."
"...in terms of command line install with switches for silent install and also configuration to the e-SPECS server so I can set up a script and then package into an installation batch file or SCCM package."
If this sounds like you, here is the command line to install e-SPECS and create the ESPECS40 DSN pointing to the server machine using Windows authentication. Must be run from an elevated command prompt (admin privileges) in order to work unattended:
msiexec /i especsRevit.msi SERVER=YOUR-SERVER\INTERSPEC40 ESPECS_DSN_EXISTS=0
If you are using SQL authentication (user is prompted for SQL login and password when launching e-SPECS), use this command instead:
msiexec /i especsRevit.msi SERVER=YOUR-SERVER\INTERSPEC40 ESPECS_DSN_EXISTS=0 AUTH_TYPE=SqlAuth SQL_USERNAME=Username SQL_PASSWORD=Password
- Replace YOUR-SERVER with the machine name of the e-SPECS server machine.
- INTERSPEC40 is the default instance name, but if you installed e-SPECS to an existing SQL instance with a different name, replace INTERSPEC40 with the instance name.
- For SQL authenticated clients, replace Username and Password with the SQL login and password that client will use.
- It's the same for e-SPECS Designer, e-SPECS Linx, and the Revit plug-ins; simply replace especsRevit.msi with the appropriate installer MSI name (especsDesigner.msi, especsLinx.msi, especsRevit2016Console.msi, etc.)