[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 326
  • Last Modified:

64-bit drivers loaded on 32-bit server - printers disappearing, can't be found

I have loaded my 64-bit print drivers onto my Windows 2003 32-bit print servers, using Print Management on a 64-bit machine.  I have troubleshooted issues with the print drivers being the same name, same version and loading universal/global print drivers when necessary.  It was a huge pain and took me a month of troubleshooting them all.   I had everything working just fine on all printers (14 remote sites) and tested without issues.  I have deployed my new 64-bit Windows 7 machines and things were working fine.  The printers were being loaded with a login script or manually by going to server and clicking on them to auto-load.  

Now, however, my users on the 64-bit machines are having intermittent issues with printers disappearing, unable to connect to them, or getting a message that the printer(s) are not installed on their machines (they were using them previously without issues).  If a user reboots, most times the problem goes away, but I can't have them reboot every time it happens.  Sometimes clicked on the installed printers on server manually from 64-bit machines, it will let the user logged in install, sometimes it won't.

I read something about DNS entries on shared printers may be set up wrong but I cannot find where those are set - I would assume somewhere in printer install?  Also, parent company removed local admin rights for users on their desktops via group policy (removed All Users AD group from local admin group), which shouldn't have affected the printers that were already installed?  I am baffled at this point.
0
rtgarr
Asked:
rtgarr
1 Solution
 
Brian BIndependant Technology ProfessionalCommented:
Any indication in the system event logs as to what is happening?

The DNS entries would be in two places. One, the printer has the correct DNS settings and also that a manual DNS entry usually has to be made in DNS for the printer's name.

Also if parent company has control over the AD policies, is there any chance they could have done something to the printer settings? For that matter it might be easier to push the printer from policy, but you want to save that argument for another day.
0
 
rtgarrAuthor Commented:
Thank you.  I will check all this out a little later today, once my new emergency has subsided :) !  
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now