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.
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Clone Caused Win 2003 Reactivation
- Thread starter planeBrad
- Start date
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."
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."
Clone Causes Re-Activation
I usually just duplicate in MacOS.
I usually just duplicate in MacOS.
planeBrad said: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."