Re: Software choice: 2000 to 2003R2 Upgrade

Tech-Archive recommends: Fix windows errors by optimizing your registry

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: Software choice: 2000 to 2003R2 Upgrade
    ... have to be Retail not OEM, even though we are supplying additional PC's. ... I recommend against OEM because it can't be moved to new hardware. ... I'm now spending $700 or whatever to buy another copy of Windows Server, ... Access Licence - Retail Licence. ...
    (microsoft.public.windows.server.sbs)
  • 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: OEM license
    ... The original Microsoft OEM operating system software cannot be ... Hardware Purchasers. ... The End User License Agreement for OEM software, ...
    (microsoft.public.windowsxp.general)
  • Re: transferring ownership of windows xp home upgrade license
    ... >> no longer require buying hardware with it, your point seems to be moot." ... >> First, LEGALLY, an OEM version cannot be sold without hardware (this is ... >> in the reseller's license agreement, ... > live in in Spain sell OEMs without hardware. ...
    (microsoft.public.windowsxp.general)
  • Re: transferring ownership of windows xp home upgrade license
    ... assembled computer system or nonperipheral computer hardware component (that ... >> First, LEGALLY, an OEM version cannot be sold without hardware (this is ... >> in the reseller's license agreement, ... > live in in Spain sell OEMs without hardware. ...
    (microsoft.public.windowsxp.general)