Secure Boot Violation - Invalid Signature detected

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

During Boot of a computer with Secure Boot option activated in the UEFI BIOS, following error appears :
Secure Boot Violation - Invalid Signature detected. Check Secure Boot Policy in Setup

Environment

Client Automation - All Versions

Cause

In the BIOS settings of the machine, <EFI Network> is at the first position in boot order.

Example :

Computer contacts the Boot Server and receives the BOOTHD file from the Boot Server.
As this file is not signed, error "Secure Boot Violation - Invalid Signature detected" appears.

Resolution

There are 2 possible workaround :

1. Change the boot order in the computer BIOS and do not put <EFI Network> option at the first place
   
   
   If this solution is not possible :
   
   
   
2. On the Boot Server rename the file 
   
   <Install DIR>\CA\DSM\Server\SDBS\var\managedpc\images\dosboot\BOOTHD
   as
   <Install DIR>\CA\DSM\Server\SDBS\var\managedpc\images\dosboot\BOOTHD.OLD
   
   

Additional Information

BOOTHD file is not signed and so not compatible with UEFI BIOS option "Secure Boot"