Event details
Join us for our March 9 “Ask Microsoft Anything” chat about Windows Server updates and upgrades. We’ll cover your questions on how to stay more secure by upgrading older servers (2008 and 2012 versio...
EricStarker
Updated Mar 09, 2023
AspenForester
Mar 09, 2023Brass Contributor
Jeff Woolsey, My org is beginning the process of replacing our 2012R2 file server VMs, going to Server 2022. We've started the inventory process with Storage Migration Services, but some shares are returning errors that the inventory failed on x number of folders. We're not seeing any logging that gives us insight on which folders it might be having trouble with. We can only assume at this point that someone has managed to break ntfs inheritance and stripped "Administrators" and
"System" of access to the folder. Is the inventory recording this anywhere, or are we currently on our own as to what folders / files are failing?
- NedPyleMar 09, 2023Former EmployeeHi JB, I own SMS and can answer here: the inventory logging is pretty light, unfortunately (the original design was just to quickly count, not look for details, for performance reasons). We have a work item to improve this, but in the meantime you can just start a transfer and let it log the actual failures, then download the errors log to find your miscreants. You can run as many transfers as you want and if most of data isn't going to transfer, it will be over with pretty fast :(. In fact it might be better just to use ICACLS to grant admin and system rights back all over the source machine first, just to eliminate the issue.
- AspenForesterMar 09, 2023Brass ContributorThanks Ned! I have some PowerShell tooling to survey the NTFS permissions, but of course that takes some time. Knowing that I can just run the transfer, and then see what's breaking is helpful!