none
FDD unknown protector state RRS feed

  • Question

  • I'm hoping someone has seen this before and can help me out here.  For some reason our laptops we're encrypting with Bitlocker all show up as non-compliant if they have an FDD.  They drive is encrypted, but MBAM sees the protector as unknown, even though they're password protected.   I'm not sure if it's a bug in bitlocker or if I missed something.  The GPO is set to require a password, but allow auto-unlock.


    Volume F: [Label Unknown]
    [Data Volume]

        Size:                 Unknown GB
        BitLocker Version:    Windows 7
        Conversion Status:    Unknown
        Percentage Encrypted: Unknown%
        Encryption Method:    AES 256 with Diffuser
        Protection Status:    Unknown
        Lock Status:          Locked
        Identification Field: Unknown
        Automatic Unlock:     Disabled
        Key Protectors:
            Numerical Password
            Password

    The Protector state shows up as "unknown", and the compliance status details shows that "An unknown error has occurred.





    Wednesday, April 22, 2015 5:51 PM

Answers

  • Hi J.Runyon,

    Would you please share more details of the issue ?
    When did the issue start to occur ?Did the MBAM work correctly before ?Have you checked the status from the client ?
    Will only this specific machine come across this issue or all the machines?
    Have you made any modifications to the machine ?

    If this is the first time to use the MBAM,we can refer to the following link to configure the MBAM
    Planning for MBAM 2.5 Group Policy Requirements
    https://technet.microsoft.com/en-us/library/dn645338.aspx

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Thursday, April 23, 2015 5:32 AM
    Moderator
  • Ben, please clear up what FDD would stand for. Floppy disk drives? In a laptop?

    And also quote the output of

    manage-bde -status c:

    launched at the command line of the laptop.

    Friday, April 24, 2015 7:37 PM

All replies

  • Hi J.Runyon,

    Would you please share more details of the issue ?
    When did the issue start to occur ?Did the MBAM work correctly before ?Have you checked the status from the client ?
    Will only this specific machine come across this issue or all the machines?
    Have you made any modifications to the machine ?

    If this is the first time to use the MBAM,we can refer to the following link to configure the MBAM
    Planning for MBAM 2.5 Group Policy Requirements
    https://technet.microsoft.com/en-us/library/dn645338.aspx

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Thursday, April 23, 2015 5:32 AM
    Moderator
  • Ben, please clear up what FDD would stand for. Floppy disk drives? In a laptop?

    And also quote the output of

    manage-bde -status c:

    launched at the command line of the laptop.

    Friday, April 24, 2015 7:37 PM