Yeah yeah, long time no blog. I know. Life gets in the way. Work gets in the way. I have a list of things I need to blog about, and I’ll get to a few of them here shortly. For now, though, this one really needs to get out there, so I’m shortcutting said list, and getting it out there for you. You’re welcome. 🙂
There seems to be very little information out there on this topic. I Googled for hours. I read the Citrix eDocs. I read everything I could find. Sure, lots of other people have blogged about it, but all they did was parrot Citrix’s announcement of the fact that the feature is back. I highly doubt that even one of them has tried to implement the feature. Or at least, if they did, they found out how big of a pain in the ass it is, and how the behavior of it is so strange that maybe they are best served by not telling the public about it.
As an anonymous blogger, I don’t have those same worries – making Citrix mad at me.
So, here I am to give you the “straight dope”, as it were.
First – the ADM template that is referenced to be used – I tried it. I verified that it was applying properly by using GPRESULT /H. It was working fine to apply the SSO settings. GPRESULT showed all the shortcut settings I had configured. Except there were no shortcuts. It wasn’t doing what it was supposed to do. The registry entries below were not configured. NO idea what the deal is with that, but in the environment I was working in, it didn’t get the job done. Now, maybe there was an environmental issue causing it? I don’t know. What I DO know is that I had to find a way to make it work, and so I’ll share that here with you just in case the ADM template doesn’t work for you, either.
PutShortcutsInStartMenu REG_SZ true
PutShortcutsOnDesktop REG_SZ true
StartMenuDir REG_SZ <whatever the directory you want apps to go into in the start menu – leave blank to put them directly in start>
DesktopDir REG_SZ <whatever the directory you want apps to go into on the desktop – leave blank to put them directly on the desktop>
SO – What’s this weird behavior? Well, for starters, it actually has to do with Storefront, not Receiver. But since Storefront and Receiver function more or less as a pair, and the issue is manifest in Receiver, I’m still blaming that. Mostly because I’m stubborn, as the issue DOES lie with Storefront. For the record, this environment was using SF2.6.
The problem is that when Storefront remembers the application subscriptions, apparently a flag is set BY RECEIVER that tells Storefront whether or not it should create the desktop shortcuts. Thus, if you have Receiver 4.0 or 4.1, and have a bunch of applications subscribed, THEN you upgrade to 4.2 – NOTHING HAPPENS. No desktop shortcuts, no start menu folder like you specified – NOTHING. How to fix this? The official answer from Citrix (that doesn’t seem to be documented ANYWHERE that I can find) is “unsubscribe and resubscribe to all your applications”. Well isn’t that just peachy.
Ok, fine. So you’ve done that.
But then – you log into another workstation, and that one isn’t configured for desktop shortcuts. Then you log back into one that is, and lo and behold – NO SHORTCUTS!
This is just ridiculous. Why is the data about whether or not to publish an application shortcut stored in Storefront to begin with? What are the implications for people who use XenDesktop, and access that environment using the HTML5 client? What then? I didn’t test this, but I’d imagine it will create a problem as well since naturally the HTML5 client relies on Storefront subscriptions, and is incapable of publishing a shortcut to the desktop on the client machine the browser is being run on.
IMO, the way this SHOULD work is Storefront just keeps track of the subscribed apps, and the Receiver handles creating and publishing shortcuts for any subscribed app. That way moving amongst machines with different Receiver versions and/or configurations won’t create a problem. I mean really, Citrix. You bill yourself as a mobility company, and yet when the rubber meets the road, now you’re saying that “Sure, you can be mobile – as long as all your access devices have the exact same version of Receiver configured the exact same way.”
Doesn’t sound very mobile to me.