Migration to Windows Server 2012 R2 Essentials - some troubles

[lossen]

Hi, today I made migration of home server from WHS2011 to 2012 R2 Essentials.

Same server, same hardware, only new system ssd instead of old 5400 RPM hdd.

Regarding earlier posts of this forum (http://community.covecube.com/index.php?/topic/1645-migrating-pool-to-new-machine-sanity-check/) http://community.covecube.com/index.php?/topic/1929-whs-2011-to-windows-server-2012-r2-essentials/?hl=migration&do=findComment&comment=13432

my procedure have this steps:

 

1. Deactivate licenses for drivepool and scanner

2. shutdown server

3. replace ssd/hdd

4. start server, check that 2 HDDs (main pool drives) are online

5. install new drivepool 2.1.1.561 (on previous was 1.x.x) and activate it

6. pool was recreated but get another letter

7. change the correct drive letter

8. run the WSS Troubleshooter http://dl.covecube.com/WssTroubleshoot/Release/download/Wss.Troubleshoot_2.0.0.1.exe   to re-share the folder

9. restart server

10. and here is trouble - in server dashboard -> storage -> server folders is only standart shares (like Users, Company, Client Computer Backups ...) but in Computer Management -> Shared Folders -> Shares I see all my shares as it was.

 

 

How to correct that and make all shares to be visible in Server Dashboard ?

[Christopher (Drashna)]

In the dashboard, try creating new shares where these shares exist.  

 

If that doesn't work, let me know

[lossen]

thanks, Christopher,

that works.

 

Another one question - earlier in drivepool 1.3.xx I can see size of each pooled folder in dashboard - drivepool main screen.

Now, in 2.1.1 - I can't.

Only one possible way I found - check in explorer size of each subfolder under X:\ServerFolders and keep in mind about duplication.

 

Is any easy way to know folder size ?

[Christopher (Drashna)]

Glad to hear it. 

 

 

As for the 1.3 version, ..... ugh.... 

 

This relied on the Windows Search service, and info from it. We've depreciated it, because it was, really, too unreliable. 

However, this is something that we'd like to re-implement in the future, but likely, with our own software (so we can ensure it's reliable)

 

 

In the meanwhile, there really isn't a good way to do this.