Apr 302015


On a HP x64 thin client WES7P image (T620) the following FBWF exclusions are recommended:

fbwfmgr /addexclusion c: “\Users\User\AppData\Local\Citrix”
fbwfmgr /addexclusion c: “\Program Files (x86)\Citrix”
fbwfmgr /addexclusion c: “\ProgramData\Citrix”
fbwfmgr /addexclusion c: “\Users\User\AppData\Roaming\ICAClient”
fbwfmgr /addexclusion c: “\Users\User\AppData\LocalLow\Citrix”
fbwfmgr /addexclusion c: “\Users\User\AppData\Local\Citrix”

This enables the use of HDX Flash redirection, not making these exceptions prevents this somehow. This is not the case with the Enhanced Write Filter.

Apr 302015

UPDATE 2016-03-04; HP made an official customer advisory on this topic: Advisory: HP Thin Client – Citrix HDX Flash Fails With Error in Application ie4uinit.exe

On a new thin client image for a HP T620 x64 dual core this error message appeared. This occured when Flash content was played in a Citrix session. The error message origin was from WES7 en not in the Citrix session. So when the HDX Flash redirection called for the local Flash plugin to play content this error was displayed.

Screen 02-apr 0004
Continue reading »

Feb 242015

Windows 8.1 / 2012r2 has a nice quick access menu with a lot of handy shortcuts. You can access it with Win + X or rightclick on the start button.


It isn’t possible to manage this through policies. If you disable access to certain parts of the OS for users they will still see them in the quick access menu. They just won’t work when you click on them. So I found a way to clean it up with help of AppSense Environment Manager.

Continue reading »

Oct 252013


  • HP Thin client T610
  • Citrix XenApp 6.5
  • Webinterface 5.4
  • McAfee VirusScan Enterprise 8.8 on Thin Client.

Screen 25-okt 0001

When opening the Citrix webinterface there is no logonscreen available, only a white background with no error massage. After troubleshooting the cause was found in the scriptscan from the McAfee VirusScan Enterprise 8.8.
Disabling the service or adding an website exclusion to the scriptscan did not solve the problem. Only unregistering the DLL with “regsvr32.exe /u SCRIPTSN.dl” solved the problem.

Continue reading »