Create a new Datastore
If there is no existing database to which Workspace Control can connect, you can add the following public properties to create a new database during the unattended installation. After creating a new database, you can optionally import a license file and Building Block. Please note that it is not possible to create a new database when installing an Agent-only installation.
|
Public property |
Value |
Description |
|---|---|---|
|
DBTYPE |
MSSQL, DB2, ORACLE, MYSQL or MSSQLAZURE |
Specifies the database type. Example: DBTYPE=MSSQL |
|
DBSERVER |
<SERVERNAME> |
Specifies the database server that Workspace Control should connect to. Example: DBSERVER=SQLServer01 |
|
DBCREATE |
YES or NO (default) |
Specifies whether a new database should be created using the specified values. Does not apply to Agent only installations. |
|
DBCREATEUSER |
<USERNAME> |
Specifies the database user name that should be used to create the new database. Example: DBCREATEUSER=SA Does not apply to Agent only installations. |
|
DBCREATEPASSWORD |
<PASSWORD> |
Specifies the database password that should be used to create the new database. Example: DBCREATEPASSWORD=SAPassword Does not apply to Agent only installations. |
|
DBPROTOCOLENCRYPTION |
YES or NO (default) |
Specifies whether protocol encryption should be used when connecting to Microsoft SQL Server. Please note, that the default value of this public property is different from the default setting when creating a new Datastore using the Management Console |
|
DBCERTVALIDATION |
YES or NO (default) |
Specifies whether the certificate that is provided by the database server must be validated against the list of Trusted Root Certificate Authorities on the Agent. |
|
DBFIPS |
YES or NO (default) |
Specifies that FIPS compliant security algorithms should be used to encrypt data in the database. |
|
DBNAME |
<DATABASENAME> |
Specifies the name of the database that Workspace Control should create. Example: DBNAME=Workspace |
|
DBUSER |
<DBUSERNAME> |
Specifies the database user name that Workspace Control should create to connect to the database. Example: DBUSER=WorkspaceUser |
|
DBIMPORTLICENSE |
<FILEPATH> |
Specifies a license file to be imported after creating a new database (optional). Example: DBIMPORTLICENSE=C:\TEMP\License.xml Does not apply to Agent only installations. |
|
DBIMPORTBB |
<FILEPATH> |
Specifies a Building Block file to be imported after creating a new database (optional). Example: DBIMPORTBB=C:\TEMP\BuildingBlock.xml Does not apply to Agent only installations. |
Example:
When the server name is SQLSERVER01, the Database name is Workspace, username/password is WorkspaceUser/WorkspaceUserPassword, the license file is located at C:\license.xml, and connections to the Datastore must be secured, the command line would be:
Msiexec /i "C:\Ivanti Workspace Control [version].msi" DBSERVER=SQLSERVER01 DBNAME=Workspace DBUSER=WorkspaceUser DBPASSWORD=WorkspaceUserPassword DBTYPE=MSSQL DBPROTOCOLENCRYPTION=Yes DBCERTVALIDATION=Yes DBCREATE=Yes DBCREATEUSER=SA DBCREATEPASSWORD=SAPassword DBIMPORTLICENSE=c:\license.xml DBIMPORTBB=C:\buildingblock.xml /qn
Example using FIPS compliant security algorithms:
When the server name is SQLSERVER01, the Database name is Workspace, username/password is WorkspaceUser/WorkspaceUserPassword, the license file is located at C:\license.xml, and the Database must be FIPS compliant, the command line would be:
Msiexec /i "C:\Ivanti Workspace Control [version].msi" DBSERVER=SQLSERVER01 DBNAME=Workspace DBFIPS=Yes DBUSER=WorkspaceUser DBPASSWORD=WorkspaceUserPassword DBTYPE=MSSQL DBPROTOCOLENCRYPTION=No DBCREATE=Yes DBCREATEUSER=SA DBCREATEPASSWORD=SAPassword DBIMPORTLICENSE=C:\license.xml /qn