Are you talking about OpenManage Server Administrator or which OM?
You can do it on commandline as well.
C:\Temp>racadm get bios.SysSecurity.SecureBoot [Key=BIOS.Setup.1-1#SysSecurity] SecureBoot=Disabled
C:\Temp>racadm set bios.SysSecurity.SecureBoot Enabled [Key=BIOS.Setup.1-1#SysSecurity] RAC1017: Successfully modified the object value and the change is in pending state. To apply modified value, create a configuration job and reboot the system. To create the commit and reboot jobs, use "jobqueue" command. For more information about the "jobqueue" command, see RACADM help.
C:\Temp>racadm get bios.SysSecurity.SecureBoot [Key=BIOS.Setup.1-1#SysSecurity] SecureBoot=Disabled (Pending Value=Enabled)
You need to create a job now and place it into the queue and on next server reboot the configuration job will be executed.
Be carefull... a Windows Server OS will not boot any more if you tooggle from BIOS into UEFI mode after its installation.
If you run vSphere ESXi it will cause no problems. Keep in my that you need to switch from SHA1 to SHA256 within the Adv. Settings option under BIOS->Security->Adv. when dealing with a modern vSphere 7.0.x (ESXi/vCenter)
Your 13Gen Server is a little bit older. Because you already mentioned that you runs Windows Server 2012R2 i would like to share some expierence that after we enabled SecureBoot some Windows Appliaction doesnt work any more. Funny error message occures and we have disabled this feature again. I have no clue if it does make any difference if you have enabled it from the beginning or later.
Origin3k
4 Operator
•
2.4K Posts
0
June 4th, 2022 08:00
Are you talking about OpenManage Server Administrator or which OM?
You can do it on commandline as well.
You need to create a job now and place it into the queue and on next server reboot the configuration job will be executed.
Regards,
Joerg
DELL-Shine K
4 Operator
•
3K Posts
0
June 5th, 2022 21:00
Is your BIOS in UEFI mode? If not can you change to UEFI mode and check whether secure boot option can be enabled
Origin3k
4 Operator
•
2.4K Posts
1
June 5th, 2022 23:00
Be carefull... a Windows Server OS will not boot any more if you tooggle from BIOS into UEFI mode after its installation.
If you run vSphere ESXi it will cause no problems. Keep in my that you need to switch from SHA1 to SHA256 within the Adv. Settings option under BIOS->Security->Adv. when dealing with a modern vSphere 7.0.x (ESXi/vCenter)
Regards,
Joerg
Origin3k
4 Operator
•
2.4K Posts
0
June 6th, 2022 03:00
Your 13Gen Server is a little bit older. Because you already mentioned that you runs Windows Server 2012R2 i would like to share some expierence that after we enabled SecureBoot some Windows Appliaction doesnt work any more. Funny error message occures and we have disabled this feature again. I have no clue if it does make any difference if you have enabled it from the beginning or later.
Regards,
Joerg
DELL-Marco B
Moderator
•
4K Posts
0
June 6th, 2022 04:00
Hello Moonlanding,
thanks to contact our community. Please let us know if those answer can helps.
Thanks
Marco
MoonLanding
1 Rookie
•
19 Posts
0
June 6th, 2022 10:00
Thanks for the help. Sorry for the delay in responding. We are using OpenManage Server Administrator on the server.
Do you happen to know why the setting option is grayed out on this server?
MoonLanding
1 Rookie
•
19 Posts
0
June 6th, 2022 10:00
Thanks for this information. No vSphere on this server.
MoonLanding
1 Rookie
•
19 Posts
0
June 6th, 2022 10:00
Thanks for the help. Under Boot Mode, it is set to BIOS. I presume then that setting this to UEFI is a prerequisite to setting Secure Boot.
MoonLanding
1 Rookie
•
19 Posts
0
June 6th, 2022 10:00
Thanks!