Re: EventID 1054 from Userenv for startup script

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hello cjg.groups@xxxxxxxxx,

Make sure you have configured:
Computer Configuration\Administrative Templates\System\Logon "Always wait for network at computer startup and logon"

XP behaves different from 2000, most o the time the network is not operational when you logon, so it uses cached credentials.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


Hello. In my Windows 2003 domain, some of my XP machines log the
following error every time they boot up:

Event Source: Userenv
Event ID: 1054
User: NT AUTHORITY\SYSTEM
Description:
Windows cannot obtain the domain controller name for your computer
network. (The specified domain either does not exist or could not be
contacted. ). Group Policy processing aborted.
However, other machines do not log this error. All machines were
configured similarly and all function normally in every other respect.

I noticed this problem when the failing machines couldn't access a
computer startup script. Verbose logging shows that SYSTEM can't find
the domain controller, but logging in as a user just seconds after
bootup will find the DC with no problem.

On one machine, I set the local policy to wait for network before
allowing login:
Computer\Administrative Templates\System\Logon\[Always wait for the
network at computer startup and logon]
This revealed a new Event Log error saying that SYSTEM simply could
not access the startup BAT file on the network. Permissions are set
the same for all computers, though some got it and some couldn't.
This must be a simple error, but everything seems set correctly and
consistently across all machines, so I can't find the problem. Any
suggestions? Thanks a million!



.

Relevant Pages

  • Local Logon Prevention in W2K / XP
    ... Have you tried to enable to the "Always wait for network ... at computer startup and logon". ... You can access it under Local Computer Policy - Admin ... Templates - System - Logon ...
    (microsoft.public.win2000.general)
  • Re: XP Pro - Logging on to Domain issues
    ... The only thing I could find that closely resembles that is under Logon not ... Group Policy and it is "Always wait for the network at computer startup and ... >> network. ... >> such as previous Win2K Pro AND XP Pro you can). ...
    (microsoft.public.windowsxp.network_web)
  • Re: local group policy winning?
    ... The option "Always wait for the network at computer startup and logon." ... is turned on (and we even have a synchronous logonscript) ...
    (microsoft.public.windows.group_policy)
  • Re: Very long delay at logon to domain
    ... Logon slow or access network slowI would keep "Always wait for the network ... at computer startup and login" is disabled and work on the slow logon. ...
    (microsoft.public.windowsxp.network_web)
  • EventID 1054 from Userenv for startup script
    ... Windows cannot obtain the domain controller name for your computer ... other machines do not log this error. ... computer startup script. ... I set the local policy to wait for network before ...
    (microsoft.public.windows.group_policy)