A. Print servers commonly have problems with a bad driver crashing. This crash brings down the entire print spooler because the drivers run within the spooler process. With the print spooler crashed, all printers become unavailable, and if you are running a print cluster then the print cluster resource becomes unavailable.

In Windows Server 2008 R2, you can select levels of isolation for print drivers. The print drivers can continue running in the same process as the spooler (no isolation, None); have several drivers running in a separate driver process (Shared); or have each driver running in its own process (Isolated). By default, print drivers are placed in a shared print process separate from the spooler.

You can configure the isolation for each driver using the Print Management MMC snap-in. Navigate to the Print Servers, <Server>, Drivers leaf, as shown here.

Click to expand.

• Q. Is Windows Server 2008 R2 built on Server 2008's kernel in the same way that Windows Server 2003 R2 was built on Server 2003's kernel?
• Top 10 New Features in Windows Server 2008 R2
• Windows Server 2008 R2: Not Your Average R2
• The Little Things About Windows Server 2008 R2