none
GPP to deploy printers - default sometimes reverts to local PDF printer

    Question

  • Hi all,

    Strange problem which I hope someone can assist with. We deploy our printers using group policy preferences (2008 R2 domain)

    Works great - we update printers if users are member of a security group and delete them if they are no longer a member of the group. However we also have steps to set the default printer, also based on group membership. The setting of the default printer works most of the time however we get several calls a day from some users after they login whose default has decided to revert to PDF995 which is locally installed on their RDS Server.

    I can't work out why this is happening!

    (see screenshot below for GPP - I have edited it just to show the applicable steps so not to confuse things)

    As I say, it does work most of the time but can't work out why it sometimes fails and reverts to the local PDF printer.

    Two things that might be completly unrelated but worth mentioning:

    Sometimes when the users default printer is reverted to PDF995, if I set the default printer back to 'FollowMe' (for example) it comes up with warning 0x00000709. I then have to re-add the printer. I can understand why in these cases that the printer would fall back onto the local PDF995 printer

    In the event logs, our RDS Servers are flooded with The user 'printername' preference item in the 'Master Printer Policy {F2D2E2A1-6F4C-4E76-8FFE-BEBDCFD6D587}' Group Policy object did not apply because it failed with error code '0x80070bc4 No printers were found.' This error was suppressed.This appears to be for all users, however everything appears to work OK

    Any ideas would be appreciated! Thanks

    Alex

    Tuesday, December 18, 2012 3:19 PM

Answers


  • Two things that might be completly unrelated but worth mentioning:

    Sometimes when the users default printer is reverted to PDF995, if I set the default printer back to 'FollowMe' (for example) it comes up with warning 0x00000709. I then have to re-add the printer. I can understand why in these cases that the printer would fall back onto the local PDF995 printer


    That is NOT unrelated:

    # for hex 0x709 / decimal 1801 :
      ERROR_INVALID_PRINTER_NAME                                    winerror.h    
    # The printer name is invalid.

    After you removed all printers, creating this printer fails. And after removing all printers, Windows elects a new default printer (by default, this is the most recent installed local printer).

    To me, this seems to be a server issue. The client can't find the printer on the server...

    NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
    Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
    Tuesday, December 18, 2012 5:54 PM