client printer autoconfigure

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Have the latest critical updates changed functionality for terminal services client printer autoconfigure. A problem with users logging in to our terminal servers appeared about two weeks ago. Client's locally attached default printers were not being automatically installed and mapped as they had been previously. The only change to the configuration was the application of serveral critical security packs due to the latest (mydoom) virus.
 
I concur with this issue. Something has been changed but I can't pinpoint
what.
Do you receive a "Device not connected" error?

Jason Kimbrough said:
Have the latest critical updates changed functionality for terminal
services client printer autoconfigure. A problem with users logging in to
our terminal servers appeared about two weeks ago. Client's locally attached
default printers were not being automatically installed and mapped as they
had been previously. The only change to the configuration was the
application of serveral critical security packs due to the latest (mydoom)
virus.
 
Back
Top