DPrinters can be connected to a Citrix session in various ways. In addition to Microsoft Group Policy, various scripts, and tools, Citrix Workspace Environment Manager (WEM) also offers the option to permanently link endpoints to specific printers. A related feature is also available in Citrix Studio, but here is a brief explanation of how it works with the „Use Device Mapping Printers“ file and WEM.
What is the actual purpose of the Use Device Mapping Printers File? The XML file defines a mapping that specifies which endpoints should be automatically connected to which printers. This can include one or more printers, with one designated as the default printer for each. Unfortunately, Citrix does not provide a dedicated tool for generating the XML file, so it must be created manually. The exact format is described in the Citrix article xml-printer-list-configuration can be found in.
After working through the XML syntax, one thing stands out, and that is the IdSite, i.e., the ID of the WEM configuration set being used! That doesn't help right away, though, because the IdSite can't be found anywhere in the WEM console, but without the IdSite, there's no mapping! Well, then let’s try the brute-force method: searching the WEM’s SQL database. The IdSite can be found in the dbo.VUEMSites table.
If you don't want to search the database right now, you can also find the IdSite using the WEM PowerShell SDK. On the WEM infrastructure server, run the following command in PowerShell: Get-UserAdObject -InfrastructureServer localhost -SiteName "Configuration Set". This section lists all user AD objects for the page, as well as the associated IdSite, which is the same for all of them.
Citrix should address this by providing a tool to generate the XML file and also display IdSite in the console and/or integrate it directly into the tool.
