Connections

Datastore in the Setup menu shows to which primary Datastore the current Workspace Control site connects. From here, you can also connect to other existing Workspace Control sites, create new ones, migrate your Datastore, split or join primary and secondary Datastores and generate a string of the database connection settings.

Primary Datastore

  • To connect to a different Datastore, click Browse button and then click Connect. This opens the Datastore Connection Wizard, which will guide you through the process. Instead of typing the connection settings of the target Datastore manually, you can also copy the Datastore connection settings of a different Datastore from the clipboard (by clicking the Copy from clipboard button) or import these settings from a TXT file (by clicking the Import from file button).
    You can also use this functionality to revert accidental changes to the connection settings of the current Datastore, or to set up Datastore location sensing for Agents.

  • When connecting to a Datastore that was previously migrated, you can choose between the following options:

    • Select Ignore this and connect anyway to connect to the "old" Datastore. Optionally also select Remove referral to new database to remove the Datastore already migrated notification. Note that other Agents will not automatically also connect to this Datastore. See Datastore Migration Wizard for more information.

    • Select Connect to the new database to connect to the migrated Datastore.

  • To create a new Datastore, click Browse button and then click Create. This opens the Datastore Wizard, which will guide you through the process. When creating a new Datastore, you can choose which module to use. See Select Workspace Control Modules. For more information about the features available in the modules, see Workspace Control Modules.

  • To migrate to a new Datastore, click Browse button and then click Migrate. This opens the Datastore Migration Wizard, which will guide you through the process.

  • To export a string of the current, primary database connection settings, click Browse button and then click Export (dbase export small). This opens the Export database connection string window, from which you can copy the Datastore connection settings to the clipboard (by clicking the Copy to clipboard (Button: Export to file) button) or export these settings to a TXT file (by clicking the Export to file (Button: Export to file) button).
    This functionality makes it easier to transfer all connection settings to another Console or to set up Datastore location sensing for Agents.

    This feature is not supported in environments that use the Workspace Control Shield API.

Secondary Datastore

This feature is not supported in environments that use the Workspace Control Shield API. (scheduled to be resolved in a next release)

  • It is possible to split the Datastore into two separate databases. One database is used for State and Configuration data (with or without Logging) and one database is used for Usage Tracking data (with or without Logging).

  • To change the credentials, click Browse button at Secondary Datastore.

  • To split or join Datastores, click Browse button at Secondary Datastore and then click Split/Join. The Split/Join Datastore Wizard will guide you through the process.

Database prerequisites

Database type

Prerequisites

Microsoft SQL Server
  • Mixed Mode authentication (only when using SQL Server login for Authentication)
  • A named SQL Server System Administrator login ID
  • If the Force protocol encryption option is enabled: Microsoft Native Client

Microsoft SQL Azure

This feature is not supported in environments that use the Workspace Control Shield API.
(scheduled to be resolved in a next release)
  • Microsoft Windows Azure credentials
  • Microsoft SQL Native Client

Oracle Database

This feature is not supported in environments that use the Workspace Control Shield API.
(scheduled to be resolved in a next release)
  • Oracle DBA credentials
  • Oracle database drivers on all Agents connecting directly to the Datastore

For an overview of supported versions, see Database Systems.

  • If allowed by the SQL server, you can specify a Login without a Password.

  • When using Windows Authentication, Agents and users must be part of a trusted Domain.

  • It is not possible to connect to a Datastore created by a previous version of Workspace Control.

  • It is not possible to migrate a secondary Datastore. To move the secondary Datastore to another location: Join the primary and secondary Datastores and create a new secondary Datastore at another location.

  • Verify that all Workspace Control Agents can connect to your Migrated / Split Datastores.

  • Ivanti recommends storing the tnsnames.ora configuration file locally, on a user's machine (desktop or laptop) in a location as described in the Oracle Database Net Services Reference.

  • To enable Muti-subnet Failover when connecting to a Microsoft SQL Server Always On Availability Group listener or Failover Cluster Instance, configure MultiSubnetFailover as a registry setting. For more details, see MultiSubnetFailover.

  • The exported Setting is encrypted and must be kept confidential. When stored in a text file, it should be placed in a secure location to protect sensitive data and maintain security.

You can also connect to another existing Workspace Control site by going to File > Connect remote database in the Management Console menu, providing the relevant information there. It is possible to import a Database connection string here.
This feature is not supported in environments that use the Workspace Control Shield API.

Microsoft provides guidelines for choosing the correct Authentication Mode.