Proper migration of windows 2008 r2 to ProxMox

Good afternoon.

The task is to replace the physical terminal server based on Windows 2008 R2 with its virtual copy. ProxMox is selected as the VM platform.

Based on your personal experience and knowledge - which is preferable:

  1. Create an empty VM with 2k8r2 and configure it slowly from scratch (install licenses, start users, deploy all software and peripherals) or

  2. Create an empty VM with 2k8r2, on an active one how to make a fullbackup of settings (software, users, licenses, rights, etc.) and roll the resulting archive to the VM ?

What do you think would be most correct?

And to avoid getting up twice: - is there a utility, script, or something that can create a map (list) of existing user file access rights? Which user has access to which directory?

Thanks.

Author: Борис, 2015-08-10

3 answers

You can first transfer to esxi, and then convert the vmdk disk using qemu-img to qcow2. Create a KVM virtual machine on proxmox with the parameters as in the source machine and connect the disk. With the 2012 server, it turned out

 2
Author: outlander, 2015-08-11 10:46:29

The disk2vhd and qemu-img utility helped. The solution was found here and here.

Slightly more detailed:

A)FS_2008 - physical server Windows 2008 r2 / disk C: lies on a 160Gb SSD

B)VM_2008 - the new Windows 2008 r2 virtual server. Only D: (install CD) and E: (virtio_win_drivers CD) are available from the disks)

On FS_2008, a C - server disk image was created using disk2vhd (from the Sysinternals package).vhdx-it took 33Gb (instead of 160Gb physical disk). This image was copied by scp to a machine with proxmox.

Then using qemu-img is converted to .qcow2 image:

qemu-img convert -O qcow2 ./SERVER.VHDX /storage/images/VMID/vm-VMID-disk-2.qcow2

Using the proxmox web interface, I couldn't connect the resulting disk and had to edit /etc/pve/local/qemu-server/VMID.conf.

I entered it there:

ide0: vm_storage:VMID/vm-VMID-disk-2.qcow2,format=qcow2,cache=writeback,size=150G

After that, VM_2008 started normally. After the initial launch and verification, the virtio device drivers-memory, disks, and network adapters - were installed. Further edit VMID. conf again and replace ide0 with virtio0. After that, restart VM_2008 and check the disk performance using hdtune.

 2
Author: Борис, 2015-08-11 15:25:31

There is a good utility StarWindV2VConverter, it can convert VHD to raw and qcow immediately.

 1
Author: Anon, 2017-09-21 08:29:34