This little thread has been going on for a while now. You can install SME on just EX01. When you launch SME for the first time (or subsequently) just point it to the server EX01, not the DAG name. Now as you know the DAG DB and log paths MUST be the same on all nodes of the DAG where the DB copy resides. Start off with suspending or removing the DB copy of any DBs between EX01 and EX02 (http://technet.microsoft.com/en-us/library/dd335158.aspx). Create the appropriate paths for the DBs and logs on each server including drive letters to match the LUNs attached to EX01. Dismount the DBs and manually move the DBs and logs to the new paths. Resume or add the database copy configuration previously established. Now run SME configuration wizard and again point it to just EX01, not the DAG. The wizard will go through and see the paths as they are and meerly record the configuration in an XML file. At the end it will show that it is dismounting and moving in the checklist, but it won't actually do this since the target configuration matches the current config.
Now with this design SME will backup EX01 and take snapshots of EX01 DBs and DB copies, but the problem with this configuration is that you will have a problem with log truncation on EX02 since SME will not back that server up. Not exactly sure how you want to handle that, maybe turn on circular logging or use Windows Backup on EX02. I have not configured SME with this specific model so I honestly don't know how the logs will be handled on EX02. It is possible that as SME truncates logs on EX01 that they will be deleted on EX02, but that brings up restore issues on EX02 with up-to-the minute restores. Might want to play around with this in a lab first.
