| Event Id | 1107 |
| Source | MetaframeEvents |
| Description | 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>. |
| Event Information | Here is an information from news group post: "My printer was working fine when connected to a Win XP machine. Then it got 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 hasnt 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". |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.