In order to better support our growing community we've set up a new more powerful forum.
The new forum is at: http://community.covecube.com
The new forum is running IP.Board and will be our primary forum from now on.
This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.
Pointing to C:\ServerPool\... in M3
I've just had an interesting support session with someone who upgraded from M2 to M3 and had a folder disappear with lots of data.
Suffice it to say, everything was still there, DrivePool was just not mounting that folder properly and I thought I'd share with everyone why.
If you were pointing an external app to C:\ServerPool\ServerFolders\... in M2 and have upgraded to M3 then I suggest you re-point that app to C:\ServerPool\ServerFolders.Mount\...
The problem happened because that app had created a new folder by itself, without asking the user. C:\ServerPool\ServerFolders\ is now managed by DrivePool in M3, and DrivePool will create / delete / share folders under this directory automatically. So in theory everything would be ok if the app didn't create directories, but since it did, DrivePool couldn't create its own directory because a directory with the same name already existed and so the Dashboard didn't see that particular folder.
Point external apps to C:\ServerPool\ServerFolders.Mount\ if you have to.