How To

Windows Server 2025 Print Server: Install and Deploy by GPO

Deploying printers used to be the easy part of running a Windows Server print server. You shared the queue, pointed a Group Policy object at it, and every PC pulled the driver from the server on first use. That stopped being automatic in 2021, when the PrintNightmare fixes made Point and Print driver installs an administrator’s job. A Windows 11 client often shows no error at all, because it quietly connects through a stand-in driver, so the real question is where each client’s driver comes from.

Original content from computingforgeeks.com - post 180764

This guide installs the Print Server role, shares a TCP/IP printer, deploys it with the Print Management console and Group Policy, and sets Point and Print restrictions so only your server hands out drivers. We used three lab VMs (a domain controller, a member print server and a Windows 11 24H2 client) and a stand-in printer that saves every job, so each result below is a job we saw arrive. The behavior described here was checked on Windows Server 2025 in October 2026.

How a Windows Server print server hands a printer to a client

A print server is a Windows machine whose Print Spooler owns the queues, and the clients only hold connections to those queues. When you understand which piece lives where, every later decision about drivers and policy follows from it. The path a document takes runs in this order:

  1. The queue: on the server, a printer object ties a driver to a port. The port is a TCP/IP address, and the driver turns a document into the language the device speaks (PCL or PostScript).
  2. The share: sharing the queue publishes it as \\PRINT01\Floor2-Laser over SMB and RPC, and publishing it in Active Directory makes it searchable.
  3. The connection: a client connects to the share by hand or through Group Policy. To render jobs locally it needs a driver that matches the server’s, and fetching that driver is the Point and Print step.
  4. The job: the client spools to the server, the server sends the rendered job to the device on TCP 9100, and the device prints it.

Group Policy only touches step 3, telling a computer or user which connection to create. It does not install anything by itself, so the driver question in step 3 is where deployments fail. The diagram below shows the lab and the order of those hops:

Architecture diagram of a Windows Server print server lab: DC01 pushes the GPO to CLIENT01, CLIENT01 connects to PRINT01 over SMB and RPC, PRINT01 prints to the network printer on RAW 9100

The domain controller holds the GPO and the published printer record, PRINT01 holds the queues, and CLIENT01 is a domain-joined Windows 11 PC where a standard user named brian signs in. The dotted branch is the one that matters most: when the client lacks the driver, Point and Print rules decide what happens next.

What you need before installing the role

The print server should be a member server, not a domain controller. Microsoft’s PrintNightmare advisory states plainly that domain controllers are affected if the print spooler service is enabled, and on our freshly promoted Server 2025 DC the spooler was running with startup type Automatic. Check yours with Get-Service Spooler. On DCs that do not share printers, stopping it is only half the job: set its startup type to Disabled too, or it comes back at the next reboot. Microsoft’s service guidance notes the trade-off: printer pruning of stale published printers runs on DCs and needs the spooler. We left DC01’s spooler alone in the lab. Our lab used these machines:

  • DC01 (10.0.1.10): Windows Server 2025 domain controller for hq.lan, created as in our Active Directory Domain Services guide.
  • PRINT01 (10.0.1.20): Windows Server 2025 member server in an OU named Servers, 2 vCPU and 4 GB RAM, cloned from a Server 2025 template on Proxmox.
  • CLIENT01 (10.0.1.30): Windows 11 Enterprise 24H2, joined to the domain in an OU named Workstations.
  • The printer (10.0.1.60): any device that accepts raw jobs on TCP 9100. Ours was a small listener that writes each job to a file, which let us inspect what the drivers produced.

Two vCPUs were tight. Microsoft Defender (MsMpEng) kept PRINT01 near 85% CPU for long stretches of the lab, and the guest stopped answering remote commands while it did. On a production server with dozens of queues, give it 4 vCPUs and 8 GB, and size the disk for the spool folder if users print large CAD or photo jobs. If you have not installed the OS yet, our Windows Server 2025 installation guide covers it.

“renaming it to ‘PRINT01’ failed with the following error message: The directory service is busy.”

