none
Event ID 6005 and 6006. 10 minutes to login to Vista Business. RRS feed

  • Question

  •  

    Installed Vista on this machine months ago, initially had this same problem and it went away after a few reboots.  But i recently had to format/reload Vista because of a different issue.  The long login time has not gone away on this fresh install.  I believe it is not affected when i take it out of the domain (2003).

     

    After searching the internet I have tried:

    NETSH INTERFACE TCP GLOBAL set autotuninglevel=disabled

    and also making sure i can connect to \\domain.local\sysvol\.

     

    Neither of those helped.  I plan on using msconfig.exe next and disabling everything at startup to see if the issue goes away. Event logs are below:

     

    Log Name:      Application
    Source:        Microsoft-Windows-Winlogon
    Date:          2/18/2008 11:02:25 AM
    Event ID:      6005
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      computa
    Description:
    The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (StartShell).
    Event Xml:
    <Event xmlns="
    http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Winlogon" Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />
        <EventID Qualifiers="32768">6005</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-02-18T16:02:25.000Z" />
        <EventRecordID>2348</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>tbdivb20008v.corp.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>GPClient</Data>
        <Data>StartShell</Data>
        <Binary>C807D200</Binary>
      </EventData>
    </Event>

     

     

    Log Name:      Application
    Source:        Microsoft-Windows-Winlogon
    Date:          2/18/2008 11:11:24 AM
    Event ID:      6006
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      computa

    Description:
    The winlogon notification subscriber <GPClient> took 600 second(s) to handle the notification event (StartShell).
    Event Xml:
    <Event xmlns="
    http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Winlogon" Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />
        <EventID Qualifiers="32768">6006</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-02-18T16:11:24.000Z" />
        <EventRecordID>2354</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>tbdivb20008v.corp.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>GPClient</Data>
        <Data>600</Data>
        <Data>StartShell</Data>
        <Binary>04000000</Binary>
      </EventData>
    </Event>

     


     

    Any help would be greatly appreciated.

    Tuesday, February 19, 2008 8:19 PM

Answers

  • Hi Matt555,

     

    I would like to confirm if there are some logon scripts applied to this machine and the policy “Run logon scripts synchronously” is enabled. If so, please temporarily disable the policy or remove the logon scripts to check the result.

     

    Hope it helps.

     

    Sincerely,

    Joson Zhou

    Microsoft Online Community Support

     

    Thursday, February 21, 2008 6:48 AM
    Moderator
  •  

    Hello Again

     

     

    OK- I think I found the answer

    I found this is happening ONLY on certain hardware. On a different hardware platform, my test login was between 45 sec to 1 min, this is ok for a domain environment with lots of group policies.  However, when i looked at the network driver, i found that the driver belongs to Microsoft, I updated the NIC driver from Intel and Broadcom (NEW Version),  and the login is back to NORMAL at last, i have to say that i only did this for few machines and tested with one test account, But i am 90 percent sure that the long login issue is because vista is using its own driver for your NIC and that is where the problem is coming frrom.

    MAtt555 , Try these, update your drivers form vendor to the latest  and if it worked please let me know so we can make sure this has been resolved.

    I will install it on few other machine and chek the result Smile

    Shaggy

    Thursday, February 28, 2008 2:45 PM

