1 of 1 people found this helpful
It sounds like DLP is inspecting the file when written to DVD. You may want to try whitelisting the application process that is writing the image and see if that fixes it. You might be able to be more granular with it but hard to say without knowing what version of DLP you have and/or what protection rules are enabled.
We were able to DISABLE DLP on a machine here and burn the vmware images successfully. MD5 sums matched perfectly. DLP is most certainly screwing up these files. I've told my coworkers to no longer trust any DVDs burned with DLP running on them (which is all unfortunately).
If you are using classification tagging, one of the methods used to tag the file itself can change the hash of the file, because the tag modifies metadata properties of the file.
There is a way to select which methods are used for tagging content in the DLP client configuration policy. Try disabling the "