Oh and an OEM license violation is a business issue/reason as much as
anything else.  If they have any Open License agreements, dealing with this
license violation may not be fun.

On Wed, Aug 22, 2012 at 10:16 AM, Jonathan Link <[email protected]>wrote:

> I did this once...just once, and my results weren't satisfying.
>
> I P2V'ed our SBS 2003 just to see what would happen.  I was forced to
> activate, but it would not accept the OEM key.  Due to other problems
> associated with that experience, I didn't pursue it very long.
>
> If you can get the media somehow (maybe the discs were copied onto a HD?),
> you're going to be much better off doing a Swing Migration.  And you can
> experiment with installing OEM media into a virtual environment to see if
> it will accept the product key.
>
> Keep in mind this is a violation of the OEM license.  You need to purchase
> an SBS license and get some downgrade rights to get back to 2003.
>
> On Wed, Aug 22, 2012 at 10:00 AM, N Parr <[email protected]> wrote:
>
>> Since SBS 2003 isn't supported on VM I doubt they will help me.  Every
>> OEM 2003 server and OEM XP I've ever done has forced an activation and
>> needed the key.  I haven't actually tried it yet but was assuming it would
>> based on previous experience.
>>
>> -----Original Message-----
>> From: David Lum [mailto:[email protected]]
>> Sent: Wednesday, August 22, 2012 8:39 AM
>> To: NT System Admin Issues
>> Subject: RE: Need to P2V and old SBS Standard 2003 server - Non OEM and
>> no Key
>>
>> Call Microsoft. :-)
>>
>> Having said that, does 2003 ask for a key when you P2V it? It doesn't
>> need online activation like Vista/Win7/W2K8. I've P2V'd WinXP without
>> issue. Vista/later take activation keys to do that though.
>>
>> -----Original Message-----
>> From: N Parr [mailto:[email protected]]
>> Sent: Wednesday, August 22, 2012 6:36 AM
>> To: NT System Admin Issues
>> Subject: Need to P2V and old SBS Standard 2003 server - Non OEM and no Key
>>
>> I've done this dozens of times with OEM licensed machines but this is
>> different.  I have an old 2003 SBS that from what I can tell isn't OEM,
>> there's no OEM in the product ID.  The original install disks/code were
>> lost in a building fire.  They grabbed the server on the way out, rest
>> burned up.  Server is on last leg for many reasons and simplest thing to do
>> virtualize it.  Especially since I will be moving them off it within the
>> next year.  And for business reason's I can't move them to a new server at
>> the moment.
>> I'm trying to figure out what to buy so when it tries to activate after
>> virtualization I'll be able to do so.  Can I just buy an old copy of SBS
>> 2003 standard and use the key from it?  Will it screw with the extra 40
>> CAL's already on the server when I do?
>>
>>
>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <
>> http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>>
>> ---
>> To manage subscriptions click here:
>> http://lyris.sunbelt-software.com/read/my_forums/
>> or send an email to [email protected]
>> with the body: unsubscribe ntsysadmin
>>
>>
>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <
>> http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>>
>> ---
>> To manage subscriptions click here:
>> http://lyris.sunbelt-software.com/read/my_forums/
>> or send an email to [email protected]
>> with the body: unsubscribe ntsysadmin
>>
>>
>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>>
>> ---
>> To manage subscriptions click here:
>> http://lyris.sunbelt-software.com/read/my_forums/
>> or send an email to [email protected]
>> with the body: unsubscribe ntsysadmin
>>
>>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to