A remote user have at home a "Brother MFC-8500 USB" multifunction printer. This is the name of the driver on his XP computer. I wanted to install the driver on our W2K3 TS to enable him to print at home. I went to the Brother web site and downloaded the "Add printer wizard" XP driver for this machine, since there was no W2K3 driver available.
Alas, when I added this driver to the Terminal Server, the name was "Brother MFC8500". So when the remote user logged in I had the infamous Event 1111 on the server's event log:
"Driver Brother MFC-8500 USB required for printer Brother MFC-8500 USB is unknown. Contact the administrator to install the driver before you log in again."
The thing is that the driver's names must match exactly for W2K3 to "see" that it is the good driver and load it.
Since it was only a name issue and I knew that the binaries were OK, I opened the OEMMF01A.INF from the extracted driver files and I seached for the "Brother MFC8500" string. I edited it to read "Brother MFC-8500 USB" and I ran the "Add Printer Driver Wizard" again. As expected the name was in the list and it installed OK.
2 comments:
I want to say thanks for this 2½ year old post. It saved me most of the hour I would have spent figuring it out on my own.
Glad it helped.
Post a Comment