Why can't I access the encrypted data on my clustered shared disk?

A. If you're having trouble accessing encrypted data on a clustered shared disk, the reason might be that you're using a local profile rather than a roaming profile, and the server by which you accessed the shared disk has failed and another machine in the cluster is now hosting access. When you encrypt a file, the cluster node that provides access creates a certificate (i.e., an encryption key) and stores it in your profile. If the node fails, another node in the cluster will begin hosting the resource, and you'll no longer have the encryption key to access the data. To work around this problem, use a roaming profile or regularly export your encryption keys from the node where you encrypted the data to the other nodes where you might have local profiles.