GHMNE
asked on
How can I bypass the F1 prompt during post?
Hello,
I'm working on getting a print server up and running. I have one SCSI drive installed and it is running Microsoft Server 2003 Std R2. The problem is during POST. After the "Press Ctrl A for SCSISelect Utility" prompt, it tells me to either Press F1 to continue or F2 to run the setup utility. I know on other servers, usually HP ones, that you can turn this prompt off within BIOS. I am not seeing this option available. Any ideas? My concern is that if the server needs to reboot, no one will be around to hit the F1 key to get it up and running. And yes, the server is off site.
Thanks!
I'm working on getting a print server up and running. I have one SCSI drive installed and it is running Microsoft Server 2003 Std R2. The problem is during POST. After the "Press Ctrl A for SCSISelect Utility" prompt, it tells me to either Press F1 to continue or F2 to run the setup utility. I know on other servers, usually HP ones, that you can turn this prompt off within BIOS. I am not seeing this option available. Any ideas? My concern is that if the server needs to reboot, no one will be around to hit the F1 key to get it up and running. And yes, the server is off site.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tried the utility, didn't realize is was only a diagnostic tool. Is my best way to install the System Config Utility before I install the server OS? I'm just not sure what the issue could be why it's prompting for F1 or F2.
ASKER
Ok, I figured out that I need the BIOS System Config Utility. I'm just searching for it on Dell's site. After that, I'm just going to reimage and install that first.
I disabled the PXE boot and it worked....
ASKER