Forum Discussion
Updating File Server OS Best Practice
Give us a bit more info.
Is this a VM or physical? Is the file share on a dedicated drive or the same as the OS?
Let's say if a VM and on a dedicated drive such as "S".
I would build a new 2022 server. Export share info from registry from the old server. (Link provided below.) Then move that S drive from the old VM to the new VM and inport the registry info. You can rename the server to the old server's name or create an CNAME (alias) in DNS, either way original links will work. Down time should be about between 5 - 10 mins.
Did this a few months ago, none of the clients were able to tell anything was changed.
https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/saving-restoring-existing-windows-shares
Leavii No, you don't have to create a copy of the disk. It's even easier than that. Use that disk. Since it's a VM. Detach the data disk and use it on new VM. That is if it's shared storage..??
Up to you, yet if it's huge waste of time creating a copy.
Go into VM1 and detach and then go into the new VM2 and attached using same drive letter. Then import the registry ACL info from VM1 and it's all done. That's how I had downtime of 5 - 10 mins.
As always, before any work confirm you have a good backup of the data.
Alban1998 For me, this being a process I hadn't thought of I simply want to test it. I have nothing to lose as I am not removing the disk from the server but going to test with a copy. It is not something I have thought of or done before, and I feel it is an interesting solution. Keep the discussion going though because I am here seeking information.
Testing with a copy of the disk will trigger the same issues as moving the disk - by examples, you may end up trying to connect a MBR-based disk to your newly build GPT/UEFI server, which is less than ideal.
You need to consider what happens at the operating system layer and not only the virtualization layer - it is simply not that easy.
And that's where Storage Migration Service will help you by taking of pretty much all the stuff.
It's important to keep in touch with newer, supported, efficient tools by Microsoft rather than relying on very old, clunky methods which may bring unexpected issues with them, unless circumstances require it (which is not the case here).
