Known Issues and Limitations

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

Unsupported features

The following features are not supported:

  • Connect remote Workspace Control 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.10.0 and higher.

Limitations

  • No Backward Compatibility. Once upgraded to the new Shield API version (10.19.10.0 or later), the system does not support backward compatibility. This applies in the following scenarios:

    • If an existing Workspace Control Console (version 10.19.0.0 or any non-Shield API version) is upgraded to Shield API-enabled version (10.19.10.0 or later), it cannot be downgraded to an earlier version.

    • A Workspace Control Datastore that has been used with the new Shield API version cannot be reconnected or used with older Workspace Control Console versions (10.19.0.0 or earlier).

      Ensure you have proper backups and have tested your upgrade process, as downgrading is not supported once the Workspace Control Console or Workspace Control Datastore has been upgraded.

  • When upgrading from an older version (such as 10.19.0.0 or any non-Shield API version like 10.18.80.0 and prior) to 10.19.10.0, then all components must be upgraded in the correct order. The Shield API must be upgraded first, followed by the Workspace Control Console, and finally all Workspace Control Agents. If the Shield API and Workspace Control Console are upgraded but the Workspace Control Agents remain on an older version (prior to 10.19.10.0), those Workspace Control Agents will no longer function. Therefore, it is mandatory to upgrade all Workspace Control Agents after upgrading the Shield API and Workspace Control Console to ensure continued operation.

  • Workspace Control Console and Workspace Control Agent do not display database details for the Workspace Control 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.10.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-Shield API to Shield API versions are still supported.

Changed behavior

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

  • Configuring the Workspace Control 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 Workspace Control 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 Control, logging into the Workspace Control 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.