Troubleshooting
•Host does not support Native Key Provider
•Virtual ICS does not boot due to signature failure
•Booting stops with error "System Integrity verification failed"
•Booting stops with error "Rootfs manifest validation related files do not exist”
•Booting stops with error "Root file system signature verification failed"
•Booting stops with error "No file entries found in the manifest"
•Upgrade aborts with error “ADM23397: This appliance cannot be upgraded to 22.8R2”
Host does not support Native Key Provider
Cause: Key Management is not enabled.
Solution: Enable Key Management in the Vcenter server.
Secure boot is disabled
Solution: Secure boot is mandatory for virtual ICS. Enable secure boot for better security.
TPM/vTPM is in lockout mode
Cause: It could be due to too many consecutive ungraceful shutdowns.
Solution: Once TPM is in lockout state, it will remain inaccessible until the recovery time has elapsed. After 1000 secs, system boots and comes up.
TPM is not attached
Solution: Attach TPM for better security.
Virtual ICS does not boot due to signature failure
Cause: The primary reason for virtual ICS not booting could be that ExtraConfigs are disabled.
Solution: Enable ExtraConfigs in your VMware settings. For details, see Specifying Advanced Virtual Machine Settings with ExtraConfig Elements.
Booting stops with error "System Integrity verification failed"
Cause: If any new files get created or existing files get modified as part of ICS system, these will be detected and prevent booting.
Solution: Securing InitramFS and RootFS feature prevents unauthorized files creation in ICS system. Select “d” to dump diagnostics to see which files are created/modified and Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.
Booting stops with error "Rootfs manifest validation related files do not exist”
Cause: If Securing InitramFS and RootFS feature dependent files are missing, the system is interrupted due to failure in validation of required files.
Solution: Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.
Booting stops with error "Root file system signature verification failed"
Cause: If Securing InitramFS and RootFS feature dependent file contents are modified, the system is interrupted due to failure in signature verification of required files.
Solution: Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.
Booting stops with error "No file entries found in the manifest"
Cause: If Securing InitramFS and RootFS feature dependent files don’t have any content, the system is interrupted due to failure in validation of required files.
Solution: Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.
Upgrade aborts with error “ADM23397: This appliance cannot be upgraded to 22.8R2”
Cause: This error indicates that the upgrade cannot proceed due to insufficient disk space in the boot partition and Factory Reset version is very old.
Solution: Contact Ivanti Support for error.