Re: Using OEM to activate eval Server 2008

Taomyn <Taomyn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks, but I will quote from:
http://www.microsoft.com/downloads/details.aspx?FamilyId=B6E99D4C-A40E-4FD2-A0F7-32212B520F50&displaylang=en

"This software is for evaluation and testing purposes. Evaluating
Windows Server® 2008 software does not require product activation or
entering a product key. Any edition of Windows Server 2008 may be
installed without activation and evaluated for an initial 60 days.

If you need more time to evaluate Windows Server 2008, the 60 day
evaluation period may be reset (or re-armed) three times, extending
the original 60 day evaluation period by up to 180 days for a total
possible evaluation time of 240 days. After this time, you will need
to uninstall the software or upgrade to a fully-licensed version of
Windows Server 2008."

Note the last sentence in the second paragraph which states
"uninstall or upgrade",

How does that contradict what Meinolf or I wrote? Plugging in a product key
doesn't make it an upgrade...and you can't plug in an OEM product key.

I wish it were otherwise, but it ain't. And with OEM you couldn't do it
anyway.

Taomyn

"Lanwench [MVP - Exchange]" wrote:

Taomyn <Taomyn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Meinwolf,

Yes, I appreciate that, as I have supplied them with both the
hardware i.e. the new server and now the OS - they just weren't able
to pay for the two at the same time, hence getting the eval in so I
didn't waste time waiting,

Taomyn

You can't use an OEM key with a non-OEM copy of Windows, sorry. You
can call MS licensing if you want confirmation of this, but I'm
pretty sure you won't be able to use your current install. Eval is
not meant to be put into production, ever. Sorry.



"Meinolf Weber" wrote:

Hello Taomyn,

OEM keys are normally shipped with hardware and should work only
with that one. Not on other systems.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


I have an eval copy of Server 2008 Standard running on a clients
new server which will need activating soon - we are happy that it
will do what they want so I can shut down there old server. I
purchased an OEM licence for it but it will not allow me to use
the product key saying "the product key you have entered will not
work with this edition of windows server".

Is there any way to get the current build to accept the new key or
am I facing a total re-install of the OS?

Cheers,
Taomyn



.

Relevant Pages

  • Re: Using OEM to activate eval Server 2008
    ... "This software is for evaluation and testing purposes. ... If you need more time to evaluate Windows Server 2008, ... Plugging in a product key ...
    (microsoft.public.windows.server.setup)
  • Re: Using OEM to activate eval Server 2008
    ... "This software is for evaluation and testing purposes. ... Any edition of Windows Server 2008 may be installed without ... If you need more time to evaluate Windows Server 2008, ... You can't use an OEM key with a non-OEM copy of Windows, ...
    (microsoft.public.windows.server.setup)
  • Re: Windows 2003 Enterprise evaluation and Exchange server 2007
    ... This process will not work with Windows Server 2003. ... You can only change the product key to a different one from the same ... |>- Choose to repair this installation and the upgrade will proceed. ...
    (microsoft.public.windows.server.general)
  • Re: Invalid installation id
    ... The 4 different support ... I installed the Windows on the server when we bought it from the store, ... It will give you the product key that was used to install SBS on the ...
    (microsoft.public.windows.server.sbs)
  • RE: Win2003Ent EVAL to Win2003Ent Gov...
    ... I understand that you want to upgrade your Windows Server 2003 from ... evaluation version to the full retail. ... Use Command Line Parameters with the Ntbackup Command in Windows ...
    (microsoft.public.windows.server.migration)