GRedner's Accepted Solutions

The list of necessary connectivity is: Each SRM must be able to talk to its local VC: Prod-SRM <--> Prod-VC DR-SRM <--> DR-VC Each SRM must be able to talk to its remote VC: Prod-SRM <--... See more...
The list of necessary connectivity is: Each SRM must be able to talk to its local VC: Prod-SRM <--> Prod-VC DR-SRM <--> DR-VC Each SRM must be able to talk to its remote VC: Prod-SRM <--> DR-VC DR-SRM <--> Prod-VC That's it. The two VC servers do not need to be able to connect to each other, nor the two SRM servers to each other. Messages sent from one SRM to another are routed through the VC server at the site that is receiving the message.
Currently, it is only possible to import to ESX 2.5 if it is managed by VC 2.0. If the box is managed by VC, give VM Importer the address and credentials of the VC server, and it should prov... See more...
Currently, it is only possible to import to ESX 2.5 if it is managed by VC 2.0. If the box is managed by VC, give VM Importer the address and credentials of the VC server, and it should provide a list of available ESX hosts which will include your ESX 2.5 box.