Connect to an existing environment

Using the following public properties, you can connect Workspace Control to an existing environment.

If you want to use dynamic Datastore configuration in your environment (Agents will obtain their Datastore connection settings from a DHCP server), it is not necessary to specify these settings in a command line when installing Workspace Control unattended. See Dynamic Datastore configuration for Agents for more information.

Connect Workspace Control directly to a Datastore

Public property

Value

Description

CONNECTFILE

<FILEPATH>

Specifies the path and filename of a Workspace Control Datastore connection string stored in a text file. In a connection string, the database password is encrypted to prevent exposure.

Create the connection string file from Primary Datastore properties at Setup > Datastore, in the Management Console.

Example: CONNECTFILE=C:\TEMP\Connectfile.txt

CONNECTSTRING

<CONNECTIONSTRING>

Specifies the connection string to connect to a Workspace Control Datastore. In a connection string, the database password is encrypted to prevent exposure.

Create the connection string from Primary Datastore properties at Setup > Datastore, in the Management Console.

Example:
CONNECTSTRING=RESPFDB=MSSQL;SRV-DB01.MyDomain.com;RESPFDBNAME;/<ENCRYPTED DATA>

Alternatively, use:

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

DBNAME

<DATABASENAME>

Specifies the name of the database that Workspace Control should connect to.

Example: DBNAME=Workspace

DBUSER

<DBUSERNAME>

Specifies the database user name that Workspace Control should use to connect to the database.

Example: DBUSER=WorkspaceUser

DBPASSWORD

<DBPASSWORD>

Specifies the plaintext password that Workspace Control should use to connect to the database.

Example: DBPASSWORD=WorkspaceUserPassword

DBPROTOCOLENCRYPTION

YES or NO (default)

Specifies whether protocol encryption should be used when connecting to Microsoft SQL Server.

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.

SERVICEACCOUNTNAME

<DOMAIN>\<USER>

Specifies the account name that should be used as the Agent service account when using Windows authentication. The service account name must be a member of the Local Administrator group.
When not using Windows authentication, providing SERVICEACCOUNTNAME is optional.
If not provided, the Agent service will run under the LocalSystem account.

Example: SERVICEACCOUNTNAME=MyDomain\AgentServiceAccount

SERVICEACCOUNTPASSWORD

<PASSWORD>

Specifies the plaintext password that should be used if a service account is specified for SERVICEACCOUNTNAME.

Example: SERVICEACCOUNTPASSWORD=AgentServiceAccountPassword

Example:

Msiexec /i "C:\Ivanti Workspace Control [version].msi" DBSERVER=SQLServer01 DBNAME=Workspace DBUSER=WorkspaceUser DBPASSWORD=WorkspaceUserPassword DBTYPE=MSSQL DBPROTOCOLENCRYPTION=Yes DBCERTVALIDATION=Yes /qn

Msiexec /i "C:\Ivanti Workspace Control [version].msi" CONNECTFILE=C:\TEMP\WMDBconn.txt /qn

Example including the Agent service account:

When the server name is SQLServer01, the Database name is Workspace, Agent service account name/password is AgentServiceAccount/AgentServiceAccountPassword, the command line would be:

Msiexec /i "C:\Ivanti Workspace Control [version].msi" DBTYPE=MSSQL DBSERVER=SQLServer01 DBNAME=Workspace DBPROTOCOLENCRYPTION=No SERVICEACCOUNTNAME=MyDomain\AgentServiceAccount SERVICEACCOUNTPASSWORD=AgentServiceAccountPassword /qn

Connect Workspace Control to a Relay Server

The public properties listed below do not apply to Console-only installations.

Public property

Value

Description

RSENVGUID

<GUID>

Specifies the GUID that uniquely identifies the Workspace Control environment that the Agent should connect to.
This GUID can be found in the Management Console, at Administration > Relay Servers, on the Settings tab.

Example: RSENVGUID={076FC22E-B7A1-477E-A021-94601893B568}

RSPASSWORD

<PASSWORD> or
<ENCRYPTED RSPASSWORD>

