Clone Caused Win 2003 Reactivation

Discussion in 'Parallels Desktop for Mac' started by planeBrad, Feb 14, 2007.

  1. planeBrad

    planeBrad

    Messages:
    12
    I just cloned a Win 2003 VM inside of Parallels and when I started the cloned machine I was forced to reactivate it. Anyone know why this happened? In the past, I've just physically copied the Parallels files to clone a machine and had no problems. I didn't think the built in clone tool would be any different.
     
  2. planeBrad

    planeBrad

    Messages:
    12
    Just to give a little more info: I'm using Win 2003 R2 and Parallels 3150.
     
  3. sfuller

    sfuller

    Messages:
    31
    My guess is that the clone would change the MAC address used by the VM's networking layer, causing the the activation to check to get tripped.
     
  4. planeBrad

    planeBrad

    Messages:
    12
    You're probably correct. I didn't think of that.

    However, is this really a clone? When I think of a clone--I think exact copy.

    In hind site, I should have deleted the clone and just copied the existing machine to a new directory. I clicked the authenticate button without thinking. Oh well, I hope I don't need to authenticate in the future or I'll probably end up call MS to "ask for permission."
     
  5. tech_head

    tech_head

    Messages:
    38
    Clone Causes Re-Activation

    I usually just duplicate in MacOS.

     

Share This Page