Hi Folks,

We have a dying Win2k8 32bit production file server that we we’ll have to ‘hand bomb’ upto Server 2022 at some point. But in the interim we are ready to move it to ESXi hosted virtual. Back end storage is all iSCSI and FC so that’s no problem and we have tested the migration using Acronis without connecting the VM to the network.

Our only concern is if the VM de-registers (at the windows level) itself due to a hardware change or whatever and we can’t re-register it again since the OS is not longer supported. I don’t know if it will or won’t which is why the ask.

Anyone done this lately? Thanks

4 Spice ups

Is this 2008 server a AD server?

P2V does not work well with AD server from what I have read and heard.

If not why not just build it from scratch in the vm atmosphere?

Its not a Domain controller if that’s what you mean. Just a simple file services role.

It will, most probably Windows 2008 R2 OEM to Volume License change after p2v , since the hardware change is pretty fundamental.

A much better option would be to spin a new fresh virtual machine running modern Windows Server and use Storage Migration Service https://www.starwindsoftware.com/blog/migrate-your-file-servers-with-storage-migration-service to migrate your file shares entirely and fully automatically, including the cutover. If that is not an option, replace it with a Linux-based virtual machine. Keeping an EoL system to work as a file server just does not make any sense.

It will, most probably Windows 2008 R2 OEM to Volume License change after p2v , since the hardware change is pretty fundamental.

Yes it did require Windows Activation again but using the MS phone system we were able to activate it again.

A much better option would be to spin a new fresh virtual machine running modern Windows Server and use Storage Migration Service https://www.starwindsoftware.com/blog/migrate-your-file-servers-with-storage-migration-service

Thanks for the link - its one of the better ones that I’ve seen so far.We needed something quick and didn’t have the time to ‘play with’ Storage Migration Services. But that is the plan moving forward when human resources allow.
For anyone reading - all the share (NTFS) and permissions came over easily with the connection of the FC and ISCS storage. Was nice to see (even though we didn’t need it) that all Share information is stored in the Windows Registry key well.
One down… lots to go.

Thank you for the update. Glad to see you have your issue resolved. Good luck and lots of fun with further projects! :wink: