eduncan911

I just did the same thing (completely different hardware; but, the same steps).
 
Yes.  It will find and have the actual full Drivepool all setup and active.  As long as the drives are "Online": using the built-in Disk Management application, you can check that they are online.
 
I recommend these steps though: Get the hardware setup first before installing the software.
 
- Deactive license, shut down old machine.
- Install HDDs in new machine, do NOT install DrivePool!!!  Hold off installing any software.
- Go to Disk Management and verify the drives are all "Online."  If they are not, right click on them and select "Online."
- Then install DrivePool, DriveScanner, etc.
 
These are the steps I took and it worked perfectly.
 
The reason why I suggestion this is you can only bring a single HDD "online" at a time.  Even though I didn't try it; I would not want DrivePool complaining that I only have 1 HDD out of my pool.  It may go wacky or whatever.
 
So, I decided to get the hardware setup first before installing the software.
 
Note: DrivePool will try go through a bit "Checking" phase.  After it is done, it will start to Balance with the DEFAULT settings.  If you are like me, you may have very custom settings setup in your Balancing.  Get that done first and don't let it start balancing.  The initial checking that happens after installing DrivePool took several hours; so, it gave me plenty of time to get things "Balanced" correctly according to my settings.
 
Scanner will run with defaults.  Mine was set to 3 AM - 6 Am for the work period (I was up until 4 AM working on mine, and wondered why throughput lowered dramatically - it was Scanner that started at 3 AM).
 
As far as virtual machines and DrivePool/Scanner, be warned that SMART access does not pass through Hyper-V to the VMs.  I originally tried to get DrivePool/Scanner all setup on VMs under QEMU (a good native hypervisor under Linux) and W2K12R2 using Hyper-V.  But times I ran into SMART data not being passed, which ticked me off.  It's a Windows/Linux thing.
 
So, I advise setting up the DrivePool / Scanner on the HOST.  If that's Windows 10, that's fine.  That will give you a single Drive Pool drive.  I name mine "A:\", as a throwback to the floppy disk days (if you don't know Floppy Disks, then enjoy your youth!).
 
Once you have that setup, I advise setting up a "Virtual Network Adapter" in Hyper-V for "Internal" only <- if that's possible under Windows 10 (I am using Windows Server 2012 R2, which allows me to do "Internal" network adapters).  Internal creates a private 10 Gbps network that all VMs can use, as well as talking to the host - you ahve to setup the proper IPs and Mask.  The advantage is there is no physical "NIC' used, so you get some great speed without interfering with remote access to the physical machine.
 
With that, setup a "Share" only for your internal private network (mine is 10.16.210.X).  The share will be for your Drivepool drive, open to all anonymous access... And there inlies yet another issue with Windows, true "anonymous" access to a shares is very difficult with so many hoops to jump through at many different security levels.  
 
Anyways, use a Windows Share from your Windows 10 box to your "internal" networking for all of your VMs you have running.

Yep, exactly.  
 
I was actually more concerned about DrivePool reading the existing data.  But now that I think about, you said you are using the hidden NTFS metadata.  Perhaps that's readable no matter the permissions.
 
But yes, and for anyone else reading: if you have custom permissions on your drivepool (e.g. \\SERVER\Users\Mommy, \\SERVER\Users\Child1), then you will want to remove all of those permissions before switching to a new server.
 
Easiest way to do that is to Right-Click at the root of your pool, go to editing the permissions, remove everyone but the defaults.  Once you do that, make sure to click the checkbox for "Replace permissions on all child objects."  that will reset it all.

For licensing, if your'e reinstalling, you'll want to deactivate the licenses prior to moving everything over.  Otherwise, you should be fine, and prompted to "transfer" the license as it's different hardware.
 
 
Aside from that, yeah, you'd want to just pass the disks through, and DrivePool won't have any issues with that.