Re: EventID 1054 from Userenv for startup script
- From: Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
- Date: Fri, 8 May 2009 05:54:57 +0000 (UTC)
Hello cjg.groups@xxxxxxxxx,
Did you configure the mentioned policy for the XP computers?
Please post an unedited ipconfig /all from the DC/DNS and a problem client.
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
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 computerThat is a typical error message for either DNS or the "always wait
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.
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 beforeOkay-- the setting is applied on all machines? What permissions are
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.
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
.
- Follow-Ups:
- Re: EventID 1054 from Userenv for startup script
- From: cjg . groups
- Re: EventID 1054 from Userenv for startup script
- References:
- Re: EventID 1054 from Userenv for startup script
- From: cjg . groups
- Re: EventID 1054 from Userenv for startup script
- Prev by Date: Re: Logoff script takes a long time to run
- Next by Date: Re: logoff script to force computer reboot doesn't work
- Previous by thread: Re: EventID 1054 from Userenv for startup script
- Next by thread: Re: EventID 1054 from Userenv for startup script
- Index(es):
Relevant Pages
|