Windows login script does not run on first startup everyday

Is the connection a wireless connection?  If so, the domain is probably trying to connect before the wireless card has made a connection. .... Thinkpads_User

Thanks for your comment Thinkpads_User.
However no, the connection is totally gigabit (clients and servers NICs are Gigabit and the connection is passed through a gigabit switch).

Thanks Rob,
This sounds very likely to solve the problem. I am trying this now and will let you know how it goes.

Yeah, hopefully it does.  I had to enable this in my organisation too, a while back, after the start of our Windows XP PCs.  Windows 2000 had this setting on be default, but Windows XP, in an effort to start up the computer faster (despite being a member of a domain) did not wait for the network, and we suffered your issue.

Regards,

Rob.

The computer described previously is currently in use so I can not test my policies but there is another system with very similar problems:
It never takes on policies or runs the login script.
I have ensured this computer is under the OU that I prescribe the policy to that you mentioned and have reset 3 times now but still no luck. I have ran gpupdate /force on the server and this client, both say they are sucessful.

Any ideas?

In your Group Policy Management Console, run the Group Policy Results Wizard, which should get a Resultant Set of Policies (RSOP) report on that computer.  This will tell you whether it thinks the policies are being applied or not.

Regards,

Rob.

Cool, thats an extreamly handy tool I did not know about Rob, cheers.
I can see though that this system has a totally different problem now.

I think it has brought me a step closer to the reason the login scripts have not been running on this computer. When I try and view the results it says access denied.
(I have even tried dropping and reattaching it to the domain same problem though)
When checking the event viewer I see a few errors stating the following (in chronological order):

Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

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.

Could not execute the following script AdministrationLoginScript.vbs. The system cannot find the file specified.

Update:
I can not add any AD domain users to the systems administrators group.
When trying to add them to the group it does not allow me to search the AD Domain only the local computer workgroup.
When trying to add a user and define their domain as the AD Domain name and add them as an administrator over this system I get the following error:
"The user could not be added because the following error has occured: The trust relationship between this workstation and the primary domain failed"

Everything I read on the net about this error is pointing to exiting the system from the domain to a workgroup restarting and rejoining the domain (like I did previously with no luck) I will try this again though and see if my luck changes ;)
Will let you know how it goes.

That did fix the viewing of the GP Results now I could make the user an administrator of the system but I still have the same problems as before.

My computer configuration policies are not propergating to the 2 systems.
I always thought that running gpupdate /force on the client machines made them request an updated policy from the server? Am I doing somthing wrong???

Ok worked out the problem lied in the DNS settings of the network interface settings. These were pointing at 2 external sources. I changed this to point the first at the domain server for windows DNS names and the second to my outside router for external DNS names and the problem is fixed on system 2.
This seems a bit strange though as before when I was pinging the server by its DNS name it was correctly resolving.
Before I changed the DNS's of the system I did a gpresult /z and noticed that it said "connected over a slow link YES" Once I change the DNS servers settings this now says NO.

I have also now enabled that "wait for network" rule to the first system and I will see if this works tomorrow morning.

Thankyou for all your help

OK, great.  That reminds me too, that I also have this setting on:
Computer Configuration --> Administrative Templates --> System / Group Policy --> Group Policy slow link detection = 0

because I had computers at remote sites that were timing out before applying the group policy...maybe that can help....

Regards,

Rob.

Thanks Rob, This worked perfectly.

System 1 logged in this morning with no problems. Thanks mate.
Thankyou for all the other tips aswell they have come in handy now and no doubt will in the future.

Thanks for the grade.  Glad you got it sorted. Group Policy / Network issues can be a real pain....

Regards,

Rob.