The reason we would like to do this is becuase we have a unknown number of machines that may have this issue and it would just be time saving while on the phone for users that just cant hit F8 in time. We have found a way to edit the boot.ini via script to boot into safe mode on next boot. It easy to push the script into the pc over the network. However the next issue is we realized the the only way to log into safe mode is with the admin account. The users on our networks wont be able to log in as there is no local admin account for anyone other than networking and techs. We tried running the repair in safemode with networking however, this doesn't repair the issue properly. We are talking over 5000+ machines with an unknown number with this issue. We are trying to keep from forcing the need to physically bring in the machine for us to trouble shoot and issues with users switching to exchange(only option available) after the server change from NT to Server 2003. Its a fun time needless to say has a number of users rush out to make sure they have W2000 or XP in order to be able to connect and get upset that they must switch to exchange for email instead of dos based pine, netscape(yes some have that still), and old versions of outlook. Well another day and I'm off to work to brainstorm some more. WildOptic