3 Replies Latest reply on Sep 6, 2011 5:58 AM by Hanoon

    vCenter Converter Dependancy

    MMazurkiewicz Novice

      My company has been running ESXI4.1 for about half of a year now and I've noticed something strange about my vCenter Converter.  Whenever I try to do an Import from within vSphere I keep getting an error if the original physical workstation that I installed vCenter on is not available, but once it is on and I can connect to it, the Import service works.

       

      I've also noticed this when I've tried to install new instances of vSphere when I install the vCenter Converter plugin through Plug-in Manager, except for there I get a message explicitly saying that it can't find that original workstation for installing the software.

       

      What I'm trying to figure out is why does this dependency exist?  How would I change whatever is creating this dependency to point to my core management VM instead of this workstation?  We're not an AD environment so my vendor that installed the SAN created a "management" VM for managing user authentication to vSphere, and I've noticed that the instance of vSphere within that VM doesn't have this dependancy issue, it is only workstations installed after installing that first instance of vSphere.

       

      Thanks!

        • 1. Re: vCenter Converter Dependancy
          Hanoon Enthusiast

          What is the error message?

           

          I have success importing powered on /off machines using standalone vCenter. Also installing converter plugin working...

          • 2. Re: vCenter Converter Dependancy
            MMazurkiewicz Novice

            If I try to use the converter from my desktop while our department's "shared" system is off or disconnected I get:

            Connection Error

            Cannot connect to VMware vCenter Converter server.  Unable to establish server connection, reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  (10060)

             

            I understand that the converter is looking for the vCenter converter host on that system, I'm trying to find a way to force it to stop looking for that particular system and to get the converter host working off of my local system instead of the remote system.  I also have the converter stand alone installed on my machine which works without any trouble, but I'd like to use the converter through vSphere if possible.

            • 3. Re: vCenter Converter Dependancy
              Hanoon Enthusiast

              "I'm trying to find a way to force it to stop looking for that  particular system and to get the converter host working off of my local  system instead of the remote system."

               

              If you install converter as a plugin - It's add on to the vCenter installation , if you would like to run it off your local machine then install the standalone converter or vCenter + plugin on your local machine.