We hit this when joining the print server with Add-Computer -NewName PRINT01 a few minutes after promoting the domain controller. The join itself worked, so the machine landed in AD under its random WIN- name, and only the rename failed. A print server’s name ends up in every share path and in the deployed-printer object, so fix it before sharing anything. Rename it with a Domain Admins account and restart (in the lab we built the credential in a script and rebooted with shutdown /r, which does the same thing):

$cred = Get-Credential
Rename-Computer -NewName PRINT01 -DomainCredential $cred -Force
Restart-Computer

After the restart, hostname returned PRINT01 and the network profile read DomainAuthenticated, which is the profile the Restrictive firewall rules need.

What installing the Print Server role adds

The role is one feature called Print-Server, and you install it from an elevated PowerShell prompt on PRINT01. The -IncludeManagementTools switch matters here, because without it you get the spooler role but not the Print Management console. List what’s available first:

Get-WindowsFeature *Print* | Format-Table DisplayName, Name, InstallState -AutoSize

Everything starts as Available on a fresh install:

DisplayName                       Name                  InstallState
-----------                       ----                  ------------
Print and Document Services       Print-Services           Available
Print Server                      Print-Server             Available
Internet Printing                 Print-Internet           Available
LPD Service                       Print-LPD-Service        Available
Internet Printing Client          Internet-Print-Client    Available
Print and Document Services Tools RSAT-Print-Services      Available

Install the Print Server role service with its tools:

Install-WindowsFeature Print-Server -IncludeManagementTools

It took 112 seconds on our VM and did not ask for a reboot. The feature result also pulls in the parent role and the Print and Document Services Tools:

Success RestartNeeded ExitCode FeatureResult
------- ------------- -------- -------------
   True            No  Success {Print Server, Print and Document Services, Remote Server Administration Tools, Print and Document Services Tools...}

Running the same Get-WindowsFeature query again shows Print-Services, Print-Server and RSAT-Print-Services as Installed, while Internet Printing and the LPD Service stay Available. Leave them off unless a specific client needs them: Internet Printing serves queues over HTTP, and LPD exists for old Unix clients and is on Microsoft’s deprecated list. What the role does not do is touch the drivers. PRINT01 still had only the inbox set (the IPP, Universal Print and Virtual Print class drivers, Print To PDF, Remote Desktop Easy Print and the Point and Print compatibility drivers), so the next step is choosing one.

Add the driver, the TCP/IP port and the shared printer

We used Microsoft’s own class drivers because they ship with Windows Server 2025 and need no download. It is more than a lab convenience. Microsoft’s end of servicing plan for third-party printer drivers stopped publishing new vendor drivers to Windows Update for Windows 11 and Server 2025 on January 15, 2026, and from July 2026 driver ranking prefers the inbox IPP class driver. A PCL6 or PostScript class driver works with most office lasers, and it’s the driver the vendor will eventually point you to anyway. Add both class drivers from the local driver store:

Add-PrinterDriver -Name 'Microsoft PCL6 Class Driver'
Add-PrinterDriver -Name 'Microsoft PS Class Driver'
Get-PrinterDriver | Format-Table Name, MajorVersion, PrinterEnvironment -AutoSize

Both land as version 4 drivers for x64, and that version number decides how clients get them later:

Name                                                    MajorVersion PrinterEnvironment
----                                                    ------------ ------------------
Microsoft PS Class Driver                                          4 Windows x64
Microsoft PCL6 Class Driver                                        4 Windows x64
Universal Print Class Driver                                       4 Windows x64
Microsoft Virtual Print Class Driver                               4 Windows x64
Microsoft Print To PDF                                             4 Windows x64
Microsoft IPP Class Driver                                         4 Windows x64
Remote Desktop Easy Print                                          3 Windows x64
Microsoft enhanced Point and Print compatibility driver            3 Windows x64
Microsoft enhanced Point and Print compatibility driver            3 Windows NT x86

Next, create a Standard TCP/IP port for the device. Add-PrinterPort with a host address builds a RAW port on 9100 by default, which is what nearly every network laser expects. Change 10.0.1.60 to your printer’s address:

Add-PrinterPort -Name 'IP_10.0.1.60' -PrinterHostAddress '10.0.1.60'
Get-PrinterPort -Name 'IP_10.0.1.60' | Format-List Name, PrinterHostAddress, PortNumber, Protocol, SNMPEnabled

