Re: EventID 1054 from Userenv for startup script

Thank you both for the feedback. The policy folder containing the
startup script currently does not have Authenticated Users in its
ACL. This is because I'm using Security Filtering to apply this
policy to a group of computers. So, the ACL gives Read & Execute
access to that group (and server-local groups like Domain Admins,
etc).

I added Authenticated Users to script folder ACL with Read & Execute
permission, but it still didn't run at startup. However, if I run the
script by hand and reboot, the next GPO after the script (software
deployment) does run.

The Local System account simply can't find the domain controller at
startup, and it never has been able to since I built the computer.
Yet, everything about this computer works, and the other computers
with this problem work fine too. It obviously gets group policy
(during a refresh after startup) because it knows to look for that
script, but it seemingly has no network access during bootup to get
it. But it can get the software deployment package from the same
server.


I currently get these three errors at startup in the Application log:
EventID 1054 from Userenv - 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.

EventID 1000 from UserInit - Could not execute the following script
StartupScript.bat. The system cannot find the file specified.

EventID 15 from AutoEnrollment - Automatic certificate enrollment for
local system failed to contact the active directory (0x8007054b). The
specified domain either does not exist or could not be contacted.
Enrollment will not be performed.

I also have this error in the System log:
EventID 5719 from NETLOGON - No Domain Controller is available for
domain MYDOMAIN due to the following:
There are currently no logon servers available to service the logon
request. .


Any idea why it's "just not working"? Thanks.


On May 7, 2:14 am, "Florian Frommherz [MVP]"
<flor...@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Howdie!

cjg.gro...@xxxxxxxxx schrieb:

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.

That is a typical error message for either DNS or the "always wait for
the network.." policy unset, originally. Have you checked client DNS
settings are ok?

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.

Okay-- the setting is applied on all machines? What permissions are on
the share (just to be sure?) Can you test "Authenticated Users" with at
least "Read" permissions?

cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog:http://www.frickelsoft.net/blog.
Maillist (german):http://frickelsoft.net/cms/index.php?page=mailingliste

.

Relevant Pages

  • Re: EventID 1054 from Userenv for startup script
    ... The startup script policy: This is a GPO which only contains a ... The "Wait for network" policy: On the server's Default Domain Policy, ...
    (microsoft.public.windows.group_policy)
  • Re: Group Policy Timeout on one server in an OU.
    ... inheritance of that login script and placed myself in the OU. ... On Error GoTo 0 ... Group Policy Information Hub: ... Group Policy Management solutions athttp://www.sdmsoftware.com ...
    (microsoft.public.windows.group_policy)
  • Re: EventID 1054 from Userenv for startup script
    ... in the right window "Group policy Inheritance tab", ... Those two contain the requirement to "Wait for network before ... where the startup script did run but the deployment GPO would not. ...
    (microsoft.public.windows.group_policy)
  • Re: Xcopy not working in startup script
    ... This is a basic batch file script that I am ... I'm deploying it during the ... startup so that every computer gets it, ... it works fine on it's own, but when deployed through group policy it ...
    (microsoft.public.windows.server.general)
  • Re: Problems with Xcopy in startup script
    ... This is a basic batch file script that I am ... deploying through group policy in the startup script to copy templates ... I'm deploying it during the ... startup so that every computer gets it, ...
    (microsoft.public.windowsxp.general)
Loading