Base de connaissances

iDRAC7 - Keytab File Exists is Failed in Active Directory Test Setting

Article Summary: This article provides information on iDRAC7: Keytab file exists is Failed in Active Directory Test Setting.


If the iDRAC7 is configured for Active Directory authentication the Keytab file exists is Failed in Active Directory Test Setting.


The issue occurs after iDRAC FW update and with a custom SSL certificate installed in iDRAC.

After update, credential vault where Keytab file is stored cannot be mounted.

The issue exists on iDRAC Firmware 1.30.30.

It happens only if there is a custom SSL certificate installed in iDRAC. By default iDRAC has a default certificate which is re-created on every firmware update, but if a custom SSL certificate is installed, this custom certificate is not touched. The problem is in the build process, every build is signed with a different key. That causes the credential vault to be encrypted with one key and not able to be decrypted when the firmware is upgraded because the key was changed.

This was fixed in iDRAC7 Firmware release 1.40.40.

Ensure that the iDRAC7 Firmware is at version 1.49.40 or higher.

For more information see the iDRAC7 Release Summary


Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution. Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure or advice set out in the Quick Tips.

ID de l'article : SLN266074

Date de la dernière modification : 09/18/2013 12:00 AM

Noter cet article

Facile à comprendre
Avez-vous trouvé cet article utile ?
Oui Non
Envoyez-nous vos commentaires
Vos commentaires comportent un caractère non valide. Les caractères spéciaux refusés sont <> () &#92;
Désolé, notre système de collecte des commentaires est actuellement indisponible. Veuillez réessayer ultérieurement.

Merci. Vos commentaires ont été envoyés.