Hi everyone

We're currently planning to roll out XP SP3, unfortunately our 802.1x
network authentication requires some local changes (that are only
possible after the first reboot with SP3) before the clients get back
network access.

I have written a small batch that can do the necessary adjustments as a
system service so in theory it would fix the problem right after the
first reboot and before the user logs in. Unfortunately the login dialog
is faster than my batch, especially during the first SP3 reboot. Is
there a way to delay the display until my service has finished? Or any
other way to prevent the user from trying to log in when my batch is
still trying to get back network access?

Thanks for any suggestions!