RIS with Autologon fails on fast computers

[Guest]

I am having serious ongoing problems using Autologon in combination with RIS
as follows:

Machine builds using RIS and sets up autologon for a domain account (RIS)
correctly. After reboot, the RIS account logs on and runs some vbscript to
install software and make some configuration changes.

That's the theory.

In practice, this works correctly on MOST machines, but I have found that
more recent / faster computers appear to attempt autologon before the
computer has fully joined the domain, and therefore unattended installs sit
there with a message ("incorrect username/password") until someone goes and
cancels the error. On cancelling the error, RIS does log in automatically and
installation continues.

The problem is that someone needs to be monitoring the RIS builds just in
case this happens, and as we're trying to migrate over 4000 computers over
the next few months (from NT to XP), this will be something of an issue if it
can't be fixed.

I have searched everywhere I can think of, but nobody else has reported the
problem, let alone found a solution.

Basically, I need to find out what is actually going on when the computer
reboots and if there's any way to either slow down the autologon attempt or
automatically cancel the error message and retry.

Any ideas?

 

[Guest]

ADDITIONAL INFO:

The problem appears to be that Windows XP is "Building domain list" while
autologon is trying to happen. It's only a couple of seconds, but it's enough
to halt an unattended install.

 

[Guest]

Try to set the "Always wait for the network at computer startup and logon"
policy. Then the computer will wait for the network to start before trying to
logon.

/Daniel

 

[Guest]

Thanks, but that option is already set via group policy and the problem still
occurs.

 

[Gordon_C]

Did you ever find a solution to his problem??

We are experiencing this a the moment and it is very annoying!!