I have recently a little-known Remedy asked us to overcome sometimes use rare compatibility issues between our 3D drivers and certain applications.
When we are aware of these problems that we are working as quickly as possible with the 3rd party vendor to resolve the issue and future versions or to ensure us and them to resolve the issue in which product (or both) the incompatibility is found. In the meantime, we sometimes use a workaround than "blacklisting" known to be a customer to ensure to no downtime lead in production, while we and / or the third party provider to fix the problem. As such, this is a temporary measure, as if the problem is often fixed in the next version of the application or XenDesktop advice is superfluous.
We have never published this workaround, since it is provided only as a fallback mechanism allow a customer to continue unimpeded short. But "a little knowledge" of workaround has semi-public and public consultation, which we found was limited, partial and misleading. As such, we were better to give a full explanation to the customer, so that they understood what they were doing, and to explain some of the information available. Indeed, " A little learning is a dangerous thing " ....
What an application to do and is a blacklist?
blacklist an application means that when an application queries for 3D GPU support will prevent it from finding and so find any. Consequently, the application is to use and draw fallback mechanism for the respective applications, where one exists, and if no fallback mechanism exists, will not be executed.
Each common use of Microsoft (GDI etc.) and then be a fallback mechanism by them for evolved 2D technologies in increasingly able to take advantage of 3D GPUs, where available. Many other applications, such as Google Chrome similar hardware opportunistic. Other applications such as Google Earth is not without 3D GPU support run
symptoms of the interoperability problem that interpret the study to an application can be a blacklist of benefits
containTypical symptoms of interoperability issue can .:
- objects if between browser tabs switching re not or incorrectly deleted or partially repaint occurs (ie note obsolete data)
- application flicker
- objects to fail to paint all (missing labels on icons, empty tabs)
- slow application rendering, and the application has a faster non-3D rendering fallback
How a single application on the blacklist .:
- Open task Manager applications tab, then right-click the app and select Go to process. Note the process name, for example "App.exe"
- Create a REG_DWORD registry key "app.exe" with the value 0:.
- XD XD 7.1 and 7.5:
- x86: reg add HKLM software Citrix vd3d compatibility / v app.exe / t REG_DWORD / f / d 0
- x64: reg add HKLM software Wow6432Node Citrix vd3d compatibility / v app.exe / t REG_DWORD / f / d 0
- XD 7.6 both x86 and x64:
- reg HKLM software Citrix vd3d compatibility / v app.exe / t REG_DWORD Add / f / d 0
- XD XD 7.1 and 7.5:
Like all apps at once blacklisted:
- Open task Manager applications tab and then the app, right-click and select Go to process. Note the process name, for example "App.exe"
- Create a REG_DWORD registry key "app.exe" with the value 0:.
- XD XD 7.1 and 7.5:
- x86: reg add HKLM software Citrix vd3d compatibility / v * / t REG_DWORD / f / d 0
- x64: reg add HKLM software Wow6432Node Citrix vd3d compatibility / v * / t REG_DWORD / f / d 0
- XD 7.6 both x86 and x64:
- reg HKLM software Citrix vd3d compatibility / v * / t REG_DWORD / f / d 0 [add
- XD XD 7.1 and 7.5:
wildcards are not supported. The asterisk * has a special meaning "all apps", but is not a traditional Wildcard. several applications to the blacklist as both appa.exe and appb.exe must individually by performed a registry key for each app.
The above commands includes the registry key to 0, this is a guaranteed value of the application blacklist that we sometimes use advised users.
There are in fact other values of these keys, the are reserved for internal use and development debug. These values can actually change from version to version, and as such are not a remedy, a customer is recommended, without using the Council of Citrix support and as a short term version specific remedy. However, it seems that a few KB articles have been published using other values like this:
- http://support.citrix.com/article/CTX133629
- http: // support.citrix.com/article/CTX137214
Where the key = 8, this value and other our developers fine-grained control mechanism different drivers provide mechanisms or change the hierarchy of behavior off. They should have not probably but now published without further background advice that they were in the wild except we felt it was better to explain so that each user who had understood the effects applied, borders and background. Any value other than 0 is only valid for a specific release XD
RemotePC -. A recent well-known problem in which the blacklist can help
There is a current known interoperability problem with some Microsoft 3D applications in which to help a blacklist. be executed in 3D modeling applications, and the session is then transferred reversed from the console of a remote connection or ica, some of these applications may hang, tried by a failing recurrent call in the DWM to find a service. We are actively working this be taken a short-term problem in the eye at a solution to this problem with Microsoft and as such. As such, if you read this blog in the future, you should examine this issue even exists.
in fact, there is a remedy to you un-hang the application in which a user can use the DWM restart of going from the Start menu:
- workplace - "enable desktop composition"> Settings-> Advanced system settings
, and then select the "performance" element "settings," then unchecking and rechecking the box point (see figure). click between each switching the user clicks "Accept" has
Win 7 and RDP 16-bit color depth. - A current known limitation
Our current WDDM driver not yet been implemented in 16bit color was outdated in fact 16-bit color support from Microsoft in Windows 8.x. In Windows 7 although DWM (Aero) was optional and therefore 16-bit color was still allowed over RDP, which means that interoperability gap, there are. We can very well look retrospectively support for 16-bit RDP connections introduce, as we have many users appreciate long update and upgrade cycles. In this scenario, a black list of applications to bypass the restriction.
Upgrading XenDesktop after applications blacklist
As I have emphasized, this is a temporary solution much that we, while we use to work with 3 rd vendors to ensure interoperability across the primary driver mechanisms. As such, if you have implemented this, you should always check to set the blacklist, if you update the application or XenDesktop to a new version, since it is very likely that the need to avoid the problem no longer exists. a new version of XenDesktop installation is to delete the registry key.
Known applications requiring a blacklist
If you have questions or applications have found that please do from blacklist benefited ask questions or comment on this forum thread , here. Please keep in mind that this procedure is that may be on a particular topic in a specific version and patch level of a product and is suitable as such, you should only examine this if you have a problem and that the information is written Community verified only instead consulting Citrix Support, unless otherwise specified and should be reviewed in our own environment.
It is very important for us that you let us know if you find that this remedy would useful as we. Prioritizing solving these issues with the utmost priority Because this gives us the opportunity to examine the need to avoid the problem and eliminate it. Our development, support and product teams will keep a watchful eye on this thread!
julianp thank my co-author of HDX engineer, for his invaluable contribution and input!
0 Komentar