Logon delay to allow wireless connection before user logon

Yes, I was under the impression that it is the same as disabling the XP fast logon feature

No - they aren't the same - try to enable that policy separately.

That policy is (and has been) enabled.

Where is the setting for disabling the XP fast logon feature?

Same place - "Always use classic logon".

But - this doesn't take effect on a domain - as the "classic logon" is used by default.

Anything else to try?

What about enabling
Computer config\Admin Templates\System\Scripts\ "Run logon scripts synchronously"

Already enabled.

If the user logs on as soon as they see the logon screen, it logs them on with cached crdentials (because it does not see the domain) so the OS does not see a script to run.

Okay - disable cached logons:

\System\User Profiles\ "Wait for remote user profile"

and...

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\LocalMachine\Software\Policies\Microsoft\Windows\System
Create a new DWORD value, or modify the existing value, called 'DeleteRoamingCache' and edit the value according to the settings above.  

Value Name: DeleteRoamingCache
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = disabled, 1 = enabled)

(basically - you can include this in your logon script)

I will try the vbs script to see what happens

I really do not want to completely disable cached logon since I will travel with tis laptop and really do not want to maintain a domain profile and a local profile.

The vbscript worked. I actually had to change it to 6 seconds but never the less it is working.

Too bad ther isn't a script that would wait for an IP address to be assigned and as soon as it is, the script would end.  Of course there would have to be a 15-20 second timeout in case I was somewhere where there is no network.

Thanks for your help

I found this on Miscrosoft site. These changes do exaclty what I am looking for. Now the computer actually waits for the DC and applies the GP (machine) settings before the logon screen is displayed.

Here are the changes:
Windows XP Service Pack 2
After you apply Windows XP Service Pack 2, you must add the GpNetworkStartTimeoutPolicyValue registry entry. This entry defines the number of seconds to wait before trying to run the Group Policy startup script again. To find the value that will work for your configuration, define a decimal value of 60, and then increase the value until the problem is resolved. To add the registry entry and to define the value, follow these steps:1. Click Start, click Run, type regedit, and then click OK.
2. Expand the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
3. Right-click Winlogon, point to New, and then click DWORD Value.
4. To name the new entry, type GpNetworkStartTimeoutPolicyValue, and then press ENTER.
5. Right-click GpNetworkStartTimeoutPolicyValue, and then click Modify.
6. Under Base, click Decimal.
7. In the Value data box, type 60, and then click OK.
8. Exit Registry Editor, and then restart the computer.
9. If the Group Policy startup script does not run, increase the value of the GpNetworkStartTimeoutPolicyValue registry entry.

Back to the top

Creating a Group Policy network start timeout policy
The GpNetworkStartTimeoutPolicyValue policy timeout can be specified in the registry in two locations:" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon
" HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System
You can do this by adding a DWORD value of GpNetworkStartTimeoutPolicyValue with a number of seconds between 30 and 600.

Windows reads the Winlogon subkey first. Then, Windows reads the Policies subkey. The value in the Policies subkey supersedes any value in the Winlogon subkey. There is no user interface that you can use to set this Group Policy object (GPO). Therefore, you have to deploy a custom ADM file in order to set the GPO.

The value specified should be of sufficient duration to make sure that the connection is made. During the timeout period, Windows examines the connection status every two seconds and continues with system startup as soon as the connection is confirmed. Therefore, setting the value larger than the minimum value of 30 is recommended. However, be advised that if the system is legitimately disconnected, Windows will stall for the whole timeout period.

That's good to know.