Configuration Protection USB 3.0 Root HUB blocked

Hi Daniel,

We only really needed to block devices, not ports, so we changed our CP policies to:

• Port Control > Physical ports: Allow
• Storage Control > : Restrict

This then opened up the ports but still blocked the devices, unless they were whitelisted.

Seeing as this isn't what you need then this won't help you.

The only other suggestion I have is that you talk to Sophos technical support...

We've got a different Configuration Protection case open with Sophos support at the moment (issue with Hybrid Control conflicting with our SSL VPN NIC, and VMWARE NIC's) and Sophos tech sent us a custom XML policy for CP.

Using the SafeGuard Management Center we had to sign the XML file, then drop the signed file into a folder on the target end-point, run "SGMCmdIntn.exe -i" from the command line on the end-point and then reboot it.

Unfortunately this custom policy file didn't fix our problem, but they may be able to do something similar for this defect?

Just remember that CP isn't truly a Sophos module; it's a Safend product. So often you'll need to work your way up the support chain to get the case up to GES (Global Engineering Support) and then onto Development, who in turn may pass onto Safend.

A tip here is to provide Sophos tech support with every single inch of detail from the outset. Otherwise GES will downgrade the call back to normal Sophos tech support, who then have to re-escalate the case back to GES. This then goes on and on.

So get:

1. An SGN trace of the issue: (http://www.sophos.com/en-us/support/knowledgebase/108081.aspx)

2. Details of the port

3.Windows System Configuration file

4. Output from Sophos SDU: (http://www.sophos.com/en-us/support/knowledgebase/33533.aspx)

5. A video helps if you can. (They never seem to believe or understand what the problem is, so a picture paints a thousand words) ;)

Lastly, I'm not sure if I posted the defect number in this thread but you can always call into Sophos support and ask them if DEFECT #59405 is still outstanding.

Regards,

John

Hi Daniel,

We only really needed to block devices, not ports, so we changed our CP policies to:

• Port Control > Physical ports: Allow
• Storage Control > : Restrict

This then opened up the ports but still blocked the devices, unless they were whitelisted.

Seeing as this isn't what you need then this won't help you.

The only other suggestion I have is that you talk to Sophos technical support...

We've got a different Configuration Protection case open with Sophos support at the moment (issue with Hybrid Control conflicting with our SSL VPN NIC, and VMWARE NIC's) and Sophos tech sent us a custom XML policy for CP.

Using the SafeGuard Management Center we had to sign the XML file, then drop the signed file into a folder on the target end-point, run "SGMCmdIntn.exe -i" from the command line on the end-point and then reboot it.

Unfortunately this custom policy file didn't fix our problem, but they may be able to do something similar for this defect?

Just remember that CP isn't truly a Sophos module; it's a Safend product. So often you'll need to work your way up the support chain to get the case up to GES (Global Engineering Support) and then onto Development, who in turn may pass onto Safend.

A tip here is to provide Sophos tech support with every single inch of detail from the outset. Otherwise GES will downgrade the call back to normal Sophos tech support, who then have to re-escalate the case back to GES. This then goes on and on.

So get:

1. An SGN trace of the issue: (http://www.sophos.com/en-us/support/knowledgebase/108081.aspx)

2. Details of the port

3.Windows System Configuration file

4. Output from Sophos SDU: (http://www.sophos.com/en-us/support/knowledgebase/33533.aspx)

5. A video helps if you can. (They never seem to believe or understand what the problem is, so a picture paints a thousand words) ;)

Lastly, I'm not sure if I posted the defect number in this thread but you can always call into Sophos support and ask them if DEFECT #59405 is still outstanding.

Regards,

John