If Citrix Universal Print Server to test identification problematic printer driver in Citrix UPS Installation - , which we in the test team look deeply, how well the product works when we perform: Print Driver Isolation compressive load tests on the entire environment when real third-party printer drivers are installed on a large scale and stressed. One of the things we have with Citrix UPS found on the print server, print insulation host and spoolsv processes have crashed.
Why does this happen?
Where are these crashes occur? For starters, we try here at Citrix always to narrow it and to find the cause of the problem. So if we execute installed on a print server with Citrix UPS different stack traces on the PCB insulation host or spoolsv processes, the cause is always of a third-party drivers on the server crash caused either process. But used depending on the driver of the administrator on the print server, it could crash another process, so what gives? Enter printer driver isolation.
What's printer driver isolation?
printer drivers are notorious for this kind of questions that and can vary greatly their quality, and Microsoft introduced to identify and reduce these problems against this mechanism. Essentially, it is a mechanism introduced Microsoft that the printer driver allows it to be carried out within separate run spaces.
printer driver isolation in three different configurations can be configured, all of them set at the driver level can be set within the "Print Management" console on the "Drivers" section. The first mode is "shared" that creates a print insulation host process that is shared with another driver that uses this mode. The second is "None", then the printer driver in this mode, the tread tells spoolsv. Finally, "isolated" creates a separate print insulation host for each active printer driver performs all printing activity.
To illustrate my point, here is what happens to a problematic printer driver in all three modes in scenarios. When a printer driver was erratic with "No" Printer isolation mode would crash spoolsv.exe. This is a huge obstacle to people who use the print server, and. In its most stable and scalable state If spoolsv crashed, no further printing operation can continue when the spooler on the print server is restarted.
The Standard "Shared" mode for printing activity permitted to continue, spoolsv is not a crashed process but instead create a separate print insulation host process is open to all printer related to the driver activity in this running space happens. But of course, if a problematic printer driver Print Isolation host were to crash, all print jobs that would work with the "shared" mode are rendered useless because they for a reboot or cleanup of Print Isolation host process waits.
The last "isolated" mode creates a separate drive space for each of the printer driver. This provides an environment an elastic print server by individual print insulation host processes crashes, so that working drivers continue their pressure within their own running chambers. The disadvantage, however, this is every print insulation host consumes a memory requirement, which could potentially increase memory usage on the print server. This may have the lowest possible storage conditions result that would occur no doubt, when the number of drivers are managed on the print server, were continually increasing.
If we UPS test large-scale print environments, we find pressure isolation Host "isolated" mode is to narrow down very useful which drivers were problematic therefore to use and specific drivers may also exclude from our tests, so that we can produce base product results based on our environment on a large scale. Once there is an established set of drivers is used, a "shared" model for all printer drivers is also believed to emulate customer environments, while a stability in spoolsv process is maintained.
If your Print Server with Citrix Universal Print Server experienced constant print insulation host and spoolsv crashes I recommend reading to learn this article in more detail, such as Print Driver Isolation and some specific recommendations for configuration
- http :. // Support.citrix.com/article/CTX136332 - pressure recommendations for XenApp / Terminal Server environment (Print Driver insulating section)
- http://msdn.microsoft.com/en-us/library/windows / hardware / ff560836 (v = VS.85) .aspx - printer driver isolation
- http://blogs.technet.com/b/askperf/archive/09/10/08/windows-7-windows-server-08-r2-print-driver-isolation.aspx - Windows 7 / Windows Server 08 R2: Print Driver Isolation
- ftp://ftp.hp.com/pub/softlib/software12/COL40853/ds-99414-1/UPD_Microsoft_Driver_Isolation_Mode.pdf - DRIVER ISOLATION MODE with the HP Universal Print Driver with
last thought - your driver, contact the manufacturer if you identify driver error
printer driver isolation principle reduction and identify a useful tool driver problems. Ideally, you would not be used in production (especially "isolated" mode. If we identify faulty drivers, we contact them to make the production attention to the issues. Often there are updates, or replacement driver available from the manufacturer.
0 Komentar