Free script parses event logs and compiles client printer autocreation errors

Everyone knows that one of the challenges of Citrix Presentation Server is that autocreated client printers sometimes don't autocreate. When this happens (or doesn't happen?)

Everyone knows that one of the challenges of Citrix Presentation Server is that autocreated client printers sometimes don't autocreate. When this happens (or doesn't happen?), the most likely cause is a printer driver mismatch between the client and the server. Whenever the Presentation Server tries but fails to autocreate an ICA client printer, it writes an event to the Application Event Log.

Robert Iutzwig has created this straightforward script that connects to your servers one-by-one and scans their application logs searching for 1103, 1104, 1106, and 1107 printer management errors. It then outputs this list of printer drivers to a text file. It also creates a second text file that lists each of the errors encountered on each server so you can see which drivers are causing the most problems.

To use it, you'll find two files in the attached ZIP archive. First you need to edit servers.txt so that it contains a list of all the servers you want to check. Then simply run CPS4ELCrawler.vbs with admin rights from one of your servers.

This script was built for Windows Server 2003 and Citrix Presentation Server 4 environments.


PrintLogCrawler.zip

Join the conversation

10 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

This is helpful!
Cancel
A very nice script indeed. looks a bit like the application that Douglas Brown created but way less advanced :)
I will crosspost it on datacrash.
Cancel
I see it's designed for W2K3 but has anyone tested it with W2K servers?
Cancel
I think it will work on windows 2000 environment simply because the script browses your security logs and reports the events back in a txt file. This works the same on 2000 as on 2003.
Cancel
I have not been able to get the script to run on 2k box.

what is the correct syntax used in server.txt file ?

I have tried \\servername and just servername


no joy! just outputs blank evtlogquery.txt & evtlogqueryfinal.txt

The user account I am using can manually access each event viewer on the citrix servers and has permissions to the "Application" event..



ORIGINAL: mutsje

I think it will work on windows 2000 environment simply because the script browses your security logs and reports the events back in a txt file. This works the same on 2000 as on 2003.
Cancel
Well I tested this fine on 2k3 boxes, all the win2k boxes failed.
 
Cancel
Thanks for the script.  I am a little unsure about the content of evtlogqueryfinal.txt.  When I look at it therer are two sections of printers.  The first is about 104 printers and the second is about 500 lines.  Is the first section the ones that are showing up most often and the second is just the total?
 
 
Thanks for the help,
 
Keith Morgan
Cancel
Evtlogquery.txt lists every 1103, 1104, 1106, and 1107 event log entry encountered for each server specified in servers.txt.  Evtlogqueryfinal.txt is a summary of Evtlogquery.txt (listing only unique printers that did not autocreate properly for each server specified in servers.txt).
Cancel
It was not written for Windows 2000.  It was written specifically for Windows 2003 and Citrix Presentation Server 4.
Cancel

I have a download not found  

Thanks for the help

Xavier

 

Cancel

-ADS BY GOOGLE

SearchVirtualDesktop

SearchEnterpriseDesktop

SearchServerVirtualization

SearchVMware

Close