GPP Printer: error code '0x80070006 The handle is invalid.'

-

hello,

we're using 2 2008 r2 domain controllers, 1 2008 r2 print server , 6 2008 r2 xenapp terminal servers.

a problem has occured 1 of terminal servers. has stopped mapping printers users during logon.

the error event in event log says: "group policy object did not apply because failed error code '0x80070006 handle invalid.' error suppressed."

the printers configured in group policy preferences using fqdn.

i installed printer on secondary print server, testing purposes, , printer mapped fine, when deploying printers residing on main print server, nothing gets mapped.

file shares , every other settings work fine.

users able browse \\printserver or \\printserver.fqdn.com , add printers without problem. can browse directory , add them.

gpupdate ends same error in eventlog.

i have tried (on terminal server) leave domain , rejoin, didn't solve this.

i need solving this. cannot tell if problem in print server or terminal server..

any ideas?

hi,

based on research, there known issue targeting in 2008 r2 gpp printer doesn't work

i suggest refer below articles more helpful information:

http://www.edugeek.net/forums/thin-client-virtual-machines/64705-tip-use-group-policy-preferences-deploy-printers-terminal-server-clients.html

in addition, please see other ways deploy printers:

http://www.petri.co.il/deploying-printers-using-group-policy-windows-2008.htm

regards,

yan li

cataleya li
technet community support



Windows Server  >  Group Policy



Comments

Post a Comment

Popular posts from this blog

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authenticati...
Read more

Failed to setup initiator portal. Error status is given in the dump data.

-
hi team, server configured boot san  after booting  facing issue windows server 2008 r2 system logs continuously generating iscsi port error event id 5 failed setup initiator portal. error status given in dump data. eventdata \device\raidport1 000004000100000000000000050000c0000000000000000000000000000000000000000000000000070200c0 binary data: in words 0000: 00040000 00000001 00000000 c0000005 0008: 00000000 00000000 00000000 00000000 0010: 00000000 00000000 c0000207 in bytes 0000: 00 00 04 00 01 00 00 00 ........ 0008: 00 00 00 00 05 00 00 c0 .......À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 07 02 00 c0 ...À hi, please read through article below troubleshoot issue: error event id 5 logged in system log on computer uses iscsi software initiator connect iscsi target device http://suppo...
Read more

Invalid pointer on gpresult /h gpreport.html

-
hello guys i getting following error when trying generate gpresult /h  xxx.html invalid pointer this happening on windows 7 pc using test group policy. tried pc same thing when same gpo applied . hi, try apply some other gpo clients, html report generated succefully? if no, may caused unregistered .dll files, try register .dll files previous thread suggested: http://social.technet.microsoft.com/forums/en-us/winservergp/thread/0ea20c5d-c0ae-457d-89d4-a1686a359e72 if yes, please tell detailed information problematic gpo settings reproduce problem , troubleshooting it. regards, cicely Windows Server  >  Group Policy
Read more