Citrix XenDesktop 7.x – Citrix Session Printers are not visible via Control Panel, Devices And Printers Affected System: Windows Server 2012 R2 as well as Windows Server 2016 Citrix Environment: XenDesktop 7.15 LTSR CU2
Just recently I was tasked to identify all Citrix Receiver Versions connecting to a Citrix XenDesktop 7.x environment. For starters, to get information on current sessions issue the following PowerShell cmdlets on your Citrix Broker Server:
Get-BrokerSession | Select MachineName,UserName,ClientPlatform,ClientVersion,*Protocol* | Out-GridView
To get hands
I came upon this quite frequent issue with my XenDesktop 7.8 Hosted Shared Desktop environment based on Windows Server 2008 R2. Folder Redirection via GPO is in place, whereas Citrix User Profile Management is not used.
Starting with Citrix XenDesktop 7.x there have been some features that have been deprecated by Citrix, such as LPT and COM Port Mapping, which are not working as expected or properly after upgrading to VDA 7.x. I stumbled upon this
This one’s quite easy, actually. Did you ever wonder how to remove those GoTo Icons from your StoreFront Store and/or Start Menu Shortcuts?
Citrix Receiver for Mac – Session Printer Mapping Issues – Printers don’t show or won’t get mapped Update: Have a look at Carl’s article as well: Print Driver for Non-Windows Clients As per Citrix CTX140208 and CTX139020: When non-Windows Receivers connect to a
Almost everybody has struggled with the now infamous Error 1030 (The connection to “ApplicationName” failed with status (1030)) when connecting with Citrix Receiver for Windows to XenDesktop through NetScaler and StoreFront. There even is an whole armada of articles available
Citrix XenDesktop 7.x – Black Screen when connecting to Published Desktop When connecting to a Windows Server 2008 R2 Published Desktop (provisioned as a VM, not a physical machine) with XenDesktop 7.x you might receive a black and blank Desktop,
Upon upgrading Citrix Profile Management to v5.2.1 on one of my Workers and rebooting my users were unable to connect to that server. It came down to a Load Evaluator Index of 10000:
After upgrading Citrix Director to v7.6.300 in order to implement the newly added Framehawk Support I ran into an error after launching Citrix Director: An internal error has occurred. For assistance, contract your administrator (including typo):