I was contacted over the weekend by an ex-colleague who was having some trouble getting the Published Application Name condition to work on his XenApp 6.0 farm. I had told him some time ago that this issue was fixed in Environment Manager version 8.1, but he was still finding the issue presenting itself having done the upgrade a few weeks previously. After verifying that the upgrade had been done properly, I felt obliged to give him a hand working the problem out.
Rather surprisingly, after we’d done a lot of testing on various parts of EM itself and drawn a blank, the solution presented itself from a rather unexpected source. We applied Hotfix Rollup 1 for Citrix XenApp 6.0 (figuring that we might as well get it done while we had a few servers offline) and promptly noticed that the issue was now resolved! Digging backwards through the multitude of Citrix hotfixes that were slipstreamed into Rollup 1, we found a reference in CTX128849 that looked like it might be the fix that had done the trick. Certainly the description from the hotfix information (below) looked fairly convincing.
When using the WFQuerySessionInformationA() API to retrieve session information, the letters in published application names can appear separated by blank spaces
So, if you’re still on XenApp 6 (and if you’re not seriously thinking about upgrading, maybe you need to start), make sure you are up-to-date with your hotfix rollups, if you are having any issues using the Published Application Name condition.
Share