SNMP comes up disabled when the port is made this way, so the queue gets no SNMP status from the device until you turn it on in the port properties:

Name               : IP_10.0.1.60
PrinterHostAddress : 10.0.1.60
PortNumber         : 9100
Protocol           : RAW
SNMPEnabled        : False

Now create the queues. -Shared publishes the SMB share, and -Published writes a printQueue object to Active Directory so users can find it by location. We made a second queue on the PostScript driver to compare driver behavior on the client later:

Add-Printer -Name 'Floor2-Laser' -DriverName 'Microsoft PCL6 Class Driver' -PortName 'IP_10.0.1.60' -Shared -ShareName 'Floor2-Laser' -Published -Location 'Floor 2, east wing' -Comment 'Mono laser by the lifts'
Add-Printer -Name 'Floor3-Plotter' -DriverName 'Microsoft PS Class Driver' -PortName 'IP_10.0.1.60' -Shared -ShareName 'Floor3-Plotter' -Published -Location 'Floor 3, design room'
Get-Printer | Where-Object Shared | Format-Table Name, ShareName, DriverName, PortName, Published -AutoSize

Both queues should show Published as True:

Name           ShareName      DriverName                  PortName     Published
----           ---------      ----------                  --------     ---------
Floor3-Plotter Floor3-Plotter Microsoft PS Class Driver   IP_10.0.1.60      True
Floor2-Laser   Floor2-Laser   Microsoft PCL6 Class Driver IP_10.0.1.60      True

Print something from the server before involving any client, because it proves the driver and port work on their own. If this fails, no Group Policy setting will fix it:

Get-Date | Out-String | Out-Printer -Name 'Floor2-Laser'

Our stand-in printer logged a 17,409-byte job from PRINT01 within seconds. Its first bytes were @PJL COMMENT MSxpsPCL6 followed by @PJL ENTER LANGUAGE=PCLXL, which means the class driver rendered the page as PCL XL (PCL6), the language a real HP-compatible laser would expect.

Why domain clients reach the share with the firewall rules off

Clients need SMB (445) and the spooler’s RPC endpoints (135 plus a dynamic port) to reach a shared queue, and on our Windows Server 2025 print server those were open for domain clients without us touching the firewall. We expected otherwise. The familiar File and Printer Sharing group stayed disabled after the role install and after sharing both printers:

Get-NetFirewallRule -DisplayGroup 'File and Printer Sharing' | Where-Object Direction -eq Inbound | Sort-Object DisplayName | Format-Table DisplayName, Profile, Enabled -AutoSize

All ten inbound rules read False, the spooler ones included:

DisplayName                                             Profile Enabled
-----------                                             ------- -------
File and Printer Sharing (Echo Request - ICMPv4-In)         Any   False
File and Printer Sharing (Echo Request - ICMPv6-In)         Any   False
File and Printer Sharing (LLMNR-UDP-In)                     Any   False
File and Printer Sharing (NB-Datagram-In)                   Any   False
File and Printer Sharing (NB-Name-In)                       Any   False
File and Printer Sharing (NB-Session-In)                    Any   False
File and Printer Sharing (SMB-In)                           Any   False
File and Printer Sharing (Spooler Service - RPC)            Any   False
File and Printer Sharing (Spooler Service - RPC-EPMAP)      Any   False
File and Printer Sharing (Spooler Service Worker - RPC)     Any   False

Yet CLIENT01 connected anyway, which sent us looking for the rule that let it in. Server 2025 has a second group called File and Printer Sharing (Restrictive), and after sharing the printers it was enabled on the Domain profile only. Microsoft first announced this SMB firewall change in Windows Insider builds, and its secure SMB traffic page lists updated firewall rules beginning with Windows 11 24H2 and Windows Server 2025. Our server was DomainAuthenticated when we shared the queues, which fits the Domain-only result:

Get-NetFirewallRule -Direction Inbound | Where-Object DisplayGroup -like '*Restrictive*' | Format-Table DisplayName, Enabled, Profile -AutoSize

Each rule exists twice, enabled for Domain and disabled for Private and Public:

