-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AutoBitLocker resource incorrectly identifies Fixed vs Removable drives #11
Labels
bug
The issue is a bug.
Comments
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
May 24, 2018
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
May 24, 2018
Do you have example output where Get-Volume report the wrong type, but CIM reports it correctly? Labeling this as a bug and help wanted. |
johlju
added
bug
The issue is a bug.
help wanted
The issue is up for grabs for anyone in the community.
labels
May 25, 2018
Sure, I found that even my SSD drive connected via USB dongle behaves this way:
|
I see that you referenced this issue in commits. You are welcome to send in a PR resolving this! 🙂 |
Will do once I have time to test the fix, possibly over the weekend.
|
johlju
added
in progress
The issue is being actively worked on by someone.
and removed
help wanted
The issue is up for grabs for anyone in the community.
labels
May 28, 2018
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
May 28, 2018
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
May 28, 2018
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
May 31, 2018
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
May 31, 2018
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
Jun 4, 2018
Fix for issue dsccommunity#11 Readme updates
MartinVokurek
pushed a commit
to MartinVokurek/xBitlocker
that referenced
this issue
Jun 4, 2018
johlju
pushed a commit
that referenced
this issue
Jun 5, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current implementation of AutoBitLocker resource uses
Get-Volume
to differentiate between Fixed and Removable drives. This does not work correctly as there are drives reported as Fixed, yet Bitlocker evaluates them as Removable and therefore applies different GPO settings to them. I saw this for certain HP SAS controllers, VMware can also behave this way (https://kb.vmware.com/s/article/1012225) - seems to be related to the way storage controller reports disk capabilities to the OS.Instead of using
Get-Volume
, I found\root\cimv2\security\microsoftvolumeencryption:Win32_EncryptableVolume.VolumeType
property to correctly report volume types as evaluated by Bitlocker:0 - OS volume
1 - Fixed volume
2 - Removable volume
The text was updated successfully, but these errors were encountered: