none
Event 4098 GPO Printers, Item-Level Targeting 0x80070bc4

    Question

  • Dear All,

    I have a Windows SBS 2008 Server with a Windows Server 2008 R2 Terminal Server.  I deploy the printers using GPO, and I also do Item-Level Targeting to manage default printers.

    When the user has no printers installed in his session, the deployment of the printers is going fine... The printers are installed, and the correct printer is taken as the default one.

    When the user logs off, and logs on again, following messages appear in the event viewer :

    The user '<user>' preference item in the 'Printer Policy' Group Policy object did not apply because it failed with error code '0x80070709 The printer name is invalid.' This error was suppressed.

    --> Item-Level Targetting is no longer applied.

    I already tried :

    - http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/3e413556-5db6-4f26-b15f-ecdb63ae6363

    - Adding the Terminal Server Computer account to the printers security

    - Played around with Group Policy LoopBack Mode

    - Gave the user administrator rights

    -...

    I really don't know what to do next and the customer is really complaining about this.

    Can somebody please help me?

    Kind Regards,

    Koen Verbeke


    Koen Verbeke ICT Consultant @ IF-IT4U bvba

    Tuesday, August 21, 2012 9:57 PM

Answers

All replies

  • Dear All,

    I have a Windows SBS 2008 Server with a Windows Server 2008 R2 Terminal Server.  I deploy the printers using GPO, and I also do Item-Level Targeting to manage default printers.

    When the user has no printers installed in his session, the deployment of the printers is going fine... The printers are installed, and the correct printer is taken as the default one.

    When the user logs off, and logs on again, following messages appear in the event viewer :

    The user '<user>' preference item in the 'Printer Policy' Group Policy object did not apply because it failed with error code '0x80070709 The printer name is invalid.' This error was suppressed.

    --> Item-Level Targetting is no longer applied.

    I already tried :

    - http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/3e413556-5db6-4f26-b15f-ecdb63ae6363

    - Adding the Terminal Server Computer account to the printers security

    - Played around with Group Policy LoopBack Mode

    - Gave the user administrator rights

    -...

    I really don't know what to do next and the customer is really complaining about this.

    Can somebody please help me?

    Kind Regards,

    Koen Verbeke


    Koen Verbeke ICT Consultant @ IF-IT4U bvba

    Tuesday, August 21, 2012 9:56 PM
  • Hi,

    I’ve helped you move the thread to the Windows Server forum so that your issue can be resolved more efficiently.

    Thanks for your understanding.

    Thanks,

    Simon

    Wednesday, August 22, 2012 6:58 AM
  • Printer connections are a Per User setting.  The Computer account name in the printer security will have zero impact since the SID during connection time is the USER SID.

    Regarding error 0x80070bc4

    http://support.microsoft.com/kb/2460922

    Group Policy preference item-level targeting does not work for 64-bit versions of Windows 7

    The printer connection is always removed in the TS session at log off and disconnect and built back up when reconnecting.   I think there is a KB for hitting this error on TS reconnection but can't find it.


    Alan Morris Windows Printing Team


    Wednesday, August 22, 2012 8:55 PM
  • Hi Alan,

    Thank you very much for your reply.  I installed the hotfix, but the error still stays the same.  The item-lever targetting non working, is just a cause of some other error, because the event id also happens when you want to eg. remove a previously installaed printer using GPO. 

    Is there something you can find on your internal database of error messages, that could help me?  0x80070bc4 must be some internal code???

    I really appreciate your help !

    Kind Regards,

    Koen Verbeke


    Koen Verbeke ICT Consultant @ IF-IT4U bvba

    Wednesday, August 22, 2012 9:49 PM
  • I use winerror.exe to make sense of the win32 error messages.

    C:\>winerror 0x0bc4
      3012 ERROR_PRINTER_NOT_FOUND <--> No NTSTATUS matched

    C:\>winerror 0x709
      1801 ERROR_INVALID_PRINTER_NAME <--> No NTSTATUS matched


    Alan Morris Windows Printing Team

    Wednesday, August 22, 2012 10:14 PM
  • This is how I solved the problem :

    - I noticed that the problem only occurs when you logon the second time.  When you logon for the first time, with no printers installed, the printers from the GPO are correctly installed with the correct default printer (according to Item Level Tagging).  The second time you logon, and something is changing on the printers (eg. change default printer), the change is not applied and an error message is logged in the event viewer.

    - So I searched for a way to uninstall all printers when a user logs off, so the next time a user log on, all printers are re-applied using GPO.

    - I used this tool con2prt.exe http://www.paulmcgrath.net/download.php?view.2 that you can find in the NT ZAK, to uninstall all network printers.

    - I made a loggoff script whith folowing command \\server\sharename\con2prty.exe /F

    - Now, on loggoff the profile of the user is clean from printers and the next time a user logs on, alle printer GPO stuff is reapplied whith the Item Level Tagging taken care off.

    More info here http://support.microsoft.com/default.aspx?scid=kb;en-us;181663, http://www.winvistatips.com/can-download-con2prt-exe-part-zak-w2k-res-kit-t564071.html and http://www.paulmcgrath.net/download.php?view.2

    It works as a charm, feel free to reply if you want more info, I searched long enough, glad to share

    Kind Regards,

    Koen


    Koen Verbeke ICT Consultant @ IF-IT4U bvba

    Saturday, September 08, 2012 12:58 PM
  • YES! This is exactly how I was able to resolve the issue.

    Use con2prt.exe from the Zero Admin Kit (google it and download), set it in the logoff script in the GPO and the subsequent default printers were set properly.

    Thursday, May 01, 2014 1:52 PM