The only problem that i see with this configuration is that there services account provided to start the SnapDrive service. Which needs to be a local administrator and an administrator on the netapp storage.
1. so solution to this is either join netapp to the domain (which in your case seems is not happening)
2. create a common user with common passwords on both systems and add them to the local administrators groups. this works for me.
Regarding SME, could work, don't seem why not. but i haven't tried it in any environment.
I know that this workaround works fine with SnapDrive alone, but in the case of SME, it seems that the SME service needs special access rights in order to manipulate the Exchange data (for instance copy & truncate the logs), access rights which come come from the AD and I would like to know if the configuration abobe (SME executed as the AD user and SnapDrive with HTTPS) is supported of not and if anyone saw it work ?
Re: SME & SnapDrive authentication configured differently for security reasons