Windows XP autologon tweak - question

[dadoph]

I'm trying to figure out how to tweak the Autologon registry entry in XP. Basically, if set, this will automatically log a user on as soon as he/she logs out. I am using this in a student computer lab in conjuction with a "clean up" program that will undo whatever the previous user has done.

So, how it's supposed to work is this: User steps up to the computer, logs into the app that is running on the computer, does their work, whatever.

Then they log out of the app, which then automatically logs out of Windows, immediately logs back into windows and presents the application's login window for the next user.

During that Windows logout/login sequence the clean up program is supposed to undo whatever the user has done.

Problem is, the clean up program has to wait until the logout process is finished, open files closed, etc. However, the Autologon happens so fast that the clean up never happens.

If I do a restart rather than logout, it works fine. If I disabled autologon, wait about 10 seconds and then log back in, it works fine.

So, question is, is there a way to slow down the autologon process to allow open files to be closed and the clean up to happen?

 

[dadoph]

I know, bad form to reply to your own post. But since I haven't gotten any responses I thought I'd give it a one time bump. Thanks.

 

[Ichinisan]

For me, that registry setting simply logs in automatically when the computer is first booted. If I log off, it stays on the Welcome screen until I log-in again manually.

 

[ND40oz]

Use a logoff script that runs on logoff. You can put a pause in it for however log you need it to be for your cleanup to run.

 

[GeekDrew]

Originally posted by: ND40oz
Use a logoff script that runs on logoff. You can put a pause in it for however log you need it to be for your cleanup to run.

I was going to suggest that, but if the cleanup script waits until the person is logged out, that won't necessarily work.

 

[ND40oz]

Originally posted by: GeekDrew

Originally posted by: ND40oz
Use a logoff script that runs on logoff. You can put a pause in it for however log you need it to be for your cleanup to run.

I was going to suggest that, but if the cleanup script waits until the person is logged out, that won't necessarily work.

True, if that's the case, maybe you can use a cleanup that you can kick off with the logoff script.

 

[GeekDrew]

Originally posted by: ND40oz

Originally posted by: GeekDrew

Originally posted by: ND40oz
Use a logoff script that runs on logoff. You can put a pause in it for however log you need it to be for your cleanup to run.

I was going to suggest that, but if the cleanup script waits until the person is logged out, that won't necessarily work.

True, if that's the case, maybe you can use a cleanup that you can kick off with the logoff script.

Indeed.

 

[pcgeek11]

Can you just set the clean-up program to have it execute with the autoexec.bat file before the login... I would think the autoexec.bat runs complete before the auto login is started.

pcgeek

 

[dadoph]

Unfortunately, I don't think I can solve this with a script. The program I'm using is "Clean Slate" from Fortres. Clean Slate does the cleanup, either at logoff or on a restart, but can only do so after all files are closed. Using the restart option works fine, but I don't necessarily want or need to have these lab computer rebooting 100 times per day. Clean up at logoff works too, but only if you let it wait for X seconds while files are closed. The other application that we're using is a custom app (VB and SQL backend), that requires the students to log into the app. They are then presented with a predefined set of programs (IE, Word, etc) that they are allowed to use. The app also tracks which applications they use and then gives them "credit" toward required study hall hours, depending on how they were using the computers. When the log out of the application, it also issues a Windows logout for the purpose of letting Clean Slate do its thing. It then autologons immediately, runs the app and waits for the next user. Problem is, the logout/login happens so fast that Clean Slate never gets a chance to clean up.

 

[GeekDrew]

OK... so what is the problem with it logging in quickly? What I'm trying to ask -- is the problem with logging in, or with the program starting again? If letting it login is OK, but the program cannot start, then you could run a login script that just forced a wait for X seconds, run the script asynchronously, and then the program would theoretically not start until after the script is done.

At least I've done that before with NetWare eD/AD environments, and I'm fairly certain that would work in an AD only environment, *if* the problem is with the program execution, rather than the profile locking.