I did find that if I right click and remove the printer, then delete this
registry key, the printer does not return upon reboot:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Print\Providers\Client Side Rendering Print
Provider\Servers\main2\Printers\{GUIDXXXXXX-XXX-XXXX-XXXXXXX}
From: [email protected] [mailto:[email protected]] On
Behalf Of Miller Bonnie L.
Sent: Tuesday, November 10, 2015 2:29 PM
To: [email protected]
Subject: RE: [NTSysADM] stop printer creation during startup
It normally would block, unless someone added a no override to the policy. You
wouldn't necessarily notice that unless expanding the Sites object in GPMC.
-Bonnie
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Melvin Backus
Sent: Tuesday, November 10, 2015 10:42 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] stop printer creation during startup
Not really an answer I suppose, but another question which may be meaningful
for the more expert on the list.
I frequently do printer GPOs at the Site level instead of OU, so that anyone in
a remote office gets attached to the printer(s) in that office instead of
whatever their normal location might be. When people move between offices it
makes life easier. Would blocking inheritance still turn that off?
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Mazzaccaro, David
Sent: Tuesday, November 10, 2015 1:33 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] stop printer creation during startup
I moved a test machine and test account into a testing OU, blocked inheritance,
and the printer still gets installed.
Also, if I right click on the printer and remove it, it goes away, but it
returns with a restart of the spooler service.
Hopefully this new info helps point me in the right direction.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Mazzaccaro, David
Sent: Tuesday, November 3, 2015 4:49 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] stop printer creation during startup
Excellent suggestion, thank you.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Tuesday, November 3, 2015 4:17 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] stop printer creation during startup
To rule out GPO, can you move a test user and computer object to an OU with
Block Inheritance and see if the printer still gets mapped?
Sent from my BlackBerry(r) smartphone on O2
________________________________
From: "Mazzaccaro, David"
<[email protected]<mailto:[email protected]>>
Sender: <[email protected]<mailto:[email protected]>>
Date: Tue, 3 Nov 2015 21:09:21 +0000
To:
[email protected]<[email protected]<mailto:[email protected]%[email protected]>>
ReplyTo: <[email protected]<mailto:[email protected]>>
Subject: RE: [NTSysADM] stop printer creation during startup
I went through the various GPOs that are getting applied, but no obvious
references to this printer in any of them.
RSOP does show a login.bat file being applied. Nothing in there w/ the share
name of the printer either.
The batch file does call a WSF file, and I checked in there, but again no
reference to this particular printer (many others though).
Still digging...
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Tuesday, November 3, 2015 3:49 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] stop printer creation during startup
What does gpresult show being applied?
Sent from my BlackBerry(r) smartphone on O2
________________________________
From: "Mazzaccaro, David"
<[email protected]<mailto:[email protected]>>
Sender: <[email protected]<mailto:[email protected]>>
Date: Tue, 3 Nov 2015 20:32:24 +0000
To: NT System Admin Issues
([email protected])<[email protected]<mailto:[email protected])%[email protected]>>
ReplyTo: <[email protected]<mailto:[email protected]>>
Subject: [NTSysADM] stop printer creation during startup
Hi all,
I have a situation where a network printer is getting added to every computer
in the company at boot up.
I am trying to figure out how this printer continues to get installed, and stop
this from happening.
Here's what I've narrowed it down to so far...
remove printer, reboot, log into LAN, printer reappears - suggests GPO, but I
can't find any GPO even referencing this printer.
remove printer, reboot, log into Laptop offline, printer reappears - Offline,
meaning not connected to the LAN at all (wired or wireless)
remove printer, *log off*, log into laptop offline, printer does not appear
reboot, log into laptop offline, printer reappears - after a reboot, the
printer comes back.
Windows 8.1
2008R2 domain
Any ideas?
Thanks in advance!
