tag:blogger.com,1999:blog-62687483129304921.post5543349362990555758..comments2024-03-28T13:13:53.318+01:00Comments on ADdict: SCCM 2007: DCM Check For A Registry Value Only If the Value ExistsThomashttp://www.blogger.com/profile/12651864373303201993noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-62687483129304921.post-9776901451131959242013-02-18T14:18:05.294+01:002013-02-18T14:18:05.294+01:00Sorry for my latish comment. I've contact my c...Sorry for my latish comment. I've contact my colleague, and it seems that for now they wrote a procedure for the helpdesk to be able to fix the situation by recreating the registry keys and recycling the spooler service. We are aware that this is not a fix but a workaround. But due to the fact that we rarely see new cases this was acceptable for us...<br /><br />Good luck with your case...Thomashttps://www.blogger.com/profile/12651864373303201993noreply@blogger.comtag:blogger.com,1999:blog-62687483129304921.post-62715494140879376902013-02-11T17:45:50.703+01:002013-02-11T17:45:50.703+01:00I'm anxiously awaiting your response! We'v...I'm anxiously awaiting your response! We've had another network admin post to that MS forum who is experiencing the same issue, so your solution would be greatly appreciated! I think MS is interested in the solution as well, for it seems to be a software bug.<br />Thanks for your time!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-62687483129304921.post-6017002838341055782013-02-06T09:02:33.508+01:002013-02-06T09:02:33.508+01:00I'll have to check with my colleagues for the ...I'll have to check with my colleagues for the actual solution. This is a customer where I only drop by everyone once in a while... I'll come back to you.Thomashttps://www.blogger.com/profile/12651864373303201993noreply@blogger.comtag:blogger.com,1999:blog-62687483129304921.post-65682553371590186202013-02-06T01:17:32.404+01:002013-02-06T01:17:32.404+01:00Thomas,
I was hoping to get some insight as to the...Thomas,<br />I was hoping to get some insight as to the solution you have found for this issue. I am having the same issue you described, and I've got an active thread about the situation open here: http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/08bc6b4b-0190-40b0-be16-8b82249148e4<br />I'm assuming the "printer feature hotfix package of Microsoft" you described was KB2647753?<br />Did that resolve your problem? The issue still occurs on our units after applying that fix.<br />We are currently running Procmon on 14 client machines to check for changes to the Dependent Files registry entry, in order to shed some light on the cause of this issue.<br />We would rather not disable client-side rendering, though it seems that this is the path most admins have chosen to combat this issue.<br />Any information you can provide would be greatly appreciated, as we are seeing 8-12 occurrences per day out of about 400 machines.<br />I will check this blog daily for your response.<br />Thanks for your time.Anonymousnoreply@blogger.com