Workspace Control 2021.1 (10.6.30.0)
The following customer support issues have been resolved in this version of Workspace Control:
| Problem ID | Title |
|
76175 |
When the Workspace Control Shell is used, Microsoft Teams cannot be closed during log off. |
|
76839 |
Citrix Private VM hosted applications are not intercepted by Workspace Control. |
|
77769 |
Executing res.exe /config commands with additional parameters from Ivanti Automation or the Windows Task Scheduler, results in failure. |
|
77993 |
When Citrix XenApp Publishing is used, the Remote Access Connection Manager service cannot start if the Secure Socket Tunneling Protocol Service is disabled on the Citrix server. |
|
78162 |
Importing a connection file in the Workspace Control Agent using the command line, results in message: Ivanti Workspace Control Agent - Configure connection. Please enter a Cloud Relay Server Account Id. |
|
78173 |
pwrcache.exe generates error: ProfileContainerConfigurationFactory.CreateConfiguration - Input String was not in a correct format. This occurs when configuration changes are made to Location and Devices or Workspace Containers in Workspace Control environments where the Microsoft Profile Container Integration was never enabled. |
|
78255 |
Registry setting MonitorEndProgram does not work when Workspace Control is configured to use French or Norwegian languages. |
|
78287 |
When a Workspace Control managed session is started, duplicate entries are created for User Registry settings of type string with Name={Default}. |
|
78327 |
After upgrading from Workspace Control 10.0.400.0 to version 10.1.100.0, User Installed Applications are not visible in the Start Menu. |
|
85813 |
Windows 10 template for capturing taskbar settings causes Workspace Control to become unresponsive while loading. |
|
86056 |
In the same Workspace Control managed session, starting second instances of Citrix published applications takes a minute before the instance starts. |
|
86077 |
Opening PDF files from Workspace Control managed App-V applications takes over a minute before the file opens. |
|
86311 |
After upgrading to Workspace Control 10.6.30.0, App-V applications configured as Workspace Control managed applications do not start. |
|
86316 |
After upgrading to Workspace Control 10.6.30.0, managed applications configured with dynamic privileges do not start. |
|
86338 |
After upgrading to Workspace Control 10.6.30.0, Folder Synchronization does not work on Windows Server operating systems. This option is found in the Workspace Control Console under Composition > Actions By Type > Files and Folders > Folder Synchronization. |
|
86354 |
After upgrading to Workspace Control 10.6.30.0, user settings with Value=(Default) are restored with empty Data fields. |
|
|
When using Ivanti Cloud Relay, Workspace Control Agents sometimes create duplicate copies of the Agent. |
|
|
When users log into Workspace Control managed sessions configured to use the Workspace Control Shell as the default desktop shell, three instances of Microsoft Edge can be opened in the taskbar and cannot be closed. This behavior prevents users from logging off. |
|
|
In the Workspace Control Console, under Administration > Agents, configuring Run Workspace Composer to either Automatic or Manual does not work correctly for Workspace ControlAgents that are configured to connect to the Cloud Relay. |
|
|
A locally authenticated user with low privileges can leverage an unspecified attack vector to bypass Files and Folders Security. This makes it possible to start unapproved applications with elevated privileges. |
Removed Fixes
The following fix was removed from this version of Workspace Control:
| Problem ID | Title |
|
77280 |
Workspace Control does not correctly restore user settings with Value=(Default) if their Data field is empty. |
|
77385 |
The execution order is incorrect when using pwrgate %ID% in execute commands under Actions by Event > At Logon. |