로그인
 
홈라이브러리학습다운로드지원커뮤니티포럼
Resources for IT Professionals >
> 
> 
One hour logon

Answered One hour logon

  • 2009년 7월 24일 금요일 오후 9:34
     
     
    로그인하여 투표
    0
    For some reason several, but not all of my Vista clients hung at the "welcome" screen for an hour before proceeding to the desktop screen. The clients were a mix of service pack 1 and 2. The domain controllers are all Server 2008, and are all service pack 1 or 2 as well. The application log has the following error: Log Name: Application Source: Microsoft-Windows-Winlogon Date: 7/24/2009 9:49:24 AM Event ID: 6006 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: PC12.mydomain.local Description: The winlogon notification subscriber took 3599 second(s) to handle the notification event (Logon). I know the GPClient is Group Policy Client. What I cannot figure out is how or what is slowing it down. Users in my own department had the logon problem, but I did not, and we are in the same groups with the same policies! Any ideas?
    • 편집됨 RandomAdmin 2009년 7월 24일 금요일 오후 9:36
    •  
     

모든 응답

  • 2009년 7월 28일 화요일 오전 10:22
    중재자
     
     
    로그인하여 투표
    0

    Hi,

     

    Thanks for posting in Microsoft TechNet Forum.

     

    Please refer to the following KBs.

     

    Winlogon notification packages do not work after you upgrade to Windows Vista

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

     

    When you try to log on to a Windows Vista-based computer, you briefly receive a "Welcome" message, and then you are logged off

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

     

    Hope this helps.

    Dale Qiao

    • 답변으로 표시됨 Dale QiaoModerator 2009년 7월 29일 수요일 오전 6:50
    • 답변으로 표시 취소됨 RandomAdmin 2009년 8월 12일 수요일 오후 6:13
    •  
     
  • 2009년 8월 12일 수요일 오후 6:20
     
     답변됨
    로그인하여 투표
    0
    As it turns out I traced the isue back to a couple of Konica-Minolta Postscript printers that were being installed via Group Policy preference.  The odd part is that the policy has been in effect for over six months without the issue occuring.  But if I remove the printers from the GPO, things are much better.  The day before the problem started I had been using a Windows 7 RC based PC to edit my Group Policies.  I am assuming it updated something in an .adm file somewhere.  Given the circumstances, it is almost impossible to really prove anything conclusively.  I am merely speculating due to the timing of events. 
    • 답변으로 표시됨 RandomAdmin 2009년 8월 12일 수요일 오후 6:20
    •  
     
  • 2012년 3월 15일 목요일 오후 8:48
     
     
    로그인하여 투표
    0

    How did you trace it to the KM printers?  I have this problems sporadically but regularly and am having real problems pinning it down.  Through 100 computers in 3 student labs it might happen 1-3 times a week.  We do have KM printers but how can I see positively if they are causing this?

    Thanks,

    -KH

     
  • 2012년 3월 15일 목요일 오후 8:59
     
     
    로그인하여 투표
    0
    It was really just a matter of trial and error.  I took a machine that was experiencing the problem and I segregated it in a test OU.  I kept adding group policies back until I broke it.  The last policy I added was the one that publishes our printers.  We run a mixed HP and Konica Minolta shop here.  Once I figured out that the printers policy was the root cause, it was then that I realized it was not affecting me because I had manually installed the Konica printers and drivers on my workstation so I could handle initial testing and setup tasks.  Every user running Vista that did not have the printers already setup manually had the problem.  Only a few areas use the Konica copiers as printers, so it became easier to just install them manually and skip GPO deployment.  I can say that we have not had the same experience with the Konica Minolta Bizhub 751 series.  The 751 series has been incorporated into out GPO deployment without incident.  The ones that caused the problem for us was the older 750 series.