Event id 1111 termservdevices microsoft


















There are no other services being used on this server. We do not have a domain, only a local workgroup. Most printers are installed locally via USB and shared, but we do have some that are network printers but not managed by the server. Those drivers are installed on the client PC's using the printer. Each time the error is generated, it generates 10 errors for various printers installed on cliant PC's XP and Vista on our workgroup. You presumably have Terminal services enabled in Remote Administration mode, and your administrators are using this to log into the server.

The event just says that TS doesn't have the printer drivers installed to enable printer redirection to the TS sessions. Of course, if no-one you know about is logging into your server that's a good time to start worrying In general whenever you try to take RDP of any server it try to map the printers installed in you desktop machine Source , so due to mismatch of the printers its through the error, just follow the below steps to avoid error event ID Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 12 years, 6 months ago.

I am new to this problem and how to fix it, today my Win Server crashed for brief event viewer stated:. Contact the administrator to install the driver before you log in again. You can just disable printer mapping while connecting to the server, use the universial driver or install the requiered device driver on the server. Office Office Exchange Server.

Not an IT pro? SQL Server. Sign in. United States English. If the printer driver installed on the client computer is an OEM driver, and a driver is available from the printer's manufacturer, replace the OEM driver with the driver that is available from the printer manufacturer. Important: After you install the printer driver, terminal server clients must log off and then log on to the terminal server before the printer driver changes take effect. To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

Run the printer's Setup program to install the printer driver. Note: If the File menu is not visible, right-click an empty area of the Printers dialog box, and then click Server Properties. You can create or modify an existing custom printer mapping file to define mappings from client-side to server-side drivers on the terminal server. To perform this procedure on the terminal server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data. After you add the new registry values, create or modify the. Follow the format used in the following example:. The left side of the equation is the exact name of the printer driver associated with the client-side print queue that is being redirected to the server. The exact name of the printer driver appears on the General tab, next to Model when you view the printer properties on the client computer.

You can also click the Advanced tab and view the driver name in the Driver list. The right side of the equation is the exact name of the server-side driver equivalent that is installed on the terminal server.

Important: You must restart the Print Spooler service on the terminal server for the changes to take effect.



0コメント

  • 1000 / 1000