Link to home
Start Free TrialLog in
Avatar of mltets
mltetsFlag for United States of America

asked on

Default Printer changes on its own

We have several users that sporadically have issues with their default printers changing on them without them doing anything. We've had some that change after printing an email from someone, printers changing while the person is away for a while, even in other applications they are changed. The default printer is fine at boot but can change anytime during the day. We have tried removing all printers on the computer and the drivers and re-adding them all, running spware scans, and virus scans too. This is happening to Windows 2000 users as well as Windows XP but I would have to say a majority of them are Windows 2000 systems with SP4.

When the printer changes, it doesn't switch to the same printer every time - it bounces around to all of our printers on the network.

Please let me know if there is any more information that is needed and I'll try to get it for you.

Thank you.

Beth Carpenter
ASKER CERTIFIED SOLUTION
Avatar of scrathcyboy
scrathcyboy
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mltets

ASKER

Our network admins are in the process of testing out login scripts for our employees. When an employee logs in, the login script setups most of the network printers but does not set the default printer for everyone. They have remarked out the printer section to see if that helps the users who are having the problems with their default printer changing. Because it doesn't happen on a regular basis, it may take a few days to see if that has helped.
Avatar of mltets

ASKER

It appears that remarking out the printers from our logon script helped with this problem.  Our biggest problem was not when the user would logon to their computer but after they had been working for a while it would all of a sudden change on them. We will consider this a closed issue since we have not had a recurrence of the problem for a couple weeks now.
Good, it probably was a script duplication somewhere.