User Profile
NedPyle
Bronze Contributor
Joined 9 years ago
User Widgets
Recent Discussions
Re: Storage Migration Service - Procedure Clarifications
AviEi640 Is there recommended maximum time i need to move between the 3 stages - Scan old server, Transfer Data, Cutoff? The only real max is how long between reboots. A design limitation of SMS transfer is that it cannot resume a transfer job if the servers involved are rebooted. If following a normal patching schedule that means 30 days max. We're adding functionality to support resuming (it will likely be to WS2022, definitely WS2025, but not to WS2019, which is out of mainstream support). If I've done yesterday the scan on my old server and planning to do the transfer only in about 2 weeks - what about the files and permissions that will change in this period of time? do i need to run a new scan on my old server near the date I'm going to do the actual transfer? should i delete or clear something from the previous scan? (The scan took about 5 hours). No, the inventory scan is just designed to give you some understanding of how big your migration is. The actual inventory runs again the moment you start the transfer (under the covers), in order to know what to transfer. 5 hours is a pretty long scan, tbh. I presume the source computer hosting a lot of files on very slow spinning drives. I understand that the process of the transfer takes care of changes that were made to the scanned file from the last scan done. Yes see above. And rerunning a transfer will catch up any changes from the last transfer differentially. I plan to add the FSRM role to the new server and after the cutoff stage to import the FSRM settings from the old server to the new one using dirquota & filescrn - is that the way to do it? shall it work on server 2022 FSRM? Yes those tools or the FSRM PowerShell. SMS has no knowledge of FSRM settings at all, so you will need to migrate those separately.Re: ISSUE: b20348.887 "Not enough quota is available to process this command" when copying bigger files
Have you lost the repro? If yes, when it happens again, please run T.cmd in an elevated CMD prompt on the server and the client. https://1drv.ms/u/s!Aj_tsbbaXqQqgYaMQPlcLuoQ2I13ZG4?e=Pg0ySe On server: t.cmd SRVON (reproduce the issue) t.cmd SRVOFF On client: t.cmd CLION (reproduce the issue) t.cmd CLIOFFFeedback on Hotpatch, SMB over QUIC, and Extended Network in Azure Edition
Heya folks, Ned here again. We released Windows Server 2022 Azure Edition in November as part of Azure Automanage, which included the Hotpatch preview, SMB over QUIC, & Azure Extended Network features. In February, we also GA'ed the Hotpatch feature. We will soon be starting the Azure Edition Insider program, where you can get a preview of new features coming to in the first major release this autumn, including big changes to Storage Replica, SMB, and some surprises. After that, we'll start the public preview of Azure Edition on Azure Stack HCI for on-premises private clouds. In the meantime, we are interested in your experience using this new operating system edition and the scenarios unlocked by these new features. If you've deployed Azure Edition, Hotpatch, SMB over QUIC, or Extended Network, we want to know how it went, what you liked, & what you need. We're looking for direct experiences and with your consent, may want to chat with you further on a short phone call. You can send us an email at aefeedback@microsoft.com or just DM me directly here (just highlight my picture and click "message"). We're very interested in hearing from you.Windows Server lifecycle & upgrade survey running
Hiya folks, Ned here again. We're running a survey on Windows Server VM lifecycle and upgrades so we can plan some future feature and management options for you. It takes just a few minutes and is anonymous - although you are free to provide contact info for a deeper conversation with us. This survey is key to making your life easier someday so I hope you can find the time. 🙂 Survey is here We're going to run this survey for a few weeks so if you just pencil us in for 5 minutes of your time by the end of the month it'll be groovy. Thanks! - Ned PyleRe: Storage Migration Service failing Validation during cutover
Hi. No one has opened a support on this afaik, and we cannot reproduce the issue here, please open a case and if the support folks don't have a rapid answer, DM me so I can look at data with them. You can gather logs for them at https://aka.ms/smslogs, running that on the orchestrator machine.Re: Domain Name Change in DC
Hi. Are you looking to rename your existing .com domain to a .local domain? That's not recommended for a few reasons: https://docs.microsoft.com/en-us/microsoft-365/enterprise/prepare-a-non-routable-domain-for-directory-synchronization?view=o365-worldwide https://social.technet.microsoft.com/wiki/contents/articles/34981.active-directory-best-practices-for-internal-domain-and-network-names.aspx https://support.apple.com/en-us/HT207511 If you're just looking to rename a domain, the steps are here: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc794869(v=ws.10)?redirectedfrom=MSDNRe: Storage Migration Service Inventory completed with errors
HI. We've handled much bigger. I really recommend you not try to bang your head here further, open an MS support case. If we find a bug it's a free case, if it's something we can get working we will. Those support folks have access to me through an internal DL as well, you won't be hung out to dry.Re: Classic server roles need your love as well
Howdy. I'll be writing & speaking about the new WS2022 file server features all month - SMB compression, SMB AES-256 encryption, SMB RDMA encryption, GMAC-accelerated signing, SMS NetApp migration - plus a very big file server feature surprise coming soon. That is the most used role in Windows Server and definitely a classic 😄