DisplayName                                                           Enabled         Profile
-----------                                                           -------         -------
File and Printer Sharing (Restrictive) (SMB-In)                         False Private, Public
File and Printer Sharing (Restrictive) (LLMNR-UDP-In)                   False Private, Public
File and Printer Sharing (Restrictive) (Spooler Service - RPC)          False Private, Public
File and Printer Sharing (Restrictive) (Spooler Service Worker - RPC)   False Private, Public
File and Printer Sharing (Restrictive) (Echo Request - ICMPv4-In)       False Private, Public
File and Printer Sharing (Restrictive) (Spooler Service - RPC-EPMAP)    False Private, Public
File and Printer Sharing (Restrictive) (Echo Request - ICMPv6-In)       False Private, Public
File and Printer Sharing (Restrictive) (Echo Request - ICMPv6-In)        True          Domain
File and Printer Sharing (Restrictive) (Spooler Service - RPC-EPMAP)     True          Domain
File and Printer Sharing (Restrictive) (Echo Request - ICMPv4-In)        True          Domain
File and Printer Sharing (Restrictive) (Spooler Service Worker - RPC)    True          Domain
File and Printer Sharing (Restrictive) (Spooler Service - RPC)           True          Domain
File and Printer Sharing (Restrictive) (LLMNR-UDP-In)                    True          Domain
File and Printer Sharing (Restrictive) (SMB-In)                          True          Domain

This matters in two situations. If Get-NetConnectionProfile on the print server reports Private or Public instead of DomainAuthenticated (a DC that was unreachable at boot is the usual cause), clients cannot connect until the profile is fixed. And if you hand out queues to machines outside the domain, enable the matching rules for that profile rather than the old group, as shown in our guide to opening ports in Windows Server Firewall. Disabling the firewall to make printing work trades one fix for a much bigger problem.

Deploy the printer with Group Policy from Print Management

Deploying from Print Management writes a per-machine or per-user printer connection into a GPO, and every computer or user the GPO applies to gets that connection the next time the client processes it (for us that took a restart and a sign-in, as shown below). Create the GPO and link it to the workstation OU first. We did that on DC01 with the Group Policy module:

New-GPO -Name 'Workstation Printers' -Comment 'Printer connections from PRINT01' | New-GPLink -Target 'OU=Workstations,DC=hq,DC=lan'

The link comes back enabled on the OU:

DisplayName          Enabled Target
-----------          ------- ------
Workstation Printers    True OU=Workstations,DC=hq,DC=lan

On PRINT01, open Print Management from Server Manager, Tools, or run printmanagement.msc. Expand Print Servers, then PRINT01 (local), then Printers. Both queues should show as Ready with their class drivers and the driver version the server installed:

Print Management console on Windows Server 2025 listing Floor2-Laser and Floor3-Plotter as Ready on PRINT01 with the PCL6 and PS class drivers

We installed the Group Policy Management tools on PRINT01 with Install-WindowsFeature GPMC before opening the deployment dialog, so its Browse button could list the domain’s GPOs, and ran Print Management as a member of Domain Admins, since the account needs rights to edit the GPO. Then right-click the printer and pick the deployment entry:

Print Management on Windows Server 2025 with the Floor2-Laser right-click menu open on Deploy with Group Policy

Choose Deploy with Group Policy… from that menu. The same menu also holds Remove from Directory, which unpublishes the queue from Active Directory without deleting it.

In the Deploy with Group Policy dialog, work through the controls in this order:

  1. Click Browse…, open Workstations.hq.lan and pick the Workstation Printers GPO.
  2. Tick The computers that this GPO applies to (per machine).
  3. Click Add and check that the new row reads Per Machine.
  4. Click OK to write the connection into the GPO.
Print Management Deploy with Group Policy dialog on Windows Server 2025 with Floor2-Laser added to the Workstation Printers GPO as Per Machine
  1. 1Browse...
  2. 2The computers that this GPO applies to (per machine)
  3. 3Add
  4. 4OK

Print Management answered with “Printer deployment or removal operation succeeded.” The checkboxes clear after Add, which looks like the setting did not stick, but the row in the list is what gets saved. Per machine means every user who signs in to a PC in the OU sees the printer, which suits shared desks and labs. Per user follows the person across PCs instead, and it’s the better fit when people hot-desk between floors.

