Service Console problem

[BenMeade]

Hi,

I was hoping i could get a bit of advice on how to go about converting some VM's between 2 different subnets

I have a network of 172.20.0.0 (new subnet) and a 192.168.0.0 (old subnet) the ESXi hosts are on teh 172 network but i have added a service console on the 192.168 vlan and can ping devices on that lan.. when trying to use the vConverter it wont connect to the source machine.

Does anybody have any ideas?

Hopefully i havent put this in the wrong forum (new to the vmware communities)

[ChrisDearden]

Where are you running vConverter from ?

I'd imagine there would need to be a network route from vCenter to the machine you want to convert as well as the host?

[BenMeade]

I guess that could be causing a problem. Im running the vcenter from a network which has no access to the 192 range. Was guessing that it would take the network settings from whatever host im right clicking on to use vconverter

[ChrisDearden]

not really - I seem to remember that converter needs to be able to see the target VM in order to deploy the agent to it. Especially if you are using ESXi , vCenter forms a pretty critical piece of the puzzle.

[AndreTheGiant]

Thread has been moved to Converter area.

Have you tried to install the Standalone Converter in your source machine and try from it?

Andre

[continuum]

stupid question ...

Can 't you simply move the directories with Fastscp, Datstorebrowser or whatever ?

[opbz]

just a suggestion...

have you tried doing p2v from stand alone converter and pointing it to an esx(i) server? bypassing vcenter?