We are planning to move some physical servers to virtualized machines soon. Also, some of the services in this machines are to be upgraded, and the consultant convinced us to set up from scratch a new server (so they are independent of other services already in those hosts, and to get to make different partitions for OS and applications). Also, it will be a good thing to set up new servers, as the old ones have been running for some years with a not-so-good maintenance.
Our issue here is that, by the time the services are upgraded, we probably won't have the hardware needed to install ESXi, so we'll try to setup them on VMWare Server and later migrate them to ESXi. In order to do that, it would be helpful for us to know some tips and advices of things to do when setting up the VM in order to make the migration easier when it arrives.For example, from what I've read, we should create our disk partitions as SCSI drives, butI wonder if there are some other advices that you could give us.
Thanks in advance. Sergio.
When you migrate from VMware Server to ESXi, you just need to use the free VMware Converter to move the files across. I haven't experienced any difficulty in moving from 1 to the other with any type of configuration.
Welcome to the Forums - as the other poster indicated it is quite simple to move from VMware Server to ESXi with the use of VMware Converter
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
If you want to save required steps to perform later, create flat and fat disks (no 2GB parts, preallocated). ESXi only supports such disks. Maybe converter does this for you during conversion, but anyway you can save this step.
Conversion without converter is not so difficult too, so if you have problems with converter this would not be the end.
I have tried with split 2gb disks and preallocated, and also without those configurations and converter always brings across the VM perfectly, so configuration shouldn't be a problem in VMware Server
This is just some general advice. Stick with single vCPU VM's unless there is absolutely a compelling need to do multi vCPU VM's. When ESX schedules CPU cycles, it must schedule multi vCPU cores at the same time. For example, what this means is that if you have a dual core physical CPU, a 2 vCPU VM will take both cores simultaneously when it needs processor time. This leaves the other VM's waiting.
Rule of thumb- start off with single vCPU VM's. It is easier on Windows 2003 and up to change to multi-CPU HAL than it is to go back to single-CPU HAL. I hope this helps.
Don't forget to use the buttons on the side to award points if you found this useful (you'll get points too).