All replies

  • Hi Matt555,

     

    I would like to confirm if there are some logon scripts applied to this machine and the policy “Run logon scripts synchronously” is enabled. If so, please temporarily disable the policy or remove the logon scripts to check the result.

     

    Hope it helps.

     

    Sincerely,

    Joson Zhou

    Microsoft Online Community Support

     

    Thursday, February 21, 2008 6:48 AM
    Moderator
  •  

    Hi Joson,

     

    I will look for that policy setting and see if its enabled.  If you see this before i respond can u tell me where it is in Group Policies?  Thanks!

     

    Matt

    Thursday, February 21, 2008 1:58 PM
  •  

    I ran a gpresult /Z and found:

     

    GPO: DivisonEveryone
                    KeyName:     Software\Microsoft\Windows\CurrentVersion\Policies\System\RunLogonScriptSync
                    Value:       1, 0, 0, 0
                    State:       Enabled

     

     

    I will need to get creative to test with only changing this option due to it being linked and enforced at the domain level.

     

    Will let you know of my results.

    Thursday, February 21, 2008 3:05 PM
  • Hi Matt555,

     

    Here is the location of that policy:

     

    User Configuration\ Administrative Templates\ System\ Scripts

     

    Hope it helps.

     

    Sincerely,

    Joson Zhou

    Microsoft Online Community Support

     

    Friday, February 22, 2008 1:54 AM
    Moderator
  •  

    Hello

    I am afraid the issue in wider than just disabling that policy “User Configuration\ Administrative Templates\ System\ Scripts” , this problem has been there since the beginning, I have managed the reduce the login time to 3 minutes or more using the group policy and disabling “Wait for network at start up and logon” and few other settings, but like Matt555, I have tried everything including disabling TCPtuning, but the problem is still there. This may be to do with windows server 2003 and domain controller. All I know is that I have tried everything including blocking all polices to user and the computer and it has NOT made a difference.

     

    On top of this- the users profile also get corrupted, shrinking ntuser.dat file to 256 kb at log off- so the next time user logs on- it says “the group policy client service has failed the logon. Access is Denied” . This is not exclusive to the domain environment as I have read about stand alone machine with a same issue.

    So far.. Microsoft has largely ignored these two important issues even though i emailed the Vista development team and few others Microsoft people in uk.

    Do you know how annoying is for users to wait such a long time to be logged on and then their profile be corrupted after that? And as the domain administrator, all you hear is moaning from your users.

    Fixing this would be really great- any help is much appreciated.

     

    Shaggy

    • Proposed as answer by JFischer00 Friday, September 23, 2016 7:27 PM
    Tuesday, February 26, 2008 5:34 PM
  • Hi Shaggy,

     

    I would like to know what is the exact time when the Windows Vista machine hangs during startup. Before or after the logon screen appears?

     

    What about booting into Safe Mode with Networking? Can the issue be resolved?

     

    As the nature limitation in forum, please understand that it may take a lot of time to analyze/resolve such tough issue. Thus, you might contact our Customer Service Support (CSS) for instant assistance, if the issue is urgent.

     

    To obtain the phone numbers for specific technology request, please check the website listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    Absolutely, you are welcomed if you would like to discuss the issue in this forum. I will do my best to help you.

     

    Sincerely,

    Joson Zhou

    Microsoft Online Community Support

     

    Thursday, February 28, 2008 5:17 AM
    Moderator
  •  

    Hi Joson

     

    the logon screen apears fast- not much delay on there. but it is the login that is the problem. I will try the safe mode with networking and get back to you. I also tried service pack 1 yesterday, but it did not resolve this issue.

     

    thanks for your help.

     

    Shaggy

    Thursday, February 28, 2008 12:28 PM
  •  

    Hello Again

     

     

    OK- I think I found the answer

    I found this is happening ONLY on certain hardware. On a different hardware platform, my test login was between 45 sec to 1 min, this is ok for a domain environment with lots of group policies.  However, when i looked at the network driver, i found that the driver belongs to Microsoft, I updated the NIC driver from Intel and Broadcom (NEW Version),  and the login is back to NORMAL at last, i have to say that i only did this for few machines and tested with one test account, But i am 90 percent sure that the long login issue is because vista is using its own driver for your NIC and that is where the problem is coming frrom.

    MAtt555 , Try these, update your drivers form vendor to the latest  and if it worked please let me know so we can make sure this has been resolved.

    I will install it on few other machine and chek the result Smile

    Shaggy

    Thursday, February 28, 2008 2:45 PM
  •  

    Bad news,,,, the new driver does not solve the problem completely, but it improves login time

    Shaggy
    Friday, April 4, 2008 1:59 PM
  • Hi!

    We've been having the same problems on our clients running vista. Logon times were around 10 minutes and eventID 6005 and 6006 from source winlogon were logged.
    In our case the problem was caused by an update deployed on the clients but not on the DC's. Since the updates was for GPO client side extensions this caused login problems. The update in case was KB 943729
    When we installed the updates on our DC's the problem was gone and logging on went back to normal.
    http://support.microsoft.com/kb/943729

    Hope this helps!
    • Proposed as answer by jennpublic Thursday, December 1, 2011 1:32 AM
    Tuesday, April 8, 2008 2:32 PM
  • i think there are too many reasons for the loggin time delay, i check my clients and DCs, non of them had this update installed. just released it with wsus, will tell you the result soon.

     

    Shaggy

     

    Tuesday, April 8, 2008 3:35 PM
  •  

    I was finally able to test this and it solved my problem! 

     

    Though it still does not make complete sense because i have another vista machine that is getting the same policy applied to it with no login problems... odd.

    Wednesday, April 9, 2008 4:29 PM
  • Hi Matt

     

    what did you test that solved the issue? what policy was that?

     

    Shaggy

    Thursday, April 10, 2008 11:05 AM
  •  mr-shaggy wrote:

    Hi Matt

     

    what did you test that solved the issue? what policy was that?

     

    Shaggy

     

    Sorry i meant to quote the post below:

     

     Joson Zhou - MSFT wrote:

    Hi Matt555,

     

    I would like to confirm if there are some logon scripts applied to this machine and the policy “Run logon scripts synchronously” is enabled. If so, please temporarily disable the policy or remove the logon scripts to check the result.

     

    Hope it helps.

     

    Sincerely,

    Joson Zhou

    Microsoft Online Community Support

     

    Friday, April 11, 2008 2:50 PM
  • Two things:

    • The GPO settings can be placed on the computer or the user. The computer setting takes precedence over the user setting.
    • Turning off this setting does not "solve" the problem. The problem is not that the logon scripts are busy for 10 minutes. Something about the processing done by GPClient makes GPClient loop for 10 minutes and then record a message stating same as it brings up the desktop. So this GPO setting, as well as some of the other "solutions" posted all over the internet, are just trigger points for the problem affecting a lot of Vista seats. What is MS doing to determine the underlying root cause? I ask because some secure environments require the synchronous setting so this band-aid to the problem is not usable. I can't even try this solution on a production seat, since the seat would be out of policy and blocked on the network and the problem only occurs when connected to the network.

    I have seats with the 10 minute delay. We have successfully rebuilt the user's profile (very painful) and the problem goes away for a week to two weeks. Then it comes back. Once the problem hits, it is constant every time the seat boots on the network.

     

    How do we look into this further and possibly get to true root cause?

     

    Thanks!

    Wednesday, April 16, 2008 11:54 PM
  • We too require this GPO setting.  Luckily this is only my test machine!  Our solution is to simply not deploy vista.  It provides no benefit to our users and introduces a ton of problems.

    Thursday, April 17, 2008 8:43 PM
  •  

    I'd have to agree...this is not a logon script problem. My problem is the same except for mine is always about 2 minutes 15 seconds. However, mine happens before login so I know it's not a script thing. Mine sits on the Vista "Please Wait" for the 2:15 before it even gets to the logon. Once I enter my credentials it takes another 45 seconds after that. I have yet to find a solution to this....and it's very annoying.
    Wednesday, July 16, 2008 8:05 PM
  • I'd like to remind everybody that the reasons for slow logon may be not so sophisticated. In my case the situation looked very similar. A user had a 10-minuted delay before every logon. Other users logged on just fine on the same machine. I've tried to re-create the profile, to update network drivers etc. The only thing I found is that it was due to Synchronous Application of Group Policy. But it is not accepatble for us to turn it off. So I continued to look for the real 'root cause'.

    The actual reason was very trivial and not related to hardware at all. We have some logon scripts for mapping network drives for different users. And in this particular case the user did not have the permissions required to connect to the network share. So the script hang for exactly 10 munutes, which is the default time-out.

    Hope this helps anybody.
    Tuesday, January 13, 2009 2:57 PM
  • I am having a similar issue with Vista Business on a Win 2003 environment.  If I log into the machine locally, i dont have any issues.  If i log into the machine with out the network cable plugged  in (cached domain credentials) then the device logs in fine with no delays.  As soon as I log into the machine with the network cable plugged in and the domain selected it takes at least 5 minutes before i can even see the desktop.  I've reloaded the machine just incase it was software conflicts.  There is no extra software install that might be causing the conflicts.  Event logs are useless because there are no error messages that might pertain to why this is happening.

    **EDIT** I am having the 6005 and 6006 error messages.
    Friday, February 6, 2009 6:23 PM
  • Check your Group Policies.  See if you have any printers added in the Control Panel Settings (User Configuration=>Preferences=>Control Panel Settings=>Printers).  If so, try removing them or change the option under Common to "Run in logged-on user's security context".
    Thursday, February 19, 2009 1:02 PM
  • I would just like to note that I had this exact problem. Windows would stay on the "Welcome" screen for several minutes and the only errors I could see were Events 6005 and 6006. I was able to resolve this by disabling the GPO in my domain that contained the Group Policy Preferences for printers. After that, log in times returned to normal.
    Monday, March 16, 2009 7:04 PM
  •  I found a resolution for my problem.  It seems that the hang up was because of the install process of network printers for the PC.  we have a script that runs and installs a printers based on groups in AD.  The issue was that Win 2k3 didnt have Vista drivers for these printers and Vista of course hung up during login process.  I was unable to allow access to these drivers because Vista wouldnt display the warning messages during the login.  Resolution was to manually add these printers and remove the user from the groups that were scripted to setup printers. 
    Tuesday, March 17, 2009 4:54 PM
  • Hi

    I am having the same problem.

    I have deployed client side prefernces on all machines in the domain. the DC also has them.

    howver since rolling out these preferences - most machines just hang at log off - or take along time to logon.

    I am going to try "Run in logged-on user's security context" but cant see how that will help.

    I have the vista printer drivers installed on the 2003 print server and I am using user preferences and adding a shared printer.

    any more advice ?
    Friday, June 5, 2009 2:44 PM
  • "Run in logged-on user's security context" didnt make any difference. same error messages. in the end I have given up and I am reverting to my printer scripts. it looks like this doesnt want to work for me with 1 2003 print server / DC and 1 2008 DC.

    :( annoying

    if anyone has any suggestions please reply :)
    Friday, June 5, 2009 2:58 PM
  • You might want to look at the group you are using to deply the GPO- I ahve no idea why it worked, but we were having 5-10 minute logon delays on all XP pro machines after last week's windows updates came down. I was messing with the permissions to make it easier to test, and noticed that as soon as I didn't use the "authenticated users" group to deploy it, it worked. I am now using 'autheticated users' with no issues.
    Monday, July 20, 2009 7:25 PM
  • Hey NormanV,
    Have you had any success in resolving this issue.  The "solutions" that I have seen as well do not 'fix' this issue in our environment.   Has anyone noticed this with multiple user profiles on the same machine, or is it normally only a single user that is having problems on the machine?

    Ian
    Wednesday, August 26, 2009 9:17 PM
  • I too am having the problems but only on Windows Server 2008 R2 and Windows 7.  We upgraded a workstation running Windows Server 2008 to 2008 R2 and started having this exact problem.  Then we installed a brand new Windows 7 Ultimate on another machine and it too started having the problem.  It only happens if you are connected to the network, if working offsite no issues.  For us it's Event ID 6005 and 6005 .. 6006 states:  "The winlogon notification subscriber <GPClient> took 232 second(s) to handle the notification event (Logon)."

    Environment:
    This site:
    Two servers, Win2k3 and Win2k8 both AD, win2k8 is GC

    Other site:
    One win2k3 AD/GC

    No one else is experiencing the issue.. Windows Vista clients logging in with no issues.

    Should I post a gpresult /z from the Win7 machine?
    Sunday, September 13, 2009 7:31 PM
  • Has any solution been forthcoming re this problem? Suddenly I am exeriencing exactly the same issue and none of the above suggestions have made any difference.

    Machine: Vista Business SP2 32bit
    Security: Norton 2010
    DC/AD: SBS 2003 R2
    Events: 6005 and 6006 following login.

    The only time the machine starts normally is if the LAN is disconnected!
    Thursday, October 15, 2009 2:35 AM
  • Hi Ziggy.
    I know this is an old post but I'm having this issue with a single user on a single machine.
    The users profile has been deleted and recreated and the problem persists. The affected user can log on to other machines in the same subnet in the same AD OU without any delay but on her specific machine the delay is an unacceptable 3599seconds (1 hour).

    Your post hinted at a similar circumstance.

    I've managed to logon to the affected desktop (a Shuttle barebones machine) without any delay and a few other standard user accounts plus my test account are unaffected.
    I can start in safe mode without issues and have disabled all but the essential startup services agains without error. I haven't bothered to narrow the services down one by one because I'm sure this is somehow user related.

    Any new info on this problem would be greatly appreciated.

    N03L.
    Monday, January 4, 2010 12:13 PM
  • Hi NoelWalsh

    There has been few things that we have attributed and found are attributing to the extended logon times. Now a 1 hour delay was certainly beyond anything that we had experienced but it could be related.  Have you recreated either the machine object or user account in AD?  When the user does finally get logged in is everything functioning without issue?


    One step that we did notice to have a pretty signficant impact on the logon was turning off logging of group policy on the users logon.  This was a attributing at times to extending logons by up to 2 minutes while it was trying to process RSOP.
    In other circumstances it was bad drivers that looked to be contributing to the extended logon times.  I have recently began to work further with Xperf and have been able to 'sniff' a bad driver by analyzing the times they are taking to load.  The Xperf logs are extensive but they do give you a fairly detailed analysis of many different components and their loading times.  

    Install Xperf and you can run the traces

    xbootmgr -trace boot -numRuns 1 -resultPath ***PATH FOR LOG FILE*** -PrepSystem -traceFlags base

    it will reboot, log in with the bad account, then a UAC for elevated priviledge, it will likely reboot again and repeat...  Once it has completed then run this 


      xperf -i ***PATH TO LOG FILE***.etl -o ***PATH TO LOG FILE*** summary.xml -a boot

    That will exact the etl file to an xml that isn't too bad to analyze.  The process does take a while though.




    Good luck, I know first hand how difficult it can be dig out these user specific issues in vista.



     
    Thursday, January 7, 2010 12:54 AM
  • I just wanted to chime in with my results because I've been working on a similar problem. In my case, this problem (10 minutes logon with Errors 6005 and 6006 logged) was happening on users logging onto a Windows Server 2008 Terminal Server, using RemoteApp. They would get stuck at a blue page (empty desktop) in the "Details" sub-frame of the Remote Desktop logon box.

    As others have pointed out the possible link with logon scripts, here's what I did to locate the problem and fix it:

    1. I logged as a local admin (not domain) on the 2008 server.
    2. I opened a file explorer and went directly to my DC's netlogon folder where logon scripts are, using one of the user's credentials. \\someserver\netlogon
    3. I ran each script that is being pushed by a GPO to the users. One is for file shares mapping, another for printers mapping.
    4. File shares went fine, but printers opened a window asking me (the admin) if I really wanted to install the necessary drivers for this printer. I clicked yes. Then another printer, clicked yes.
    5. Voilà.

    Wednesday, March 24, 2010 12:47 PM
  • Hello,

    After the logging in as a domain user on Vista Business 32 machines, I only get to the blank screen. The mouse cursor is visible and movable; task manager does not show up or function. This event only happens after any domain user logs in; local users does not have this problem.

    Any suggestions? Thanks.

    Saturday, April 3, 2010 6:07 AM
  • GenesisX,

    I had the same problem, except it would load after 10 to 15 minutes.

    If anyone is still having this problem, I recommend running all of your scripts that run through group policy. My problem was being caused by a Printer Driver Installation pop-up. As soon as I installed the driver the login time went down to 1 minute.


    Good luck!

    • Proposed as answer by Daniel Fielder Sunday, February 27, 2011 7:50 PM
    Tuesday, May 11, 2010 2:41 PM
  • I just wanted to chime in with my results because I've been working on a similar problem. In my case, this problem (10 minutes logon with Errors 6005 and 6006 logged) was happening on users logging onto a Windows Server 2008 Terminal Server, using RemoteApp. They would get stuck at a blue page (empty desktop) in the "Details" sub-frame of the Remote Desktop logon box.

    As others have pointed out the possible link with logon scripts, here's what I did to locate the problem and fix it:

     

    1. I logged as a local admin (not domain) on the 2008 server.
    2. I opened a file explorer and went directly to my DC's netlogon folder where logon scripts are, using one of the user's credentials. \\someserver\netlogon
    3. I ran each script that is being pushed by a GPO to the users. One is for file shares mapping, another for printers mapping.
    4. File shares went fine, but printers opened a window asking me (the admin) if I really wanted to install the necessary drivers for this printer. I clicked yes. Then another printer, clicked yes.
    5. Voilà.

     


    Hi!

    We have the exact same issue (Windows 2008 Domain with 2008 Terminal Servers). Unfortunately a user cannot see that "printer driver" popup during the logon process, but there is a GPO called "Point and Print Restrictions" which can prevent that popups:

    Computer Configuration -> Policies -> Administrative Tools -> Printers

    or

    User configuration -> Policies -> Administrative Tools -> Control Panel -> Printers

    After configuring that GPO the logon process was much faster and the event logs 6005 and 6006 disappeared.

    Regards

    SvenO

    Tuesday, May 18, 2010 9:01 AM
  • Just wanted to hop in and give you a big "thank you".  I've been searching for quite some time trying to figure out why the long hold-up for Windows 7 users and this seems to be it.  Went from a 10 minute wait to less than a minute.  Something so simple causing so much of a headache.  
    Thursday, July 22, 2010 12:13 PM
  • I had the same issue when i deployed printing preferences via group policy. I also has issues with hanging when the user logged out and only happended on VIsta machines-  XP and WIn7 worked fine.

     

    Removing the printer preferences from the GPO fixed it for me. When I manually install the printers from the share on the server they work fine, its only when i use group policy preferences that it has issues ....which is a darn shame as it makes life much easier but if it causes this sort of issue I can use it.

    Wednesday, January 5, 2011 6:15 AM
  • Thanks.  This helped me.  I'm logging into a Win 2003 DC from a Win 2008 R2 client.
    Wednesday, March 23, 2011 5:22 PM
  • We no longer have logon scripts. The were discontinued with the advent of Group Policy Preferences. For those of us still using logon scripts, I highly recommend replacing them with GP Preferences, utilizing the registry key section (even hkey_current_user), mapped drives, shortcuts, and printer deployment. If you have something that cannot be done with preferences, I'd love to know what.

    We have XP and 7 computers but skipped Vista. Our logon time from a cold boot to being able to see the start menu after logon is about 1min 20 seconds on HP 6005 model computers (Dual core Athelon II with 4GB memory) running windows 7 32bit. This includes 2 mapped drives, and 3 printers all set to "replace" in group policy. This is also with no existing profile for the particular user in question. This is true in my building (where we have a local on site domain controller).

    For our other schools, we have a minimum of a 100Mbps fiber connection to our SAN which has all our virtual servers. In these schools, logon times are from 2 minutes to 8 minutes and it's hard for me to track down why. Even in my building, the mapped drives and the print servers are all virtual on this SAN, only the domain controller is local. The log says that the gpclient is taking about 70 seconds which isn't horrible but I wish there was a progress bar instead of the endless circling icon.

    With windows 7 you must specific the policy mentioned above that disabled the need to "authenticate" your print servers. We've also found that you must turn on GP loopback if you plan on deploying printers based on computer OU's rather than users.

    computer->policies->admin templates->printers->Point and Print Restrictions->Disabled

    computer->Policies->system->group policy->user group policy loopback processing mode -> Enabled (Merge) DON'T FORGET MERGE

    I don't know why it's not a computer setting to begin with since we want a user to have printers close by no matter which computer they use. It seems like there would be very few circumstances where you'd want to deploy a printer to a user no matter where they were in the organization.

    I will explore this delayed start on services to see if we have some agents that slowing down the computers. Our server team has used wireshark (free network sniffer) to see how long different things are taking network wise, but I really wish there was a way to tell what it's currently waiting for during the logon process.

    One last thing, we do have “wait for the network at computer startup and logon” set to enabled or else users without profiles will not get mapped drives or printers.  This certainly slows down the logon process but is required for consistency.  I wish we could have it do everything else and have it complete these tasks after logon (cause I know it can) rather than having everything wait. 

    • Proposed as answer by KCS_74 Tuesday, September 6, 2011 1:51 PM
    • Unproposed as answer by KCS_74 Tuesday, September 6, 2011 2:05 PM
    Monday, August 22, 2011 11:39 PM
  • Beware of your RDP-Tcp Settings!

    In most cases you transfer your "local printer" to the Terminal Server Session.
    Try to disable the Printer Ressources in MSTSC Settings or - if possible you can disable it on the Host generally by using RDP-Tcp Properties/Client Settings.

    Good Luck,
    K*

    • Proposed as answer by KCS_74 Tuesday, September 6, 2011 2:08 PM
    Tuesday, September 6, 2011 2:08 PM
  •  We no longer have logon scripts. The were discontinued with the advent of Group Policy Preferences. For those of us still using logon scripts, I highly recommend replacing them with GP Preferences, utilizing the registry key section (even hkey_current_user), mapped drives, shortcuts, and printer deployment. If you have something that cannot be done with preferences, I'd love to know what.

     We have XP and 7 computers but skipped Vista. Our logon time from a cold boot to being able to see the start menu after logon is about 1min 20 seconds on HP 6005 model computers (Dual core Athelon II with 4GB memory) running windows 7 32bit. This includes 2 mapped drives, and 3 printers all set to "replace" in group policy. This is also with no existing profile for the particular user in question. This is true in my building (where we have a local on site domain controller).

     For our other schools, we have a minimum of a 100Mbps fiber connection to our SAN which has all our virtual servers. In these schools, logon times are from 2 minutes to 8 minutes and it's hard for me to track down why. Even in my building, the mapped drives and the print servers are all virtual on this SAN, only the domain controller is local. The log says that the gpclient is taking about 70 seconds which isn't horrible but I wish there was a progress bar instead of the endless circling icon.

    With windows 7 you must specific the policy mentioned above that disabled the need to "authenticate" your print servers. We've also found that you must turn on GP loopback if you plan on deploying printers based on computer OU's rather than users.

    computer->policies->admin templates->printers->Point and Print Restrictions->Disabled

    computer->Policies->system->group policy->user group policy loopback processing mode -> Enabled (Merge) DON'T FORGET MERGE

    I don't know why it's not a computer setting to begin with since we want a user to have printers close by no matter which computer they use. It seems like there would be very few circumstances where you'd want to deploy a printer to a user no matter where they were in the organization.

    I will explore this delayed start on services to see if we have some agents that slowing down the computers. Our server team has used wireshark (free network sniffer) to see how long different things are taking network wise, but I really wish there was a way to tell what it's currently waiting for during the logon process.

    One last thing, we do have “wait for the network at computer startup and logon” set to enabled or else users without profiles will not get mapped drives or printers.  This certainly slows down the logon process but is required for consistency.  I wish we could have it do everything else and have it complete these tasks after logon (cause I know it can) rather than having everything wait. 

     

    Many thx for this proposal Mike and also Laurent, I had this annoying issue at a customer site where I deployed a Win2008 R2 Sp1 RDS Server last week, initially no problems at all, but today several users had that annoying 2min delay with "Blue Window". All I had to do was to set this on the logonscript GPO which maps the printers.

    computer->policies->admin templates->printers->Point and Print Restrictions->Disabled

    And voilá, instant access to the desktop almost :)


     


    Thx /Tony
    Tuesday, October 11, 2011 8:39 PM
  • This was the solution for me - 2 vista PCs on the domain were taking 1hr+ after logon - showing only welcome screen.  Event viewer gave a number of GP events incl. Event ID 6005.  

    Had already totally wiped one PC and upgraded to Win7 to get around this - but tried just uninstalling the update on the 2nd one... that did the trick!!!

    THANKS SO MUCH

    Thursday, December 1, 2011 1:32 AM
  • Stumbeld upon exactly the same problem last week when we replaced a Windows 2003 sbs server by a Windows 2011 sbs server at a customer.One PC (only one) running Windows Vista Ultimate hangs for about 10 minutes before showing ctrl-alt-del. We narrowed it down to GPO issues (event ID 6006). Other PC's in the domain (even some with Windows Vista) do not show this behaviour.

    What we tried, in vain (meaning the issues was not solved):

    - "Run logon scripts synchronously” disabled

    - update nic drivers

    - msconfig.exe disabling all startup items

    - a group policy installing printers : we do not do it, only one drive is being mapped through GPO (other GPO elements are standard out-of-the-box SBS2011

    - checked KB 943729: not present on server, not on PC. One remark: when I installed the new server, one of the check point is to see if all computers have Group Policy Preference Client Side Extensions for Windows (XP or Vista). This computer told me the update did not apply to the system

    - Remove the PC from the domain (and become member of the WORKGROUP workgroup): problem gone

    - Add PC to the domain: problem back

    Basically I am suspecting some kind op GPO messing things up. What is the best approach to troubleshoot this step-by-step?

    Kind regards,

    Wouter Pinkhof


    Wouter Pinkhof PINKH bvba, PC-Hulp.com

    Friday, October 12, 2012 12:29 PM

  • --
    .
    --
    "wouterpinkhof" wrote in message news:1e0a6ee3-171c-47ca-93df-a14d108ce35a...

    Stumbeld upon exactly the same problem last week when we replaced a Windows 2003 sbs server by a Windows 2011 sbs server at a customer.One PC (only one) running Windows Vista Ultimate hangs for about 10 minutes before showing ctrl-alt-del. We narrowed it down to GPO issues (event ID 6006). Other PC's in the domain (even some with Windows Vista) do not show this behaviour.

    What we tried, in vain (meaning the issues was not solved):

    - "Run logon scripts synchronously” disabled

    - update nic drivers

    - msconfig.exe disabling all startup items

    - a group policy installing printers : we do not do it, only one drive is being mapped through GPO (other GPO elements are standard out-of-the-box SBS2011

    - checked KB 943729: not present on server, not on PC. One remark: when I installed the new server, one of the check point is to see if all computers have Group Policy Preference Client Side Extensions for Windows (XP or Vista). This computer told me the update did not apply to the system

    - Remove the PC from the domain (and become member of the WORKGROUP workgroup): problem gone

    - Add PC to the domain: problem back

    Basically I am suspecting some kind op GPO messing things up. What is the best approach to troubleshoot this step-by-step?

    Kind regards,

    Wouter Pinkhof


    Wouter Pinkhof PINKH bvba, PC-Hulp.com

    Sunday, October 14, 2012 9:18 AM
  • That was a very good tip. I seem to have found the place in the log that indicates the issue (I can post the full log if necessary). You can find it underneath around the 15:04 mark, the next log time is 15:11. And some messages seeming to indicate things not happening as expected. What does this all mean?

    GPSVC(5a4.650) 15:02:50:052 There is connectivity before running scripts
    GPSVC(d64.c98) 15:03:43:452 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x1b0
    GPSVC(d64.c98) 15:03:43:452 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.fdc) 15:03:43:452 Target = Machine
    GPSVC(d64.c98) 15:03:43:452 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.fdc) 15:03:43:452 Target = Machine, ChangeNumber 0
    GPSVC(5a4.5f0) 15:04:49:176 Target = Machine
    GPSVC(5a4.5f0) 15:04:49:176 Target = Machine, ChangeNumber 0
    GPSVC(504.6e0) 15:04:49:924 CGPNotify::RegisterForNotification: Entering with target Machine and event 0xc5c
    GPSVC(504.6e0) 15:04:50:157 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.5f0) 15:04:50:329 Target = Machine
    GPSVC(504.6e0) 15:04:50:329 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(504.6e0) 15:04:50:484 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.5f0) 15:11:07:066 Target = Machine
    GPSVC(5a4.5f0) 15:11:07:066 Target = Machine, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:066 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:066 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:066 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:22:331 Setting GPsession state = 1
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Entering with target Machine and event 0xfa0
    GPSVC(504.930) 15:12:04:944 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.408) 15:12:04:944 Target = Machine
    GPSVC(504.930) 15:12:04:944 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x1124
    GPSVC(504.930) 15:12:04:944 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(5a4.408) 15:12:04:944 Target = S-1-5-18
    GPSVC(5a4.408) 15:12:04:944 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:04:944 Caller requesting for user notification/lock is from session 0
    GPSVC(504.930) 15:12:04:944 Client_RegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.408) 15:12:04:944 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:04:944 Caller requesting for user notification/lock is from session 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x2f8
    GPSVC(c04.ae0) 15:12:24:902 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.408) 15:12:24:902 Target = Machine
    GPSVC(c04.ae0) 15:12:24:902 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x340
    GPSVC(c04.ae0) 15:12:24:902 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(5a4.408) 15:12:24:902 Target = S-1-5-18
    GPSVC(5a4.408) 15:12:24:902 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:24:902 Caller requesting for user notification/lock is from session 0
    GPSVC(c04.ae0) 15:12:24:902 Client_RegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.408) 15:12:24:902 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:24:902 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.650) 15:12:49:491 Application complete with bConnectivityFailure = 0.
    GPSVC(5a4.5fc) 15:12:56:804 SID = S-1-5-21-3722272522-4175653812-3644033897-1170
    GPSVC(5a4.5fc) 15:12:56:820 bMachine = 0
    GPSVC(5a4.5fc) 15:12:56:820 Setting GPsession state = 1
    GPSVC(5a4.8cc) 15:12:56:820 StartTime For network wait: 47408ms
    GPSVC(5a4.8cc) 15:12:56:820 Current Time: 673097ms
    GPSVC(5a4.8cc) 15:12:56:820 MaxTimeToWaitForNetwork: 30000ms
    GPSVC(5a4.8cc) 15:12:56:820 TimeRemainingToWaitForNetwork: 0ms
    GPSVC(5a4.8cc) 15:12:56:820 UserPolicy: Waiting for machine policy wait for network event with timeout 0 ms
    GPSVC(5a4.8cc) 15:12:56:835 GPLockPolicySection: Sid = (null), dwTimeout = 30000, dwFlags = 65538
    GPSVC(5a4.8cc) 15:12:56:835 LockPolicySection called for user <Machine>
    GPSVC(5a4.8cc) 15:12:56:835 Sync Lock Called
    GPSVC(5a4.8cc) 15:12:56:835 Reader Lock got immediately. m_cReadersInLock : 1
    GPSVC(5a4.8cc) 15:12:56:835 Lock taken successfully


    Wouter Pinkhof PINKH bvba, PC-Hulp.com

    Wednesday, October 17, 2012 1:48 PM
  • That was a very good tip. I seem to have found the place in the log that indicates the issue (I can post the full log if necessary). You can find it underneath around the 15:04 mark, the next log time is 15:11. And some messages seeming to indicate things not happening as expected. What does this all mean?

    GPSVC(5a4.650) 15:02:50:052 There is connectivity before running scripts
    GPSVC(d64.c98) 15:03:43:452 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x1b0
    GPSVC(d64.c98) 15:03:43:452 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.fdc) 15:03:43:452 Target = Machine
    GPSVC(d64.c98) 15:03:43:452 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.fdc) 15:03:43:452 Target = Machine, ChangeNumber 0
    GPSVC(5a4.5f0) 15:04:49:176 Target = Machine
    GPSVC(5a4.5f0) 15:04:49:176 Target = Machine, ChangeNumber 0
    GPSVC(504.6e0) 15:04:49:924 CGPNotify::RegisterForNotification: Entering with target Machine and event 0xc5c
    GPSVC(504.6e0) 15:04:50:157 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.5f0) 15:04:50:329 Target = Machine
    GPSVC(504.6e0) 15:04:50:329 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(504.6e0) 15:04:50:484 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.5f0) 15:11:07:066 Target = Machine
    GPSVC(5a4.5f0) 15:11:07:066 Target = Machine, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:066 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:066 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:066 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:22:331 Setting GPsession state = 1
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Entering with target Machine and event 0xfa0
    GPSVC(504.930) 15:12:04:944 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.408) 15:12:04:944 Target = Machine
    GPSVC(504.930) 15:12:04:944 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x1124
    GPSVC(504.930) 15:12:04:944 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(5a4.408) 15:12:04:944 Target = S-1-5-18
    GPSVC(5a4.408) 15:12:04:944 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:04:944 Caller requesting for user notification/lock is from session 0
    GPSVC(504.930) 15:12:04:944 Client_RegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.408) 15:12:04:944 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:04:944 Caller requesting for user notification/lock is from session 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x2f8
    GPSVC(c04.ae0) 15:12:24:902 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.408) 15:12:24:902 Target = Machine
    GPSVC(c04.ae0) 15:12:24:902 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x340
    GPSVC(c04.ae0) 15:12:24:902 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(5a4.408) 15:12:24:902 Target = S-1-5-18
    GPSVC(5a4.408) 15:12:24:902 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:24:902 Caller requesting for user notification/lock is from session 0
    GPSVC(c04.ae0) 15:12:24:902 Client_RegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.408) 15:12:24:902 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:24:902 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.650) 15:12:49:491 Application complete with bConnectivityFailure = 0.
    GPSVC(5a4.5fc) 15:12:56:804 SID = S-1-5-21-3722272522-4175653812-3644033897-1170
    GPSVC(5a4.5fc) 15:12:56:820 bMachine = 0
    GPSVC(5a4.5fc) 15:12:56:820 Setting GPsession state = 1
    GPSVC(5a4.8cc) 15:12:56:820 StartTime For network wait: 47408ms
    GPSVC(5a4.8cc) 15:12:56:820 Current Time: 673097ms
    GPSVC(5a4.8cc) 15:12:56:820 MaxTimeToWaitForNetwork: 30000ms
    GPSVC(5a4.8cc) 15:12:56:820 TimeRemainingToWaitForNetwork: 0ms
    GPSVC(5a4.8cc) 15:12:56:820 UserPolicy: Waiting for machine policy wait for network event with timeout 0 ms
    GPSVC(5a4.8cc) 15:12:56:835 GPLockPolicySection: Sid = (null), dwTimeout = 30000, dwFlags = 65538
    GPSVC(5a4.8cc) 15:12:56:835 LockPolicySection called for user <Machine>
    GPSVC(5a4.8cc) 15:12:56:835 Sync Lock Called
    GPSVC(5a4.8cc) 15:12:56:835 Reader Lock got immediately. m_cReadersInLock : 1
    GPSVC(5a4.8cc) 15:12:56:835 Lock taken successfully


    Wouter Pinkhof PINKH bvba, PC-Hulp.com

    Wednesday, October 17, 2012 1:48 PM
  • See if these gives you ideas
     
     
    Also try typing in a command prompt
     
    gpresult /z
     
    for clues.

    --
    .
    --
    "wouterpinkhof" wrote in message news:02b5bee0-bff7-4c26-9020-a58cadf98074...

    That was a very good tip. I seem to have found the place in the log that indicates the issue (I can post the full log if necessary). You can find it underneath around the 15:04 mark, the next log time is 15:11. And some messages seeming to indicate things not happening as expected. What does this all mean?

    GPSVC(5a4.650) 15:02:50:052 There is connectivity before running scripts
    GPSVC(d64.c98) 15:03:43:452 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x1b0
    GPSVC(d64.c98) 15:03:43:452 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.fdc) 15:03:43:452 Target = Machine
    GPSVC(d64.c98) 15:03:43:452 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.fdc) 15:03:43:452 Target = Machine, ChangeNumber 0
    GPSVC(5a4.5f0) 15:04:49:176 Target = Machine
    GPSVC(5a4.5f0) 15:04:49:176 Target = Machine, ChangeNumber 0
    GPSVC(504.6e0) 15:04:49:924 CGPNotify::RegisterForNotification: Entering with target Machine and event 0xc5c
    GPSVC(504.6e0) 15:04:50:157 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.5f0) 15:04:50:329 Target = Machine
    GPSVC(504.6e0) 15:04:50:329 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(504.6e0) 15:04:50:484 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.5f0) 15:11:07:066 Target = Machine
    GPSVC(5a4.5f0) 15:11:07:066 Target = Machine, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:066 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:066 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:066 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:07:082 Target = S-1-5-20, ChangeNumber 0
    GPSVC(5a4.5f0) 15:11:07:082 Could not find user by sid, finding user by session id
    GPSVC(5a4.5f0) 15:11:07:082 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.5f0) 15:11:22:331 Setting GPsession state = 1
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Entering with target Machine and event 0xfa0
    GPSVC(504.930) 15:12:04:944 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.408) 15:12:04:944 Target = Machine
    GPSVC(504.930) 15:12:04:944 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x1124
    GPSVC(504.930) 15:12:04:944 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(5a4.408) 15:12:04:944 Target = S-1-5-18
    GPSVC(5a4.408) 15:12:04:944 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:04:944 Caller requesting for user notification/lock is from session 0
    GPSVC(504.930) 15:12:04:944 Client_RegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(504.930) 15:12:04:944 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.408) 15:12:04:944 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:04:944 Caller requesting for user notification/lock is from session 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x2f8
    GPSVC(c04.ae0) 15:12:24:902 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(5a4.408) 15:12:24:902 Target = Machine
    GPSVC(c04.ae0) 15:12:24:902 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x340
    GPSVC(c04.ae0) 15:12:24:902 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(5a4.408) 15:12:24:902 Target = S-1-5-18
    GPSVC(5a4.408) 15:12:24:902 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:24:902 Caller requesting for user notification/lock is from session 0
    GPSVC(c04.ae0) 15:12:24:902 Client_RegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(c04.ae0) 15:12:24:902 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(5a4.408) 15:12:24:902 Could not find user by sid, finding user by session id
    GPSVC(5a4.408) 15:12:24:902 Caller requesting for user notification/lock is from session 0
    GPSVC(5a4.650) 15:12:49:491 Application complete with bConnectivityFailure = 0.
    GPSVC(5a4.5fc) 15:12:56:804 SID = S-1-5-21-3722272522-4175653812-3644033897-1170
    GPSVC(5a4.5fc) 15:12:56:820 bMachine = 0
    GPSVC(5a4.5fc) 15:12:56:820 Setting GPsession state = 1
    GPSVC(5a4.8cc) 15:12:56:820 StartTime For network wait: 47408ms
    GPSVC(5a4.8cc) 15:12:56:820 Current Time: 673097ms
    GPSVC(5a4.8cc) 15:12:56:820 MaxTimeToWaitForNetwork: 30000ms
    GPSVC(5a4.8cc) 15:12:56:820 TimeRemainingToWaitForNetwork: 0ms
    GPSVC(5a4.8cc) 15:12:56:820 UserPolicy: Waiting for machine policy wait for network event with timeout 0 ms
    GPSVC(5a4.8cc) 15:12:56:835 GPLockPolicySection: Sid = (null), dwTimeout = 30000, dwFlags = 65538
    GPSVC(5a4.8cc) 15:12:56:835 LockPolicySection called for user <Machine>
    GPSVC(5a4.8cc) 15:12:56:835 Sync Lock Called
    GPSVC(5a4.8cc) 15:12:56:835 Reader Lock got immediately. m_cReadersInLock : 1
    GPSVC(5a4.8cc) 15:12:56:835 Lock taken successfully


    Wouter Pinkhof PINKH bvba, PC-Hulp.com

    Thursday, October 18, 2012 8:04 AM
  • This is a Windows Vista machine and the WMI hotfiw references are for Windows 7. I have made the gpresult /z and it did not give me clues on what was happening. I could post it, but the PC is in Dutch, so some of the text in is Dutch. It is also a long report (most of it containing entries like this:

    Groepsbeleidsobjecten: Windows SBS Client - Windows 7 and Windows Vista Policy
                    Instelling: SOFTWARE\Policies\Microsoft\WindowsFirewall\FirewallRules\CoreNet-ICMP6-PP-Out
                    Naam:       118, 0, 50, 0, 46, 0, 48, 0, 124, 0, 65, 0, 99, 0, 116, 0, 105, 0, 111, 0, 110, 0, 61, 0, 65, 0, 108, 0, 108, 0, 111, 0, 119, 0, 124, 0, 65, 0, 99, 0, 116, 0, 105, 0, 118, 0, 101, 0, 61, 0, 84, 0, 82, 0, 85, 0, 69, 0, 124, 0, 68, 0, 105, 0, 114, 0, 61, 0, 79, 0, 117, 0, 116, 0, 124, 0, 80, 0, 114, 0, 111, 0, 116, 0, 111, 0, 99, 0, 111, 0, 108, 0, 61, 0, 53, 0, 56, 0, 124, 0, 80, 0, 114, 0, 111, 0, 102, 0, 105, 0, 108, 0, 101, 0, 61, 0, 68, 0, 111, 0, 109, 0, 97, 0, 105, 0, 110, 0, 124, 0, 73, 0, 67, 0, 77, 0, 80, 0, 54, 0, 61, 0, 52, 0, 58, 0, 42, 0, 124, 0, 65, 0, 112, 0, 112, 0, 61, 0, 83, 0, 121, 0, 115, 0, 116, 0, 101, 0, 109, 0, 124, 0, 78, 0, 97, 0, 109, 0, 101, 0, 61, 0, 64, 0, 70, 0, 105, 0, 114, 0, 101, 0, 119, 0, 97, 0, 108, 0, 108, 0, 65, 0, 80, 0, 73, 0, 46, 0, 100, 0, 108, 0, 108, 0, 44, 0, 45, 0, 50, 0, 53, 0, 49, 0, 49, 0, 55, 0, 124, 0, 68, 0, 101, 0, 115, 0, 99, 0, 61, 0, 64, 0, 70, 0, 105, 0, 114, 0, 101, 0, 119, 0, 97, 0, 108, 0, 108, 0, 65, 0, 80, 0, 73, 0, 46, 0, 100, 0, 108, 0, 108, 0, 44, 0, 45, 0, 50, 0, 53, 0, 49, 0, 49, 0, 56, 0, 124, 0, 69, 0, 109, 0, 98, 0, 101, 0, 100, 0, 67, 0, 116, 0, 120, 0, 116, 0, 61, 0, 64, 0, 70, 0, 105, 0, 114, 0, 101, 0, 119, 0, 97, 0, 108, 0, 108, 0, 65, 0, 80, 0, 73, 0, 46, 0, 100, 0, 108, 0, 108, 0, 44, 0, 45, 0, 50, 0, 53, 0, 48, 0, 48, 0, 48, 0, 124, 0, 69, 0, 100, 0, 103, 0, 101, 0, 61, 0, 70, 0, 65, 0, 76, 0, 83, 0, 69, 0, 124, 0, 0, 0
                    Status:  Ingeschakeld

    )

    I am trying some other stuff for the moment (uninstalling Symantec Endpoint Protection, in case I have a firewall of network connectivity issue)


    Wouter Pinkhof PINKH bvba, PC-Hulp.com

    Thursday, October 18, 2012 4:11 PM
  • Uninstalled Symantec and this is an extract of the gpsvc log. Still same issue at 18:21 and 18:31. I do not know what these things mean.

    PSVC(590.5b4) 18:13:05:631 Target = Machine, ChangeNumber 0
    GPSVC(4d0.aa4) 18:13:06:489 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x4b0
    GPSVC(4d0.aa4) 18:13:06:645 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(590.5b4) 18:13:06:864 Target = Machine
    GPSVC(4d0.aa4) 18:13:06:864 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(4d0.aa4) 18:13:07:020 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(37c.844) 18:14:11:719 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x2f4
    GPSVC(37c.844) 18:14:11:719 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(590.5b4) 18:14:11:719 Target = Machine
    GPSVC(37c.844) 18:14:11:719 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(37c.844) 18:14:11:719 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(590.5b4) 18:14:11:719 Target = Machine, ChangeNumber 0
    GPSVC(37c.844) 18:14:11:719 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x33c
    GPSVC(37c.844) 18:14:11:719 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(590.5b4) 18:14:11:719 Target = S-1-5-18
    GPSVC(590.5b4) 18:14:11:719 Could not find user by sid, finding user by session id
    GPSVC(590.5b4) 18:14:11:719 Caller requesting for user notification/lock is from session 0
    GPSVC(37c.844) 18:14:11:719 Client_RegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(37c.844) 18:14:11:719 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(590.5b4) 18:14:11:719 Could not find user by sid, finding user by session id
    GPSVC(590.5b4) 18:14:11:719 Caller requesting for user notification/lock is from session 0
    GPSVC(590.6cc) 18:21:09:605 Application complete with bConnectivityFailure = 0.
    GPSVC(f18.b88) 18:31:18:709 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x240
    GPSVC(f18.b88) 18:31:18:709 Client_InitialRegisterForNotification: User = machine, changenumber = 0
    GPSVC(590.6bc) 18:31:18:709 Target = Machine
    GPSVC(f18.b88) 18:31:18:709 Client_RegisterForNotification: User = machine, changenumber = 0
    GPSVC(f18.b88) 18:31:18:709 CGPNotify::RegisterForNotification: Exiting with status = 0
    GPSVC(f18.b88) 18:31:18:709 CGPNotify::RegisterForNotification: Entering with target S-1-5-18 and event 0x294
    GPSVC(f18.b88) 18:31:18:709 Client_InitialRegisterForNotification: User = S-1-5-18, changenumber = 0
    GPSVC(590.6bc) 18:31:18:709 Target = S-1-5-18
    GPSVC(590.6bc) 18:31:18:709 Could not find user by sid, finding user by session id
    GPSVC(f18.b88) 18:31:18:709 Client_RegisterForNotification: CheckRegisterForNotification returned error 0x5
    GPSVC(f18.b88) 18:31:18:709 CGPNotify::RegisterForNotification: failed with 5
    GPSVC(f18.b88) 18:31:18:709 CGPNotify::RegisterForNotification: Exiting with status = 5
    GPSVC(f18.b88) 18:31:18:709 CGPNotify::AbortAsyncRegistration: No asyn registration is pending
    GPSVC(590.23c) 18:32:28:621 SID = S-1-5-21-3722272522-4175653812-3644033897-1170
    GPSVC(590.23c) 18:32:28:621 bMachine = 0
    GPSVC(590.23c) 18:32:28:621 Setting GPsession state = 1
    GPSVC(590.8a0) 18:32:28:621 StartTime For network wait: 37830ms
    GPSVC(590.8a0) 18:32:28:621 Current Time: 1342419ms
    GPSVC(590.8a0) 18:32:28:621 MaxTimeToWaitForNetwork: 30000ms
    GPSVC(590.8a0) 18:32:28:621 TimeRemainingToWaitForNetwork: 0ms
    GPSVC(590.8a0) 18:32:28:621 UserPolicy: Waiting for machine policy wait for network event with timeout 0 ms
    GPSVC(590.8a0) 18:32:28:684 GPLockPolicySection: Sid = (null), dwTimeout = 30000, dwFlags = 65538
    GPSVC(590.8a0) 18:32:28:684 LockPolicySection called for user <Machine>
    GPSVC(590.8a0) 18:32:28:684 Sync Lock Called
    GPSVC(590.8a0) 18:32:28:684 Reader Lock got immediately. m_cReadersInLock : 1
    GPSVC(590.8a0) 18:32:28:684 Lock taken successfully
    GPSVC(590.8a0) 18:32:28:684 UnLockPolicySection called for user <Machine>
    GPSVC(590.8a0) 18:32:28:684 Found the caller in the ReaderHavingLock List. Removing it...
    GPSVC(590.8a0) 18:32:28:684 Setting lock state as notLocked
    GPSVC(590.8a0) 18:32:28:684 UnLocked successfully
    GPSVC(590.8a0) 18:32:28:699 GetDomainControllerConnectionInfo: Enabling bandwidth estimate.
    GPSVC(590.8a0) 18:32:30:712 Started bandwidth estimation successfully
    GPSVC(590.8a0) 18:32:30:712 GetDomainControllerConnectionInfo: Getting Ldap Handles.
    GPSVC(590.8a0) 18:32:30:712 GetLdapHandle:  Getting ldap handle for host: SBS2011.immo-dominique.local in domain: IMMO-DOMINIQUE.LOCAL.
    GPSVC(590.8a0) 18:32:30:712 GetLdapHandle:  Server connection established.
    GPSVC(590.8a0) 18:32:30:728 GetLdapHandle:  Bound successfully.


    Wouter Pinkhof PINKH bvba, PC-Hulp.com

    Thursday, October 18, 2012 4:42 PM
  • Aha...this was it for me!

    I tried driver replacements, policy changes, changes on the client and changes on the server, but as soon as I changed this policy to disable the desktop came up right after the welcome screen.

    This was not the case for another Latitude laptop I have running Windows 7; it was actually another script I disabled; the Run Login Scripts Synchroniously script.

    So for me it was the Point and Print restrictions. After I disabled that script the 10 minute delay after login was no more and the desktop came up immediately.

    Thank you for taking the time to post your answer. 

    Wednesday, November 5, 2014 4:29 PM
  • I recently experienced similar issue on one of the user which was taking more than an hour and i have tried all possible solution like remove network printer, all group policies, updated network card driver etc. etc. At the end i found that Mozilla firefox is the culprit. 

    Mozilla Firefox saved the huge crash reports almost 300,000 files in C:\Users\'uesrname"\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending folder. Every time user log in and log out caused those files to write back and read back to server and client computer.

    I also disable the option in Mozilla firefox not to send error reports and deleted all those files from pending folder and next user login/log off was within 1 minutes.

    Hope this information will help some admins.

    Tuesday, January 26, 2016 3:46 PM
  • Found this on google while searching for the same error event ID 6006 with administrator user <g class="gr_ gr_64 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del" data-gr-id="64" id="64">logon</g> taking 180 seconds. 

    Had recently done a profile and <g class="gr_ gr_104 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="104" id="104">homedir</g> relocation to a new FS and had changed the <g class="gr_ gr_169 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="169" id="169">homedir</g> attribute for every user except administrator. We don't really use that property for mapping Homedir <g class="gr_ gr_290 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="290" id="290">any more</g> as it's done by <g class="gr_ gr_243 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del" data-gr-id="243" id="243">logon</g> script, just to create the folder with the correct permissions. 

    After changing the <g class="gr_ gr_314 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="314" id="314">homedir</g> property to the correct file server, my logons went back to normal, under 5 seconds. 

    Monday, November 27, 2017 5:53 AM