Re: Software choice: 2000 to 2003R2 Upgrade

That's not my understanding - OEM can be upgraded to the boxed upgrade SKU
(which is the only upgrade as far as I know). I actually even think (but
don't know for sure) that you should be able to move to different hardware
with that boxed upgrade. What you can't do is to migrate the OEM license
from the hardware it was purchased on. So in my case, I can't install the
OEM copy of Windows Server from my existing server onto my new hardware. In
your case, my logic would be that you can upgrade the OEM on the existing
hardware, at which point you'll be running a boxed product that can be moved
to new hardware.

My thinking is that there is fairly extensive information on upgrading on
the page I sent you, and on links from that page. None of it says you can't
use the upgrade SKU from OEM, even on new hardware (unless you see something
I missed). I'm neither a lawyer or a licensing expert, but I'd be deciding
what to buy based on the information on those pages, independent of
speculation from me or others who are not MS licensing experts.


"Andy Baguley" <andy_baguley@xxxxxxxxxxx> wrote in message
news:469fcd59$0$1627$ed2619ec@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Dave

From what you suggest my OEM 2000 SBS can not be "upgraded" to 2003R2?

I need to now double check this, and I wouldn't for one minute wish to put
anyone's head on the block!!

At the end of the day it will be my purchase, so I need to get it right,
no
one else.

But I need opinion and feedback to influence my decision.

Is there anywhere, (within Microsoft?) where I can get the definitive
answer?

Yes the site you note is where I got the initial guidance, but it is not
100% clear there, as T75-01256 mentions nothing about OEM / Retail
originals
to upgrade from.

As an aside my UK software supplier says the additional 2 x 5 CAL's will
have to be Retail not OEM, even though we are supplying additional PC's.
Now
that's another one!

Licensing and product specification is a minefield, and if you buy wrong
you can't get a refund or exchange!! Perhaps I should be looking at Linux?

Rgds
Andy



"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:OSMQDKiyHHA.4004@xxxxxxxxxxxxxxxxxxxxxxx
Sorry, I'm not going to be the guy you're cursing if you end up with the
wrong SKU : -)

However, you should be able to find all the current SKUs at
http://www.microsoft.com/windowsserver2003/sbs/howtobuy/pricing.mspx.

I recommend against OEM because it can't be moved to new hardware. I've
got a member server I need to replace right now, and because I saved a
small amount of money by getting OEM WS03 when I bought the current box,
I'm now spending $700 or whatever to buy another copy of Windows Server,
instead of just migrating the license from the old hardware. IMO in the
case of server software, OEM is penny wise and pound foolish.


"Andy Baguley" <andy_baguley@xxxxxxxxxxx> wrote in message
news:469f37d6$0$1631$ed2619ec@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm just embarking on my first 2000 upgrade. It will be a new clean
install, on new hardware, so hopefully no major migration issues.

Planning to copy user data, and pst files, and re-create everything else
as new on the new hardware. No swinging on this one!

Could someone please double check my software purchase list, before I
spend? I wouldn't want to get it wrong!!

Existing (supplied by me) is SBS2000 (OEM) and 4 x 5 client CAL's (OEM)
(E76-00321, 00039-014-322-361)

Proposed:-
1 x T75-01256 Microsoft Small Business Server 2003 Premium inc 5 CAL
Version Upgrade R2 - Retail Boxed. (presumably showing the original 2000
CD to the install process is all that is required?) Is this a CD, or
DVD?

4 x Microsoft Small Business Server 2003 Upgrade Additional 5 Client
Access Licence - Retail Licence. (Not sure here which one! MS lists
Device: T74-01214, and User: T74-01215. We need device licensing as
there
are more users than devices. The original 2000 licences are however
clients.) Therefore probably T74-01214? What are the upgrade issues
here,
as there is no floppy on the new hardware. Do the existing CAL's have to
be "unloaded" back to the floppies?

2 x T74-01040 Microsoft Small Business Server 2003 - OEM Additional 5
Device Client Access Licence (CALs). (To increase the total licences to
35. We are supplying hardware co comply with the OEM element)

Thanks for any observations












.

Relevant Pages

  • Re: MS Licensing
    ... You might consider upgrading the hardware in those computers having the ... OEM installs of Windows. ... HARDWARE is a single computer system, or shall mean the computer system ... drive and then upgrade it. ...
    (microsoft.public.windowsxp.general)
  • Re: Gateway Upgrade Policy for MCE 2005
    ... The OEM model works fine. ... As I said the choice of upgrade provision is with the OEM. ... > the original hardware is compatible. ... required to support those only given the limited information the end user ...
    (microsoft.public.windows.mediacenter)
  • Re: Deactivate my license.
    ... to Windows 2000 or another 32-bit windows, as my hardware (such as my ... An OEM version is tied to the first computer on which it's installed. ... The next step is to upgrade it so it can run an AMD 64 processor, which, of course, will involved changing the motherboard again and upgrading the RAM. ...
    (microsoft.public.windowsxp.general)
  • Re: SBS 2003 Disaster Recovery Guide
    ... intending to purchase the OEM Version along with the new hardware. ... of licensing that allows you to upgrade the OEM to anything that allows you ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrade from Standard to Premium OEM
    ... you can upgrade OEM to premium. ... look for a non-R2 upgrade SKU. ...
    (microsoft.public.windows.server.sbs)