Published apps icon will group with local apps in Taskbar
Article ID: CTX461449
Updated On:
Description
Published apps icon will group with local apps in Taskbar
User is difficult to recognize virtual app and local app icon from task bar
Resolution
Set the TWITaskbarGroupingMode key to the following value in the path
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Seamless Windows
Name: TWITaskbarGroupingMode
Type: REG_SZ
Value: GroupNone
Set the TWITaskbarGroupingMode key to the following value in the path HKEY_CURRENT_USER\Software\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Seamless Windows
Name: TWITaskbarGroupingMode
Type: REG_SZ
Value: GroupNone
We get the icon from the application’s binary, so if we want to change the icon, we need to change the binary of the application.Even we can use third-party program to change it, we cannot suggest this method to the customer. It is a hack behavior.
• Applications must have matching bitness (32-bit or 64-bit) in order to be grouped in the taskbar. This is a limitation of Windows (Vista, XP, and Windows 7/8/10) and occurs with local apps as well. For example:
Publish 32-bit IEXPLORE.EXE on server and run on client, run local 64-bit IEXPLORE.EXE on client -> will not group properly
Publish 64-bit IEXPLORE.EXE on server and run on client, run local 32-bit IEXPLORE.EXE on client -> will not group properly
Publish 32-bit IEXPLORE.EXE on server and run on client, run local 32-bit IEXPLORE.EXE on client -> will group properly
Publish 64-bit IEXPLORE.EXE on server and run on client, run local 64-bit IEXPLORE.EXE on client -> will group properly
• The application executables must have the same name. This will not typically be an issue, but if someone renames Notepad.exe to My_Notepad.exe, it will no longer group with Notepad.exe. This is a function of Windows, and occurs with local apps as well.
• Some applications are only designed such that only one instance of them is running at a time (i.e. WMPLAYER.EXE). Currently, in this scenario the client allows one remote instance in addition to one local instance. When this occurs, taskbar grouping works as it would work with normal applications.
• In Windows 7 and above when a local instance and a remote instance of an app are being grouped in the taskbar, right-clicking on the taskbar button always shows the jumplist for the local app.
• Grouping does not work properly in 64-bit Windows Vista/XP, but it does in both 32- and 64-bit versions of Windows 7 and above. This limitation will be fixed in a future version of the feature.
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Seamless Windows
Name: TWITaskbarGroupingMode
Type: REG_SZ
Value: GroupNone
Set the TWITaskbarGroupingMode key to the following value in the path HKEY_CURRENT_USER\Software\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Seamless Windows
Name: TWITaskbarGroupingMode
Type: REG_SZ
Value: GroupNone
We get the icon from the application’s binary, so if we want to change the icon, we need to change the binary of the application.Even we can use third-party program to change it, we cannot suggest this method to the customer. It is a hack behavior.
Problem Cause
Mode used for Seamless Taskbar Grouping of hosted, published applications. Set this parameter to the desired value for Seamless Taskbar Grouping support. If GroupAll is specified, hosted, published app instances are grouped together on the Windows Taskbar by app. Likewise, these app instances are grouped together with corresponding local app instances. If GroupNone is specified, the Seamless Taskbar Grouping feature is disabled. As a result, all instances of all hosted apps are grouped together in the Windows Taskbar in the same group, and not with local apps.• Applications must have matching bitness (32-bit or 64-bit) in order to be grouped in the taskbar. This is a limitation of Windows (Vista, XP, and Windows 7/8/10) and occurs with local apps as well. For example:
Publish 32-bit IEXPLORE.EXE on server and run on client, run local 64-bit IEXPLORE.EXE on client -> will not group properly
Publish 64-bit IEXPLORE.EXE on server and run on client, run local 32-bit IEXPLORE.EXE on client -> will not group properly
Publish 32-bit IEXPLORE.EXE on server and run on client, run local 32-bit IEXPLORE.EXE on client -> will group properly
Publish 64-bit IEXPLORE.EXE on server and run on client, run local 64-bit IEXPLORE.EXE on client -> will group properly
• The application executables must have the same name. This will not typically be an issue, but if someone renames Notepad.exe to My_Notepad.exe, it will no longer group with Notepad.exe. This is a function of Windows, and occurs with local apps as well.
• Some applications are only designed such that only one instance of them is running at a time (i.e. WMPLAYER.EXE). Currently, in this scenario the client allows one remote instance in addition to one local instance. When this occurs, taskbar grouping works as it would work with normal applications.
• In Windows 7 and above when a local instance and a remote instance of an app are being grouped in the taskbar, right-clicking on the taskbar button always shows the jumplist for the local app.
• Grouping does not work properly in 64-bit Windows Vista/XP, but it does in both 32- and 64-bit versions of Windows 7 and above. This limitation will be fixed in a future version of the feature.
Additional Information
https://docs.citrix.com/en-us/citrix-workspace-app-for-windows/downloads/ica-settings-reference.pdf
Was this article helpful?
Yes
No
Powered by
