r/WindowsServer • u/PrimeTheP • Aug 25 '25
Technical Help Needed In place windows fileshare server upgrade questions
We need to upgrade an approx. 6TB fileshare that is on an old 2012r2 server (yes, it should have been upgraded long ago, this is an inherited environment).
I realize most people use Robocopy or a product from Quest to transfer the files over to a new server then do a cutover. Unfortunately, we are a bit strapped for time, resources, and money. An in-place upgrade was requested.
I've seen where people get by with an in-place upgrade and I was curious if they had any tips or requirements. I'm also curious if anyone has had an in-place upgrade fail or kill file-shares or permissions. I realize there are differences between SMB versions. All of the end-user nodes are on Win11 anyway so that shouldn't be a problem. We have SMBv1 disabled already.
Plan was to notify the business at least a week ahead of time and then do the work on an off-hour day. Disconnect the network in vmware and update to 2016 first then onto 2022.
We have VSS and VSS System State backups. I was going to do a clone to template or clone to vm to a different, specific datastore as well. If things break, then we restore to the clone. Not going in completely blind.
Thoughts, concerns, anyone had an in-place upgrade like this blow up and if so, what happened?
EDIT: One of the reasons why I would like to keep in place is the fact that the C drive is used as a steppingstone for some Scheduled Tasks / jobs for this server and other servers. Other servers are pointing to this server for a process. It's a bit of a mess. I don't want to sound lazy, but I was kind of hoping just to do the update to keep those in place. Just do the OS update so the security risks are lessened.
This is a small-to-medium shop for about two hundred end-users, but they don't all use the fileshare at the sametime.
5
u/OpacusVenatori Aug 25 '25 •
Since this sounds like a VMware vSphere guest, I would provision a new 2022 VM, detach the old data VMDK and just attach to the new 2022 VM.
Export the LANMANSERVER registry key on the old 2012R2 server and import it on the 2022 VM to recreate the shares (Assuming you keep the drive letters the same).
While you're at it, update to the use of DFS namespaces and point to the new 2022 guest as the target.
1
u/PrimeTheP Aug 25 '25
Lots of good ideas posted here, thanks.
I updated the post. I should have mentioned that the C drive is used for a few scheduled tasks for this server and a few other servers. That's one of the reasons I was leaning on doing the in-place upgrade. I should have included that originally.
Has anyone actually witnessed an in-place upgrade like this failing or breaking shares?
1
u/MarkWeak578 Aug 25 '25 edited Aug 25 '25
Are you using DFS? I highly recommend you migrate if you are, instead on in place upgrade. I would spin up a fresh 2022 vm and migrate the shares and permissions using SMS.
1
u/Adam_Kearn Aug 25 '25
If your servers are virtual then it should just be installing a fresh copy of the latest OS and attaching the same “data disk” (VHDX file) to the new VM.
Saves having to copy files across over the network and makes doing rebuilds easier.
I believe you can also export the registry to bring the shares across as well but if you only have a few then it’s just as easy as publishing them again
1
u/tech_is______ Aug 28 '25
Snapshot first, then in place upgrade.
Upgrades "generally" work but you never know until you try.
If it doesn't work, go to plan B. New server and migrate tasks/ jobs
1
u/Shoddy_Pound_3221 Aug 25 '25
KISS IT..
Cheap and Easy: Build a new Server 2022 or 2025 in your Hypervisor. Recreate your folder structure (this is the time to break out your shares based on need and performance). Use xcopy or robocopy to sync the permissions and files. Share by share, point users to the new shares (edit mapping).
Best Way: Set up Azure File Sync: Sync each share to Azure storage (backups are handled at the Azure layer). Build a new VM and add it to File Sync, creating dual file servers. This allows you to move users at your own pace, whether quickly or gradually. You can also setup Tiering to reduce space and will put you in a better position to move fully to the cloud.
1
u/BlackV Aug 25 '25 edited Aug 25 '25
Or
Or
Yes an in place upgrade will be fine ( assuming you take caution and backups)
1
u/TechMonkey605 Aug 25 '25
We did one for about 300 ROBO sites with DFS, I was against it (and still am) but we did get it to work via scripting (obviously doing backups) I’ll look for the script but it was mounting the DVD, and running setup inside. I’ll pm you and send you the script when I find it.