Highlighted
Absent Member.
Absent Member.
749 views

Printer Policies

I'm trying to get my Printer Policies to consistently work in ZCC11.2.3,
but I'm not having much luck. I have a basic Printer policy assigned to
a workstation group (we do printers by location here), assigned one
iPrint printer, and then its set to be default.

On the device (windows 7 workstation) I see the following 2 errors
repeated over and over:

Failed to Add iPrint Printer:
POLICYHANDLERS.PrinterPolicy.IPrintPrinterAddFailed

and then

The action printer policy (ID:printer policy) failed due to the reason :
partiallyFailedToEnforcePolicy, however the action is set to continue on
failure.

I haven't been able to find any information about what these each mean.
Or more importantly, how to resolve them.

iPrint is installed already, and works perfectly as any user.

Thanks in advance for any help.

Matt
Labels (2)
0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Re: Printer Policies

I got this when the iPrint client hadn't installed yet. If the iPrint client isn't there then the policy to install the printer will fail. Once we made sure that the iPrint client had installed the printers started working, with a caveat, the policy does not seem to work with Win7x32, only with x64 for some reason. Every Win7x32 that we have has had to have their printers installed manually even though iPrint will install. Also, we used a bundle to install the iPrint client using the correct version of nipp with switches that allowed for an unattended install.

Hope this helps
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Printer Policies

We install iPrint in a bundle as well. And the error keeps coming up each time the policy tries to apply, which appears to be every few hours. Although its interesting that you haven't had luck with Win7x32, that's of course what we're running.

Matt

cbowser814;2282497 wrote:
I got this when the iPrint client hadn't installed yet. If the iPrint client isn't there then the policy to install the printer will fail. Once we made sure that the iPrint client had installed the printers started working, with a caveat, the policy does not seem to work with Win7x32, only with x64 for some reason. Every Win7x32 that we have has had to have their printers installed manually even though iPrint will install. Also, we used a bundle to install the iPrint client using the correct version of nipp with switches that allowed for an unattended install.

Hope this helps
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Printer Policies

Just found some errors. Has anyone seen anything like this before?

c:\NDPS\ippErrs.txt


9/16/2013 - 12:58:24 PM
Module: spoolsv.exe
Trace Info: registry.c, line 5180, thread 00000854
Routine: IppGetInstallInfoFromRegistry - RegOpenKeyEx failed 2
Error: The system cannot find the file specified.


9/16/2013 - 12:58:24 PM
Module: spoolsv.exe
Trace Info: printer.c, line 7471, thread 00000854
Routine: AddPrinterConnection2 - Printer is already installed
Error: The printer has already been installed.

9/16/2013 - 12:59:55 PM
Module: zenuserdaemon.exe
Trace Info: myhttp.c, line 1994, thread 00000628
Routine: HTTPReadResponseHeader - bad HTTP status (301)
Error: HTTP 301 - Moved permanently.

9/16/2013 - 12:59:56 PM
Module: zenuserdaemon.exe
Trace Info: ippmain.c, line 15548, thread 00000628
Routine: GetPrinterInfoWithGoodStatus - Printer has been renamed to this URI (ipp://winn02.winnebagoschools.org/ipp/BWCopiers)
Error: iPrint Client - The printer was renamed.

9/16/2013 - 12:59:57 PM
Module: spoolsv.exe
Trace Info: registry.c, line 5180, thread 00000910
Routine: IppGetInstallInfoFromRegistry - RegOpenKeyEx failed 2
Error: The system cannot find the file specified.


9/16/2013 - 12:59:57 PM
Module: spoolsv.exe
Trace Info: printer.c, line 7471, thread 00000910
Routine: AddPrinterConnection2 - Printer is already installed
Error: The printer has already been installed.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Printer Policies

Making some headway. We have a pretty hacked version of Windows 7 that we're using as a base image. I tried a relatively stock windows 7 image, and only got that message 2 times, then it seems to have worked. I wonder if that's a timing thing with our imaging process.

If I ever find what registry hacks cause trouble, I'll post back here. But I gather its something we're doing that interferes with iPrint Policies.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.