Hard coded right now. A config file would be nice.
Could remove all menu items if you need. Would you like to keep the restart option?
Removing all items would be perfect. As long as the reboot command works then we are in business. For the admins who need to debug a faied imaging attempt I could just inject both PEshells into the PE image and have a trigger in our script that will kill the currnet locked down PEshell and start the new PEshell you created.
The other option for locking down the PXE Environment was to password protect the bootprocess. I tried the Secure PXE Image during SP2 and it never worked. Is this fixed? I wrote a quick little autoit script that prompts the user for a password which is pre populated in the registry at bootup. ( string pieced togather by location specific information ). If entered wrong thee times it just kicks off a reboot. This In combination with the modified locked down PEShell will be a sweet combo.
Thanks again! ![]()
You don't have to kill PEShell, in fact you cannot without causing a reboot. You can however, have a PEShell.exe, PEShell1.exe and run them on top of eachother. The last one run is the one you can click on.
For the password protected PXE option, please start a separate community thread in OSD subcommunity about this. It is probably resolvable.
Thanks for the Info. Having two PEShell's in the WINPE image will be perfect. Are you going to post the Locked down PEShell in this Comment thread, or are you posting another article?
I'm looking forward to the locked down PEShell. This will be very useful for other folks in the educational environment.
The PEShell with no items in the menu should be on the download page now. It is named as such, so you will have to rename them as needed.
Which download page?? I did not see it posted @ the WinPE Add-on: Updated PEShell.exe for 8.8 link above.
Thanks again.
Sorry...all documents have an approval process. I submitted it Monday night, but it wasn't approved until this morning. Look now.
Sweet!!! It worked perfect. We added a passcode into our WINPE image which will launch the ADMIN PE shell when needed. Thanks again!!
| ||||||
Sweet additions Jared! How exactly are you making additions to the PEShell? I work in a school environment and we did alot of custom scripting which tags the PE registry with some sensative data for a brief time during the imaging process. Would it be possiable for you to build functionality into the PEShell perhaps that would accept an argument which would disable the GO Menu. Then all we would have to do is edit the .ini file which launches the Shell and add the pertcular argurment to disable it. That would be stellar!
We would like to disable access to the command prompt which allows students to launch tools like regedit. This would really help lock down the PE environment and prevent students from causing issues. This would also prevent the students from checking out the sysprep file that's injected which contains clear txt passwords!! I tried renaming the PEShell which prevented it from launching although once the shell is dead I'm unable to reboot the computer!!
Thanks in advance!