Error in Configuring Kiosk Mode via Intune - Event ID 404 and 454

Jamal Talibi 0 Reputation points
2023-07-26T08:10:35.46+00:00

Hello ,

I hope you are all doing well. I am facing an issue while trying to configure Kiosk mode via Intune. However, I keep encountering the following error in the event logs with event IDs 404 and 454:

Event ID 404: ConfigurationManager GPM: The command failed. Configuration source ID: (F8D00FFB-9890-47DF-9858-B267CEEEAD98). Registration name: (MDMDeviceWithAAD). Provider name: (AssignedAccess). Command type: (Add: from Replace or Add). Encryption service provider URI: (./Device/Vendor/MSFT/AssignedAccess/Configuration). Result: (The mapping between account names and security IDs was not done.).

Event ID 454: ConfigurationManager MDM : statut d'échec de la commande. ID de source de configuration : (F8D00FFB-9890-47DF-9858-B267CEEEAD98), Type d'inscription : (MDMDeviceWithAAD), Nom du fournisseur de solutions cloud : (Policy), Type de commande : (Add: from Replace or Add), Résultat : (./Vendor/MSFT/Policy/Config/Bluetooth/SetMinimumEncryptionKeySize).

Could you please provide some guidance on how to troubleshoot and resolve this issue? Any help or insights would be greatly appreciated

Windows for business | Windows Client for IT Pros | User experience | Other
Microsoft Security | Intune | Other
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Limitless Technology 44,751 Reputation points
    2023-07-26T15:24:35.3133333+00:00

    Hello Jamal,

    Thank you for your question and for reaching out with your question today.

    Hello! I'm glad to assist you with the issue you're facing while trying to configure Kiosk mode via Intune.

    The error messages you are encountering suggest that there is an issue with the configuration settings for Assigned Access (Kiosk mode) in Intune. The error indicates that there might be a problem with the mapping of account names and security IDs or with the configuration for Bluetooth encryption key size.

    To troubleshoot and resolve this issue, you can follow these steps:

    1. Verify Configuration Settings: Double-check the configuration settings for Assigned Access (Kiosk mode) in Intune to ensure that they are correctly configured. Make sure that you have specified the correct user or group for Kiosk mode and that all required settings are properly set.
    2. Review Event Logs: Review other related event logs in the Event Viewer on the affected device. Look for additional error messages or warnings that might provide more context about the issue.
    3. Check Intune Compliance Policies: Ensure that the device is compliant with the Intune policies that are being applied. If the device is non-compliant, it might be causing the configuration failure.
    4. Check Assigned Access Profiles: Ensure that there are no conflicting Assigned Access profiles on the device. Multiple conflicting profiles might cause conflicts and lead to configuration issues.
    5. Verify Network Connectivity: Ensure that the device has a stable and active network connection to communicate with Intune and receive configuration updates.
    6. Update Intune and Device Firmware: Ensure that both Intune and the device's firmware are up-to-date with the latest updates and patches. Outdated software might cause compatibility issues.
    7. Run Intune Troubleshooter: Microsoft provides a built-in Intune Troubleshooter that can help diagnose and resolve common issues. You can run the troubleshooter on the affected device to see if it detects any issues related to Kiosk mode configuration.
    8. Contact Microsoft Support: If the issue persists and you cannot identify a resolution, consider reaching out to Microsoft Support for further assistance. They can help you diagnose the specific issue in your environment and provide tailored solutions.

    Keep in mind that troubleshooting Intune configurations might require in-depth knowledge of the platform and its policies. If you are not familiar with Intune or its configurations, seeking the help of experienced IT professionals or Microsoft Support is recommended.

    I hope these steps help you in resolving the issue. If you have any further questions or need additional assistance, feel free to ask!

    I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

    If the reply was helpful, please don’t forget to upvote or accept as answer.

    0 comments No comments

  2. Crystal-MSFT 53,981 Reputation points Microsoft External Staff
    2023-07-27T01:27:33.7533333+00:00

    @Jamal Talibi, Thanks for posting in Q&A.

    For the first error, it seems the account you set in the xml is unable to find its SID. Please check which account you set and see if it is in your environment. For the second error, as this is not English, I translate it and it seems the issue is with ./Device/Vendor/MSFT/Policy/Config/Bluetooth/SetMinimumEncryptionKeySize. Please check if the value you set is between 1 to 16.

    https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-bluetooth#setminimumencryptionkeysize

    Please check the above information and if there's any update, feel free to let us know.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Jamal Talibi 0 Reputation points
    2023-07-27T12:21:16.07+00:00

  4. Jamal Talibi 0 Reputation points
    2023-07-28T07:23:36.2733333+00:00

    @Crystal-MSFT Thanks for the reply, Please find attached the kiosk configuration profile Sans titre.png


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.