Score:0

can't delete printers on Windows Server 2022

in flag

I have this very weird and hard to solve problem on my domain controller (Windows Server 2022).

I have 3 Windows Servers in my domain: Server1 is a member server which acts only a print server (printers are installed on this server and shared).

Server2 is the (only) domain controller. Printers shared on Server1 are deployed to users via a user-GPO. In the past these printers got installed on the DC itself but now I have denied this GPO to deploy printers on the DC/user that logs on to this DC. Server3: just a file server (member server)

The weird thing is: the network printers that were once installed through GPO, I cannot delete them permanently ! When I deleted these printers from Server2 (right click-remove device) they got deleted but after a reboot, they show up again.

I don't understand why they're coming back as an installed printer because:

  • GPO is excluded now. The proof is, after deleting the printers (Devices & Printers is empty), I run GPUPDATE /FORCE and they do not show up again! It's only after a reboot that the printers come back.
  • Proof number 2 is more convincing: I deleted the printers (Devices & Printers is empty), I disable all network connectivity for this Server2 and reboot the server2 via the console. After reboot, the printers are back while still not having network connectivity at all.

What have I done already ?

  1. cleaned up the Device Manager for old hidden printers
  2. emptied the following key in the registry: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SWD\PRINTENUM
  3. emptied the following key in the registry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers
  4. sfc /scannow
  5. dism /online /cleanup-image /restorehealth

Some facts I noticed:

  • When I log on with another admin account on this Server2, the printers are also installed again automatically.

  • When I go into Powershell and launch: GET-PRINTER, the list is empty while they are shown in DEVICES & PRINTERS !!! of course I cannot delete them from powershell also then.

  • I also notice that I cannot install network printers anymore manually on this Server2 ... I can browse to the shared printer but when I try to connect to it, it says: Connecting to on Server1 ... nothing more (no timeout or error)

  • when logging on with the same admin-account on Server3, everything is OK (no printers that are installed automatically)

  • Server2 is a brand new server just setup last week.

I really have not more idea why is this and where this is coming from. I even searched the whole registry for these printer names and deleted everything I found with these names but still those printers show up again as installed.

Many thanks in advance for helping me with this.

Marc

Score:0
cn flag

Following the fact;

When I log on with another admin account on this Server2, the printers are also installed again automatically.

On the DC Server2 validate in gpedit.msc as even if no local user exist local GPO can be created. I dont know why someone would do that, but just in case validate.

GPO is excluded now. The proof is, after deleting the printers (Devices & Printers is empty), I run GPUPDATE /FORCE and they do not show up again! It's only after a reboot that the printers come back.

This GPO below will cause that effect, in the Computer section; It add a network map to a printer to the computer. Everyone that log will see them. It's rare you push printer by there, but it make the symptom you see, that the printqueue get re-added at startup.

enter image description here

If your domain is old, make sure too that no script are pushed that add a printer connection. Via a GPO or via the User account script's setting.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.