If you just need the logger and not the other most excellent features then the Print Logger should work. You need to enable logging on your print server first, then it gets written to the Event Log. I would add that if you only want to see what was printed under 2k8R2 you should filter by the event ID Windows SP2 ver 6.
You can still see the logs if you've enabled them as previously stated, but they show up in the "System" log in the Windows Logs folder. Likely too late to help you, but maybe someone else will find it useful as I would have about 10 minutes ago!
I already did that and i found the logs. But the logs shows the Ip but i actually want the host name. Please help if possible.
If you do not obtain the hostname for the machine, get this working and the spooler should resolve back to the same source.
Below command works on server It queries windows event viewer for event id and extracts the information and saves it to printerjobs. You may need to adjust the properties. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads.
Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. This is a bit of a long shot, however, someone's printed a huge amount and not claimed it, so, we wanted to see who's responsible, without asking a few obvious suspects!
I had a look around on the server and nothing jumped out - I'm guessing this kind of functionality would require configuration and perhaps third party software?
The domain has around 60 users, printing is not typically high volume. Monday, October 19, PM. Hi, Thanks for the post. Unfortunately, Windows Server does not provide this kind of function to monitor the print jobs with these information. It should be a lot of third party program regarding the print job monitoring. Hope this helps. Tuesday, October 20, AM. By default the UI opens in user context so you cannot modify these.
Alan Morris Windows Printing Team. Wednesday, February 6, PM. Thanks for the clarification Miles, that's a shame, but at least I didn't spend hours trying to figure out where it was!
Our community of experts have been thoroughly vetted for their expertise and industry experience. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange. All rights reserved. Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! On Server I could right click in the Printers window and get into Server Properties for the print server.
Here I could check a box to log the print spooler events so that all print jobs are logged. Where is this in Server R2? Select "Properties" from the menu and verify that the "Log size" is correctly set to "Overwrite events as needed". Also verify that the "Maximum log size" is sufficiently big.
As such the following requirements exist: 1. You can have the EventSentry agent automatically enable print tracking when the service starts by selecting "Enable information events in print spooler" from the Print Server Properties. The application event log "Log Size" needs to be configured to "Overwrite events as needed", it also recommended to specify a size of at least kb.
0コメント