Bug Age: >5 Years
https://social.technet.microsoft.com/Forums/exchange/en-US/3a0e7e9c-f1ea-4324-8a17-f4c447efcbb0/some-storage-cmdlets-do-not-work-under-winpe?forum=winserverpowershell

Also mentioned as a known problem in the talk OS Deployments using WinPE + PowerShell and WindowsImageTools panel by David Jones at the 2018 Global DevOps and PowerShell Summit

Reported by me on the PowerShell GitHub in 08/01/2019 at which subsequent to which I was directed to report this here.
https://github.com/PowerShell/PowerShell/issues/7429

Steps to reproduce

Follow this: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-adding-powershell-support-to-windows-pe

Attempt to use:

Clear-Disk

or

Format-Volume

Expected behavior

Clears and or formats the disk in question

Actual behavior

Unspecified Error 0x80004005

Since Windows 10 1803 there is no image preview in Explorer. However, some people need this feature for their work. I find it particularly annoying that this will not work even if "On Demand File Access" is disabled.

still true on 1910

Add a cmdlet in powershell to let administrators peek into the status of work folders for current user or all users on this computer.

Today i have to look at file attributes and the exitcode in the registry.

When a user has almost 300 000 files in its Work Folder it seems that the control panel applet does not update as it should. The general feeling is that the computer is busy with going through the filelist rather than informing the user about what its busy doing. This leads to frustration from the enduser and an incertainty about the current syncstate.

We are currently using Windows 10 1803 Edu 64-bit on our clients, is this better in newer versions?

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?

Support for Samba, NAS, SAN DESTINATION! Can't believe this is not one of THE biggest feature requests. We have so many times where we may be, wait for it... migrating AWAY from Windows Servers onto NAS devices. We still use and migrate to Windows Server 2016 and 2019, but we also have need to do the same migrations TO destinations that are NAS devices.

Storage Replica is not currently available for Dynamic disks, that makes it non usable with spanned disk

Would be nice to have a faster Delta Sync for the Storage Migration Service. It takes many hours to run the delta sync.

When selecting shares to transfer within Storage Migration Service's Transfer Data section, all shares are selected by default. We have 435 shares and would like to transfer just one.

The cutover portion of the storage migration appears to use local accounts. We follow the CIS baselines and network access/remote login with local accounts is disabled. It would be nice to be able to use a domain account that has local admin rights to do the cutover.

Storage Replica limitation is very tight in Standard Edition - this should be increased. 2TB is very little in any single node, especially as price/tb continues to fall rapidly, having a limit tied to TB's is like putting an expiry date on its usefulness. Perhaps limiting to number of nodes will be more effictive limitation ie, 2 or 3 nodes?

Windows Storage Migration Service Errors with Couldn't transfer storage on any of the endpoints.

Has anyone run into this and what was the fix?

Make it possible to have different file systems between source and destination servers. So we can easily upgrade file shares to run on ReFS instead of NTFS.

During testing of doing a storage migration from a Windows Server 2008R2 to a Windows Server 2019. Everything works successfully until we reach the cutover phase. During Validation the following failure is listed.

"We can test token filter policy on the destination computer"
Fail: Access is denied

Create a new PowerShell alias GSJ for Get-StorageJob

We redirect "Documents" and other well-known folders to Work Folders. Some applications write files to the Documents or other synched paths and this prevents them being able to synch. For example, many Add-in Express apps write their log files to a subfolder of Documents, and the iTunes library file writes to a subfolder of music. Both of these are examples of files that are constantly open for writing and thus cannot be synched.

I'd like to be able to exclude some file types from Work Folders synch, and I'd like to be able to exclude some sub-folders based on name.

When you open table with details of all backups and sort it on date there is bug that sort date field as string instead as date (1.1. 11.3. 12.1 instead 1.1. 12.1 11.3) (Even Windows Server 2008 R2 had it correct).