none
Deploying Printers via GPO to windows 8.1 RRS feed

  • Question

  • When I attempted to deploy a printer connection on Win 8.1 x64 via "Deploy with Group Policy"  as outlined here https://technet.microsoft.com/en-us/library/cc731292.aspx (the directions are for 7 but the process is still the same), the printers would not deploy.  GPresult logs gave this error for the gpo that was used to push the printer: "Filtering: Not Applied (Empty)".  To get the gpo to apply and the printer to deploy,  I need to add a startup script to run pushprinterconnections.exe.  My understanding was that pushprinterconnections was only required for xp and 2003.  I have seen several articles, including this technet one https://technet.microsoft.com/en-us/library/cc772505(v=ws.10).aspx that state that it is required for Operating systems prior to vista.  This article https://technet.microsoft.com/en-us/library/hh875629.aspx on pushprinterconnections states that it applies to newer operating systems (7, 8, etc).  So which one is it?
    Saturday, February 20, 2016 7:07 AM

Answers

  • I don't think my question was understood or maybe I didn't reiterate it clearly enough.  The problem I was seeing was that when only a Deployed printer setting was configured in a GPO, it would show up as filtered out Empty until I included the pushprinter connections exe.  I tested with a new GPO and do not see this problem any more so I am guessing it was due to some corruption with the GPO etc.  The definitive answer is no pushprinterconnections is not needed after xp and can be removed as it is a login script that could potentially slow down logins.
    • Marked as answer by Misha Rudiy Tuesday, March 1, 2016 9:12 PM
    Tuesday, March 1, 2016 9:12 PM

All replies

  • pushprinterconnections.exe is intended for pre-Vista OS's, because those older OS's didn't have the inbuilt capability.

    Vista and later OS's already have the capability inbuilt. (so, the documentation reference you found, is misleading/inaccurate/incomplete on that point)

    "Filtering: Not Applied (Empty)", means that the for that particular GPO, there were no settings resolved as applicable, for that context.

    For specifics, you need to look at that section of the gpresult/RSoP, and consider the context (either User Configuration, or, Computer Configuration).
    e.g. if the section of gpresult/RSoP refers to a GPO named "deploymyprinters", and the context is "computer", and status is (Empty), you have not configured any settings in that "computer" context of that GPO. So, in this example I would examine the "user" context section and see if the "Filtering" status appears there or not.
    Check to see if listed in gpresult /h somefilename.html
    (I find this easier than other gpresult outputs, as a starting point)
    You should see "Applied GPOs" and also "Denied GPOs"

    When you followed the guide, did you select to apply the policy to "users" or "computers"?
    Did you then link the GPO to the domain root? Or to a site? Or to an OU containing user accounts? Or to an OU containing computer accounts?

    Also, note that when using gpresult at the client computer, you may need to use CMD elevated (run as admin) to be able to get the complete gpresult output (i.e. both user configuration *and* computer configuration) - by default, CMD will not be elevated for a standard user and so this means only the user configuration results are shown.
    Thus, if you created computer configuration settings but the standard user not-elevated is not able to display the computer configuration results, this would display as (Empty).

    Here is a mockup/example, where a standard user (not admin / not elevated), does not display the "COMPUTER SETTINGS" (Computer Configuration)

    RSOP data for contoso\don on WIN7PC-1 : Logging Mode
     ---------------------------------------------------------
    OS Configuration: Member Workstation
     OS Version: 6.1.7601
     Site Name: N/A
     Roaming Profile: N/A
     Local Profile: C:\Users\don
     Connected over a slow link?: No

    USER SETTINGS
     --------------
     CN=don,OU=Employees,DC=contoso,DC=com
     Last time Group Policy was applied: 2/19/2016 at 9:56:06 AM
     Group Policy was applied from: DC01.contoso.com
     Group Policy slow link threshold: 500 kbps
     Domain Name: contoso
     Domain Type: Windows 2008
     Applied Group Policy Objects
     -----------------------------
     Default Domain Policy
     deploymyprinters
     The following GPOs were not applied because they were filtered out
     -------------------------------------------------------------------
     deploymyprinters
     Filtering: Not Applied (Empty)
     ....etc

    Some examples/references

    https://technet.microsoft.com/en-us/library/cc779631(v=ws.10).aspx

    https://community.spiceworks.com/topic/519158-gpo-and-rsop-the-dreaded-reason-denied-empty

    https://technet.microsoft.com/en-us/library/cc787386(v=ws.10).aspx

    You can also seek further expert experience and advice in the dedicated GP forum:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverGP


    Don [doesn't work for MSFT, and they're probably glad about that ;]


    Saturday, February 20, 2016 10:17 AM
  • Hi,
    Would you mind letting me know the result of the suggestions? If you need further assistance, feel free to let me know. I will be more than happy to be of assistance.

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, February 26, 2016 8:46 AM
    Moderator
  • I don't think my question was understood or maybe I didn't reiterate it clearly enough.  The problem I was seeing was that when only a Deployed printer setting was configured in a GPO, it would show up as filtered out Empty until I included the pushprinter connections exe.  I tested with a new GPO and do not see this problem any more so I am guessing it was due to some corruption with the GPO etc.  The definitive answer is no pushprinterconnections is not needed after xp and can be removed as it is a login script that could potentially slow down logins.
    • Marked as answer by Misha Rudiy Tuesday, March 1, 2016 9:12 PM
    Tuesday, March 1, 2016 9:12 PM