Re: Slow login to AD
- From: Prith <Prith@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Apr 2007 20:18:03 -0700
Is this problem user specific or computer specific?
The best to do in these kinds of cases is to enable a USERENV log on the
clinet which is seeing the problem and see what is cauing he delay.
There could be a bunch of reasons why these might be happening:
logon scripts, too many group policies being processed, roaming profiles,
earlier profile unload issues.... so we really cannot say anything without
looking at the logs.
How to enable user environment debug logging in retail builds of ...
Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon Entry: UserEnvDebugLevel Type: REG_DWORD Value
data: 10002 (Hexadecimal)
support.microsoft.com/kb/221833
Enabled this logged in as the admin on the machine and then log off and log
back in as the problem user and let the logon process complete.
open the log file and search for username u logged in with and check the
profile load scrolling down wards... you would see the time stamps on the
left site, check were you are seeing a lot of time difference.. that should
give you a heads up on the issue.
Thanks
Prith
"Danny Sanders" wrote:
Slow logons in AD are usually related to DNS being set up wrong. In the.
properties of TCP/IP on these computers, do they point to the same IP
address for DNS as one of the computers not having the slow log on problem?
hth
DDS
"Jeremy" <Jeremy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:38CC43B0-9EF7-425C-A499-3BAF48DC8B67@xxxxxxxxxxxxxxxx
Well if it is only on SOME computers, then it has to be something to do
with
some of the processes that are running on THOSE computer when the user
logs
in. It can't be an AD problem.
"Lasse" wrote:
The problem is from the user enters his/her password and press ENTER and
to
the loginscript starts to run. It's only a problem with 5-10 of the
computers
and we have 75.
It's not caused by a slow loginscript since it works fine on the rest of
the
computers.
"Jeremy" wrote:
Hi,
You need to ensure that you are troubleshooting a slow logon, rather
than a
slow startup. Ensure a clean boot of a client an wait for all services
to
finish stating up and the machine to be idle. Then start timing the
logon
process. If logons are slow becuase of GPO you would expect them to be
slow
at all times. Luckily, this is pretty easy to rule out. Move the user
and
computer accounts to different OUs that avoid all policies and re-test
the
logon process.
You may also need to run some performance monitoring on your DCs while
clients login to see if they are resource contrained.
Typically slow logons that really are slow can be caused by:
1: Resource constrained DC/Server
2: Bad/Slow logon scripts
3: Slow sysvol performance (say over a slow link)
I once had a situation where some DCs for remote sites had been built
in the
main location and left on for a few weeks then shipped interstate.
Some
client had faulty sysvol referrals with a 120 day lifetime instead of
15
minutes, so all the traffic was going over a slow link. It sounds to
me like
your network is a bit smaller than this.
Cheers,
Jeremy.
"Lasse" wrote:
Hey
I am having problems with some client computers that are very slow to
login
to our AD. The DNS settings are working fine because it's not all the
computers that have the problem. All the computers have two DNS
servers that
are both internal.
The only things I can come up with is either problems with the local
profile
or our GPOs are slowing up the login process (We have 4 GPOs).
/Lasse
- References:
- Re: Slow login to AD
- From: Danny Sanders
- Re: Slow login to AD
- Prev by Date: Re: ADFS and Certificate Services
- Next by Date: Re: Workstations permissions to its own AD computer object
- Previous by thread: Re: Slow login to AD
- Next by thread: Remote site authentication
- Index(es):
Relevant Pages
|
