Bug Fixes

If the Citrix XenApp Publishing integration is enabled in the Workspace Control Console, applications that point to network drives or shares take a long time to remotely publish. The publishing process can time out and generate the following error: Publish remote FAILED for farm '<Farm name>' on <Publishing Server> - Timeout occurred waiting for task ready.

Link to KB article

Sometimes, when opening the Workspace Control Console, the following error occurs: Connection to primary database could not be established. Connection could not be established. Invalid connection string attribute. Login failed for user <username>.
Reopening the Workspace Control Console fixes the issue.

Link to KB article

When publishing a new Managed Application to Citrix XenDesktop using the Workspace Control Console, the following error occurs: Workspace Control Console failed to publish the application to the following farms: <farmname> - Unknown error while publishing.

Link to KB article

After creating a new Citrix administrator account with the same Active Directory access and Citrix role as the previous administrator account, and configuring the new administrator in the Workspace Control Console, the following error occurs when publishing a new managed application to Citrix XenDesktop: Workspace Control Console failed to publish the application to the following farms: <farmname> - Unknown error while publishing.

Link to KB article

Logging onto a VMware Horizon View session from a Workspace Control managed session results in the Horizon View session to claim a separate Workspace Control license, instead of using the license present in the Workspace Control session on the local client.

Link to KB article

When Workspace Control is configured to manage Citrix Published Applications using Citrix XenApp/XenDesktop, and there are over 150 Citrix Delivery Groups in the environment, results in the Citrix Delivery Groups to go missing after some time elapses.

Link to KB article

After a virtual machine is re-imaged and it keeps its name, setting up a new Workspace Control Agent on the machine can result in duplicate Agent entries in the Workspace Control Console, under Administration > Agents. This occurs if, under the Settings tab, the option Identify Agents by is set to Computer domain name and NetBIOS name.

Link to KB article

When Read-Only Blanketing is enabled in the Workspace Control Console, under Security > Data > Read-Only Blanketing, and Tracing is also enabled, various Workspace Control components are blocked from writing in the trace file by Read-Only Blanketing.

Link to KB article

When Workspace Control is set up to manage Citrix Published Applications in an environment with over 150 Citrix Delivery Groups, if configuration changes within the Workspace Control product required the Citrix Published Application to be unpublished first, the following error occurs: Workspace Control Console failed to unpublish the application. Please remove the published application manually from the following farms: Unknown error while publishing.

Link to KB article

In Workspace Control managed sessions running on Microsoft Windows 10 21H1, if the option Windows Shell shortcut creation is set to Replace all unmanaged shortcuts in the Workspace Control Console, under Composition > Applications > Settings tab, an unmanaged Microsoft Edge icon remains present on the taskbar.

Link to KB article

Starting the Restore User Settings wizard as application from the Start Menu, after another application was already opened and its window maximized, results in the wizard to not launch into focus and remains hidden behind the maximized application. The wizard's icon is visible on the taskbar.

Link to KB article

When the Windows PowerShell is used to display custom Toast message to end users, the message is not shown if in the Workspace Control Console, under Composition > Applications > Settings tab, option Windows Shell shortcut creation is set to Replace all unmanaged shortcuts. This option can also be configured on Workspace Containers.

Link to KB article

Using Citrix StoreBrowse to start managed published applications in Published Desktop sessions on newly installed Published Desktop hosts, results in the following error: Application can't be started Instant passthrough could not be resolved.

Link to KB article

Workspace Control Reporting Services fail to retrieve data from Workspace Control Agents after an installation or upgrade is done to the Agents.

Link to KB article

When launching Workspace Control Usage Tracking Viewer, the splash screen displays an incorrect version of the product. The Usage Tracking Viewer is started from the Workspace Control Console, under Diagnostics > Usage Tracking Overview > Settings tab > Start viewer.

Link to KB article

In a specific scenario, RD Broker collections that contains a single RD host are emptied after the RD host is restarted. This impacts application publishing using Workspace Control. Details on the specific scenario are found in the KB article.

Link to KB article

If the Workspace Control Console is configured to use another language than English, navigating to Setup > Ivanti Products > Neurons for Edge Intelligence, results in the following error: Prog: pwrtech.exe Procedure: frm\WSIntelConfig.LoadSettings Error: (383) 'Text' property is read-only Machine: <Machine name>.

Link to KB article

After installing or upgrading to Workspace Control 2021.1 Service Update 1 (10.6.40.0), pwrcache.exe stops working on machines running Microsoft Windows Server 2008 R2 or Windows 7.

Link to KB article

When changing Workspace Control environments and enabling the Cloud Relay feature in the new environment, Workspace Control Agents that have their Datastore connection changed to inherited from any other setting fail to correctly apply the new configuration.

In a specific scenario, the Cloud Relay connection wizard tries to register on the Cloud Relay back-end with an incorrect account ID and registration key.