Known Issues and Limitations

Using the Ivanti Workspace Control Shield API (mandatory for Workspace Control 10.19.0.0 and higher) has the following known limitations:

Unsupported features

The following features are not supported:

  • Connect remote Datastore
  • Database type DB2, MySQL, Oracle and Microsoft SQL Azure (support for MySQL and Oracle is scheduled to be resolved in a next release) (the feature)
  • Dynamic Datastore configuration (the feature)
  • Export database connection string (both Copy to clipboard and Export to file) (the feature)
  • Windows authentication with Designated account (for Datastore connection) (the feature). If you are using Windows authentication for the Datastore connection, the Shield API server user must have DBO (Database Owner) access to the database.
  • Silent installation of Shield API component (scheduled to be resolved in a next release)
  • RDS virtual environment support (scheduled to be resolved in a next release)
  • Importing building blocks with large data in applications (scheduled to be resolved in a next release) the feature.
  • Azure Active Directory (the feature)

  • Installing Workspace Control or Workspace Control Agent while logged in as a Local Admin user is not supported (scheduled to be resolved in a future release).

  • Support for Multi-Environment setups.

If your environment requires using one or more of these features, do not install Workspace Control version 10.19.0.0 and higher.

Limitations

  • Console and agent do not display database details for the Datastore.
  • Registry Setting DoNotAcceptSelfSignedCert and the public property /ACCEPTSELFSIGNEDCERT do not apply to connections to the Shield API.
    Rejecting self-signed certificates cannot be enforced for these connections.
  • Self-signed certificate for Shield API is not generated automatically during installation. The behavior of the Relay Server installation remains unchanged.
  • Upgrades to version 10.19.0.0 and higher cannot be performed using the Workspace Control Auto Upgrade Pack.
  • If the Shield API is configured to use a specific database (e.g., Database-A) and the Ivanti Workspace Control Console (Non-API version) is linked to a different database (e.g., Database-B), upgrading the Ivanti Workspace Control Console to the API version is not recommended.

    This action will update the Shield API’s database configuration from Database-A to Database-B, which could result in conflicts and unintended behavior.

  • An installation of Ivanti Workspace Control components version 10.18.99.0 (Early Access) or higher that uses the Shield API cannot be directly upgraded to version 10.19.0.0. To upgrade, you must first uninstall the Ivanti Workspace Control components of the prior version that uses the Shield API. After uninstalling, you can install version 10.19.0.0. However, upgrades from non-API to API versions are still supported.

Changed behavior

The following features behave differently for environments that use the Shield API:

  • Configuring the Datastore connection using %respfdir%\svc\res.exe /config is not possible.
    However, Relay Server configuration is supported using %respfdir%\svc\res.exe /config. The Workspace Control Agent connects to the Shield API. Configuration of the Datastore connection for the Shield API is done through the Workspace Control Console. To view or edit the Shield API that the Workspace Control Agent connects to, go to the registry setting:
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\RES\Workspace Manager\ShieldApiUrl
    Change the Shield API connection for Workspace Control Agent using %respfdir%\svc\res.exe /configApi. See Reconfiguring the Shield API.

  • After installing the Workspace Control Agent or applying new configuration updates from the Workspace Console, logging into the Agent machine will prompt the Composer to update its configuration data. During syn-chronization, a splash screen will appear (as shown below). Composer will proceed with configuring the machine only after the update is complete.