Autologon Delay

May 7, 2010 at 13:12:25
Specs: Windows XP
Does anyone know if there is a way to set a few seconds delay for autologin? When we try to use TweakUI or this method it logs into a local profile instead of the domain. If we log in maually it works fine This is an old computer from a vendor and I assume it's probably a slow connecting NIC or slow routing causing it not to see the domain in time to pull the roaming profile. I have Googled 'till my fingers are raw and all I see on other forums are flame wars on other worthless options. If anyone has any ideas I would be most greatfull.

See More: Autologon Delay

Report •

May 7, 2010 at 14:20:55
Why does this old machine have a roaming profile?

I don't see how a delay in logon is going to address your issue. Profile doesn't download until you logon.

Report •

May 7, 2010 at 14:34:23
Not to be rude but this is the sort of responses I am seeing on other forums. I'm not going to debate on the how and whys of the way this computer is set up.This is the way the vendor has it set up and we really don't have the option to change it unfortunately. It's not a showstopper, but the clients (nurses) prefer the autologin method.

The problem really seems to be a timing issue. When we use an autologin, it comes up with an error message that it can't find the roaming profile so Windows will use a local profile instead. If we remove the autologin, and log in manually, all is well.

Report •

May 7, 2010 at 14:57:23
When you say autologon what do you mean? Do you mean logon with no authentication or what. It would be impossible to do what you are suggesting because in order to use the Roaming Profiles the system must be able to identify you with an active directory user and if you logon on without authentication then it can not id who you are and will (as you have seen) log you on a a local user. So I think the real answer is you can not use roaming profiles without a logon.

Report •

Related Solutions

May 7, 2010 at 15:06:26
Yes, the computer logs on to a domain with authentication. You have to put in a username and password. And yes, there is a profile for this computer in AD. By using autologon, I mean TweakUI or the Microsoft method inserts both the username and password automatically for you.

Here's more to the story if it will help. There has been an old Dell GX270 in place for several years. It died last week so the vendor sent us a new computer. Unfortunately their idea of a "new" computer was to send us another antiquated Dell GX270. The old computer would log in just fine using the TweakUI autologin method but for some reason this computer which is set up the exact same way as the old one gives us the error.

Report •

May 7, 2010 at 15:43:46
Have you looked at this?

Did you search the registry for the autologon keys?
Is this machine joined to the domain?

Not sure what the "debate" is concerning using a roaming profile. I have yet to meet a vendor that demanded one. All settings should be local so this makes me wonder if there really is a roaming profile being downloaded or its just a domain profile we are talking about.

Additionally, delaying logon does not address the issue. Do you understand this?
You want a pause AFTER the logon not BEFORE the logon.

Report •

May 7, 2010 at 15:49:17
Hi Wanderer, yes i did see that, it basically enters the registry entries like this

Yes I have searched the registry for the autologin and set it up as according to the Microsoft article. And it does autologin but with the error of it not finding the roaming profile. Yes, this machine is joined to a domain.

I agree with you about not necessarily being a roaming profile but a domain profile, I think it's more of a Windows generic answer when it can't find the domain in time so it loads a local profile. But non the less, the issue is still there and the patient monitoring program won't run properly when this happens.

"Additionally, delaying logon does not address the issue. Do you understand this?
You want a pause AFTER the logon not BEFORE the logon."
I dissagree. Something is keeping windows from seeing the domain while loging in, be it a driver for the NIC not loading in time or whatever. Like I said, if we manually wait for the login screen to come up, then press CRTL+Alt+Delete and enter the password, everything works fine, it sees the domain and the monitoring program functions..

Report •

May 7, 2010 at 16:30:46
profile doesn't load until after logon. I believe this is a false trail since if at control-alt-delete you still haven't logged in but that works when you do.

Given what you describe I would suspect services, networking in particular, haven't loaded yet before the logon attempts to take place.

That autologon was meant for a local workstation logon not a domain logon when it first came out.

I can't think of a single thing to delay autologon. You might consider making a logon script cmd file that would be placed in Startup instead of using autologon. Something to the effect like this using visual basic
@echo off
wscript %0\..\NetLogon.vbs

That should provide enough delay for the services to load to then successfully logon.

Another tact to take would be to pare down to bare minimum what is loading on startup.

Report •

May 9, 2010 at 14:30:48
Take a look at Logonexpert autologon software, they declare:

Delayed or scheduled logon and scheduled logoff

"Configure a simple pre-logon delay, or set up an advanced configuration with the built-in scheduler."

Report •

Ask Question