On Thu, 19 Feb 2009 10:55:45 -0800, "Steve Jain [MVP]"
<noreply.-@-.essjae.com> wrote:
Quote:
>On Thu, 19 Feb 2009 09:25:18 -0500, dgk <dgk@xxxxxx> wrote:
> Quote:
>>On Tue, 17 Feb 2009 15:12:12 -0500, dgk <dgk@xxxxxx> wrote:
>> Quote:
>>>On Tue, 17 Feb 2009 11:32:12 -0800, "Steve Jain [MVP]"
>>><noreply.-@-.essjae.com> wrote:
>>>
>>>>On Tue, 17 Feb 2009 08:19:44 -0500, dgk <dgk@xxxxxx> wrote:
>>>>
>>>>>On Fri, 13 Feb 2009 09:15:51 -0500, dgk <dgk@xxxxxx> wrote:
>>>>>
>>>>>>I'm using the SharePoint vhd from Microsoft for a series of lessons. I
>>>>>>like it so much that I'd be willing to use a license and activate it
>>>>>>just so I can practice Active Directory stuff and SharePoint but I
>>>>>>can't figure out how to move it between work and home. The whole thing
>>>>>>will time out in a year anyway (according to the documentation) but I
>>>>>>can live with that.
>>>>>>
>>>>>>The vhd I'm using at home still has a week before requiring
>>>>>>activation. When I shut it down and bring the vhd and vmc files to
>>>>>>work, it requires immediate activation. From what I've read, I need to
>>>>>>make sure that the hardware changes the VM sees isn't enough to
>>>>>>trigger an activation request.
>>>>>>
>>>>>>Is the problem with activation because I haven't activated it yet or
>>>>>>will I still have the same problem once I activate it? What do I need
>>>>>>to do to keep it from re-requiring activation as I move it back and
>>>>>>forth?
>>>>>
>>>>>No pointers for this?
>>>>
>>>>My guess would be that since you didn't activate and then moved the VM
>>>>to a system with a different CPU type caused the activitation to kick
>>>>off.
>>>
>>>Ok, then there's only one sure test. I'll activate and see what
>>>happens.
>>
>>
>>Oh joy of joys. I activated the VM I have at home, brought it to work
>>and it seems to be fine. Now, can I keep moving it back and forth
>>without activating again? Only one way to be sure on that. >
>Not sure, the only thing that would be different for the VM between
>the 2 host PCs is the CPU.
>what CPU do you have at work and home? They're both AMD - one is an dual core Opteron 165, the other is a
single core Athlon XP.