In this post I’m going to show you how to setup Citrix Receiver Start Menu Integration and troubleshoot in case it doesn’t work.
First off, to get this working you NEED to use HTTPS. Check out my previous posts Securing Citrix X1 StoreFront with Powershell and Citrix StoreFront Complete Automation.
I’m using Citrix Receiver 4.3 and Citrix Storefront 3.0. Let’s install Citrix Receiver using the following Powershell code:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
Write-Verbose "Setting Arguments" -Verbose $StartDTM = (Get-Date) $Vendor = "Citrix" $Product = "Receiver" $PackageName = "CitrixReceiver" $InstallerType = "exe" $Version = "4.3" $LogPS = "C:\Windows\Temp\$Vendor $Product $Version PS Wrapper.log" $LogApp = "C:\Windows\Temp\$Product.log" $Destination = "${env:ChocoRepository}" + "\$Vendor\$Product\$Version\$packageName.$installerType" $UnattendedArgs = '/silent /includeSSON' Start-Transcript $LogPS CD $Version Write-Verbose "Starting Installation of $Vendor $Product $Version" -Verbose (Start-Process "$PackageName.$InstallerType" $UnattendedArgs -Wait -Passthru).ExitCode Write-Verbose "Customization" -Verbose copy-item "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Citrix Receiver.lnk" -Destination "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\Citrix Receiver.lnk" -Recurse Write-Verbose "Stop logging" -Verbose $EndDTM = (Get-Date) Write-Verbose "Elapsed Time: $(($EndDTM-$StartDTM).TotalSeconds) Seconds" -Verbose Write-Verbose "Elapsed Time: $(($EndDTM-$StartDTM).TotalMinutes) Minutes" -Verbose Stop-Transcript |
This will install Citrix Receiver with Single Sign On and copy the icon to the Startup folder.
Please be aware that if you install 4.3 Technical Preview you need to do some manual clicks. This will go away when it’s official.
One of the most common mistakes is forgetting to add your Storefront URL to the Trusted Zone List. You’ll find the GPO in Administrative Templates – Windows Components – Internet Explorer – Internet Control Panel – Security Page.
Let’s create a Group Policy for Citrix Single Sign On with Storefront Configuration. You need to import the ADM templates.
I’m keeping the ADM templates with the binaries. You’ll find these under C:\Program Files (x86)\Citrix\ICA Client\Configuration.
Navigate to Administrative Templates – Classic Administrative Templates – Citrix Components – Citrix Receiver – User Authentication – Local username and password. Set the following:
Navigate to Administrative Templates – Classic Administrative Templates – Citrix Components – Citrix Receiver – Storefront – Storefront Accounts List. Enable the policy and define your Store.
1 |
Store;https://sf-01.ctxlab.vmw/Citrix/Store/discovery;On;SF01 |
Navigate to Administrative Templates – Classic Administrative Templates – Citrix Components – Citrix Receiver – Self Service and enable the first 3 policies.
I prefer to enable SelfServiceMode and Add/Remove Account at this stage. This makes it much easier for troubleshooting.
This is how I link the Internet Explorer and Citrix Receiver SSON policies.
Now restart the computer and make sure it belongs to the OU where you have linked the GPO.
Head over to Store and configure Domain Pass-through.
To add the application shortcut to the Start Menu you need to set KEYWORDS:auto.
Logon to your test computer. If everything works it should look like this.
When you disable SelfServiceMode you’ll get all applications populated via the Citrix Receiver Start Menu Integration.
Troubleshooting
Single Sign On
The first step is to verify that the Single Sign On process ssonsvr.exe is running in Task Manager.
Now open your browser and verify that you get Single Sign On to StoreWeb. Please note that this works with both HTTP and HTTPS.
Add Account
The Store has not been configured in GPO.
Your apps are not available at this time
Your Store is not configured to use HTTPS.
You can verify this by clicking Accounts. If you have the Store configured with HTTPS in GPO, but the account show HTTP, you have certification problems. Verify that HTTPS works with StoreWeb.
Cannot start App – Please contact your helpdesk
You’ll find various error messages in the event log of your Storefront server.
You need to enable TrustedXML on your delivery controllers, check CTX140045 for more info.
1 2 |
asnp Citrix* Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $true |
Citrix Receiver Start Menu Integration not working
Make sure to go through the steps above. If you can manually add icons in Citrix Receiver / StoreWeb and they show up in the Start Menu there´s something wrong with your application keywords.
Resources
Why are you using the ADM file and not the ADMX file?
Webster
I prefer using the old ADM until Citrix learns how to properly create ADMX files! “ADMX Migrator encountered a policy that does not have a supportedOn value.” http://www.verboon.info/2015/07/citrix-receiver-4-3-now-with-admx-support-for-receiver-group-policy-well-almost/
When you state to import the templates, are you suggesting to import them into sysvol, and the client machine?
I have gotten the web portion to work, I go to the storefront page, i get prompted to use the current user credentials.. say yes. Apps are enumerated etc.
Receiver is another story, I have tried to configure the store via studio and that seems to give it the proper store but I get an error that the apps are not available, try again later.
If I add the store it works!
I have set the receiver policies and copied to my dc and desktop image in the policy definitions folders respectively. RSOP shows that the settings get applied.
If i remove the store defined in studio, and attempt to run receiver with just the policy set – it comes up as if no connection has been set. if i add it i am sure it will work.
Suggestions?
The only thing I did not do is install receiver via command line and defining the store, sso etc. Is that required for this? Going to try this next anyway but if the initial install was done manually and i specified to enable sso (4.3) doesnt that carry over to my imaged desktop?
Hi Juan.
1. Import to sysvol only
2. The first step is to verify that the Single Sign On process ssonsvr.exe is running in Task Manager. Therefore install Receiver with SSO -> ‘/silent /includeSSON’
ADMX Migrator encountered a policy that does not have a supportedOn value when a import admx to policyDefinitions…
i will have some issues with these warning?
Thanks!
Yes, that’s why you should stick to ADM from Citrix Receiver 4.2 until Citrix gets the ADMX straight….
Has anyone tested running Citrix receiver 4.2 ADM template with a 4.3 receiver deployment? This would be strictly for testing.
Yes they should work, if I remember correctly there wasn’t any with the 4.3 release.
Thanks for the information.