tcash19

Unless you need some of the newer features, then using 1.3 would be the better option. It's more tightly integrated into the dashboard.
 
However, if you need/want some of the features such as reparse point support, or the File Placement rules, then you should use 2.1. 
 
Also, it's worth noting that the license is valid for either product, and the pool is backwards and forwards compatible.

I have DrivePool installed on two PCs.  A WHS2011, and a Windows 7 pc.  The WHS2011 copy is working fine but when I reboot the Win7 PC DP creates another pool with one of the existing drives.
The Win7 pc has 4 drives + CD.  The boot drive is SSD and is not in any DP configuration.  Drive D (3TB), E(2TB) and F (3TB) are in pool as drive G.  Drives D & E also have some non-pooled data; Drive F is entirely dedicated to the pool.
 
When the pc boots up, DP says that drive D is missing, but what really happens is that DP creates a pool for Drive H and uses drive D for that - thus drive D is missing for pool G.  Pool drive H has one empty folder in it: My Pictures.  Interesting note is that the 'PoolPart.*' folder for the newly created pool H has the old timestamp on it and the old 'PoolPart.*' folder has the current timestamp.
 
To correct the problem, I go into DP and remove drive D from the second pool (H) and then DP finds D available for the original pool (G).  I don't reboot that often and would not swear that it happens every time, but I believe that it does.  No data is lost, as far as I have observed.
 
Just in case it means anything - drive H is normally mapped to a share on the WHS2011 pc, but not the pool created by DP there.
 
H E L P ! !
---
Ted