I've done the first part of this, before, so I will comment only on that. I wrote a script for our help desk to remotely reboot PCs into Safe Mode. editing the boot.ini file is the only way, as far as I could find out. I looked around; nada -- which makes sense. Windows doesn't decide to hit safe mode until the boot menu, so that's where you tell it to do so. The safe way of doing it (the one I used) was to stick to minimal changes in the boot.ini, and backup a copy first. Reverting changes is a matter of recopying the original file back, which I did with a PendingFileRaname. That way, your file is replaced at the first available opportunity (before logon). For the logon, I used the autoadminlogon (yes, by editing the registry) which I have used without a problem many times. I wasn't clear if that was the method you have, but I find it best. Don't be afraid of the registry - just stick to simple, verified changes, and it's pretty reliable. As far as the last part, getting your second-half script to run is a matter of putting it (or a reference to it) in one of the startup folders, or one of the runkeys in the registry. If you use the HKLM Run key, your script will run before logon completes, but should do fine. If you opt for running it after logon completes, you might be better off putting it in your admin account's Start Menu Startup folder -- as it's easier to write that than try to get into HKCU for a not-logged-in user. hth
