I would add the following additional questions:
- Is the system using a dock?
- Are the ports USB 2.0 or USB 3.0? (Specs from Samsung show 2x USB 3.0 ports as the only USB ports)
- Are the devices USB 2.0 or USB 3.0?
- Have you checked to make sure the USB 3.0 drivers are up to date and active, and that the 3.0 root hub is still active after installing SED?
It is not expected behavior that SED would block device drivers, but it looks like the system you referenced only has USB 3.0 ports, so the policy applied for the system might be a factor. When the policy is set to make external drives read-only, it should still initialize them, notify the user that they are going to be set as read-only, and be accessible. It is possible that if the policy is setting them to read-only (or otherwise trying to manage the external drives), and they are on USB 3.0 ports that it could cause some issues, since USB 3.0 is not supported as of yet with SED.
If there is no policy applied to the external drives by SED, I am not sure what might be causing that sort of issue, as the drives should mostly be ignored. If the policy is set to allow users to encrypt/decrypt external drives, you may want to try disabling that also just in case.
Thanks in advance for your answers!
-Mike