I logged in and did the copy / rename, reran the test and set the password to a new password successfully.Īll this suggests that many more options are available. Once again it failed to find a reset file. This time I shut down completely and went into the reset via a bad password. I added a couple more machine reset files and tried a more realistic scenario with a win7 desktop. I did the shutdown -r again and it was fine on this boot. Told the dialog to restart instead of fixing and it booted fine The only odd thing was I rebooted the laptop with a shutdown -r and got a startup error. I renamed the correct pwd file and successfully reset the password to the correct current password. The reset asked for a new password and hint and issued this error (due to the wrong reset file). Then I copied the desktop file, renamed it to userkey.psw and tried again. I logged off and then typed a bad password. I generated keys for two more machines with appropriate renaming. Generated the key and renamed it to HP-Laptop-userkey.psw. I deleted both files to start clean again. So it looked like a simple filename rename would work. This time it did not complain and generated the userkey.psw file. Then I renamed the key to HP-Laptop-userkey.psw and ran the wizard again. In addition to the usual warning boxes, I got this warning: I did a quick format on an old flash drive. So first I wanted to see if it looked like MS looked at the exact filename. Of course the named folder should work as well and with a copy from the folder to the root eliminate confusion as well. That way I wouldn't have to worry about forgetting to rename the file back back to the obscured version and getting files mixed up. My thinking was that if I need to use a reset, I would copy the appropriate key and rename it back to userkey.psw. Seems like the renaming scheme works fineĪfter thinking about this, I thought that the preferable organization would be to have all files in the root with the names changed.
0 kommentar(er)
