+ Post New Thread
Results 1 to 12 of 12
Windows Server 2000/2003 Thread, pushprinterconnections.exe in Technical; Hi. I have a problem with removing deployed printers from an XP machine using group policy on 2008 server with ...
  1. #1

    Join Date
    Sep 2008
    Location
    Birmingham
    Posts
    82
    Thank Post
    31
    Thanked 8 Times in 7 Posts
    Rep Power
    13

    pushprinterconnections.exe

    Hi.

    I have a problem with removing deployed printers from an XP machine using group policy on 2008 server with the pushprinterconnections utility.
    Apparently, using the Server 2003 R2 version of it should fix my problem, according to the technet MS forums.

    So could someone please send it me?

    Its located in %windir%\system32

    Thanks in advance!

    Adam

  2. #2

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Interesting - I can send you a copy later this evening if you like, unless someone beats me to it! What problems are you having deploying to XP machines?

  3. #3

    Join Date
    Sep 2008
    Location
    Birmingham
    Posts
    82
    Thank Post
    31
    Thanked 8 Times in 7 Posts
    Rep Power
    13
    The printers deploy fine. Then when I remove the printers from the policy, update it and restart a couple times, the printers are still there. Then if you delete them manually and restart the computer they come back again.

    According to this topic it could be down to the newer version of the utility.

  4. #4

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    That is a little strange as you have to ask what exactly is creating the printers without pushprinterconnections.exe running at logon/startup?

    I will send you the file later as promised

  5. Thanks to Michael from:

    AdamK (28th April 2009)

  6. #5

    Join Date
    Aug 2007
    Location
    Deal, Kent
    Posts
    343
    Thank Post
    12
    Thanked 73 Times in 51 Posts
    Rep Power
    27
    What i found with push printer connections is that if you dont remove the printer from the deployed printers list before deleting the printer in the printer list, it will dstill deploy a blank printer in accordance to the policy (no drivers, no settings, doesnt print) that you cannot delete even as admin.

    Simon

    Edit - solution was to create a printer of the same name (even if its not same drivers etc..) then click "Deploy with Group Policy" and remove the printer from the list instead of adding the fake one.

    edit2 - pm me your email addy and ill send you it zipped now.
    Last edited by Psymon; 28th April 2009 at 02:44 PM. Reason: my solution

  7. Thanks to Psymon from:

    AdamK (28th April 2009)

  8. #6
    Netman's Avatar
    Join Date
    Jul 2005
    Location
    56.343515, -2.804118
    Posts
    911
    Thank Post
    367
    Thanked 190 Times in 143 Posts
    Rep Power
    54
    What about using 'User Config - Prefs - Control Panel Settings - Printers' to deploy them instead. It works really well and you can choose to set as default as well. Only thing is you need the client side extensions on the clients, but that's easy if you have WSUS. Particularly nice is the item-level targeting in it. If you want more info, just ask... I could probably run off a quick how-to as I've just changed over to this last week...

  9. Thanks to Netman from:

    AdamK (28th April 2009)

  10. #7

    Join Date
    Sep 2008
    Location
    Birmingham
    Posts
    82
    Thank Post
    31
    Thanked 8 Times in 7 Posts
    Rep Power
    13
    Quote Originally Posted by Netman View Post
    What about using 'User Config - Prefs - Control Panel Settings - Printers' to deploy them instead. It works really well and you can choose to set as default as well. Only thing is you need the client side extensions on the clients, but that's easy if you have WSUS. Particularly nice is the item-level targeting in it. If you want more info, just ask... I could probably run off a quick how-to as I've just changed over to this last week...
    I was trying that originally, but the printers didn't get deployed. Then I found a post about using the pushprinterconnections.exe utility, so I followed the instructions for that and it worked straight off with several printers.

    Then I go to remove the printers and do it properly, but all the removed printers just come back every time I log back on or restart. Why can't things just work for a change!

    Adam

  11. #8

    DaveP's Avatar
    Join Date
    Oct 2006
    Location
    Can't talk now: The mother-ship is calling!
    Posts
    8,783
    Thank Post
    351
    Thanked 1,274 Times in 870 Posts
    Blog Entries
    4
    Rep Power
    1126
    Hi,

    I am using KIX to deploy printers to students and staff at logon. I have an issue that I have not been able to resolve. The issue is that the network insists on adding a printer for all users which is not the printer I want for that room/user. I have put a command at the top of the KIX script for all users which deletes the 'random' printer. Now it adds another printer instead.

    Scenario:

    Staff/student user logs on in Room 1. They should get the Room 1 printer [which they do] but they also get the Room 96 printer. KIX for all users now deletes the Room 96 printer. Now when any user logs on in Room 1 they get the Room 40 printer. Add a command for all users to delete the Room 40 printer [which now may or may not work] and they then get another network printer [Room 2 perhaps] They DO get the printer I want them to get in the room they login but they also get A-N-Other printer I do not want them to be able to print to.

    How can I prevent this?

    What is happening?

    Help?

    TIA.

  12. #9

    Join Date
    Sep 2008
    Location
    Birmingham
    Posts
    82
    Thank Post
    31
    Thanked 8 Times in 7 Posts
    Rep Power
    13
    Hi,

    Thanks for everyone's help.

    After a good nights sleep and a bit more research I found that the cause of the problem was that when the printers are removed from group policy it wasn't updating the registry on the assigned machines due to an error. Apparently there is a hotfix on the MS website, but they only seem to have one for Vista and Server 2008, not XP.

    So I came up with my own solution. I modified a vbscript on the technet website to to delete all the registry entries for the printers:

    Code:
    On Error Resume Next
    
    Const HKEY_LOCAL_MACHINE = &H80000002
    
    strComputer = "."
    strKeyPath = "SYSTEM\CurrentControlSet\Control\Print\Connections"
    
    Set objRegistry = GetObject("winmgmts:\\" & _
        strComputer & "\root\default:StdRegProv")
    
    DeleteSubkeys HKEY_LOCAL_MACHINE, strKeypath
    
    Sub DeleteSubkeys(HKEY_LOCAL_MACHINE, strKeyPath)
        objRegistry.EnumKey HKEY_LOCAL_MACHINE, strKeyPath, arrSubkeys
    
        If IsArray(arrSubkeys) Then
            For Each strSubkey In arrSubkeys
                DeleteSubkeys HKEY_LOCAL_MACHINE, strKeyPath & "\" & strSubkey
            Next
        End If
    
        objRegistry.DeleteKey HKEY_LOCAL_MACHINE, strKeyPath
    End Sub
    I then added the script to the group policy and set it to run before the push printers exe.

    I've tested it deploying the printer and that works fine. I've also removed the printer and the script does the job of removing it.

    I'm not sure if that was the best solution to my problem, but at the end of the day, it works, so I'm happy again


    Adam

  13. Thanks to AdamK from:

    ICT_GUY (23rd June 2009)

  14. #10
    ICT_GUY's Avatar
    Join Date
    Feb 2007
    Location
    Weymouth
    Posts
    2,261
    Thank Post
    646
    Thanked 283 Times in 204 Posts
    Rep Power
    104
    Wow, that actually worked, a constant head ache gone at last.

    W00HOO!

  15. #11
    BryanDavidWilliams's Avatar
    Join Date
    Jan 2010
    Location
    Arizona
    Posts
    13
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    I am still having no luck with this even. I put the VBS script in right before pushprinterconnections.exe I put a question in with MS. This is driving me crazy. I was trying to make our printer deployment more compatible with Windows 7 and this is the headache I get.. lol..

  16. #12

    Join Date
    Aug 2007
    Location
    Deal, Kent
    Posts
    343
    Thank Post
    12
    Thanked 73 Times in 51 Posts
    Rep Power
    27
    Quote Originally Posted by BryanDavidWilliams View Post
    I am still having no luck with this even. I put the VBS script in right before pushprinterconnections.exe I put a question in with MS. This is driving me crazy. I was trying to make our printer deployment more compatible with Windows 7 and this is the headache I get.. lol..
    Pushprinterconnections is only needed for Windows XP, its not needed for Vista / 7.

    You will have better success pushing the printers out with group policy using Windows Print Management console.

    That way you avoid all the scripting.

    The only script we have running is the default printers, everything else is group policy.

    Simon

SHARE:
+ Post New Thread

Similar Threads

  1. DSStore.exe
    By E1uSiV3 in forum Windows
    Replies: 8
    Last Post: 20th July 2013, 03:47 PM
  2. Pushprinterconnections.exe reliant files
    By mrforgetful in forum Windows
    Replies: 16
    Last Post: 26th August 2010, 08:15 PM
  3. Exe files
    By sippo in forum Wireless Networks
    Replies: 22
    Last Post: 29th September 2008, 09:37 AM
  4. Lsass.exe and Lssas.exe
    By ndavies in forum Network and Classroom Management
    Replies: 5
    Last Post: 30th October 2007, 03:19 PM
  5. simsmanualsetup.exe
    By leon in forum MIS Systems
    Replies: 0
    Last Post: 25th April 2007, 08:39 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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