{"id":1663,"date":"2019-03-27T13:00:00","date_gmt":"2019-03-27T13:00:00","guid":{"rendered":"http:\/\/neu.koetzingit.de\/drucken-unter-citrix-und-grosse-spool-dateien\/"},"modified":"2026-06-02T13:32:49","modified_gmt":"2026-06-02T13:32:49","slug":"drucken-unter-citrix-und-grosse-spool-dateien","status":"publish","type":"post","link":"https:\/\/www.koetzingit.de\/en\/drucken-unter-citrix-und-grosse-spool-dateien\/","title":{"rendered":"Large spool files with Citrix UPD (EMF)"},"content":{"rendered":"

N<\/span>As before, not everyone is aware that the Citrix Universal Printer Driver (UPD) can sometimes generate very large spool files. On a LAN, print jobs with large amounts of data aren\u2019t a big deal, but they can cause massive problems over WAN connections. These large spool files are often print jobs from Adobe PDF documents, but they can also occur with other file types like Word, etc.<\/p>\n

How do these print volumes arise, and what can be done about them? Those who understand the issue can reduce print volumes by more than 99%!<\/p>\n

<\/p>\n

The spool file with the Citrix UPD<\/span><\/h3>\n

Users of the Citrix Universal Printer Driver (UPD) use Microsoft's Enhanced Metafile (EMF) format by default. Citrix has enhanced the EMF with various features, including the ability to optimize printouts over WAN connections. This feature was first introduced with Presentation Server 4.5 and has been continuously improved and expanded.<\/p>\n

However, despite all the optimizations, spool files can still grow to enormous sizes. This means that the source file\u2014for example, a 9 MB PDF document\u2014will result in a spool file of 450 MB<\/strong>, which may need to go through a WAN connection<\/span><\/strong>.\u00a0<\/p>\n

\"News<\/p>\n

Even if the UPD is set to maximum compression, more than 50% of print data remains, and thus 225 MB of data<\/strong>.<\/p>\n

\"News<\/p>\n

With Riverbed, NetScaler SD-WAN, etc., this can possibly be optimized further, but the real problem lies elsewhere: Microsoft EMF can't handle Raster data<\/strong> can't handle it well, or worse: it increases them even further<\/strong>. Microsoft has described the EMF issue, noting that EMF should turned off<\/strong> will be!<\/p>\n