Where the setting lands explains several odd behaviors later. It isn’t an Administrative Templates value: Print Management creates an msPrint-ConnectionPolicy object inside the GPO’s container in Active Directory, which you can read from DC01:

$g = Get-GPO 'Workstation Printers'
Get-ADObject -SearchBase "CN={$($g.Id)},CN=Policies,CN=System,DC=hq,DC=lan" -Filter 'objectClass -eq "msPrint-ConnectionPolicy"' -Properties printerName, serverName, uNCName | Format-Table printerName, serverName, uNCName -AutoSize

The object sits under CN=PushedPrinterConnections,CN=Machine, and it stores the server by its short name:

printerName  serverName uNCName
-----------  ---------- -------
Floor2-Laser \\PRINT01  \\PRINT01\Floor2-Laser

The published printQueue record for the same printer, by contrast, uses the full name \\PRINT01.hq.lan\Floor2-Laser. Keep that difference in mind when you fill in the Point and Print server list below, which names servers too.

Why gpupdate alone didn’t add the printer

A policy refresh can report success while the deployed printer is still missing, and Microsoft’s own documents disagree on when it should arrive. The Deploy printer connections page says per-computer connections are added when the user logs on, while the older PushPrinterConnections documentation ties them to a restart. On CLIENT01 we ran a forced computer refresh first:

gpupdate /target:computer /force
gpresult /r /scope computer

The GPO was applied from DC01, which rules out linking and filtering problems:

COMPUTER SETTINGS
------------------
    CN=CLIENT01,OU=Workstations,DC=hq,DC=lan
    Group Policy was applied from:      DC01.hq.lan

    Applied Group Policy Objects
    -----------------------------
        Workstation Printers
        Default Domain Policy

Even so, no printer appeared until we restarted the PC and brian signed in again, and the PrintService Operational log on the client then recorded the printer as created. We did not test a sign-out without a restart, or a per-user deployment, so the safe expectation for a per-machine printer is a restart plus a sign-in, not the minute you click OK. The restart itself took about 15 minutes on our client because Windows chose that moment to install pending updates, so do not promise a user a quick reboot.

Run this as the signed-in user to see what they got:

Get-Printer | Format-Table Name, Type, DriverName, ComputerName -AutoSize

brian had connected to the same queue by hand earlier, using the full name, so he now saw it twice:

Name                                Type DriverName                                ComputerName
----                                ---- ----------                                ------------
Microsoft Print to PDF             Local Microsoft Print To PDF
\\print01.hq.lan\Floor2-Laser Connection Microsoft enhanced Point and Print driver print01.hq.lan
\\PRINT01\Floor2-Laser        Connection Microsoft enhanced Point and Print driver PRINT01

Windows treats \\PRINT01 and \\print01.hq.lan as two different printers because the connection name is the key, and Print Management wrote the short name in our test. The duplicate is harmless for printing, yet it confuses users and breaks any script that matches on the printer name. Pick one way to hand out each queue, and when you move users from manual connections to Group Policy, plan to remove the old manual connections from their profiles. We did not script that cleanup in the lab, so test whatever you use on one PC first.

How Point and Print restrictions decide who installs a driver

Two separate controls govern driver installs, and they don’t stack the way people assume. The first is the registry value RestrictDriverInstallationToAdministrators under HKLM\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint. Per KB5005652, a value of 1, or no value at all, means only administrators can install a driver through Point and Print, and that overrides every other Point and Print setting. Setting it to 0 lets non-administrators install signed and unsigned drivers again, subject to whatever the Point and Print Restrictions policy still enforces. Microsoft says no combination of other settings is as safe as 1, so treat 0 as a temporary measure while you pre-stage drivers.

The second control is the Point and Print Restrictions policy. It limits which servers clients will take drivers from and what prompts appear. Its settings map to these values in the same key:

  • Restricted = 1 and TrustedServers = 1: users can only point and print to the servers in ServerList.
  • ServerList: fully qualified names separated by semicolons. Since the September 2021 updates, IP addresses work too.
  • InForest = 0: “Users can only point and print to machines in their forest” stays unticked, because the explicit server list is the stricter control.
  • NoWarningNoElevationOnInstall = 0 and UpdatePromptSettings = 0: “Show warning and elevation prompt” for new and updated drivers. Microsoft says any non-zero value leaves the device exposed.

