4 Replies Latest reply on Aug 15, 2018 8:13 PM by nancyz

    Migration issue

    Loizou56 Lurker

      I'm trying to migrate my PC with windows 10 pro to my MacBook pro and keep on getting unable to connect to the network share "\vmwareMigration83

        • 1. Re: Migration issue
          batuhandemirdal Enthusiast



          What exactly do you want to do?

          Have you updated VMTools?

          • 2. Re: Migration issue
            a.p. Guru
            User ModeratorsvExpertCommunity Warriors

            Please explain your current network configuration, and from where you start the converter (which I assume you are using).

            The "169.254.x.x" is an APIPA (automatic private IP addressing) address, which gets assigned to systems which are configured for DHCP, but do not get a DHCP lease/address.


            • 3. Re: Migration issue
              dlhotka Virtuoso

              So first, converting a physical machine almost always results in a bloated, buggy, unstable VM.  Since most still require the purchase of a legal, retail windows license (OEM can't be virtualized), it's better to build one from scratch.


              If you still want to convert it, using the standalone VMWare VCenter Converter has much better luck than over a network.

              • 4. Re: Migration issue
                nancyz Hot Shot
                VMware Employees

                Hi Loizou56 ,


                Please put your windows 10 PC and your MacBook pro in the same LAN, and retry the process. Then your PC and Mac could communicate to each other and so does VMware Agent and Fusion. Hope that could help.