Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1107 Source: MetaframeEvents

Client printer auto-creation failed.  The driver could not be installed. Possible reasons for the failure: The driver is not in the list of drivers on the server. The driver cannot be located. Driver mapping is incorrect. Client name: <computer> Printer: <printer> Client Printer driver: <printer driver> Server Printer driver: <server printer driver>.
From a newsgroup post: "My printer was working fine when connected to a Win XP machine. Then it was moved to a W2K laptop and the error appeared in my error log. Someone told me to check the wtspurn.ini file in the &systemroot%/system folder to see if there hasn't been a mapping that has changed since the client driver name for Win XP may be different to the W2K one. He also advised me to check that the wtsprnt.inf in %windir%\system32 has the read-only attribute not set. The IMA Service takes settings from the data store and writes to this file. With a read-only attribute set the driver mapping will cease to function".

See the link to "Citrix Support Document ID: CTX105577" and "Citrix Support Document ID: CTX108546" for additional information on this problem.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.