We set all of them in the same GPO with Set-GPRegistryValue on DC01, which also works for the driver restriction value that isn’t in the inbox Printers templates. Adjust print01.hq.lan to your server’s name:

$k = 'HKLM\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint'
Set-GPRegistryValue -Name 'Workstation Printers' -Key $k -ValueName Restricted -Type DWord -Value 1
Set-GPRegistryValue -Name 'Workstation Printers' -Key $k -ValueName TrustedServers -Type DWord -Value 1
Set-GPRegistryValue -Name 'Workstation Printers' -Key $k -ValueName ServerList -Type String -Value 'print01.hq.lan'
Set-GPRegistryValue -Name 'Workstation Printers' -Key $k -ValueName InForest -Type DWord -Value 0
Set-GPRegistryValue -Name 'Workstation Printers' -Key $k -ValueName NoWarningNoElevationOnInstall -Type DWord -Value 0
Set-GPRegistryValue -Name 'Workstation Printers' -Key $k -ValueName UpdatePromptSettings -Type DWord -Value 0
Set-GPRegistryValue -Name 'Workstation Printers' -Key $k -ValueName RestrictDriverInstallationToAdministrators -Type DWord -Value 1
Get-GPRegistryValue -Name 'Workstation Printers' -Key $k | Format-Table ValueName, Type, Value -AutoSize

The read-back lists seven values in the GPO:

ValueName                                    Type          Value
---------                                    ----          -----
Restricted                                  DWord              1
TrustedServers                              DWord              1
ServerList                                 String print01.hq.lan
InForest                                    DWord              0
NoWarningNoElevationOnInstall               DWord              0
UpdatePromptSettings                        DWord              0
RestrictDriverInstallationToAdministrators  DWord              1

The GUI path gives the same result. Edit the GPO and go to Computer Configuration, Policies, Administrative Templates, Printers. On Server 2025 that node holds 45 settings, and Point and Print Restrictions now reads Enabled:

Group Policy Management Editor Printers node on Windows Server 2025 with Point and Print Restrictions shown as Enabled

Opening the policy shows how the registry values above map onto the dialog:

Point and Print Restrictions policy enabled on Windows Server 2025 with print01.hq.lan as the only allowed server and elevation prompts for driver installs
  1. 1Enabled
  2. 2Users can only point and print to these servers
  3. 3Server list
  4. 4When installing drivers for a new connection
  5. 5When updating drivers for an existing connection

Each mark on the dialog corresponds to one of the values set above:

  1. Enabled turns the restriction on.
  2. Users can only point and print to these servers is ticked (Restricted and TrustedServers).
  3. The Server list field holds print01.hq.lan (ServerList).
  4. When installing drivers for a new connection is set to Show warning and elevation prompt.
  5. When updating drivers for an existing connection gets the same choice.

Read the policy’s help text closely: “If a compatible print driver is not available on the client, no connection will be made.” That sentence describes a world before version 4 drivers. What our client actually did is the next section.

What happened when a standard user connected

The connection succeeded with no prompt, even though the client had no PCL6 driver and the policy restricts driver installs to administrators. brian, a plain domain user, connected to the share from PowerShell:

Add-Printer -ConnectionName '\\print01.hq.lan\Floor2-Laser'

It finished in 13 seconds, and the driver column explains why nothing was blocked:

Name                                Type DriverName
----                                ---- ----------
Microsoft Print to PDF             Local Microsoft Print To PDF
\\print01.hq.lan\Floor2-Laser Connection Microsoft enhanced Point and Print driver

Windows 11 did not download the server’s driver at all. It bound the connection to the Microsoft enhanced Point and Print driver, a version 4 driver that ships with Windows, so there was no third-party code to install and nothing for the restriction to stop. The rendering moves to the server instead, and the PrintService Operational log on PRINT01 shows it. We ran the wevtutil line to make sure the log was enabled, then read it after brian printed:

wevtutil sl Microsoft-Windows-PrintService/Operational /e:true
Get-WinEvent -LogName 'Microsoft-Windows-PrintService/Operational' -MaxEvents 15 | Where-Object { $_.Id -in 842,307 }

