Results 1 to 3 of 3

Thread: Deployed printers from other locations still mapping

  1. #1
    PreviousPoster is offline 100+ Helpful Posts! 50+ Helpful Posts
    Join Date
    Dec 1969
    Posts
    1,254

    Default

    I have several locations that I have deployed network printers through GP to the machines through the startup script pushprinterconnections.exe. At times the machines are moved between stores as demand dictates so having the printers mapped automatically is essential.

    I have 4 machines that were moved from one location to another and I am experiencing all of the printers from both locations are still mapping to the machines. I have verified with GP Result in the Group Policy MGMT Tool that only the correct policy has been applied to the machines. I have removed the machine from the domain, changed the name, restarted the machine, logged in as a local admin and the printers were still mapping. I even removed the machine account from AD, renamed the machine, deleted the printers, restarted and the printers came back.

    I am not sure if there is a specific script or setting I need to change to make the printers from the original location stop being mapped. I have changed the permissions on the printers at the original location to deny access to these specific machines, yet I have experienced the same results.

    Thank you for your help.

    Brian Young

  2. #2
    PreviousPoster is offline 100+ Helpful Posts! 50+ Helpful Posts
    Join Date
    Dec 1969
    Posts
    1,254

    Default

    Hi

    Have you managed to find a resolution to the problem with pushed printers not being deleted?

    Regards
    Mike

  3. #3
    PreviousPoster is offline 100+ Helpful Posts! 50+ Helpful Posts
    Join Date
    Dec 1969
    Posts
    1,254

    Default

    Mike,

    Here is what I found as a workable solution. I ran cleanspl.exe in the windows resource kit to remove ALL printers and their drivers from the machines. Once this was done the printers using pushprinterconnections.exe worked properly. Keep in mind that when you run cleanspl.exe on a machine it removes ALL printers, including locally attached ones. They will have to be reinstalled afterwards if they need to still be used by the end users.

    I have also started using a rundll call to map the printers by user or machine and this method seems to be working much better and with a greater success rate than pushprinterconnections.exe. Here is a website that I used as a reference to build my script strings to map printers.

    http://www.robvanderwoude.com/2kprintcontrol.html

    Hope this helps.

    Brian

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Search Engine Friendly URLs by vBSEO