none
XP hangs on "Applying Computer Settings"

    Question

  • We have mixture of domain controlers running 2000 and 2008. I am experiencing performance issues our XP SP3 Pro systems. During booting up, prior to the Ctrl-Alt-Del screen being presented, the system hang at applying computer settings. I have narrowed this down to a Domain GPO that is applying a policy setting Always wait for the network at computer startup and logon.   But of course this appears to not be the actual problem, it just makes the system slow down. 

    I have enabled debugging for userenv. 

    I have noticed a few lines in the log that points to be a DNS issues on the system (see below). It appears what is creating our lag at boot up is DNS unavailable.  I have run several tests on the system after logging in and it appears DNS is working and available. 

    Does anyone have additional recommendation on what else I can try to troubleshoot or look at? If I deny the GPO with the Always wait for the network at computer startup and logon setting the system boots up fast, however I believe there is an underlying issue and the GPO is not our problem.  

    From the Userenv.log 
    GetUserDNSDomainName:  Domain name is NT Authority.  No DNS domain name available  
    ImpersonateUser: Failed to impersonate user with 5.
    GetUserNameAndDomain Failed to impersonate user




    JW
    Friday, August 28, 2009 5:30 PM

Answers

  • http://blogs.technet.com/askperf/archive/2008/10/14/help-i-m-stuck-at-applying-computer-settings.aspx


    Do you have proper kerberos, LDAP, SVR, SOA, and NS entries in your DNS (is your DNS configured properly)?

    ImpersonateUser leads me to believe that you have WMI issues; or that the computer object is failing.  Have you tried disjoining and rejoining the domain?

    What is the reasoning behind maintaining the "Always wait for the network at computer startup and logon" policy?  Is it worth "waiting this long?"


    If all else fails, perform a network capture in line and see what's going on when.


    Are you cascading/daisy-chaining switches?  Is your NIC set to auto-negotiate speed with the switch?  Is the switch port set to auto-negotiate with the NIC?

    Enjoy this article with a warm glass of milk: http://virtualthreads.blogspot.com/2006/02/beware-ethernet-flow-control.html


    Just found this really cool info: http://smallvoid.com/article/winnt-verbose-boot.html
    Friday, August 28, 2009 8:35 PM

All replies

  • check to if all programs are  closed  before  you retry to start this install  close as many of online programs aka messenger online and log off the first. This  should help very good as much as posssble.
    Friday, August 28, 2009 7:38 PM
  • http://blogs.technet.com/askperf/archive/2008/10/14/help-i-m-stuck-at-applying-computer-settings.aspx


    Do you have proper kerberos, LDAP, SVR, SOA, and NS entries in your DNS (is your DNS configured properly)?

    ImpersonateUser leads me to believe that you have WMI issues; or that the computer object is failing.  Have you tried disjoining and rejoining the domain?

    What is the reasoning behind maintaining the "Always wait for the network at computer startup and logon" policy?  Is it worth "waiting this long?"


    If all else fails, perform a network capture in line and see what's going on when.


    Are you cascading/daisy-chaining switches?  Is your NIC set to auto-negotiate speed with the switch?  Is the switch port set to auto-negotiate with the NIC?

    Enjoy this article with a warm glass of milk: http://virtualthreads.blogspot.com/2006/02/beware-ethernet-flow-control.html


    Just found this really cool info: http://smallvoid.com/article/winnt-verbose-boot.html
    Friday, August 28, 2009 8:35 PM
  • did you ever find a fix? we are seeing this on 5 of our 20 xp machins
    Wednesday, June 06, 2012 1:32 PM
  • GetUserDNSDomainName:  Domain name is NT Authority.  No DNS domain name available  
    ImpersonateUser: Failed to impersonate user with 5.

    The Above errors are very generic in the Userenv logging, This could also be that GPO applied on the startup hangs the machine. Do you have any scrip added on the Startup script of the machine, If any try removing the script and test.

    Wednesday, June 06, 2012 7:47 PM