Hi all, I started getting calls about printing failing on a new 2X/RDS server, when i went to check the spooler was stopped- which I found odd- after the 3rd call , i decided to dig a bit deeper- it turns out the printers (from the clients remoting in) were being installed as WSD- further research showed WSD to be a curse; http://aaron-kelley.net/blog/2010/08/wsd-printers-crashing-print-spooler-service-in-windows-7/
http://community.spiceworks.com/topic/393203-wsd-printer-port-seems-to-stop-users-from-being-able-to-print http://social.technet.microsoft.com/Forums/en-US/26ff7f74-12eb-4695-963e-490f6681460e/print-server-role-server-08-r2-hp-wsd-printer-ports http://h30499.www3.hp.com/t5/Printers-LaserJet/WDS-port-wont-quit-over-writing-static-IP/td-p/5592377#.VCSWzBZ50sI Since these printers are on the client end, (their home, remote office etc,,) i have no control to disable WSD from within the printer itself, one article said; "Disable PnP-X IP Bus Enumerator service" If this service is stopped or disabled, presence of NCD devices will not be maintained in PnP. All pnpx based scenarios will stop functioning. I have disabled the service, but yet when someone remotes in with one of these "glorious" HP printers it recreates the printer port as WSD then subsequently crashes the spooler- Is there perhaps a registry key to BLOCK/DISABLE the creation of a WSD port? or any other way maybe via GPO? Thanks
