What if you want to mimic PNAgent functionality like the old days? Put the users apps in the start menu and keep the “Receiver” stuff out of their faces so they aren’t even aware of it…well thats what this article will show you.
This is “kind of” a followup to my previous article HERE about configuring StoreFront 2.0 and Receiver 4.0 for pass through authentication. Now in that post I showed how to install a receiver client fully configured from the command line without any end user intervention or enrollment required (No e-mail or server address entry). Now, the way I set it up and directed you was to copy over the Receiver shortcut into Start Menu-> Startup because Receiver doesn’t auto launch as it has in the past. Note that Single Sign On (SSO) DOES launch and can be seen if you check task manager..if you followed my directions in the last article once you logon, with Receiver shortcut in “Startup” it will pop open Receiver and you would run with your apps from there.
Okay, remember the goal here is zero user touch, the only thing the user should end up with is Published Applications in their Start Menu. Along that line, install using the command line options from the last article. Make sure your GPO is set and IE Trusted Sites (again, all in my last Tips From the Field article), and don’t copy the Receiver.lnk to startup..we don’t want the Green-bubble receiver popping open for end users.
The key to this is another entry called out in our eDocs link that tells us if we set a certain couple of regkey’s then whatever is set on the XenApp application under “Client Application Folder” will be where the app is placed in the Start Menu. Which is exactly how a lot of you are used to seeing it when you had Web Interface and not StoreFront. The text from eDocs reads as such:
For applications published through XenApp with a Client applications folder (also referred to as a Program Neighborhood folder) specified, you can specify that the client applications folder is to be appended to the shortcuts path as follows: Create the entry REG_SZ forUseCategoryAsStartMenuPath and give it the value “true”. Use the same registry locations as noted above.
Okay, so if we inject these RegKey’s then the Client Applications folder on the published apps should matter again? So looking around the web so I didn’t have to write something from scratch I stumbled on a great post by Trond Haavarstein (@XenAppBlog on Twitter) HERE with a simple .BAT file for installing Receiver..so credit to him for that, I took that and with a few modifications it now suits my needs. It installs with the options I needed, it injects my RegKeys so that “Client Application Folder” now “works”, and it reboots once the install is done. You could also just as easily give all this info to your SCCM admin for them to build their package with too.
REM This is used to deploy and configure Citrix Receiver for Windows 7/8
REM Set variables
IF NOT DEFINED LOGDIR SET LOGDIR=%SystemRoot%\TEMP
REM Below sets install to Silent
SET OPTIONS=%OPTIONS% /silent
REM Below sets option to Include Single Sign On
SET OPTIONS=%OPTIONS% /includeSSON
REM Below locks addition of any more Stores
SET OPTIONS=%OPTIONS% /ALLOWADDSTORE=N
REM Below sets to enable Pre-launch ability with this client
SET OPTIONS=%OPTIONS% /ENABLEPRELAUNCH=TRUE
REM Below sets our default store
SET OPTIONS=%OPTIONS% /STORE0=”Store;https://sf.mydomain.com/Citrix/Store/discovery”
REM Adds RegKey to use the “Client Application” folder specified in AppCenter as the Start Menu location to place apps.
REG ADD HKLM\SOFTWARE\WOW6432NODE\Citrix\Dazzle /f /v UseCategoryAsStartMenuPath /t REG_SZ /d True
REM Adds RegKey to use the “Client Applicaton” folder specified in AppCenter as the Start Menu location to place apps.
REG ADD HKCU\Software\Citrix\Dazzle /f /v UseCategoryAsStartMenuPath /t REG_SZ /d True
START /WAIT CitrixReceiverWeb.exe %OPTIONS%
SHUTDOWN /r /t 00
Once the computer reboots, any applications configured with a “Client Application Folder” and an application description of “KEYWORDS:Auto” will auto populate into the end users Start Menu in the folder defined, or going forward any apps the user subscribes to. Thats about as close to WI/PNagent as we can get nowadays…zero user touch, apps auto-populate into the start menu, and its simple for the who matters most: the end user.