Re: Windows Login

In news:%23dM5W4DNHHA.5016@xxxxxxxxxxxxxxxxxxxx,
RichF <rfandma@xxxxxxxxxxxxxxxx> typed:
Hello:

We manage several hundred client networks. None of these client
network are connected. They are separate customers. All of the
networks are very similar in that most are Windows 2003 domains,
Windows XP desktops, Exchange 2003, WSUS deployments SQL, etc. A
very typical Microsoft setup. Recently, we have seen a spike in a
very specific issue - a very significant spike. At about 10-20% of
our client sites over the past 1-2 months, users have been having an
issue logging in. When they initially login in the morning, they
don't get their desktop. In other words, they type in their username
and password, press enter, it goes thru the applying settings stuff,
then they just stare at a blank desktop. They can wait 1 minute or
an hour, but the desktop never appears. They then press
CTRL-ALT-DEL, select Logoff, and RE-login, and they can login
perfectly fine in a few seconds.
Unfrotunately, we have not been able to narrow this down much. In
all cases that we have sampled, there are no errors or warnings in
the Application or System log at the time of login. There are
varying login scripts at each site, but we have verified the login
scripts all run to completion. Although I can't say for certain, all
desktops are Windows XP SP2 as we keep up to date pretty regularly. The
problem is intermittant in that it will happen to USER-A one day,
then USER-B the next, but not USER-A. As noted these are different
networks and it's happening at multiple sites.
I certainly don't expect someone to come up with the a wiz-bang answer
(although that would be nice), but we are at the end of our
troubleshooting method. I need some better logging info than the
Eventlogs and ECHOing lines in a login batch file to a text file. How can
we better troubleshoot the Windows XP login process to a
Windows 2003 domain? If you do have any suggested solutions or known
issues, that would be great too.
Any help is much appreciated.

Thanks,
RichF

Are you using roaming profiles?
Even if you're not, have you installed the User Profile Hive Cleanup utility
(free download from MS) on all workstations?
DNS set up 100% correctly -with all clients pointing *only* at the internal
DNS server IP, and *no* public IPs at all?



.

Relevant Pages

  • Re: 802.1X Setup using Server 03 and Aironet 1200 Series WAP help
    ... Office/Home Office or Small Organization Networks" ... communication between the wireless client and IAS just was not ... most of the 170 pg Microsoft pdf located at the link below. ... Windows" documentation http://technet.microsoft.com/en-us/library/bb457068.aspx ...
    (microsoft.public.internet.radius)
  • Re: Windows Login
    ... perfect...no public DNS servers used internally at all. ... We manage several hundred client networks. ... Windows XP desktops, Exchange 2003, WSUS deployments SQL, etc. ... CTRL-ALT-DEL, select Logoff, and RE-login, and they can login ...
    (microsoft.public.windows.server.setup)
  • Re: Windows 98 getting stuck logging into a W2K3 domain.
    ... > workaround I've turned off Windows 98's ability in Client for MS ... > login stating that the domain can not be found, ... > Client for MS networks does the password validation. ...
    (microsoft.public.win2000.general)
  • Re: AutoLogin
    ... I understand that you may want to configure your Windows XP client to ... I would like to confirm whether you type the user2 ... but this login does not appear on the ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Windows Login
    ... perfect...no public DNS servers used internally at all. ... We manage several hundred client networks. ... Windows XP desktops, Exchange 2003, WSUS deployments SQL, etc. ... CTRL-ALT-DEL, select Logoff, and RE-login, and they can login ...
    (microsoft.public.windows.server.setup)
Loading