Known Issues and Limitations

Using the Ivanti Workspace Control Shield API (mandatory for Workspace Control 10.18.99.0 (Early Access) 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 (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.18.99.0 (Early Access) 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.18.99.0 (Early Access) 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 IWC Console (Non-API version) is linked to a different database (e.g., Database-B), upgrading the IWC Console to the API version is not recommended. This action will change the Shield API's database configuration from Database-A to Database-B, potentially causing conflicts.

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.

  • In the non-Shield API version of the Workspace Control Agent, the cache update starts automatically when the machine is turned on. Upon logging in, the user has access to the latest cache.
    In contrast, the Shield API version initiates the cache update only after the user logs in. Occasionally, users may not receive the updated cache immediately after logging in. In such cases, once the Composer starts successfully, the user must log off and log back on to ensure they receive the updated cache.