Re: Slow logon because of "Applying computer settings..."



Hi
Check
Is this a slow logon issue or slow boot issue?
Check if the client is pointing to the correct DNS server, GPO settings, maybe some GPO is tring to apply some software or running some script, search for event errrors, logon scripts....
also
http://www.chicagotech.net/winslow.htm


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Dominique" <dominique.kilcher@xxxxxxx> wrote in message news:1181304029.508802.103580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
Our Windows XP users are suffering from slow logon times. When the
user starts his workstation in the morning and enters the username and
password it takes about 6 minutes before the taskbar shows up and the
user is actually logged in.
The main problem is that the message "Applying computer settings..." is
taking about 3 minutes. This delay occurs only after the computer has
been turn off for a few hours (like during the night). Once the
computer has been started any following reboot is reasonable fast and
the "Applying computer setting..." message won't appear again. We do
have that problem with workstations and notebooks (which are in
different OUs with different computer policies assigned to them)
It seems to be related to computer policies but I can't figure out
which one. Actually it looks like any of our computer policies are
causing the issue.
When I move the computer account to an OU where GPOs are blocked the
problem is gone.
I've searched the MS KB and newsgroups and it looks like many people
have similar problems but none of the published solutions work in our
case.
Many people are pointing to DNS to be the problem but I've checked it
with nslookup and netdiag and everything looks good.
The "set" command shows that the workstation is connected to the
correct site and logged on to one of the local domain controllers.
"Dfsutil /pktinfo" shows that the policies were loaded from the SYSVOL
of a local DC within the client site.

I'm positive that isn't related to W2K3 SP2 or any other of the
recently installed Windows updates. We do have that problem for quite
a while now but didn't have time to take a closer look at it.

The fact that the delay occurs only in the morning or after the
computer has been turned of for a while makes it diffcult to
troubleshoot.
Does Windows XP cache computer policies locally on the harddisk for a
couple of hours?

Details about our Active Directory structure:
- 1 Child Domain (Windows 2003 native)
- 20 Domain Controllers (3 on my site)
- 8 Sites (all subnets are configured and belong to the correct site)
- OSn o all Domain Controllers is Windows 2003 SP2
- All DCs are AD-Integrated DNS servers and are pointing to their self
as primary DNS
- Clients are using DHCP and their local DC as DNS server


Any input is appreciated

Regards
Dominique


.



Relevant Pages

  • Re: Win2003 "cannot access the file gpt.ini"
    ... 'WINS' names is missing. ... Please wait for 30 minutes for DNS server ... > were fine, so we created a new blank GPO, then copied its gpt.ini back to ... >> Windows cannot query for the list of Group Policy objects. ...
    (microsoft.public.windows.server.setup)
  • Re: Client take too long to get in.
    ... only one GPO and two scripts there in that GPO. ... There are two DNS server for the entire domain. ... Is there any tool that can report the login the process and the time taken. ... How many GPOs, Scripts are being processed? ...
    (microsoft.public.windows.server.active_directory)
  • Re: file is created on system32 everytime a gpo is applied
    ... > I've noticed that one of our dc's (dns server, ... > letters changing) everytime a gpo is applied. ... > changed it to 960 decimal) and it stopped reaplying the ...
    (microsoft.public.win2000.group_policy)
  • Re: DNS Server settings HELP!!!
    ... be referred to the Primary but by pointing them both there ... to the other DNS server works just fine. ... > directly to the NS of my web host. ... can resolve on the Internet. ...
    (microsoft.public.windows.server.dns)
  • Re: ID 1000
    ... Your poblem does not really belong to the GPO itself. ... Then check your DNS configuration, in a single domain all servers and clients should only point to the local DNS server from your domain and if you go to internet, your DNS server should have configured a forwarder. ... new domain controller group policy ...
    (microsoft.public.win2000.group_policy)