Endpoint Encryption

 View Only
  • 1.  Compatibility between Symantec File Share Encryption and Microsoft DFS-R & VSS

    Posted Aug 30, 2016 03:21 PM

    Hi,

     

    We are planning to use Symantec Encryption Management Server (EMS) for managing File Share and Drive Encryption in our environment.  Some of our FIle Servers use Microsoft DFS-R & VSS. I want to know if there are any potential issues or compatiability issues that can arise when used with Symantec File Share Encryption? Any help in this regard will be much appreciated. Thanks.



  • 2.  RE: Compatibility between Symantec File Share Encryption and Microsoft DFS-R & VSS

    Broadcom Employee
    Posted Sep 01, 2016 09:15 AM

    hi,

    I can confirm that dfs/dfsr is compatible with File Share Encryption.



  • 3.  RE: Compatibility between Symantec File Share Encryption and Microsoft DFS-R & VSS

    Posted Sep 01, 2016 12:11 PM

    Hi W-D,

     

    Many thanks for your reply. Much appreciated. Finally a ray of hope that this forum is not indeed dead :)

     

    Do you also have any idea about File Share Encryption compatiability with Volume Shadow Copy (VSS) as it is also being utilized on the servers and we want to ensure before implementing that there aren't any potential compatiability issues?

     

    Thanks.



  • 4.  RE: Compatibility between Symantec File Share Encryption and Microsoft DFS-R & VSS

    Broadcom Employee
    Posted Sep 02, 2016 08:00 AM

    Regarding VSS, we do not have anywhere documented that File Share Encryption can work with that or not, so I would say this was not tested and we cannot offically say it is supported. I would suggest that you raise an official support ticket with Symantec and raise this question.



  • 5.  RE: Compatibility between Symantec File Share Encryption and Microsoft DFS-R & VSS

    Posted Sep 02, 2016 08:13 AM

    Got it w-d. Any idea about compatiability of Drive Encryption with VSS? Is the below link a proof that they can't work together or the newer versions have fixed this problem as this article is from 2010. 

     

     

    https://support.symantec.com/en_US/article.TECH132826.html