Dear support,
i downloaded converter 6.3 from vmware
i installed the server and client on a windows server, i have two HP dl360 g9 server, windows 2016, one of them is DC, and other other one is a DFS server. i configured RAID1 on both servers. we use iLo port, and 2 networks as teaming in windows.
my questions:
1. can i convert a Physical server using Teaming into vm server by vcenter convertor?
2. on the convertor server, i am using the client on the server, now i come to the windows of options of converstion task. i am not sure how to select the options for disks and network.
for disks, as you can see from the attachment, there are 2 virtual disks, but there are some unknown partition like this 128M one. shall i select all of there volumes?
for network, as you can see it list 5 network card, i guess this include ILo, but shall i convert all these network adapters. do you know which one is iLo which is realy network card i am using?
i also attach all the default options it has. could you kindly advise what options i should give to my HP DL360 G9 to allow sueccessful conversion.
by the way, since one of the server is DC in our domain. therefore, i just would like to know, what if after conversion, i power on the virtual server, will the SID changed? if it's not working properly, i might want to power on my physical server again, which this has any influence on a DC? same question for DFS server .
thanks for your support!
I believe the DL360 G9 only supports up to vSphere ESXi 7.0
Hi
To your questions:
1. For the disk options it is best to include all volumes listed - some of them are system volumes used by Windows and if missing the target might be unbootable
2. For the network options - by default Converter lists all network cards detected on the source and creates the same number of network cards on the destination. There is not much to preserve for the networkinc expect the count of the NICs on the destination. You can modify that number to as much network cards as you want to have on the destination.
3. For the Advanced/other options - it is best if you leave everything to default unless you want to make use of any of them. The screenshot you have provided looks OK.
That said, historically there have been issues reported by some customers that converting a DC is not always successful, meaning the machine is converted and boots, but the domain controller starts acting odd. Probably it is related to the IP/network change on the destination, but this is just a speculation. Anyway, be warned and better do some testing before switching over to the migrated one. Probably it would make sense to try to demote it and then promote it to a domain controller again, but I personally have not tried that workflow.
Hope it helps,
Ivan
Hi,
First, if the plan is to convert a DC, you should never P2V a DC. Just create a VM Windows, then promote it to DC and add it to your domain and then copy all the data you need(if is a File Server), and then decommission the old DC.
vSphere 7/8 even is not supported in a G9 it will work. You just need to check the CPU parameter.
Hi,
You can install vSphere 8 and vCenter 8 on hardware that isn't supported.
If its not supported when u go to install it says error and wont continue the install. I have a dell EMC R530 with v4 Xeon E-5's and it runs vSphere 8