Two events describe brian’s job:

307 Document 2, Print Document owned by brian on CLIENT01 was printed on Floor2-Laser through port IP_10.0.1.60. Size in bytes: 57173. Pages printed: 1. No user action is required.
842 The print job 2 was sent through the print processor MS_XPS_PROC on printer Floor2-Laser, driver Microsoft PCL6 Class Driver, in the isolation mode 0 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x0.

Read them together and the mechanism is clear. The client spooled a 57,173-byte XPS document, the server’s XPS print processor rendered it with the PCL6 class driver, and our stand-in printer received an 18,983-byte PCL XL job, the same format as the test page printed on the server itself. Isolation mode 0 means the driver ran inside the spooler process itself rather than in a sandbox.

We then tried the obvious fix for “the client doesn’t have the real driver”: an administrator installed the PostScript class driver on CLIENT01 with Add-PrinterDriver -Name 'Microsoft PS Class Driver', which took 2 seconds, and brian connected to Floor3-Plotter. The connection still came up on the Microsoft enhanced Point and Print driver. So with Microsoft’s version 4 class drivers on the server, pre-staging the same driver on clients changed nothing in our test, and every job is rendered on the print server.

Server-side rendering moves that work onto PRINT01, so the print server is where a busy fleet’s load lands. We did not measure rendering cost itself, but we did see how a starved server behaves: brian’s first job sat in the server queue as “Printing, Retained” with a size of 0 while Defender (MsMpEng) held the 2 vCPU server near 85%, and it reached the printer about 20 minutes later. Partway through the lab we added a Defender exclusion for the spool folder with Add-MpPreference to keep the VM responsive; weigh that against your own security policy rather than copying it.

Where this model breaks down

Our setup stays clean because every queue uses a Microsoft class driver. The assumptions behind it stop holding in a few places, and each one is worth checking against your own fleet before you copy the design:

  • Vendor version 3 drivers: a queue on a classic vendor driver needs that driver on each client, and KB5005652 means only an administrator can install it through Point and Print. We did not test a vendor driver here, so plan to push it with your software deployment tool instead of relying on the connection.
  • Server names: our server list held only print01.hq.lan, and the GPO’s \\PRINT01 connection still worked because no driver had to be downloaded. We did not test a driver download against a name missing from the list, so if you use vendor drivers, list both print01.hq.lan and PRINT01 and test one PC before rolling out.
  • Rendering load: with the enhanced Point and Print driver, the server renders every page. We only printed single pages, so size a busy print server from your own job volume rather than from our 2 vCPU lab.
  • Non-domain networks: the Restrictive firewall rules only open the Domain profile, so laptops on a Private network or a misdetected server profile lose printing until you open the matching rules.

None of these is a reason to go back to the old habit of setting RestrictDriverInstallationToAdministrators to 0 so users can install drivers again. That value reopens the exact path PrintNightmare used. The better mental model for a 2026 print server is that the GPO decides which queue a PC sees, the server owns the driver and the rendering, and the client only needs Windows’ own driver. If you’re building out the rest of the domain around it, our WSUS on Windows Server 2025 guide keeps the print server’s own updates under your control, and the Windows Server administration books we recommend cover printing and Group Policy in more depth.

Keep reading

Create a Bootable Windows 11 USB and Install Windows 11 Windows Create a Bootable Windows 11 USB and Install Windows 11 Set Up a Samba Share on Windows 11 and Access It from Linux Networking Set Up a Samba Share on Windows 11 and Access It from Linux Create Disk Partitions in Windows Using diskpart Windows Create Disk Partitions in Windows Using diskpart Windows LAPS Setup with Group Policy on Windows Server 2025 Security Windows LAPS Setup with Group Policy on Windows Server 2025 Windows Run Commands Cheat Sheet: .msc, .cpl, ms-settings (PDF) Cheat Sheets Windows Run Commands Cheat Sheet: .msc, .cpl, ms-settings (PDF) Install and Use winget on Windows 11 and Windows Server 2025 Windows Install and Use winget on Windows 11 and Windows Server 2025

Leave a Comment

Press ESC to close