Forum Discussion
MS Print servers
- Feb 05, 2014
Here's the new link to the guide for creating the WMI monitor. As I recall it was pretty straightforward. I'm even using the same interval and timeout. Looking at my monitor properties, the only thing I see that is different is my alias service port is 3389 and the external program path is /usr/bin/monitors. Also, you'll need to enable remote WMI requests on the win2k8 boxes if not already enabled.
Monitoring WMI Services from Big-IP
Something interesting I found yesterday while trying to get our Optio app printing to the 2008 print server VS, the print jobs were erroring out with an error code 5. This is indicative of a permissions issue. Per Optio, the fix for 2003 server is to change local security policy to allow everyone permissions to apply to anonymous as the jobs are created by the system account on the Optio server and are treated as anonymous by the remote print server. This fix wasn't working in 2008 and Optio support was at a loss. After a bit of digging I found that you must also edit the "named pipes that can be accessed anonymously" local security policy to include SPOOLSS. After making this change, the jobs started printing successfully.
I hope someone may find this info useful as I wasn't finding much myself while trying to figure this out.
Chris
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com