The blocking and whitelisting appears to work but nothing I do will restore write or copy access for the whitelisted devices. I can see the files on the drive, browse folders etc but cannot open anything, nor copy or edit files............... Thoughts?
Very nice video , thank you . I cannot achieve similar results . I can indeed block devices by preventing installation of drivers matching setup classes but I am unable to allow exceptions for USB devices (VID , PID , Instance path etc ... ) .
Thank you for the great video. I'm having a terrible time with device control. How can I block all USB sticks for user A on a shared device and allow a specific USB stick for user B? Is this possible?
The blocking and whitelisting appears to work but nothing I do will restore write or copy access for the whitelisted devices. I can see the files on the drive, browse folders etc but cannot open anything, nor copy or edit files...............
Thoughts?
Very nice video , thank you . I cannot achieve similar results . I can indeed block devices by preventing installation of drivers matching setup classes but I am unable to allow exceptions for USB devices (VID , PID , Instance path etc ... ) .
Hello, did you manage to fix the issue ?
@@clementcastel7958 Yes , I have used another approach to create a policy based on a reddit post Block access to USB storage devices with whitelist
nice video thank you
Great Video. I was looking to create a policy to Block All USB Storage excluding a list o devices. This will help
Thank you for the great video. I'm having a terrible time with device control. How can I block all USB sticks for user A on a shared device and allow a specific USB stick for user B? Is this possible?
Include / exclude groups should work. But user based policies is always a bit of a struggle in terms of timing and reliability.
Thanks for the video - would be even better if you demoed a blocked device that then get’s approved - not work for me so far either.
Remember that the reusable settings are still in preview. I can confirm, that blocking class GUID works perfectly fine.
You should have taken it step by step and created a policy in the demo, this would have been a little more easier to know