Specifies the plaintext or encrypted password of the Workspace Control environment that the Agent should connect to. This password must already be set in the Administration > Relay Servers node in the Management Console.
When using an encrypted password, the public property RSPWENC must be specified as YES (see below)

RSPWENC
(version 10.2 and higher)

YES or NO (default)

Specifies whether the value that is specified at RSPASSWORD is encrypted.
Technical managers can obtain the encrypted version of the Environment password by using one of the following command lines on a machine running the Management Console:

  • pwrtech.exe /getrspassword
    With Ctrl+C, the encrypted password can be copied from the dialog box to the clipboard.
  • pwrtech.exe /getrspassword /f=<full file path>
    The encrypted password is saved in the specified file at the given location.

Alternatively, the encrypted password can be found in the XML configuration file that was generated on a Relay Server that connects to another Relay Server.
Create the configuration file from the Relay Server Configuration Tool, by clicking Save to XML.

Example: RSPASSWORD=<ENCRYPTED RSPASSWORD> RSPWENC=YES

ACCEPTSELFSIGNEDCERT

YES or NO (default)

Specifies whether the Agent should accept a self-signed certificate from the Relay Server to secure the Agent - Relay Server connection.

Use ACCEPTSELFSIGNEDCERT=YES if the Relay Server is not configured to use a certificate that was issued by a Trusted Root Certification Authority.

RSDISCOVER

YES or NO (default)

Specifies whether the Agent should discover Relay Server(s) using multicast.

RSLIST

<SERVERNAME1>:<PORTNUMBER>;
<SERVERNAME2>

Specifies the list of Relay Servers to connect to, separated by a semicolon (;). When a Relay Server in this list uses a non-default listening port, its servername should be followed by a colon (:) and the listening port.

Example: RSLIST=Server1;Server2:2012;Server3.MyDomain.com

RSRESOLVE

<RELAY SERVER FQDN>

Specifies the FQDN of a Relay Server to be resolved by DNS.

Example: RSRESOLVE=Relay.MyDomain.com

Examples:

Msiexec /i "C:\Ivanti Workspace Control [version].msi" RSENVGUID={7C1FF8AB-5FC8-40C9-AB4C-E285A788A2C0} RSPASSWORD=password RSDISCOVER=yes/no RSLIST=server1;server2 RSRESOLVE=Relay.MyDomain.com /qn

Msiexec /i "C:\Ivanti Workspace Control [version].msi" RSENVGUID={7C1FF8AB-5FC8-40C9-AB4C-E285A788A2C0} RSPASSWORD=YuSaVRGyjK7LubF9LMzez9XMAexQF5xkADcRKM1V6dOgYQi6sPA2YRbFDg= RSPWENC=yes RSDISCOVER=yes/no RSLIST=server1;server2 RSRESOLVE=Relay.MyDomain.com /qn

Pre-load Agent cache (ZIP file) during offline installations

With a pre-loaded cache, it is possible to install Agents in your Workspace Control environment and start them in an offline state. This means that the Agents do not (yet) have a connection to a Relay Server or directly to the Datastore. The ZIP file is extracted to the Agents cache folder and is updated once the Agent connects to a Relay Server or directly to the Datastore.

Please note that no logging is available in the Datastore for the Agents with a pre-loaded cache until they connect to a Relay Server or directly to the Datastore.

Public property

Value

Description

CREATEFILEFROMCACHE

<FILEPATH>

Creates the ZIP file from the cache (.zip). Elevated privileges are necessary to run this command line. Make sure the ZIP file is stored in a secure location and can only be accessed by authorized Workspace Control administrators.

Example: <IWC Installation folder>\pwrcache.exe /CREATEFILEFROMCACHE=C:\temp\cache.zip

LOADCACHEFROMFILE

<FILEPATH>

Loads the cache to the Agent. Elevated privileges are necessary to run this command line.

Example: Msiexec /i "C:\Ivanti Workspace Control [version].msi" LOADCACHEFROMFILE=C:\temp\cache.zip /qn