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

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

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 authentication type: - eap t
Read more