Print Policy Errors

Question

I am getting a lot of these errors on our iPrint policies.
Unable to get the user deamon while enforcing printer policy. Printer Policy may only be partially enforced.
Full Message:
POLICYHANDLERS.PrinterPolicy.UserDeamonNotFound{}
Additional Information:
Failed to set default
Severity: Error
Date: August 30, 2010 9:00:16 AM
Acknowledged Date: None
Source: /Devices/Workstations/KHS/Area109/khs1086-01
Message ID: POLICYHANDLERS.PrinterPolicy.UserDeamonNotFound
Probable Cause URL: None
Log ID: 456139d4ce4d0afae8073ff92174ef24
Related Objects: None
and
POLICYHANDLERS.CommonClasses.HandlerTimedOut{print er policy}
Full Message:
POLICYHANDLERS.CommonClasses.HandlerTimedOut{print er policy}
Additional Information:
None
Severity: Error
Date: August 27, 2010 11:44:28 AM
Acknowledged Date: None
Source: /Devices/Workstations/KHS/Area109/khs1088-01
Message ID: POLICYHANDLERS.CommonClasses.HandlerTimedOut
Probable Cause URL: None
Log ID: c815a78d7eb00c565af52060a8b8af26
Related Objects: /Policies/Printer Policies/KHS/PRN-KHS-Area109
Can anybody shed some light on these errors. Especially the User daemon not found error.
We are running ZCM 10.3.1. Clients are WinXP SP3, most of them having the ZCM 10.3.0 agent on them.
Thanks!

Answer 1

I have three labs on the 2nd floor. Students need to be able to print to all the printers in each lab just to be flexible in case there is a printer problem. However, each lab required that its printer be the default. So yes I created two printer policies for each printer that needed to be a default printer for one of the labs. But I'm not having nearly the amount of difficulty with getting them to work.
I believe there is a setting on the printer policy that will remove all other printers except for the ones delivered from ZEN. So that might be an option for.
I was frustrated, at first, that I couldn't have more than one printer per policy at times, but my current work around is really not so bad.
I end up with 7 printer policies to handle the 4 printers in three labs. However, because they are all single printer policies, it is pretty obvious exactly what is being assigned without having to drill down into the policy itself. It makes it really simple to see what the printer setup is then for the dynamic groups we use for the labs or for an individual workstation. So it has actually grown on me quite a bit. Here is how mine are laid out for just this snippet of our environment. Most of the other labs only have one printer to deal with so this is really the only mildly complex setup.
Lab 200 - Printer200 (default), Printer210, Printer211, Printer211color
Lab 210 - Printer210 (default), Printer200, Printer211, Printer211color
Lab 211 - Printer 211 (default), Printer200, Printer210, Printer211color
It is going to get a lot more complicated when we start rolling through faculty and staff, but I think I'm going to take the same approach. Every printer gets at least one printer policy object. If a printer needs to be a default printer for someone then it will get a new printer policy that is set to make it the default.
As I think through our printing environment, this approach may actually use less printer policies than setting up a printer policy with multiple printers for every situation. There will be far more re-use of the individual policies than there would be for multiple printer policies. I think at the very least it would be a wash between the two options.