Re: Volume License Key problem

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

From: Jonathan Maltz [MS-MVP] (jmaltz_at_mvps.org)
Date: 03/30/04 

Date: Mon, 29 Mar 2004 22:40:01 -0500

Hi Cindy,

That error message still means it was a volume licensed copy. Even if there
were a way to change the product key (which there is, it's a WMI script -
this should work
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q328874), it won't
work since an OEM key only works on an OEM installation (which this doesn't
appear to be) 

-- 
--Jonathan Maltz [Microsoft MVP - Windows Server, Virtual PC]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site :-)
http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004?  Find out
here
Only reply by newsgroup.  I do not do technical support via email.  Any
emails I have not authorized are deleted before I see them.
"cindy" <anonymous@discussions.microsoft.com> wrote in message
news:10e0901c415fd$e77e2690$a001280a@phx.gbl...
> Hi- thanks for your responses...
> My error in terminology...  I should not have put "Volume"
> License Key in the title.  Sorry....
>
> Here is the Exact Error Message we get when running
> Windows Update:
> "Cannot Validate the Product Key"
> The product key used to install Windows is not valid.
> ...........and contact your sys admin.....
> ***************
> We DO have a legal license key code .... however, when
> the third party did the upgrade, they used a number other
> than ours.
> We just want to get it corrected - the wrong number out
> and ours in!  Windows XP allows you to change the license
> code by making some registry changes.  What I'm looking
> for is a safe method to do this on Server 2003.  or Can
> we use that same procedure?  (I do not have that
> knowledge base number right now.)  I'm not at work now,
> so can not check to see if those log files are there -
> but can do so tomorrow.
> Does this additional information help at all in
> determining whether or not this can be changed without
> reloading?
>
> thanks again for your time and knowledge..
> Cindy
> >-----Original Message-----
> >Hi,
> >
> >It is true that you can't upgrade with an OEM license.
> Unfortunately, it is
> >also true that an OEM license isn't a volume license, so
> unless you have a
> >certificate of authenticity with the new key, then your
> installation of
> >Windows is unlicensed, and judging by that error
> message, the third party
> >just used a pirated copy of Windows Server 2003 and
> charged you for it
> >
> >http://www.microsoft.com/piracy
> >
> >-- 
> >--Jonathan Maltz [Microsoft MVP - Windows Server,
> Virtual PC]
> >http://www.visualwin.com - A Windows Server 2003 visual,
> step-by-step
> >tutorial site :-)
> >http://vpc.visualwin.com - Does <insert OS name> work on
> VPC 2004?  Find out
> >here
> >Only reply by newsgroup.  I do not do technical support
> via email.  Any
> >emails I have not authorized are deleted before I see
> them.
> >
> >
> >"Cindy" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:10d1301c415dd$eee30e70$a001280a@phx.gbl...
> >> Hi-
> >> We purchased a server with Windows 2003 Standard Server
> >> installed.  Due to some unforseen circumstances -- we
> >> ended up uninstalling Windows 2003 Server software - We
> >> loaded Windows NT server- copied over all of our NT
> >> server data - and then UPGRADED to Windows 2003 Server.
> >> (The 3rd party that we contracted to do this - had a
> >> License Key that they were able to use, since the
> upgrade
> >> would not take our OEM number)
> >> All seemed OK - until we tried to get our security
> >> patches and service packs up to date. Now when we run
> the
> >> Windows Update - we get a message that says we have
> >> an "Invalid License Key".
> >> What can we do to correct this problem?  I can find
> >> instructions for XP - but have not been able to find
> >> anything for Server 2003.
> >> Does anyone know where there is documentation for this?
> >> Thanks in advance for any ideas or suggestions you
> might
> >> have....
> >> Cindy
> >
> >
> >.
> >

Relevant Pages

  • RE: RWW problem on one Client machine
    ... Welcome to SBS newsgroup. ... services licensing service on a Windows 2000 domain controller. ... terminal license successfully. ... messages in the event log saying that "A terminal license server cannot be ...
    (microsoft.public.windows.server.sbs)
  • Re: Anonymous connections.
    ... Windows Server 2003 Licensing Server can control ... you may use the New External Connector License option. ... Microsoft Partner Support ...
    (microsoft.public.windows.terminal_services)
  • Re: Connecting to SQL Without Windows Authentication
    ... This is why the "license group" concept was introduced - to account ... Also note that you not only need SQL CALs but also Windows CALs in case the ... > Domain and our Windows 2000 server in another domain. ...
    (microsoft.public.sqlserver.security)
  • Re: [SLE] Microsoft Terminal Server access from SuSE 9.3
    ... >> problem by logging on locally and checking the event logs for license ... > Just my friend came to visit me and with his laptop with Windows XP I ... > connected with RDC to my server with my name and passw without trouble...? ... get 2 TSCALs for access, for remote admin only of course. ...
    (SuSE)
  • RE: RWW problem on one Client machine
    ... I think we are looking for something on his client. ... > services licensing service on a Windows 2000 domain controller. ... > terminal license successfully. ... > messages in the event log saying that "A terminal license server cannot be ...
    (microsoft.public.windows.server.sbs)