My issue is transfering files with long path names or where I have access denied in the Storage Migration Service.

Error "Couldn't transfer storage on any of the endpoints" and "Check if the source device is online - we couldn't access it."
Transfer validation failed. ErrorCode: 40961
As to this URL:
https://docs.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues#error-couldnt-transfer-storage-on-any-of-the-endpoints-and-check-if-the-source-device-is-online---we-couldnt-access-it

But if I use Robocopy I can copy these files with long path names or if I get access denied.

May we have the same possibilities?

In my SQL server I got 6 drives:
c: local drive
D: Data
L: Log
S: system databases
T:Temp database
B: backups
and recently I started to get a warning from scom about 100% logical fragmentation on disk L and disk T but they are both 10 GB space but only 100MB in use...

Official support for running ReFS on iSCSI san volumes on enterprise san.
There are so many reasons for running ReFS over NTFS, it's a shame it's not officially supported on SAN storage volumes.

I just renamed a top level directory on 5 of our file servers. There is 40TB of data across all these servers. Renaming each folder took an abnormally long time, but eventually finished. Come to find out, Windows reset the NTFS permissions on the folder. I did this same operation on two 2008r2 servers and it worked just fine. Windows should not being changing permissions on a simple folder rename

More Details can be found on this Technet post.

https://social.technet.microsoft.com/Forums/en-US/4147d167-86d8-4e77-b470-86b5af34f6a4/2012r2-renaming-a-folder-causes-ntfs-permisions-to-reset?forum=winserverfiles

Currently there are only blocking apis for querying the file system (enumerate list of files in a directory, get names etc)

This is problematic when disks are asleep, remote, slow etc

Adapt Storage migration to support live conversion from VHD to VHDX on running VM and from dynamic to fixes and vice versa.

As detailed in this KB article from March 2014 (https://support.microsoft.com/en-gb/kb/2938148) the Grant-DFSNAccess cmdlet requires use of the GUI to work, or there is a workaround of using the old dfsutil command instead.

Is it possible to have this fixed so that we can use native PowerShell to configure the DFS environment?

The traditional read only chkdsk is finding errors and then recommends running the new chkdsk /scan function. When I run the new /scan function it says there is no problems. Which is it? Details can be found on this Technet post.

https://social.technet.microsoft.com/Forums/windowsserver/en-US/4f41c221-960f-4f6b-9568-28b22c1740ba/chkdsk-scan-has-a-bug?forum=winserverfiles&prof=required

From Windows Explorer, besides every volume letters, we have the volume (network location) Type: Local Disk / CD Drive / Clustered Disk / Network Drive. Would like to have a simple powershell command get it.

Forever you Need third Party Tools too easy enlarge or reduze the size of the System Partition. I think it`s time too integrate this in a easy way into the Basic Server Disk Management. (Also if there is no space next to the System Partition)

Allow for Persistent Mounts at the OS level for the NFS Client instead of making the mount like a mapped drive that is done in user context.