Mark Minasi's Tech Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Endaar

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 22
Reply with quote  #1 

Hi All,

OK this is a weird one...we've been using group policy preferences to map printers to users (via loopback processing) for years without issue. It worked fine on 7 and 8.1 on thousands of PCs. We've now started to roll out W10 and are running into a consistent problem.

If we attempt to set the default printer via GPP, the printer CSE will crash the group policy service. This only happens if we set a default - if the GPP is just mapping the printer without a default, it works fine.

The event logs show this happening, and I've also done a crash dump of gpsvc, which clearly shows calls to the spooler and other printer related functions at the time of the crash, so there's no question as to what's happening - it's just why.

It's not related to the printer driver, user, or anything else other than setting a default printer. I've exhausted everything I can think of and can't come to any conclusion other than this is a bug of some sort.

Any suggestions? Is there some way of reporting a bug without having to pay PSS? (Good luck getting a credit card in a school district...)


Thanks,
James

0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 241
Reply with quote  #2 
Sounds like a bug.

Can you turn on gpsvc logging (http://blogs.technet.com/b/mempson/archive/2010/01/10/userenvlog-for-windows-vista-2008-win7.aspx) and post the relevant bits directly after a crash? Perhaps with system and GroupPolicy events to go along with it? I can have a quick look if you like.

(I may be slow to respond because I'm at a conference)

__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Mafervus

Grumpy Old Men
Registered:
Posts: 34
Reply with quote  #3 
Maybe a dumb question, but have you installed windows 10 drivers on the server?
__________________
The problem with troubleshooting is that trouble shoots back. ~Author Unknown
0
Endaar

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 22
Reply with quote  #4 

To answer the driver question...the same problem occurs regardless of if I continue to use the drivers that work on 7/8.1, or if I install new drivers that 'officially' support Win 10.

wkasdo , I enabled logging per your comment. Not much really to see:
GPSVC(1024.1078) 14:47:50:769 ProcessGPOList:++ Entering for extension Group Policy Printers
GPSVC(1024.1078) 14:47:50:769 UserPolicyCallback: Setting status UI to Applying Group Policy Printers policy
GPSVC(1024.1318) 14:47:50:769 Message Status = <Applying Group Policy Printers policy>
GPSVC(1024.1318) 14:47:50:769 CStatusMessage::UpdateWinlogonStatusMessage::-- (Status: 997)
GPSVC(1024.1318) 14:47:50:769 CGroupPolicySession::QueueItemForPolicyApplication::-- (Status: 997)
GPSVC(1024.1318) 14:47:50:769 CGPApplicationService::UserLogonEvent::-- (Status: 997)
GPSVC(1024.1318) 14:47:50:769 CGPEventSubSystem::GroupPolicyOnLogon::-- (Status: 997)
GPSVC(1024.1318) 14:47:50:769 CGPEventSubSystem::GroupPolicyOnLogon::++ (SessionId: 1)
GPSVC(1024.1318) 14:47:50:769 CGPApplicationService::UserLogonEvent::++ (SessionId: 1, ServiceRestart: 0)
GPSVC(1024.1318) 14:47:50:769 CGPApplicationService::CheckAndCreateCriticalPolicySection.
GPSVC(1024.1318) 14:47:50:769 User SID = <S-1-5-21-1060284298-117609710-725345543-33940>
GPSVC(1024.1318) 14:47:50:769 Setting GPsession state = 1
GPSVC(1024.1318) 14:47:50:769 User SID = <S-1-5-21-1060284298-117609710-725345543-33940>
GPSVC(1024.1318) 14:47:50:769 CGPApplicationService::GetMachinePolicyProcessingCompletionEvent.
GPSVC(1024.1318) 14:47:50:769 CGPApplicationService::GetMachinePolicyWaitForNetworkCompletionEvent.
GPSVC(1024.1318) 14:47:50:769 CGroupPolicySession::QueueItemForPolicyApplication::++ (bTriggered: 0, bConsole: 1)
GPSVC(1024.1318) 14:47:50:769 PolicyApplicationState is True.
GPSVC(1024.1318) 14:47:50:769 AsyncThreadsProcessing is False.
GPSVC(1024.1318) 14:47:50:769 CGroupPolicySession::QueueItemForPolicyApplication::Applying policy in Sync
GPSVC(1024.1318) 14:47:50:769 CStatusMessage::UpdateWinlogonStatusMessage::++ (bMachine: 0)
GPSVC(1024.1078) 14:47:50:769 LogExtSessionStatus: Successfully logged Extension Session data
GPSVC(1024.1078) 14:47:50:769 ProcessGPOList: lpGPOInfo->lpGPInfoHandle->dwExtnCount is 2 for Group Policy Printers.

System log has event ID 1128: The Group Policy Client Side Extension Group Policy Printers may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue recurs.

Also 7031: The Group Policy Client service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

(In this case the 7031 was logged before the 1128, but I've seen it the other way also. I guess it's just a timing thing.)

In the GP operation log, we get event 6330: An unfinished invocation of the Group Policy Client Side Extension {BC75B1ED-5833-4858-9BB8-CBF0B166DF9D} from a previous instance of the Group Policy Service was detected.  This may indicate that the extension caused the Group Policy Client Service to terminate unexpectedly.

Anything you can do is appreciated.

James

0
Endaar

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 22
Reply with quote  #5 
We have a case open with Microsoft, which sadly has not been much help. That said, KB3140743 was released a few days ago and appears to fix this. There's no mention of it in the release notes but our preliminary testing looks good.

James
0
gmossin

Still Checking the Forum Out
Registered:
Posts: 1
Reply with quote  #6 
Helllo

I have the same Problem with Windows 10 1511. I Also opened a case by Microsoft but it didn't helped.

Have you found any Solutions?
0
Endaar

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 22
Reply with quote  #7 
KB3140743 seems to have fixed it for us. Have you tried on a fully patched Win 10 install?

James
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.